March 2017 - Tei-council - lists.tei-c.org

co-operative stylesheet education session #8
by Syd Bauman 28 May '17

28 May '17

We are planning to meet next Thu, 04-06 at 13:00Z, i.e.: Thu 2017-04-06 06:00 PDT (poor Martin) Thu 2017-04-06 09:00 EDT Thu 2017-04-06 14:00 BST Thu 2017-04-06 15:00 CEST Martin will be sending out details on 2 more issues we thought might be worth addressing. They are https://github.com/TEIC/Stylesheets/issues/246 and another (that I don't think has a ticket yet) which is an error in common/common_figures.xsl (roughly lines 226-240): the stylesheet makes the erroneous assumption that if there is a @width attribute, then there will be a @height attribute. Moreover, there are still the agenda items from our last meeting, most of which are still to be addressed. They include: * table review (http://wiki.tei-c.org/index.php/Mapping_ODD_processing) - we still need rows for TEI ODD -> documentation * generation of PDF from within oXygen framework * stylesheet re-write project * re-working the Stylesheet/Test/ suite (see Martin's Test2/, which uses 'ant') * ticket: https://github.com/TEIC/Stylesheets/issues/227 I can try to be the one to establish a Google Hangout and invite people, but I have been remarkably unsuccessful at this in the past. So if anyone would like to volunteer ...

9 18

Fwd: deprecation information incomplete
by Kevin Hawkins 11 May '17

11 May '17

Council, The TEI webmasters received the below message from Lou. It took me a bit to figure out what he was referring to, but I've got it now. At http://www.tei-c.org/Activities/Council/Working/tcw27.xml , he suggests changing the first bullet under "Deprecated" from: * The appropriate spec is modified to add@validUntilon the appropriate<elementSpec>,<classRef>, or<attDef>elements. The value of@validUntilshall be no sooner than two years from the date of the change (thus guaranteeing/at least/one year from the release in which the deprecation is announced to the change in which the feature disappears). to: * The appropriate specification is given a@validUntilattribute indicating the intended date after which the specification will be withdrawn. Specifications which can be deprecated in this way are all members of the class att.deprecated. This seems straightforward, but please Luis and me know by April 1 if you object by replying to all. Kevin -------- Forwarded Message -------- Subject: deprecation information incomplete Date: Fri, 24 Mar 2017 21:24:40 +0000 From: Lou Burnard <lou.burnard(a)retired.ox.ac.uk> To: web(a)tei-c.org The list of elements which can carry a @validUntil attribute on this page is incomplete. The full list should be attDef <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-attDef.html> classSpec <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-classSpec.html> constraintSpec <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-constraintSpec.html> dataSpec <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dataSpec.html> elementSpec <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-elementSpec.html> macroSpec <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-macroSpec.html> moduleSpec <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleSpec.html> paramSpec <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-paramSpec.html> schemaSpec <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-schemaSpec.html> valDesc <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-valDesc.html> valItem <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-valItem.html> valList <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-valList.html> defaultVal. Or you could simply refer to the class att.deprecated. <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-defaultVal.html> "The appropriate spec is modified to add @validUntil on the appropriate <elementSpec> , <classRef> , or <attDef> elements." should perhaps change to say "The appropriate specification is given a @validUntil attribute indicating the intended date after which the the specification will be withdrawn. Specifications which can be deprecated in this way are all members of the class att.deprecated. "

1 1

RomaJS development update
by Raffaele Viglianti 02 May '17

02 May '17

Dear council members, I've completed a first phase of development of RomaJS (a placeholder name) and I would like to both give you an update and seek volunteers for the next phase of work. *The prompts for your contributions are highlighted in bold below (bring friends!).* The code is on GitHub: https://github.com/raffazizzi/romajs 1. Summary of work: I've have been writing this Redux / React <http://redux.js.org/docs/basics/UsageWithReact.html> application by focusing on data operations first, user interface second. Briefly, the application is now capable of: - reading in an ODD file from the web or from disk - reading in a source file (ie p5 subset in JSON format) - add and remove modules - add and remove elements - write an updated ODD to disk (This is actually only mocked for user testing at the moment.) - provide basic UI components for these operations (working towards what's been sketched in the wireframes <https://docs.google.com/presentation/d/1sUESuY9pF3DkHoQMJJjrVMV2SPFQYE1YqmG…> ) 2. Tests Each operation is comprehensively tested. I've aimed at creating a solid testing infrastructure that is at the core of the application development. I have created two wiki pages to help understanding and developing tests: - a list of test scenarios <https://github.com/raffazizzi/romajs/wiki/Test-scenarios> - a short guide on how to write tests <https://github.com/raffazizzi/romajs/wiki/How-to-write-tests> *Please look at the list of test scenarios: have I not tested something?* You'll see that the list includes different ways of including/excluding modules and elements in ODD. *Have I covered all the mechanisms for doing so? What's missing?* We could discuss this on this email or on the wiki. It would be awesome if then someone besides me would write new tests that result from the discussion! 3. Parsing ODD In order to avoid using a heavy DOM processor, and to make it possible to include ODD directly in the application state, I've opted to convert ODD to JSON. At first I was using an off the shelf library that served me very well until I had to serialize back to XML and realized that mixed content was all screwy... So I wrote my own library here: https://github.com/raffazizzi/squash-xml-json The library is quite central to the success of RomaJS and while it has some tests, it needs more extensive testing. *Would anyone like to help test and develop it? Or perhaps know of viable alternatives I've overlooked?* 4. Getting started with the UI I've created basic UI components to do the operations described above. Here is the current very bare version: https://raffazizzi.github.io/romajs/ *Please try it out with as many (canonicalized) ODD files that you have lying around. Does it do what you expect? Do you get back XML that matched what you wanted? **Please break it (hopefully it will take a few hits first).* 5. Next steps I think I may focus more on UI development now (as per wireframes <https://docs.google.com/presentation/d/1sUESuY9pF3DkHoQMJJjrVMV2SPFQYE1YqmG…>). Getting started with a CSS framework library and nail down general functionality up to the point where we are now. At the same time, I'd like to get started on operations to change elements (basically creating elementSpec[@mode="change"]). *This would be a good time for others to step in the development process: others could start writing operations and tests for changing elements while I focus on UI. Or viceversa. The current module/element operations and tests provide examples of how this all works (and of course I'd be happy to explain stuff).* 6. Finally: decision tree At the F2F we started talking about a possible "decision tree" as a way into RomaJS. I started a document <https://docs.google.com/document/d/1r33QbY7O0HqOHvTxZtOq_-MrYqtIE572YqPEY3J…> with a list of possible questions to the user; James commented on it. *Please comment and add your additions if you can. I would be thrilled if others would want to explore this further as a mind map, etc. so that it's nicely planned out before starting development on a decision tree feature.* As development gains momentum, I hope to write similar reports to this one at least once monthly. Raff

5 10

The C-word and its tickets
by Lou Burnard 06 Apr '17

06 Apr '17

I am a great believer in fostering the illusion of progress. So, even though I know the topic is not one that gets Council members' pulses racing, I crave a few moments of their attention in the matter of the changes needed to chap 23. You may recall that one cmsmcq raised a number of tickets a month or so ago , most of which spawned some heated debate, none of which has yet been resolved although I have identified some (marked Green for Go) where I think some minor changes to wording would allow them to be closed. I take the liberty of summarizing what I believe to be the state of play, but by all means review and shout if I have overlooked something. https://github.com/TEIC/TEI/issues/1596 : proposed resolution is to create a new <empty/> element. No-one has reacted to this (comparatively simple) proposal yet. https://github.com/TEIC/TEI/issues/1591 : (GREEN) : revised wording proposed https://github.com/TEIC/TEI/issues/1590 : (GREEN) : revised wording proposed https://github.com/TEIC/TEI/issues/1589 : agreed that there is a stylesheets issue (https://github.com/TEIC/Stylesheets/issues/235) ; necessary wording changes not yet clear https://github.com/TEIC/TEI/issues/1588 : is this resolved by wording changes proposed for 1587 ? https://github.com/TEIC/TEI/issues/1587 : (GREEN) : revised wording proposed https://github.com/TEIC/TEI/issues/1586 : lots of heat but little light as yet My question today is: shall I go ahead and just implement the changes proposed by the green tickets ?

4 3

Jenkins build became unstable: TEIP5-dev #2800
by Victoria TEI Jenkins 31 Mar '17

31 Mar '17

http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/2800/

3 9

Agenda for Thursday
by Hugh Cayless 30 Mar '17

30 Mar '17

Hi All, A reminder that we are scheduled to meet this Thursday at 09:00 EDT / 14:00 BST / 15:00 CEST. As we agreed at the F2F, we'll switch gears a bit and try to tackle one or two of our more troublesome tickets. Agenda is at https://docs.google.com/document/d/1cZ_LFHlKd4KBSypS8u8I7xFVr1lARMCiGY2HXsv… Hugh

6 10

pattern for ANY in RELAX NG
by Syd Bauman 27 Mar '17

27 Mar '17

Kudos to George Bina, who actually simply asked James Clark and Makoto Murata about the "Conflicting ID-types" problem. All we need to do is change the definition of the anyXML pattern so that an @xml:id that it matches that is already defined is declared as ID, not text! Gads, why didn't I think of that? The problem is this is not all that easy to do. The idea isn't so hard to grok, but implementation may be a tall order. Pretend we have a schema that defines only 3 elements. The root <test>, which has one or more <para>s, each of which can have text or <name>; of course, any element in our system can have an @xml:id: start = element test { attribute xml:id { xsd:ID }?, para+ } para = element para { attribute xml:id { xsd:ID }?, ( text | name )* } name = element name { attribute xml:id { xsd:ID }?, ("Horslips" | "Heart" | "Berlin" | "Blondie" | "Quarterflash" | "Renaissance") } That's a lovely working schema.[1] Let's say I also want to allow a single element <otherStuff> to precede the paragraphs, and allow it to have ANY content. Easy, with this method: start = element test { attribute xml:id { xsd:ID }?, otherStuff?, para+ } para = element para { attribute xml:id { xsd:ID }?, ( text | name )* } name = element name { attribute xml:id { xsd:ID }?, ("Horslips" | "Heart" | "Berlin" | "Blondie" | "Quarterflash" | "Renaissance") } otherStuff = element otherStuff { attribute xml:id { xsd:ID }?, ( text | anyXMLelement )* } anyXMLelement = # for elements that already have @xml:id defined as ID, define it # as ID here, too element test | otherStuff | name | para { attribute * - xml:id { text }*, attribute xml:id { xsd:ID }?, ( text | anyXMLelement )* } | # for all other elements, define @xml:id (and all other attrs) as # just text element * - ( test | otherStuff | name | para ) { attribute * { text }*, ( text | anyXMLelement )* } This is also a lovely working schema. It has the HUGE advantage that it does not trip over the "Conflicting ID-types" error. It has the (minor) disadvantage that for some elements inside <otherStuff> (namely, those that are NOT the enumerated <test>, <otherStuff>, <name>, <para>) @xml:id values are not required to be NCNames, and uniqueness of @xml:id values is not enforced. BUT those same problems occur with our current method (and our previous method) of doing this, and even more so as with those methods it applies to *all* descendant elements. The main problem, as I see it, is that it is hard to create the schema. That list of names (here "test | otherStuff | name | para") cannot be handled with indirection, because (AFAIK) an <rng:name> cannot be inside an <rng:define>. It has to be built at schema-build time, and then tucked into both places. And while building it you have to remember to include namespaces where necessary (for us that is only for "teix:egXML").[2] Another monkey wrench is that to build the list you not only have to go through all of the <tei:elementSpec>s in your flattened ODD, but also all the <rng:element>s in any schemas included by a <tei:moduleRef url="[MathML, SVG, whatever]"/> (And no, I have not thought through whether you want *all* element names, or only those that actually occur (perhaps indirectly via a class) in a content model, or if it matters.) I don't know how to do any of that off the top of my head, but my thought is that it is probably not too hard, albeit a significant amount of work. To see what a resulting tei_all.rnc would look like, feel free to take a look at [3], particularly the last dozen lines. Notes ----- [1] Working because the prefixes "xml:" and "xsd:" are magically defined. [2] And, if you're writing in the compact syntax (which we wouldn't be), to put a backslash in front of those names RELAX NG already uses (for us that's \list, \namespace, \default, \text, and \div) [3] http://paramedic.wwp.northeastern.edu/~syd/temp/TEI_Council/tei_all_new_ANY…

1 0

Build failed in Jenkins: TEIP5-dev #2796
by Victoria TEI Jenkins 21 Mar '17

21 Mar '17

http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/2796/Changes: [stadlerpeter] added a check for rnv with a URL hint (#1612) [stadlerpeter] escaping parentheses ------------------------------------------ Started by upstream project "TEIP5-Documentation-dev" build number 2480 originally caused by: Started by upstream project "TEIP5-Test-dev" build number 3269 originally caused by: Started by an SCM change Building in workspace <http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/TEIC/TEI.git # timeout=10 Fetching upstream changes from https://github.com/TEIC/TEI.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/TEIC/TEI.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/dev^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/dev^{commit} # timeout=10 Checking out Revision 4977312783acf2f9a06b9bfb5d6eba9cf471327b (refs/remotes/origin/dev) > git config core.sparsecheckout # timeout=10 > git checkout -f 4977312783acf2f9a06b9bfb5d6eba9cf471327b > git rev-list 4a4cc532a80730bdb7f4f273f26f0be01a4a698f # timeout=10 [workspace] $ /bin/bash -xe /tmp/jenkins177956701811658908.sh + svn update Skipped '.' Summary of conflicts: Skipped paths: 1 [workspace] $ /bin/bash -xe /tmp/jenkins6029062105703173107.sh + cd P5 + rm -f dist-source.stamp dist-schema.stamp dist-test.stamp dist-database.stamp dist-exemplars.stamp [workspace] $ /bin/bash -xe /tmp/jenkins2544929341668460481.sh + cd P5 ++ pwd + make VCS=git INJENKINS=true XSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/../../../Stylesheets-dev…> clean deb dist (cd Exemplars; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/Exemplars'> mv tei_lite_fr.nvdl tei_lite_fr.nvdl.bak rm -f *.processed *.xsd *.dtd *.doc.* *.rnc tei*.xsl tei*.rng *.compiled* *~ *.xi *.isosch *.epub *.pdf *.html *.nvdl *-teix* mv tei_lite_fr.nvdl.bak tei_lite_fr.nvdl rm -f exnames.xml rm -f enrich.rng isofs.rng rm -f names.xml *properties rm -f [A-Z]*xml make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/Exemplars'> (cd Test; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/Test'> rm -f test*.doc.xml test*.rnc test*.dtd test*.compiled.* test*.xsd test*.rnc test*.rng test*.xsl test*.isosch rm -rf LOG *~ *.xsd Schema RomaResults DTD rm -rf *.doc.* rm -f detest.log detest.log.all rm -f *-examples.rng *-examples.rnc *test*.nvdl *-ex.odd rm -f detest.rnc detest.rng detest.dtd detest.isosch make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/Test'> rm -rf release Guidelines Guidelines-web Schema DTD dtd Split rm -rf Guidelines.??? Guidelines-* rm -f *.isosch.xsl rm -f *.stamp rm -f *.xsd rm -f Exemplars/stdout rm -f Test/*.isosch rm -f Test/detest.dtd Test/detest.rnc Test/detest.rng Test/detest.xsl rm -f Test/stdout rm -f Utilities/guidelines.xsl rm -f anything buildweb.xml rm -f p5.sch p5.isosch p5.xml p5subset.xml p5subset.json p5subset.js rm -f p5attlist.txt rm -f p5odds-examples.rng p5odds-examples.rnc p5odds.rng p5odds.rnc p5odds.isosch rm -f pdfbuild.log rm -f stripspace.xsl.model rm -f tei-*.zip rm -f tei-p5-*_*build rm -f tei-p5-*_*changes rm -f tei-p5-*_*deb rm -f teiwebsiteguidelines.zip rm -rf FASC-* rm -rf catalogue.* modList rm -rf valid v.xml ValidatorLog.xml Utilities/pointerattributes.xsl graphics.sh missfont.log v.body v.header Schematron1.xml Schematron2.xml sh ./mydch debian-tei-p5-database/debian/changelog version in Debian (3.1.1a) is the same as 3.1.1a sh ./mydch debian-tei-p5-doc/debian/changelog version in Debian (3.1.1a) is the same as 3.1.1a sh ./mydch debian-tei-p5-exemplars/debian/changelog version in Debian (3.1.1a) is the same as 3.1.1a sh ./mydch debian-tei-p5-schema/debian/changelog version in Debian (3.1.1a) is the same as 3.1.1a sh ./mydch debian-tei-p5-source/debian/changelog version in Debian (3.1.1a) is the same as 3.1.1a sh ./mydch debian-tei-p5-test/debian/changelog version in Debian (3.1.1a) is the same as 3.1.1a rm -f tei-p5-*_*deb rm -f tei-p5-*_*changes rm -f tei-p5-*_*build BUILD: make Debian tei-p5-database package (cd debian-tei-p5-database; debclean;debuild -eXSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/../../../Stylesheets-dev…> -eVCS=git -eINJENKINS=true --no-lintian -nc -b -i.svn -I.svn -uc -us) Cleaning in directory . dh_testdir dh_testroot rm -f build-stamp configure-stamp dh_clean dpkg-buildpackage -rfakeroot -D -us -uc -nc -b -i.svn -I.svn dpkg-buildpackage: source package tei-p5-database dpkg-buildpackage: source version 3.1.1a dpkg-buildpackage: source distribution natty dpkg-buildpackage: source changed by TEI <editors(a)www.tei-c.org> dpkg-source -i.svn -I.svn --before-build debian-tei-p5-database dpkg-buildpackage: host architecture amd64 debian/rules build dh_testdir touch configure-stamp dh_testdir touch build-stamp fakeroot debian/rules binary dh_testdir dh_testroot dh_installdirs install -d <http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/debian-tei-p5-database/d…> install -d <http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/debian-tei-p5-database/d…> (cd ..; make VCS=git INJENKINS=true XSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/../../../Stylesheets-dev…> PREFIX=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/debian-tei-p5-database/d…> install-database) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5'> Checking you have running XML tools and Perl before trying to run transform... Ant:/usr/bin/ant Perl:/usr/bin/perl Java:/usr/bin/java xmllint:/usr/bin/xmllint rnv (https://github.com/dtolpin/RNV):make[1]: *** [check.stamp] Error 1 make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5'> make: *** [install] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 debuild: fatal error at line 1364: dpkg-buildpackage -rfakeroot -D -us -uc -nc -b -i.svn -I.svn failed make: *** [deb] Error 29 Build step 'Execute shell' marked build as failure Archiving artifacts

1 1

Build failed in Jenkins: TEIP5-Test-dev #3268
by Victoria TEI Jenkins 21 Mar '17

21 Mar '17

http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/3268/Changes: [stadlerpeter] added a check for rnv with a URL hint (#1612) ------------------------------------------ Started by an SCM change Building in workspace <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/TEIC/TEI.git # timeout=10 Fetching upstream changes from https://github.com/TEIC/TEI.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/TEIC/TEI.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/dev^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/dev^{commit} # timeout=10 Checking out Revision 45dc1afee90af8e869adcb0555731b111ebe3047 (refs/remotes/origin/dev) > git config core.sparsecheckout # timeout=10 > git checkout -f 45dc1afee90af8e869adcb0555731b111ebe3047 > git rev-list 4a4cc532a80730bdb7f4f273f26f0be01a4a698f # timeout=10 [workspace] $ /bin/bash -xe /tmp/jenkins5418818102376558057.sh + cd P5 ++ pwd + make VCS=git INJENKINS=true XSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/../../../Stylesheet…> clean validate test (cd Exemplars; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Exemplars'> mv tei_lite_fr.nvdl tei_lite_fr.nvdl.bak rm -f *.processed *.xsd *.dtd *.doc.* *.rnc tei*.xsl tei*.rng *.compiled* *~ *.xi *.isosch *.epub *.pdf *.html *.nvdl *-teix* mv tei_lite_fr.nvdl.bak tei_lite_fr.nvdl rm -f exnames.xml rm -f enrich.rng isofs.rng rm -f names.xml *properties rm -f [A-Z]*xml make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Exemplars'> (cd Test; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Test'> rm -f test*.doc.xml test*.rnc test*.dtd test*.compiled.* test*.xsd test*.rnc test*.rng test*.xsl test*.isosch rm -rf LOG *~ *.xsd Schema RomaResults DTD rm -rf *.doc.* rm -f detest.log detest.log.all rm -f *-examples.rng *-examples.rnc *test*.nvdl *-ex.odd rm -f detest.rnc detest.rng detest.dtd detest.isosch make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Test'> rm -rf release Guidelines Guidelines-web Schema DTD dtd Split rm -rf Guidelines.??? Guidelines-* rm -f *.isosch.xsl rm -f *.stamp rm -f *.xsd rm -f Exemplars/stdout rm -f Test/*.isosch rm -f Test/detest.dtd Test/detest.rnc Test/detest.rng Test/detest.xsl rm -f Test/stdout rm -f Utilities/guidelines.xsl rm -f anything buildweb.xml rm -f p5.sch p5.isosch p5.xml p5subset.xml p5subset.json p5subset.js rm -f p5attlist.txt rm -f p5odds-examples.rng p5odds-examples.rnc p5odds.rng p5odds.rnc p5odds.isosch rm -f pdfbuild.log rm -f stripspace.xsl.model rm -f tei-*.zip rm -f tei-p5-*_*build rm -f tei-p5-*_*changes rm -f tei-p5-*_*deb rm -f teiwebsiteguidelines.zip rm -rf FASC-* rm -rf catalogue.* modList rm -rf valid v.xml ValidatorLog.xml Utilities/pointerattributes.xsl graphics.sh missfont.log v.body v.header Schematron1.xml Schematron2.xml Checking you have running XML tools and Perl before trying to run transform... Ant:/usr/bin/ant Perl:/usr/bin/perl Java:/usr/bin/java xmllint:/usr/bin/xmllint /bin/sh: 1: Syntax error: "(" unexpected make: *** [check.stamp] Error 2 Build step 'Execute shell' marked build as failure

1 1

Re: [tei-council] purifying tei_xinclude.odd exemplar
by James Cummings 21 Mar '17

21 Mar '17

Actually, now that I've tried it, I still get the same schematron error. Changed them all to: <datatype> <dataRef key="teidata.text"/> </datatype> but I still get: datatype content must be in the namespace '' Have I mis-declared the @ns on the elementSpec? -James On 21/03/17 13:33, Lou Burnard wrote: > You cant use textNode as a child of datatype. Change them tp > datRef key teidata.text > > Sent from my Huawei Mobile > > -------- Original Message -------- > Subject: purifying tei_xinclude.odd exemplar > From: James Cummings > To: TEI Council ,Lou Burnard > CC: > > > Hi all, > > Because we should just purify these, but mostly because I wanted > to include XInclude into an ODD I'm writing, I tried to purify > the elementSpecs in > https://github.com/TEIC/TEI/blob/dev/P5/Exemplars/tei_xinclude.odd#L73 > > > > My attempt is at > https://gist.github.com/jamescummings/b01882b2e33f612ec7ea361c6060698a > > > But keeps giving me a schematron error "datatype content must be > in the namespace '' ". > > I remember having a conversation with Lou about datatypes and > namespaces but can someone remind me why I'm getting this error? > > -James > > -- > Dr James Cummings, James.Cummings(a)it.ox.ac.uk > Academic IT Services, University of Oxford > -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

2 1