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

Re: XPath for Infoset extensions [was Annotations in


Re:  XPath for Infoset extensions [was Annotations in
Hi John,

> There's a confusion of levels lurking here. An infoset may be
> represented in two different ways: as the native XML from which it
> was derived, or with some other representation particular to
> infosets. This latter may or may not be an application of XML.

Thank you for articulating it like that! This is what I've been trying
to say about LMNL -- you can represent a LMNL data model / infoset in
a "native" form, as LMNL syntax, or with some other representation
peculiar to the LMNL data model. The latter may or may not be an
application of LMNL. We have, though, defined a standard "reified LMNL
layer", which is an application of LMNL that represents a LMNL data
model (and a few other things that are useful in LMNL syntax).

> The first representation has the advantage that it is simple and
> clear; it has the disadvantage that it cannot in general represent
> infosets that contain non-standard item types or properties. The
> second representation is generally quite opaque, but has the
> advantage that it can easily be extended to represent enhanced
> infosets.
>
> SLAIX is a general-purpose representation of infosets that has the
> advantages of uniformity, extreme extensibility, and being an
> application of XML. Its disadvantages are that it is verbose,
> grotesque, and unreadable. See
> http://lists.xml.org/archives/xml-dev/200208/msg00875.html

Having a short, elegant and readable representation for moving around
augmented Infosets was one my primary reasons for pursuing LMNL.

In LMNL syntax, the Infoset represented by the XML document:

  <book>
    <author sort="brownjohn">John Brown</author>
    <title>My Life</title>
  </book>

would look like:

  [book}
    [author [sort}brownjohn{]}John Brown{author]
    [title}My Life{title]
  {book]

If you wanted to augument this infoset, for example to say that the
xsi:type of the [sort] annotation was xs:token, you could do that by
adding an annotation to the [sort] annotation:

  [!ns xsi="http://www.w3.org/2001/XMLSchema-instance"]
  [book}
    [author [sort [xsi:type}xs:token{]}brownjohn{]}John Brown{author]
    [title}My Life{title]
  {book]

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/


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.