As promised, I've now updated my little tutorial on pure ODD. A PDF version is attached, and you can find the source in the repo at https://github.com/TEIC/TEI/blob/dev/Documents/pureODD/pureODDtutorial.xml : I am wondering if it needs a section on "how to convert your existing odd", which would however be much easier to write with input from some early adopters... (that's you chaps) If you sniff around in that bit of the repo, you'll also find a more ambitious document by Sebastian called "The TEI Customisation Handbook" ( https://github.com/TEIC/TEI/blob/dev/Documents/oddmanual/oddmanual.xml) This was written some time ago and doesn't therefore discuss pure odd. I haven't yet had the heart to bring it up to date.
Hi Lou, thanks to your reminder I tried to convert the existing CMIF ODD [1] to pure ODD. It worked well, despite a <dataRef> within <content>, which didn’t produce the desired output. The relevant elementSpec: <elementSpec ident="idno" mode="replace" module="header"> <desc xml:lang="en" versionDate="2015-10-16">Provides the URL of the CMI file</desc> <content> <dataRef key="teidata.pointer"/> </content> <attList> <attDef ident="type" mode="add" usage="req"> <valList mode="add" type="closed"> <valItem ident="url"/> </valList> </attDef> </attList> <exemplum> <egXML xmlns="http://www.tei-c.org/ns/Examples"> <idno type="url">http://weber-gesamtausgabe.de/correspDesc.xml</idno> </egXML> </exemplum> </elementSpec> Is there something wrong with my definition or is it a bug? Best Peter [1] https://github.com/TEI-Correspondence-SIG/CMIF/blob/master/odd/cmi-customiza...
Am 26.01.2016 um 12:35 schrieb Lou Burnard <lou.burnard@retired.ox.ac.uk>:
As promised, I've now updated my little tutorial on pure ODD. A PDF version is attached, and you can find the source in the repo at https://github.com/TEIC/TEI/blob/dev/Documents/pureODD/pureODDtutorial.xml : I am wondering if it needs a section on "how to convert your existing odd", which would however be much easier to write with input from some early adopters... (that's you chaps)
If you sniff around in that bit of the repo, you'll also find a more ambitious document by Sebastian called "The TEI Customisation Handbook" ( https://github.com/TEIC/TEI/blob/dev/Documents/oddmanual/oddmanual.xml) This was written some time ago and doesn't therefore discuss pure odd. I haven't yet had the heart to bring it up to date.
<pureODDtutorial.pdf>-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
Many thanks Peter. I am pretty sure that it's a bug: dataRef as child of content is not currently processed correctly by the stylesheets. I will check and raise an issue. On 08/02/16 11:36, Peter Stadler wrote:
Hi Lou,
thanks to your reminder I tried to convert the existing CMIF ODD [1] to pure ODD. It worked well, despite a <dataRef> within <content>, which didn’t produce the desired output. The relevant elementSpec:
<elementSpec ident="idno" mode="replace" module="header"> <desc xml:lang="en" versionDate="2015-10-16">Provides the URL of the CMI file</desc> <content> <dataRef key="teidata.pointer"/> </content> <attList> <attDef ident="type" mode="add" usage="req"> <valList mode="add" type="closed"> <valItem ident="url"/> </valList> </attDef> </attList> <exemplum> <egXML xmlns="http://www.tei-c.org/ns/Examples"> <idno type="url">http://weber-gesamtausgabe.de/correspDesc.xml</idno> </egXML> </exemplum> </elementSpec>
Is there something wrong with my definition or is it a bug?
Best Peter
[1] https://github.com/TEI-Correspondence-SIG/CMIF/blob/master/odd/cmi-customiza...
Am 26.01.2016 um 12:35 schrieb Lou Burnard <lou.burnard@retired.ox.ac.uk>:
As promised, I've now updated my little tutorial on pure ODD. A PDF version is attached, and you can find the source in the repo at https://github.com/TEIC/TEI/blob/dev/Documents/pureODD/pureODDtutorial.xml : I am wondering if it needs a section on "how to convert your existing odd", which would however be much easier to write with input from some early adopters... (that's you chaps)
If you sniff around in that bit of the repo, you'll also find a more ambitious document by Sebastian called "The TEI Customisation Handbook" ( https://github.com/TEIC/TEI/blob/dev/Documents/oddmanual/oddmanual.xml) This was written some time ago and doesn't therefore discuss pure odd. I haven't yet had the heart to bring it up to date.
<pureODDtutorial.pdf>-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
Hi Peter I looked into this a bit more closely, and yes you're right that <content><dataRef key="teidata.pointer"/></content> does not do the right thing. Interestingly, <content><dataRef name="anyURI"/></content> DOES though. I have raised a Stylesheet issue accordingly https://github.com/TEIC/Stylesheets/issues/141 By the way, I noticed in your ODD that you have @status on your <schemaSpec> which is not currently legal in P5: if you think it should be (and I can't see why it shouldnt), could you raise a ticket proposing to add <schemaSpec> to the att.docStatus class please? Lou On 08/02/16 11:36, Peter Stadler wrote:
Hi Lou,
thanks to your reminder I tried to convert the existing CMIF ODD [1] to pure ODD. It worked well, despite a <dataRef> within <content>, which didn’t produce the desired output. The relevant elementSpec:
<elementSpec ident="idno" mode="replace" module="header"> <desc xml:lang="en" versionDate="2015-10-16">Provides the URL of the CMI file</desc> <content> <dataRef key="teidata.pointer"/> </content> <attList> <attDef ident="type" mode="add" usage="req"> <valList mode="add" type="closed"> <valItem ident="url"/> </valList> </attDef> </attList> <exemplum> <egXML xmlns="http://www.tei-c.org/ns/Examples"> <idno type="url">http://weber-gesamtausgabe.de/correspDesc.xml</idno> </egXML> </exemplum> </elementSpec>
Is there something wrong with my definition or is it a bug?
Best Peter
[1] https://github.com/TEI-Correspondence-SIG/CMIF/blob/master/odd/cmi-customiza...
Am 26.01.2016 um 12:35 schrieb Lou Burnard <lou.burnard@retired.ox.ac.uk>:
As promised, I've now updated my little tutorial on pure ODD. A PDF version is attached, and you can find the source in the repo at https://github.com/TEIC/TEI/blob/dev/Documents/pureODD/pureODDtutorial.xml : I am wondering if it needs a section on "how to convert your existing odd", which would however be much easier to write with input from some early adopters... (that's you chaps)
If you sniff around in that bit of the repo, you'll also find a more ambitious document by Sebastian called "The TEI Customisation Handbook" ( https://github.com/TEIC/TEI/blob/dev/Documents/oddmanual/oddmanual.xml) This was written some time ago and doesn't therefore discuss pure odd. I haven't yet had the heart to bring it up to date.
<pureODDtutorial.pdf>-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
Hi Lou, thanks for looking into this! Regarding the @status on <schemaSpec> I just realized it *was* valid until 2.9 – I’ll raise a ticket … Best Peter
Am 08.02.2016 um 16:02 schrieb Lou Burnard <lou.burnard@retired.ox.ac.uk>:
Hi Peter
I looked into this a bit more closely, and yes you're right that <content><dataRef key="teidata.pointer"/></content> does not do the right thing. Interestingly, <content><dataRef name="anyURI"/></content> DOES though. I have raised a Stylesheet issue accordingly https://github.com/TEIC/Stylesheets/issues/141
By the way, I noticed in your ODD that you have @status on your <schemaSpec> which is not currently legal in P5: if you think it should be (and I can't see why it shouldnt), could you raise a ticket proposing to add <schemaSpec> to the att.docStatus class please?
Lou
On 08/02/16 11:36, Peter Stadler wrote:
Hi Lou,
thanks to your reminder I tried to convert the existing CMIF ODD [1] to pure ODD. It worked well, despite a <dataRef> within <content>, which didn’t produce the desired output. The relevant elementSpec:
<elementSpec ident="idno" mode="replace" module="header"> <desc xml:lang="en" versionDate="2015-10-16">Provides the URL of the CMI file</desc> <content> <dataRef key="teidata.pointer"/> </content> <attList> <attDef ident="type" mode="add" usage="req"> <valList mode="add" type="closed"> <valItem ident="url"/> </valList> </attDef> </attList> <exemplum> <egXML xmlns="http://www.tei-c.org/ns/Examples"> <idno type="url">http://weber-gesamtausgabe.de/correspDesc.xml</idno> </egXML> </exemplum> </elementSpec>
Is there something wrong with my definition or is it a bug?
Best Peter
[1] https://github.com/TEI-Correspondence-SIG/CMIF/blob/master/odd/cmi-customiza...
Am 26.01.2016 um 12:35 schrieb Lou Burnard <lou.burnard@retired.ox.ac.uk>:
As promised, I've now updated my little tutorial on pure ODD. A PDF version is attached, and you can find the source in the repo at https://github.com/TEIC/TEI/blob/dev/Documents/pureODD/pureODDtutorial.xml : I am wondering if it needs a section on "how to convert your existing odd", which would however be much easier to write with input from some early adopters... (that's you chaps)
If you sniff around in that bit of the repo, you'll also find a more ambitious document by Sebastian called "The TEI Customisation Handbook" ( https://github.com/TEIC/TEI/blob/dev/Documents/oddmanual/oddmanual.xml) This was written some time ago and doesn't therefore discuss pure odd. I haven't yet had the heart to bring it up to date.
<pureODDtutorial.pdf>-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
Dear Lou, finally, I read the documentation on Pure ODD more carefully and have some comments. You can find them in the PDF document as notes. As expected, it is written clearly and it is very comprehensible, also for someone who wasn't involved in the development. Following the documentation, I converted a very simple ODD document to Pure ODD, generated an HTML documentation and a .rng. It all seems to work. For <rng:ref name="macro.phraseSeq"/> I used <macroRef key="macro.paraContent" />, but that description is missing in the tutorial. Best, Martina -----Ursprüngliche Nachricht----- Von: tei-council-bounces@lists.tei-c.org [mailto:tei-council-bounces@lists.tei-c.org] Im Auftrag von Lou Burnard Gesendet: Dienstag, 26. Jänner 2016 12:36 An: tei-council@lists.tei-c.org Betreff: [tei-council] pure odd doc As promised, I've now updated my little tutorial on pure ODD. A PDF version is attached, and you can find the source in the repo at https://github.com/TEIC/TEI/blob/dev/Documents/pureODD/pureODDtutorial.xml : I am wondering if it needs a section on "how to convert your existing odd", which would however be much easier to write with input from some early adopters... (that's you chaps) If you sniff around in that bit of the repo, you'll also find a more ambitious document by Sebastian called "The TEI Customisation Handbook" ( https://github.com/TEIC/TEI/blob/dev/Documents/oddmanual/oddmanual.xml) This was written some time ago and doesn't therefore discuss pure odd. I haven't yet had the heart to bring it up to date.
Many thanks for the careful reading Martina. I've corrected the errors you noted, and will add a new section on macroSpecs as soon as I can! L On 26/02/16 14:29, Scholger, Martina (martina.scholger@uni-graz.at) wrote:
Dear Lou,
finally, I read the documentation on Pure ODD more carefully and have some comments. You can find them in the PDF document as notes.
As expected, it is written clearly and it is very comprehensible, also for someone who wasn't involved in the development.
Following the documentation, I converted a very simple ODD document to Pure ODD, generated an HTML documentation and a .rng. It all seems to work. For <rng:ref name="macro.phraseSeq"/> I used <macroRef key="macro.paraContent" />, but that description is missing in the tutorial.
Best, Martina
-----Ursprüngliche Nachricht----- Von: tei-council-bounces@lists.tei-c.org [mailto:tei-council-bounces@lists.tei-c.org] Im Auftrag von Lou Burnard Gesendet: Dienstag, 26. Jänner 2016 12:36 An: tei-council@lists.tei-c.org Betreff: [tei-council] pure odd doc
As promised, I've now updated my little tutorial on pure ODD. A PDF version is attached, and you can find the source in the repo at https://github.com/TEIC/TEI/blob/dev/Documents/pureODD/pureODDtutorial.xml : I am wondering if it needs a section on "how to convert your existing odd", which would however be much easier to write with input from some early adopters... (that's you chaps)
If you sniff around in that bit of the repo, you'll also find a more ambitious document by Sebastian called "The TEI Customisation Handbook" ( https://github.com/TEIC/TEI/blob/dev/Documents/oddmanual/oddmanual.xml) This was written some time ago and doesn't therefore discuss pure odd. I haven't yet had the heart to bring it up to date.
participants (3)
-
Lou Burnard -
Peter Stadler -
Scholger, Martina (martina.scholger＠uni-graz.at)