W3C home > Mailing lists > Public > xmlschema-dev@w3.org > June 2003

Re: XML result set schema validation

From: Tony Opatha <tonyopatha@yahoo.com>
Date: Wed, 18 Jun 2003 04:08:43 -0700 (PDT)
Message-ID: <20030618110843.99110.qmail@web20507.mail.yahoo.com>
To: "Henry S. Thompson" <ht@cogsci.ed.ac.uk>
Cc: xmlschema-dev@w3.org
If a document instance has some XML fragments included or excluded
depending on the level of detail than how can the XSD schema be used to
validate that instance? Using xsd:nil seems to indicate that the element
is not present rather than the fact that multiple types of elements may
be present or not present. 
I think semantically this should be possible to validate keeping in mind
the required level of detail of the result set. should eacl level of detail
result set have its own XSD? That would defeat the purpose of trying
to model the result of the query as the same type of information?
Get me my bank account transaction information such that I see all 
checks cleared in past one month.

Get me my account transaction information such that I see all ATM
transactions as well as check cleared in past one month.
Get me my account information such that I see all transactions for
last one year.
All of these are semantically a result set of XML schema based query.
However, each query result ends up including different types of
account information.
How would we ensure that each result set corresponds to same
XSD schema and that each result set can be validated keeping
in mind the specific level of detail for that result set. E.g., if we have
maximum level of detail we do want to do schema validation for all
the required elements expected. For a lower level of detail we do
not want to impose schema validation of a higher level of detail.
Any ideas?
Tony Opatha.

"Henry S. Thompson" <ht@cogsci.ed.ac.uk> wrote:

Tony Opatha writes:

> I need to design the XML schema for a document that may need
> to be initialized with a XML fragment that may vary with
> different levels of details.

If I've understood you correctly, your best bet is xsi:nil -- this
allows you to validate an empty element even though the schema
requires it to have content.

Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
Half-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]

Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
Received on Wednesday, 18 June 2003 07:08:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:15:11 UTC