[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: A multi-step approach on defining object-orientednature of

• To: <xml-dev@l...>
• Subject: Re: A multi-step approach on defining object-orientednature of DOM
• From: "Jeff Rafter" <jeffrafter@d...>
• Date: Thu, 22 Aug 2002 01:21:51 -0500
• References: <8BD7226E07DDFF49AF5EF4030ACE0B7E06621F77@r...> <1029896844.25933.160.camel@marajen>

These are all great points...

> 2. API users who have written schemas using the usual defaults
> (elementFormDefault qualified, attributeFormDefault unqualified) get
> into a fidget when their instances don't validate (because they assign
> namespace-qualified names to attributes, instead of unqualified ones).
> In one of the three occasions that I recall, the developer became
> increasingly hostile to discussion of the behavior of attributes,

By usual defaults do you mean de facto defaults? The actual defaults are
both unqualified. The actual defaults create documents that make little or
no sense from what I have seen because, regardless of the "unqualified"
setting, the root (because it is global) *must* be:

<n:name xmlns:n="http://www.example.com">
  <first/>
  <second/>
  <last/>
</n:name>

I remember myself and others arguing strongly against this on xmlschema-dev
but to no avail. I think the de facto defaults (i.e. what the books teach,
elementFormDefault qualified, attributeFormDefault unqualified) on the other
hand are not problematic. I think that they are a symptom of a larger
problem. They simply expose the overall strange behavior of attributes with
namespaces.

Cheers,
Jeff Rafter
Defined Systems
http://www.defined.net
XML Development and Developer Web Hosting

• Follow-Ups:
  • Namespaces blur (A multi-step approach on definingobject-orientednature of DOM)
    • From: Eric van der Vlist <vdv@d...>

• References:
  • RE: A multi-step approach on defining object-oriented nature of DOM
    • From: "Dare Obasanjo" <dareo@m...>
  • RE: A multi-step approach on defining object-orientednature of DOM
    • From: Amelia A Lewis <amyzing@t...>

• Prev by Date: Best Practice = Vanilla XML? (was A multi-step approach on defining object-orientednatureof DOM)
• Next by Date: Namespaces blur (A multi-step approach on definingobject-orientednature of DOM)
• Previous by thread: Re: A multi-step approach on defining object-orientednature of DOM
• Next by thread: Namespaces blur (A multi-step approach on definingobject-orientednature of DOM)
• Index(es):
  • Date
  • Thread