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

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: X-Schema syntax

[ Lists Home | Date Index | Thread Index ]
  • From: Paul Prescod <paul@prescod.net>
  • To: xml-dev@ic.ac.uk
  • Date: Mon, 28 Jun 1999 15:11:51 -0400

Andy Dent wrote:
> 
> I'm really not sure I understand what you're talking about here so
> the following comments may be totally inapplicable, but I think my
> point below is still valid.

Inapplicable but nevertheless intersting.

>  From a usability point of view (which drives a LOT of my API design)
> I think it is much easier for most people to understand definitions
> in context.
> 
> Many document types, and particularly database documents, will define
> elements that are only meaningful in a larger context (eg: LastName
> within Person).
> 
> The X-schema and DTD modes seem to support only defining all atomic
> elements separately from a context saying where they are used.
> 
> This requires the reader and writer of these schemae to build an
> abstract model in their heads that puts the definitions in context.

There are not many elements that appear in one and only one context.
Therefore it is necessarily the case that readers must put definitions in
context "in their heads." When you see the definition for LI in HTML OL,
you need to keep in your head the fact that that same element type can
occur in HTML UL. If you define it in both places then you need some way
of saying that they are really the "same thing" -- the opposite of your
definitions in context.

If I had to choose, reusing element types (possible in DTDs) is more
important than being able to have locally named element types (just use a
local prefix!). In other words if I am required to choose I would have to
say that DTDs made the better of the two choices.

I don't have a big problem with contextually specific element types but
there are usuability issues there. Is it okay for you that dragging and
dropping a LastName from one context in a document to another would render
it invalid because the same tag means completely different things in the
same document? I'm not convinced that local element types are worth
causing this problem.

-- 
 Paul Prescod  - ISOGEN Consulting Engineer speaking for only himself
 http://itrc.uwaterloo.ca/~papresco

Those who profess to favor freedom and yet depreciate agitation, are men 
who want crops without plowing up the ground. They want rain without 
thunder and lightning. They want the ocean without the roar of its many 
waters. - Fredrick Douglass
 http://www.informamerica.com/Articles/Quotes.htm

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/ and on CD-ROM/ISBN 981-02-3594-1
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