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


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: XML API specification

[ Lists Home | Date Index | Thread Index ]
  • From: Peter@ursus.demon.co.uk (Peter Murray-Rust)
  • To: xml-dev@ic.ac.uk
  • Date: Thu, 27 Feb 1997 15:19:56 GMT

This is very helpful, thanks.

In message <199702271514.KAA24157@nathaniel.ebt> gtn@ebt.com (Gavin Nicol) writes:
> I think for XML, we should probably get more concrete. The question
> is how much more concrete? How much information *must* the API support?

There are possibly two questions here.  Do we need to _pass the information_,
and do we need to _have special names_ (rather than just Property).  I suspect
that you will find it difficult to get rid of anything below that will
satisfy everyone.  My own simple experience is that I would actively use
the following:

> Do we *need* 
Element,     Y
Attribute,   Y
Comment,     N  (an XML processor _may_, but need not, pass these.
		where would they be attached?)
PI,          Y 
Header,      Y
DTD,         Y
MarkedSection,    N
EntityReference,  Possibly, when I get brave
Entity etc. etc?

I would, however, be prepared to receive them as Property, so long as they
were clearly documented, and I assume that they might well be subclassed
from Property anyway.

Peter Murray-Rust, domestic net connection
Virtual School of Molecular Sciences

xml-dev: A list for W3C XML Developers
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To unsubscribe, send to majordomo@ic.ac.uk the following message;
unsubscribe xml-dev
List coordinator, Henry Rzepa (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