[
Lists Home |
Date Index |
Thread Index
]
Alessandro Triglia wrote:
> I absolutely agree. Another way of saying this is that
> the stream of SAX callbacks coming from parsing/decoding
> an encoding of ASN.1 (BER, PER, EXTENDED-XER) has to be
> exactly the same stream, for a given schema and a given
> instance, regardless of the encoding rules in use (BER, PER,
> EXTENDED-XER), and has to be the same stream as would be
> generated by a "normal" SAX parser parsing the XML document.
Great! I'm glad to see that someone who is doing one of the
implementations agrees on this one.
Excuse my ignorance here, but is there anything like a "SAX
Test Suite" that can be used to demonstrate conformance in an
objective manner? Ideally, we'd have a schema and a bunch of XML
messages along with traces from a "correct" SAX 2 system. The ASN.1
folk would then need to show that they can convert the schema to ASN.1
(either automatically or manually) and encode the XML messages. Then
they should show that their SAX code, when reading the binary
encodings, generates the same trace as the reference trace. Do such
conformance tests exist? Or, are their conformance tests that can be
leveraged here?
bob wyman
-----Original Message-----
From: Alessandro Triglia [mailto:sandro@mclink.it]
Sent: Monday, November 10, 2003 10:48 AM
To: bob@wyman.us
Cc: xml-dev@lists.xml.org
Subject: RE: [xml-dev] SAX for Binary Encodings (preserving
investment) (ASN.1 and SAX)
Bob Wyman wrote:
>
> I argue that if something is
> marked to be an attribute when converted to XML, then it
> should be marked as an attribute when it is passed through an
> interface like SAX which is commonly used to process XML-like
> data. If this were not the case, then binary data would look
> different to the user of SAX when it was read directly via
> SAX rather than being read from a chunk of XML written by the
> XML encoder. This would be silly and unproductive.
I absolutely agree. Another way of saying this is that the stream of
SAX
callbacks coming from parsing/decoding an encoding of ASN.1 (BER, PER,
EXTENDED-XER) has to be exactly the same stream, for a given schema
and a
given instance, regardless of the encoding rules in use (BER, PER,
EXTENDED-XER), and has to be the same stream as would be generated by
a
"normal" SAX parser parsing the XML document. It must be possible to
replace a normal SAX parser used by an application with an ASN.1
parser/decoder for either XML or binary encodings with minimum changes
to
the application code. This will give us the interoperability we need
between the two worlds.
Alessandro Triglia
|
