- From: Jose Kahan <jose.kahan@w3.org>
- Date: Fri, 8 Oct 2004 18:55:01 +0200
- To: www-xkms@w3.org
Hi folks, My brain is fried right now, so I can't find the right answer to this problem. There's an XML error in the changes that Shivaram did. See for example par 101 in part-1. I'm not sure if he was trying to make an xkms entity &xkms; or if he wanted to say &xkms; or ... in all cases, he us using an &xkms; entity and this results in a parsing error. -------- !-- ResponseMechanism --> <simpleType name="ResponseMechanismEnum"> <restriction base="anyURI"> <enumeration value="&xkms;Pending"/> <enumeration value="&xkms;Represent"/> <enumeration value="&xkms;RequestSignatureValue"/> </restriction> </simpleType> <simpleType name="ResponseMechanismOpenEnum"> <union memberTypes="xkms:ResponseMechanismEnum anyURI"/> </simpleType> <element name="ResponseMechanism" type="xkms:ResponseMechanismOpenEnum"/> <!-- /ResponseMechanism --> ---- The xkms.xsd file lists this as: --- <simpleType name="ResponseMechanismEnum"> <restriction base="anyURI"> <enumeration value="http://www.w3.org/2002/03/xkms#Pending"></enumeration> <enumeration value="http://www.w3.org/2002/03/xkms#Represent"></enumeration> <enumeration value="http://www.w3.org/2002/03/xkms#RequestSignatureValue"></enumeration></restriction></simpleType> -- Any idea on which piece of text is the correct one? -jose
Received on Friday, 8 October 2004 16:55:26 UTC