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

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: [xml-dev] Re: Can XLink be fixed?

[ Lists Home | Date Index | Thread Index ]

Joe English writes:
> AFAICT, it's not so much the idea of an augmented infoset
> that people find disagreeable about the PSVI, it's the
> nature (and quantity!) of the data that a W3C XML Schema
> validator adds to the Infoset.

Yes.

> Come to think of it, if the Infoset augmentation is expressed
> as a set of attributes with a distinguished namespace name,
> instead of as a new set of [information item]s, then
> the current XLink draft could work unchanged.  You just
> need to explicitly state that the xlink:* attributes need
> not be present in the source document, and may instead
> be added by some (unspecified) preprocessing transformation.

I'm starting to think in terms of transformations - some
decorative/additive (CSS, maybe LSI), and others more drastic and/or
intrusive (PSVI value spaces, SLAIX possibilities, lots of XSLT
transforms).

For general-purpose information description, decorative transformations
seem like a safer bet.  CSS and LSI also have the bonus of applying to
elements (even though they may use attributes or elements), which makes
for an easier decoration.

I think we've still got a lot of figuring to do here.

-- 
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com




 

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

Copyright 2001 XML.org. This site is hosted by OASIS