[
Lists Home |
Date Index |
Thread Index
]
In article <FB4F95390166B14C90E4DD950D69D6E21A8074@EXCHVS2.cs.cornell.edu> you write:
> XML 1.0 says "...must match the Name production."
> http://www.w3.org/TR/REC-xml#id
> XSD Part 2 says "...set of all strings that match the NCName production..."
> http://www.w3.org/TR/xmlschema-2/#ID
XML 1.0 also warned against using colons in names, and Namespaces 1.0 +
errata says:
Definition: A namespace-well-formed document is namespace-valid
if it is valid according to the XML 1.0 specification, and all
tokens other than element types and attribute names which are
required, for XML 1.0 validity, to match the XML production for
Name, match this specification's production for NCName.
It follows that in a namespace-valid document
* No attributes with a declared type of ID, IDREF(S),
ENTITY(IES) or NOTATION contain any colons.
The point is that Namespaces introduced an interpretation for names
with colons in, and chose not to put IDs in namespaces. XML Schemas
are built on XML + Namespaces.
-- Richard
|
