[
Lists Home |
Date Index |
Thread Index
]
Dare, agreed with what you say about Schema Infoset, actually I also said
that it is pretty much useless w.r.to what we were discussing.
I have some questions regarding PSVI:
a) specific question: In section 3.3.5 -- there is a statement which says
something like "The first (item isomorphic) alternative above is provided
for applications such as query processors"... hmm.. actually what is meant
by the first alternative -- is it going against the "intuitive"
determinism which one might expect???
Anyways, my actual question is this --
Is there any application for the type definition associated with an
element information item in the PSVI?? My concern is again querying. Now
if we assume that every query always tries to start from the root and
select a set of nodes based on a path expression, then what we need is
type inferencing. The type associated with an element information item in
PSVI seems useless here..
Also, consider element declaration -- that might be needed for checking
integrity constraints like how XML Schema defines them. The following may
be slightly vague -- there are two other ways of specifying integrity
constraints -- using path expressions, or using type names. If path
expressions are used, then we do not need element declarations, or type
names for element information items. If we use type names, then we need
type names for element information items, but I do not think we need to
know the element declaration for an element information item.
Anyways, my question is -- where will the type names and element
declarations associated with an element information item in PSVI be used?
cheers and regards - murali.
On Tue, 28 May 2002, Dare Obasanjo wrote:
> Appendix C2 of the W3C XML Schema recommendation describes the
> contributions to the Post-Schema-Validation Infoset (PSVI). Which are
> basicaly additions to an XML document's infoset made after it has been
> validated.
>
> http://www.w3.org/TR/xmlschema-1/#outcomes
>
> IBM's proposal describes requirements for an API for manipulating W3C
> XML Schema components which is not related.
>
> PS: To properly describe the PSVI for your document, I'd need an
> actually schema with targetNamespaces, defaults, schema locations and
> the whole hog.
>
> --
> PITHY WORDS OF WISDOM
> If two wrongs don't make a right, try three.
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> For example, let us consider a simple schema to see how PSVI works.
>
> Book -> book (Title)
> Title -> title (String)
>
> and the document
>
> <book><title>Intro to XML</title></book>
>
> what is the PSVI for the above document?
>
> thanks and regards - murali.
|
