18 Jan
2017
18 Jan
'17
4:55 p.m.
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