[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: more on ASN.1 and SOAP

My reading is that the body of the soap message is encoded as
an opaque string, but that's the part of interest to NETCONF.

Perhaps the message body should also be encoded in ASN.1 using
the methods mentioned here:

http://asn1.elibel.tm.fr/xml/

Ted.

On Thursday, June 19, 2003, at 10:40 AM, Andy Bierman wrote:


At 09:24 AM 6/19/2003, Randy Presuhn wrote:

Hi -

Though current discussion on this list has been focusing on beep,
I think this update on the use of ASN.1 and SOAP might still be
of interest, especially in bandwidth-limited environments:

http://asn-1.com/soap.htm

(Am I the only one who finds the ASN.1 easier to read than
the W3C's documentation?)  If the proposed new work is taken
on by ISO (several national bodies are known to be likely to vote
yes; at least five are necessary) the US part of the work would
take place in INCITS T3.

Is this for the documentation of syntax -- a replacement for XSD?

I would much rather use XSDs to document the syntax of netconf
messages (and data model content).  It is more widely supported
by SW tools.


Randy

Andy






--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>