If you haven't, you should read the xenoData tagdoc source= attribute suggested values and perhaps examples before I merge xenoData into master tomorrow a.m. for the freeze. Who is taking care of @degree by tomorrow? I will be able to unless there are issues with <xenoData> that need to be tackled. I plan to do the language stuff tonight.
When I run `make test` (in the sydb-xenodata branch, but I don't think that matters) I get an error in a test that looks like it is supposed to exercise the RELAX NG schema as fragments. The errors are: .../header.rnc:869:28: error: reference to undefined pattern "macro.anyXML" .../header.rnc:890:7: error: reference to undefined pattern "att.enumerated" Fastest way to reproduce this yourself is: $ cd .../TEI/P5/Test $ make test-frag My instinct is that this is not a problem, but that's an instinct born of ignorance. :-) Any thoughts?
This test works fine in the master branch, and also in the TEI-Pure branch, but not in the sydb-xenodata branch. So it does look a bit like a problem to me. On 30/09/15 23:56, Syd Bauman wrote:
When I run `make test` (in the sydb-xenodata branch, but I don't think that matters) I get an error in a test that looks like it is supposed to exercise the RELAX NG schema as fragments.
The errors are: .../header.rnc:869:28: error: reference to undefined pattern "macro.anyXML" .../header.rnc:890:7: error: reference to undefined pattern "att.enumerated"
Fastest way to reproduce this yourself is: $ cd .../TEI/P5/Test $ make test-frag
My instinct is that this is not a problem, but that's an instinct born of ignorance. :-)
Any thoughts?
I'll intrude on Council discussions just to ask for clarification. Are you working in the "for-xenoData" branch? I see @type (not @source) on xenoData, with two suggested values: * source * transcription Is that what you meant? On 9/30/15 3:16 PM, Syd Bauman wrote:
If you haven't, you should read the xenoData tagdoc source= attribute suggested values and perhaps examples before I merge xenoData into master tomorrow a.m. for the freeze.
Who is taking care of @degree by tomorrow? I will be able to unless there are issues with <xenoData> that need to be tackled.
I plan to do the language stuff tonight.
Hey Kevin! Oh dear. Methinks you are looking at the "for-xenoData" branch of our Subversion repository on Sourceforge[1], yes? We are now working with a git repository on GitHub.[2] There I'm talking about the "sydb- xenodata" branch. I'd like to just point you to the page on Jenkins where you can see the built product, but I don't know where it is, if it's even there. So, here's the bit that corresponds to what used to be @type: @scope: Status: Recommended Datatype: data.enumerated Suggested values include: source The metadata stored in this xenoData element describes the source document(s) identified in sourceDesc. transcription The metadata stored in this xenoData element describes the digital TEI document in which it is found. both All of the content of this xenoData element simultaneously describe the source document(s) identified in sourceDesc and the digital TEI document in which the xenoData itself is found. other The metadata stored in this xenoData element describe something other than the source document(s) identified in sourceDesc or the digital TEI document in which the xenoData itself is found. Notes ----- [1] https://svn.code.sf.net/p/tei/code/branches/P5/for-xenoData/ [2] https://github.com/TEIC/TEI
I'll intrude on Council discussions just to ask for clarification. Are you working in the "for-xenoData" branch? I see @type (not @source) on xenoData, with two suggested values: * source * transcription Is that what you meant?
Right, I knew we moved to GitHub, and I poked around [2] for a while till I found this: https://github.com/TEIC/TEI/blob/P5/for-xenoData/Source/Specs/xenoData.xml I hadn't browsed down the long list of branches far enough to find "sydb-xenodata". But now I see it: https://github.com/TEIC/TEI/blob/sydb-xenodata/P5/Source/Specs/xenoData.xml Anyway, for the record, we're talking about @scope, not @source. --Kevin On 9/30/15 9:19 PM, Syd Bauman wrote:
Hey Kevin!
Oh dear. Methinks you are looking at the "for-xenoData" branch of our Subversion repository on Sourceforge[1], yes? We are now working with a git repository on GitHub.[2] There I'm talking about the "sydb- xenodata" branch. I'd like to just point you to the page on Jenkins where you can see the built product, but I don't know where it is, if it's even there.
So, here's the bit that corresponds to what used to be @type:
@scope: Status: Recommended Datatype: data.enumerated
Suggested values include:
source The metadata stored in this xenoData element describes the source document(s) identified in sourceDesc. transcription The metadata stored in this xenoData element describes the digital TEI document in which it is found. both All of the content of this xenoData element simultaneously describe the source document(s) identified in sourceDesc and the digital TEI document in which the xenoData itself is found. other The metadata stored in this xenoData element describe something other than the source document(s) identified in sourceDesc or the digital TEI document in which the xenoData itself is found.
Notes ----- [1] https://svn.code.sf.net/p/tei/code/branches/P5/for-xenoData/ [2] https://github.com/TEIC/TEI
I'll intrude on Council discussions just to ask for clarification. Are you working in the "for-xenoData" branch? I see @type (not @source) on xenoData, with two suggested values: * source * transcription Is that what you meant?
participants (3)
-
Kevin Hawkins -
Lou Burnard -
Syd Bauman