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] The subsetting has begun

[ Lists Home | Date Index | Thread Index ]

What I find very sad indeed is that users of J2ME cannot get good low 
resource XML parsing APIs without getting the unnecessary bloat of the 
web services APIs.

There is a real need for XML support (conformant) being provided in 
J2ME. The need to build in web services support at this time is not 
apparent. The specifications are not stable and the J2SE APIs for web 
services should probably go through an iteration or two before being 
incorporated into J2ME. If you are worried about resource consumption on 
J2ME cut the web services parts instead of XML conformance.

With the current spec you will be add the bloat of JAX-RPC to the 
platform while still forcing application developers to package a real 
XML parser in their applications to be able to parse XML.

What should be done is to split the two goals of section 1.1 into two 
separate JSRs, one for XML and one for WS. Then you could let the WS JSR 
use a non conformant parser, as long as you don't call it an XML parser.

/Fredrik Lindgren

Jon.Ellis@Sun.COM wrote:
> Mike Champion <mc@xegesis.org> wrote: 
>>--- Evan Lenz <evan@evanlenz.net> wrote:
>>>Indeed. The bare minimum requirements for a
>>>non-validating XML parser
>>>are unambiguous and hardly onerous. I'm tired of
>>>people making gross
>>>generalizations and using them as excuses for
>>>nonconformance, as if the
>>>complexity of the XML rec approached that of WXS.
>>So why do you think they are bothering to implement
>>only a subset if full compliance is "hardly onerous?" 
> Makes you wonder doesn't it ;-)
> The footprint requirements just don't appear allow it. There are more productions to process the DTD than the XML document, and that's before you have to deal with what you find there.
> As always, we'd be happen to be proved wrong. Given a way to be fully compliant, within the limitations of the devices, we would use it. The EG spent quite some time looking for such a solution...
>>It would be real nice to hear from someone on the
>>Expert Group on this matter, hint, hint, if you're
>>lurking out there.  Don't worry, the humiliation from
>>being abused on xml-dev only stings for a little while
> Public review is an interesting process. We are asking for feedback and we'll take what we are given. It would be nice to receive it in the spirit in which it was requested. :-)
> j.
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>


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

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