[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XML API specification

  • From: Peter@u... (Peter Murray-Rust)
  • To: xml-dev@i...
  • Date: Thu, 27 Feb 1997 14:54:40 GMT

xml wether information
In message <199702271419.JAA24115@n...> gtn@e... (Gavin Nicol) writes:
> I think that for the *parser*, we should define an event-handling
> interface, as it is much simpler to build certain applications
> that way, and because you can build a tree from a stream of
> events if you need to.

In CoST Joe English supported both eventStreams and trees (I'm sure Joe will
have some wisdom on this one).  I started off using the event mechanism 
and switched to a tree-based one but I suspect that this was the nature of the 
application.

My current problem may highlight this.  A CML document is highly 
tree-structured and contains no mixed content, so that eventStreams don't
contribute much. BUT it also includes chunks of HTML where a tree structure
is quite inappropriate.  If I take a Lark-based approach (or my own
parser) the HTML gets rendered into a tree.  I am now hacking this 
back into an event stream to render the hypertext.  Not only does it
take more effort, but I'm sure that holding HTML as a tree has a
memory hit.  Ideally when I'm parsing CML, and come to the
tag <XHTML> (sic) which contains <BODY>, I'd like to tell the parser
'stop parsing as a tree and just hold a hypertext string until </XHTML>.
We *could* do this with a PI, but would have to all agree.

> 
> Some questions that will affect the API is whether one sees empty
> element as elements containing nothing, or as elements unable to

Yes.
> contain anything, and wether entity/attribute type information needs
> to be passed across thr API.

I have been convinced that entity information needs to be preserved and I
assume there are people who are concerned about attribute_type.  If
nothing else, this is probably critical for ID/IDREF.
> 
> What do people think? How much information must the parser pass 
> along?

At least what comes out of sgmls/ESIS, probably with general entities
added.  We also need to know the DOCTYPE info.
[...]

	P.

-- 
Peter Murray-Rust, domestic net connection
Virtual School of Molecular Sciences
http://www.vsms.nottingham.ac.uk/

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


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.