• From: james anderson <James.Anderson@m...>
• To: "xml-dev@i..." <xml-dev@i...>
• Date: Mon, 20 Dec 1999 21:23:26 +0100

If your goal is a simple interface, use symbols. That is, reify the names as
first class objects. One of the properties of the respective symbol is its
package. One of the properties of the package is its static name. In the
simple case, this name is the URI.
If you go this route, you need only
> 
> - type of piece (eg. element, attribute, PI, comment, text, etc.)
> - the name-symbol
> - text (when applicable)
> 

The per-element-type case does not change the interfaces, as the name of the
package is generated to accomplish the desired partition. (once you figure out
what that is...)

> It seems that the following additional pieces are needed to represent attribute belonging to the per-element-type namespace partition:
> 
> - namespace URI of the associated element type (subsumed in package name)
> - local name of the associated element type (subsumed in package name)
> 

There's an xml processor which comes with the cl-http server. It passes
symbols around. nothing else.


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 unsubscribe, mailto:majordomo@i... the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• References:
  • The per-element-type namespace partition
    • From: Joe Lapp <jlapp@w...>

• Prev by Date: Re: SAX2: Namespace proposal
• Next by Date: Re: SAX2: Namespace proposal
• Previous by thread: The per-element-type namespace partition
• Next by thread: Re: The per-element-type namespace partition
• Index(es):
  • Date
  • Thread