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


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[xml-dev] PSVI in the instance

I see the idea of an instance document "decorated" with the PSVI 
contributions in an xml 1.0 readable way as having the most traction here.

I propose the following requirements for such a beast:

1. All exposed PSVI items should be accessible to an application through 
typical "XML 1.0 + namespaces" APIs and techniques.

2. As far as possible, it should be Schema-Language agnostic, to promote 
interoperability between XML schema, DTDs, Relax, etc.

3. Every single PSVI item does not need to be exposed this way, only the 
most useful or important ones ( hit the 80/20 point).

4. The structure of the instance document should not be excessively altered 
by the "decorating" it with these PSVI items. Ideally, All elements and 
attributes in the document would be unchanged, with new infoset 
contributions added only in the form of "global attributes" (as suggested by 
ERH ).

If these simple requirements are agreeable, the next step is to gain 
consensus on:

   Which PSVI information should be exposed in this manner

and then on

   How should these infoset decorations be represented in the instance 

This is mostly orthogonal to the (very useful) idea of a "normalized schema" 
- the only entanglement is if we wish to have xlinks from an instance 
document into the normalized schema.

-Wayne Steele

>From: Eric van der Vlist <vdv@dyomedea.com>
>For the first time, I "see" a concrete PSVI. I find this very helpful to
>understand it and I hope you will develop your idea of including the
>PSVI contributions for ID/IDREF/IDREFS and unique/key/keyref as well
>which might give an answer to another thread raised on the xsl-list.
>Now, if the objective is to have a lightweight language which minimizes
>the changes on the source document and tries to be as independent as
>possible from the schema language, it might be used as a starting point
>of a XSLT transformation as you mentioned but isn't a good candidate as
>a "final" step!

Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp