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

Colonialism, SAX, Java, and Namespaces

• From: "Simon St.Laurent" <simonstl@s...>
• To: Paul Prescod <paul@p...>, xml-dev@i...
• Date: Fri, 05 Feb 1999 10:12:30 -0500

<vent temp="2000">

At 08:00 AM 2/5/99 -0600, Paul Prescod wrote:
>I don't think that "average developers" need to worry about namespaces. It
>is quite simple to build powerful, useful applications without them. I
>mean if you are implementing RDF or XSL then you need them, but short of
>that, I wouldn't bother.

I would really appreciate if someday the people building W3C specs would
acknowledge that 'average developers' actually do have to worry about
namespaces, notations, parameter entities, include/ignore sections, and
trying to read the specs themselves. If they would then take that knowledge
and apply it to the specification-writing process, from start to finish, we
might be able to move forward with a lot less back-and-forth about what
these things are really supposed to mean.

I get the feeling that some of the writers on this list - though
_certainly_ not all - view the 'average developer' as some kind of
primitive creature that should be shunted aside in the name of progress.
This colonialist view (I don't know what else to compare it to - simple
elitism seems inadequate) has contributed to the development of a lot of
tools that people talk about but very few people understand.  If, instead
of treating average developers as know-nothings to be conquered (they don't
need to know the details, they just need to use it), we treat average
developers as potential contributors, we might move farther along with XML.

Namespaces themselves, in most cases, aren't that hard to use.  They do,
however, contain the potential for disaster if applied in certain
circumstances in certain ways, and understanding that potential (and how to
avoid it) is critical information that's needed for anyone building a
namespace-aware application or using those sets of tools.  Not all of those
people are in the core XML community, and not all of them give a damn about
XML, but they may need to know what it takes to use namespaces effectively
and safely.

</vent>


Simon St.Laurent
XML: A Primer / Building XML Applications (March)
Sharing Bandwidth / Cookies
http://www.simonstl.com

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Average developers (was Re: Colonialism, SAX, Java, and Namespaces)
    • From: James Robertson <jamesr@s...>
  • Re: Colonialism, SAX, Java, and Namespaces
    • From: Paul Prescod <paul@p...>

• References:
  • Re: SAX, Java, and Namespaces (was Re: Restricted Namespaces for XML)
    • From: hpyle@a...
  • Re: SAX, Java, and Namespaces (was Re: Restricted Namespaces forXML)
    • From: Paul Prescod <paul@p...>

• Prev by Date: Re: Component Markup Language
• Next by Date: Re: Fw: Namespaces does *not* formally introduce "global attributes"
• Previous by thread: Re: SAX, Java, and Namespaces (was Re: Restricted Namespaces forXML)
• Next by thread: Re: Colonialism, SAX, Java, and Namespaces
• Index(es):
  • Date
  • Thread