- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 11 Mar 2006 02:06:58 +0000
- To: public-i18n-its@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2878 ysavourel@translate.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Segmentation data category |"Element within text" data | |category ------- Comment #4 from ysavourel@translate.com 2006-03-11 02:06 ------- OK, I'm revising my opinion on not needing XPath. I've just found in DocBook some cases of elements that are sometimes within text, and sometimes not within text: <firstname>, <surname>, <lineage>, and <othername> are both in: <personname> which has the following content model: personname ::= ((honorific|firstname|surname|lineage|othername)+) and is also in <address> which has the following content model: address ::= (#PCDATA|personname|honorific|firstname|surname|lineage|othername| affiliation|authorblurb|contrib|street|pob|postcode|city|state| country|phone|fax|email|otheraddr)* And I suspect there are many more like this in DocBook. So I suppose that makes the use of its:selector a must in <its:withinTextRule> (and DocBook a good candidate to test any implementation to the limits).
Received on Saturday, 11 March 2006 02:11:33 UTC