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] A multi-step approach on defining object-orientednature of

[ Lists Home | Date Index | Thread Index ]

From: "Amelia A Lewis" <amyzing@talsever.com>
 
> 3. API users who have generated schemas with attributeFormDefault
> qualified.  Testing with namespaced attributes works great, but when
> they try to "simplify the serialization" by using the default namespace,
> everything breaks.  This time it's because the namespace isn't declared,
> and trying to explain that elements can be unqualified and in a
> namespace, but attributes can't, is a somewhat painful exercise.  Tow
> occasions, one of them a direct result of revision of schema due to item
> #2; after that a different developer was given responsibility for the
> XML problem and the first became a general opponent XML for any use.

Is this just as much a problem with attributeFormDefault as with namespaces?

> 6. Several instances of the use of java.net.URL for normalization of a
> namespace URI that breaks comparability.  This leads to explanations
> that "a namespace URI is *not* a [java.net.]URL!"

Could you give some more details of this one?
 
Cheers
Rick Jelliffe




 

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

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