XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] "Introducing MicroXML, Part 1: Explore the basicprinciples of MicroXML"

cbullard@hiwaay.net scripsit:

> <opcheck-tswp wpno="T0104-1-1520-237" wpseq="0104 00">
> <?frame id="wp0104_000_001" title="MFD/CAUTION/ADVISORY WARNING
> SYSTEM HH-60A HH-60L [WP 0104 00]" toclevel="3" previous='#DMN'?>
> <wpidinfo> ...
> 
> while strictly legal gets no support past syntax.  IOW, the developer
> of this application is on their own as far as getting to the data
> inside the processing instructions if they adopt MicroXML.

The spec says that parsers SHOULD provide PI information to applications,
whereas element, attribute, and character content information MUST
be reported.  If you use the MicroLark push or pull parser, you get
PI events reported; if you use the tree parser, they are discarded.

I look forward to Part 2!

-- 
Barry thirteen gules and argent on a canton azure           John Cowan
fifty mullets of five points of the second,             cowan@ccil.org
six, five, six, five, six, five, six, five, and six.
        --blazoning the U.S. flag           http://www.ccil.org/~cowan


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS