2719 2006-01-16 14:02:13 +0000 Namespace requirement and selector values 2006-09-18 04:40:55 +0000 1 1 1 Unclassified ITS ITS tagset WorkingDraft PC Windows XP CLOSED FIXED P2 normal PublicationFebruar20 1 ysavourel fsasaki public-i18n-its oldest_to_newest 7852 0 ysavourel 2006-01-16 14:02:16 +0000 The specification does not include information about how the selectors values should be set with regard to namespaces. Applying XPath expressions with or without namespace will have different results depending on how the document is written. What should be the standard process to resolve this? 8000 1 fsasaki 2006-01-27 06:34:16 +0000 I think a solution can be in the way it is done by schematron, see http://www.schematron.com/elements.html . Schematron has the same problem as ITS: XPath expressions are used within a schematron document, but how should one deal with default namespaces? The schematron solution is: have a separate <ns> element which is used for namespace definitions for the XPath expressions, like in the @context and @test attribute below: <schema xmlns="http://purl.oclc.org/dsdl/schematron"> <title>A Schematron Mini-Schema for Schematron</title> <ns prefix="sch" uri="http://purl.oclc.org/dsdl/schematron"> <pattern> <rule context="sch:schema"> <assert test="sch:pattern" ... No prefix means no namespace. We have still to define how to use the <ns> element if we have in situ ITS markup. But that would be a minor issue, I think. 8176 2 fsasaki 2006-02-09 14:14:59 +0000 The working group decided - to use no selector attributes in situ, which resolves this issue for in situ ITS markup (See http://lists.w3.org/Archives/Public/public-i18n-its/2006JanMar/0098.html) - to use zero or more <ns prefix=".." uri=".."> elements inside the <documentRules> to specify a namespace binding for XPath expressions, which resolves the issue for dislocated ITS. See http://lists.w3.org/Archives/Public/public-i18n-its/2006JanMar/0100.html