Marc,
Here you go, I passed the following XML through a validating XML parser:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
<command>
<create>
<domain:create
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
<domain:name>example.com</domain:name>
<domain:authInfo>
<domain:pw>2fooBAR</domain:pw>
</domain:authInfo>
</domain:create>
</create>
<update>
<domain:update xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"/>
</update>
<clTRID>ABC-12345</clTRID>
</command>
</epp>
This is the result:
XML error:
Line....: 13
Column..: 13
Message.: : cvc-complex-type.2.4.a: Invalid content was found starting with
element 'update'. One of '{"urn:ietf:params:xml:ns:epp-1.0":extension,
"urn:ietf:params:xml:ns:epp-1.0":clTRID}' is expected.
XML file domain-multi-command.xml is NOT valid
org.xml.sax.SAXException: XML error:
Line....: 13
Column..: 13
Message.: : cvc-complex-type.2.4.a: Invalid content was found starting with
element 'update'. One of '{"urn:ietf:params:xml:ns:epp-1.0":extension,
"urn:ietf:params:xml:ns:epp-1.0":clTRID}' is expected.
at XMLErrorHandler.error(XMLErrorHandler.java:38)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
at
org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown
Source)
at
org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
at
org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
at
org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at XMLValidator.validateXML(XMLValidator.java:190)
at XMLValidator.main(XMLValidator.java:400)
--
JG
James Gould
Fellow Engineer
jgo...@verisign.com
<applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com>
703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.com <http://verisigninc.com/>
On 10/20/22, 7:53 AM, "regext on behalf of Marc Blanchet"
<regext-boun...@ietf.org on behalf of marc.blanc...@viagenie.ca> wrote:
A suggestion to get the final word and to reply to your registrar: Use an
XML schema checker, feed it with the schema and the XML message you receive and
then look at the result of the parsing: it would tell you if the xml source is
valid against the schema. An example of such tool is xmllint —schema
$schemafile $inputFile . Xmllint is pretty available in any distribution.
Marc.
> Le 20 oct. 2022 à 06:06, Stephane Bortzmeyer <bortzme...@nic.fr> a écrit :
>
> We got a message from a registrar saying that having several commands
> under an <epp> element is legal:
>
> <epp>
> <command>
> <create>
> ...
> </create>
> <update>
> ...
>
> and that "it works with all the other registries".
>
> XML schema is difficult to read but RFC 5730, section 2.5 uses the
> singular to talk about the command. So, my opinoion is that the
> registrar is wrong. Advices?
>
> _______________________________________________
> regext mailing list
> regext@ietf.org
>
https://secure-web.cisco.com/1jr3xhRFKwYfvWYT-EHeb10qS4xHcGlfnN2kLwBIbL-BErTJDX7eZDE-9dXfTSmSVCc5B6M1AI4qLSJSuMrJynZC_94sjYfUaNZ5gmegv1MnNj4doLds6PJffck4mp4JT0AU8C7JliqQd_lCNuXrH1AN7Y4NkfSSmF0tChm1uewxbdhjPaquZC7dD1kFdp3vdxkl5zu7JN7sntg21vXiOD64aNAG8fz0p3-YNXiA4tlyfvtbB2ftWEQMYUillr2kC/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext
_______________________________________________
regext mailing list
regext@ietf.org
https://secure-web.cisco.com/1jr3xhRFKwYfvWYT-EHeb10qS4xHcGlfnN2kLwBIbL-BErTJDX7eZDE-9dXfTSmSVCc5B6M1AI4qLSJSuMrJynZC_94sjYfUaNZ5gmegv1MnNj4doLds6PJffck4mp4JT0AU8C7JliqQd_lCNuXrH1AN7Y4NkfSSmF0tChm1uewxbdhjPaquZC7dD1kFdp3vdxkl5zu7JN7sntg21vXiOD64aNAG8fz0p3-YNXiA4tlyfvtbB2ftWEQMYUillr2kC/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
