OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] RE: Why a "general" solution? (was: RE: [xml-dev] XML Bina

[ Lists Home | Date Index | Thread Index ]

Claude L Bullard wrote:
> If we follow this to a logical conclusion, I 
> think we will end up with a binary-design 
> toolkit, not a single binary. 
	I doubt it. For XML interop, we only need to worry about the
use of alternatives that are appropriate for use in the same domain in
which XML is useful. Thus, we don't have to worry about the *general*
problem of binary-format design. (i.e. there may be techniques that
are appropriate when designing something like jpeg but I don't think
we have to worry about XML interchange of image data any time soon.
(<pixel red="999" blue="333"...</pixel>)
	For the domain in which XML is useful and thus XML interop is
meaningful, I am confident that we'll eventually "discover" that ASN.1
(either traditional or X.finfo) is sufficient to be the common binary
form. Thus, I would suggest that the XML community focus on interop
with ASN.1 and friends rather than trying to solve the general
binary-interop problem.

	One nice feature of accepting ASN.1 is it's name... It doesn't
include any "X"'s. Thus, you get compactness, speed of parsing, and
even patent protection! (i.e. no creative lawyer will be able to argue
that ASN.1 is just an alternative form of XML and is covered by the
growing number of XML specific patents...)

		bob wyman


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS