Hello Jesse, Thursday, September 25, 2003, 7:06:53 PM, you wrote:
First of all, let me thank you, Rich Salz and others for interest in the problem. JP> I think that's the core question: does the Visa spec call for handling their JP> CDATA "id" attribute as if it were an ID? I don't know anything about the JP> spec, except that it causes this question to arise periodically JP> (occasionally inducing me to rant). Slava, can you point to it, or excerpt JP> relevant sections? Do you mean a spec from Visa? It is "3-D Secure: Protocol Specification Core Functions v1.0.2 July 16, 2002" Unfortunately, I can't give you an URL where to download this document. It is not distributed freely. But I think, I can repost here a part of 3D-secure DTD: <!ELEMENT ThreeDSecure (Message)*> <!ELEMENT Message ((CRReq | CRRes | VEReq | VERes | PAReq |(PARes, Signature) | Error))> <!ATTLIST Message id CDATA #REQUIRED > <!ELEMENT PARes (version, Merchant, Purchase, pan, TX, IReq?, Extension*)> <!ATTLIST PARes id CDATA #REQUIRED> ... Examples of ThreeDSecure messages was already published in this forum. For example, see message: http://www.aleksey.com/pipermail/xmlsec/2003/000666.html -- Best regards, Slava mailto:[EMAIL PROTECTED] _______________________________________________ xmlsec mailing list [EMAIL PROTECTED] http://www.aleksey.com/mailman/listinfo/xmlsec
