Yes, I agree too. The DTD says CDATA, but should the schema be
xsd:string, or should it be the longer and more precise content
specifier I posted yesterday?
John Boyer, Ph.D.
Senior Product Architect
PureEdge Solutions Inc.
-----Original Message-----
From: Gregor Karlinger [mailto:gregor.karlinger@iaik.at]
Sent: Thursday, December 05, 2002 11:54 PM
To: John Boyer
Cc: w3c-ietf-xmldsig@w3.org
Subject: RE: Exclusive C14N Error: Using #default in NMTOKENS
I agree with Joseph that we should fix the DTD rather than changing
the name "#default" since this influences already existing implemen-
tations of EC14N.
Liebe Gruesse/Regards,
Gregor Karlinger
> -----Original Message-----
> From: w3c-ietf-xmldsig-request@w3.org
> [mailto:w3c-ietf-xmldsig-request@w3.org] On Behalf Of John Boyer
> Sent: Wednesday, December 04, 2002 6:57 PM
> To: w3c-ietf-xmldsig@w3.org
> Subject: Exclusive C14N Error: Using #default in NMTOKENS
>
>
>
> The PrefixList is defined to be of type NMTOKENS, but the #
> character is not allowed according to the XML rule for NmToken.
>
> This can be fixed in one of two ways:
>
> 1) Change from NMTOKENS to CDATA
>
> 2) Change from # to :
>
> The latter approach is reasonable because namespace prefixes
> do not contain a colon. This would allow us to keep the
> NMTOKENS content model. However, according to Joseph Reagle,
> the use of #default is designed to profile XSLT.
>
> John Boyer, Ph.D.
> Senior Product Architect
> PureEdge Solutions Inc.
>
>