Lists Home |
Date Index |
- From: David Brownell <db@Eng.Sun.COM>
- To: James.Anderson@mecomnet.de
- Date: Thu, 12 Nov 1998 09:55:39 -0800
James -- I see you accept the point that the problem isn't that
simple. However, there's also the implied one that different
folk need different answers. The answers I would have given to
those questions are not the ones you gave. Different assumptions
can lead to a need for different answers. A base mechanism must
be a bit more flexible than that.
james anderson wrote:
> David Brownell wrote:
> > Graham Moore wrote:
> > >
> > > Eliot wrote
> > >
> > > > The last two [java class for elements / swing classes] are no different
> > > > from requiring a style sheet--someone still has to provide
> > > > a per-document or document type definition of what the styling should
> > > > be
> > >
> > > The functional binding / class => element could be done as a default. Look
> > > in the location where the document was acquired from using the element name
> > > as the class name. It would just work, with no additional configuration
> > > files. If no class exists then the node is just a node.
> > That doesn't seem sufficient to me. What's the package name?
> a mapping from the namespace name. (java packages may require an intermediate)
Assumes there's a namespace name.
> > What about classes that should represent multiple element types?
> specialize the class appropriately
Assumes creating a class is zero cost, and doesn't accomodate open
ended sets of element types.
> > What about the different semantics associated with different namespaces?
> that's what packages are for.
Assumes folk don't have common semantics in different namepaces.
> > Suppose you want the element and class names to be different, perhaps because
> > you and your users work with different natural languages?
> support an architectural attribute, with appropriate defaults in the
> attribute definitions.
Assumes the folk defining the mappings are the ones defining the
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)