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: ASN.1 is an XML Schema Language (Fix those lists!)and

[ Lists Home | Date Index | Thread Index ]

Huh?  Plug in decoders for binaries that they don't recognize or 
that they don't have in a library?  I can't speak for the X3D WG 
although I serve on the Web3DC BoD, but I don't think any decisions 
have been made although the RFP text does want a single binary. 
A pluggable decoder is fine and probably desirable by some.  Just 
let me be clear that no decisions are made at this time and bidders 
are stepping up.  Note the IPR policies are royalty-free.


From: Pete Kirkham [mailto:pete.kirkham@baesystems.com]

Conversely to Len's example of X3D, streaming media players support
mechanisms to 
plug in decoders for formats they don't recognise. 

If the encoding was expressed in suitable form, then that could be retrieved
compiled instead having a library of native decoders. Such a mechanism would
allow any XML encoding of the same data, and shift the encoding of data as 
attribute or element into the encoding rules rather than using [ATTRIBUTE]
or list 
inline - in effect making ENCODING-CONTROL XER pluggable but with alias,
and graph serialisation controls. Kind of like architectural forms but with
binary formats (and possibly other text formats) thrown in free. 

Since one of the projects I work on has to support legacy text files, random

formats from other tools, its own XMI data and SOAP messages (which are
aliases of each other), I can think of one use case for plugging encodings
this; but at the moment someone ends up writing the encoder manually, rather
being generated off a concrete syntax description.


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

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