Re: [poe] XML Schema design

For "plain old" XML a rule like "append the namespace URI and the local name to create a URI for the element" does not exist. This was "invented" by RDF.
See "plain old" namespace rules at https://www.w3.org/TR/xml-names/#ns-using - example:
`<edi:price xmlns:edi='http://ecommerce.example.org/schema' units='Euro'>32.18</edi:price>`
This would result in this URI for the price element `http://ecommerce.example.org/schemaprice` - not an invalid URI but hard to use in practice. (http://ecommerce.example.org/schemaprice and http://ecommerce.example.org/schemataxClass vs. http://ecommerce.example.org/schema#price and http://ecommerce.example.org/schema#taxClass, the latter is much easier to publish by a single core document/resource.)
Or look at the "old" HTML namespace: xmlns:html='http://www.w3.org/1999/xhtml
Only the "RDF-aware" namespace URIs required to have a separator at the end, e.g. # or /


-- 
GitHub Notification of comment by nitmws
Please view or discuss this issue at https://github.com/w3c/poe/issues/197#issuecomment-310592930 using your GitHub account

Received on Friday, 23 June 2017 07:26:36 UTC