OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: Namespaces and XML validation

[ Lists Home | Date Index | Thread Index ]
  • From: David Megginson <david@megginson.com>
  • To: XML Dev <xml-dev@ic.ac.uk>
  • Date: Sat, 8 Aug 1998 09:09:50 -0400

Peter Murray-Rust writes:

 > I know it's a slack time of year but it's catalysed (in my mind) by
 > the XML DevCon in Montreal in 12 days time. It would be nice to get
 > a feeling as to what activities people are thinking of for
 > implementing namespaces. So far we have had a few suggestions,
 > particularly James Clark, John Cowan, David Megginson and the
 > XSchema group. If DavidM reads this, it might be useful if he can
 > suggest how SAX might react to namespaces...

I'm looking forward to talking with as many of you as possible during
the XML Dev Day(s) in Montreal.  I first raised the issue of SAX and
namespaces on XML-Dev a few weeks ago -- after reading dozens of
postings and private messages, I am convinced that the only clean
solution is to define a special data type for two-part names,
something like the following:

  package org.xml.sax;

  public interface Name 
    public String getURI ();
    public String getLocalName ();

This, however, is the easy part; the hard part is figuring out how to
work this into SAX.  Here are some of the problems

1. How should SAX make the prefix map available to applications?  One
   option is to create a new handler type, called NamespaceHandler:

     public interface NamespaceHandler
       public void startNamespaceScope (String prefix, String uri);
       public void endNamespaceScope (String prefix);

   Another option is to create a new type of object called a Namespace

     public interface NamespaceResolver
       public Name resolveIndependentName (String name);
       public Name resolveDependentName (String name);

   This could be set by the NamespaceHandler:

     public interface NamespaceHandler
       public void setNamespaceResolver (NamespaceResolver resolver);

2. Should DocumentHandler be replaced or extended?

3. Does AttributeList now require a two-part lookup key, or should it
   stick to the unresolved (one-part) names?

4. Is namespace processing a core SAX service or a filter on top of

All the best,


David Megginson                 david@megginson.com

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


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

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