Additional information:
If I remove all elements, tagged with "chord:" and "ext:" from the XML
everything is fine. But I believe this is not the intention.
Regards
neil.young schrieb:
10.1:
I'm unable to generate a proxy class from the XML. Normaly I'm using
xsd.exe to convert plain xml to an xsd, if the xsd isn't provided. The
schema then is converted to proxy class, which might easily be used in
C# code. This works with several XML based information contents in
3GPP projects, but not with RELOAD.
Furthermore the XML is syntactically incorrect in the line containing
"<turn-density> 10 </turn-density><"
The final "<" has to be removed.
I was taking this xml and fed it to xsd.xml
c:\xsd reload.xml
The resulting 3 xsd files (reload.xsd, reload_app1.xsd,
reload_app2.xsd) could not be converted to a wrapper class by
c:\xsd reload.xsd /language:cs /classes
The error is:
Schema validation warning:
urn:ietf:params:xml:ns:p2p:config-ext1:example-extention-Element not
declared. Line 18, position 16.
Schema validation warning:
urn:ietf:params:xml:ns:p2p:config-chord:chord-ping-interval-Element
not declared. Line 19, position 16.
Schema validation warning:
urn:ietf:params:xml:ns:p2p:config-chord:chord-update-interval-Element
not declared Line 20, position 16.
Schema validation warning: Das
urn:ietf:params:xml:ns:p2p:config-ext1:example-kind-extention-Element
not declared. Line 56, position 34.
Although this is just warnings, the code generation fails too in the
first step:
Error: Error generating classes for schema 'reload'.
- 'urn:ietf:params:xml:ns:p2p:config-ext1:example-extention' missing.
Regards
neil.young schrieb:
5.3.1.1
<quote>
Thus, the 3-byte value
"Foo" would be encoded as: 03 46 4f 4f.
</quote>
In fact it should be "encoded" as "03 46 6f 6f", or it should be
named "FOO" :) (BTW: Those kind of errors in your draft is on the
level I'm able to discover... :))
Question behind: May I assume, that every "opaque" value, as far as
no explicitly determined in length, is preceded by a length byte (or
more bits) on the wire?
Regards
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
