Why is @name of <param> defined as an XPath (via teidata.xpath)? The prose definition says it's a name, and all examples in the Guidelines look like names,[1] and it's hard to imagine what we would do with an XPath in there. So unless someone can explain the rationale for teidata.xpath pretty soon, I plan to plop in a ticket and change it to teidata.name. Notes ----- [1] 11 alternate 10 default 7 content 4 place 2 width 1 uri 1 url
That seems very likely just to be an error. Presumably because @value is an
XPath. I say do it.
On Wed, Jan 18, 2017 at 10:55 AM, Syd Bauman
Why is @name of <param> defined as an XPath (via teidata.xpath)? The prose definition says it's a name, and all examples in the Guidelines look like names,[1] and it's hard to imagine what we would do with an XPath in there.
So unless someone can explain the rationale for teidata.xpath pretty soon, I plan to plop in a ticket and change it to teidata.name.
Notes ----- [1] 11 alternate 10 default 7 content 4 place 2 width 1 uri 1 url -- 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
OK, changed it to teidata.enumerated. But now my local build is failing on many, if not all, of the P5/Test/*.xsd files. But I can't tell *why* or *how* it's failing. I think it more likely that there is something wrong with my local build environment than my change actually breaks XSD generation. So I'm going to push and see what Mr. Jenkins has to say about it.
That seems very likely just to be an error. Presumably because @value is an XPath. I say do it.
participants (2)
-
Hugh Cayless -
Syd Bauman