- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 27 Jan 2006 14:54:28 +0000
- To: public-i18n-its@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2761 ------- Additional Comments From fsasaki@w3.org 2006-01-27 14:54 ------- Hi all, I thought about how to achieve the simple conformance "ITS without selector attributes". This is my solution proposal: Let's get rid of selector attributes in situ. It occurred to me that there is *no real need* for selector attributes *in situ*. Every XPath expression in an selector attribute which is in situ can be transformed into an XPath expression in an selector attribute which is at an <its:documentRule> element. Hence, my proposal: - Say in the spec that the in situ attributes are only to be used at the <its:documentRule> element, and change the markup definition in that sense (that is, the selector attributes are now not global attributes, but local ones at <its:documentRule>.) - have a conformance level which makes a schema conformant if it implements only the data category attributes, but not the selector attributes and the <documentRules> element. benefits of this change besides the conformance issue: - better validation of the attribute usage. It is not possible to use in situ *only* selector attributes. - GREAT benefit: it is now possible to say that every selector attribute value has to start with "/", since they are only dislocated. So: we can have a datatype with a regular expression like "/.*" for the selector attributes. - processing of in situ usage of ITS becomes easier. - explanation to users becomes easier: in situ we have only default selections, and dislocated we have XPath. Looking forward to discuss this via mail. Regards, Felix.
Received on Friday, 27 January 2006 14:54:33 UTC