ISSUE-13

Using PSVI Features in Schemas

State:
CLOSED
Product:
Advanced
Raised by:
Paul Downey
Opened on:
2006-01-24
Description:
"""
* Proposal:       

Explicitly identify these features and specify usage
Advise developers to not assume callers have rich PSVI
implemented.

Most toolkits contain schema validation tools that by now have excellent
compliance with the XML Schema specification.  XML Schema validation
tools take an Infoset and XML schema set as input and emits a
post-schema-validated-Infoset (PSVI).  The problem is that type
generators and/or serializers do not actually use proper schema
validation mechanisms.  Instead, type generators/serializers emulate
selected XML Schema features - like xs:default - meant to be managed by
the validation process.

There are several issues I think this working group should consider:
First, is it even wise for a service description to contain use PSVI
features in response messages?  In the case of xs:default, it seems
impolite to return elements with empty content to expect the caller to
fulfill the default value requirements.  Second, are there other XML
Schema features that are meant to impact the PSVI?  Perhaps this working
group should list such features and describe how type
serializers/generators should emulate the intent of the Schema spec.
Finally, should the working group tell developers to avoid Schema
features that presume the caller has a schema validation capability?

Erik Johnson

Epicor Software Corp.
"""

http://lists.w3.org/Archives/Public/public-xsd-databinding/2006Jan/0033.html
Related emails:
  1. ISSUE-13: Using PSVI Features in Schemas (from dean+cgi@w3.org on 2006-01-24)
  2. Agenda: XML Schema Patterns for Databinding Telcon 31 January 2006 (from paul.downey@bt.com on 2006-01-30)
  3. Agenda: XML Schema Patterns for Databinding Telcon 7 February 2006 (from paul.downey@bt.com on 2006-02-06)
  4. Minutes from XML Schema Patterns for Databinding call 7 February 2006 (from paul.downey@bt.com on 2006-02-08)
  5. Minutes from XML Schema Patterns for Databinding call 21 February 2006 (from paul.downey@bt.com on 2006-02-22)
  6. Agenda: XML Schema Patterns for Databinding F2F 27-28 February 2006 (from paul.downey@bt.com on 2006-02-22)
  7. Revised Agenda: XML Schema Patterns for Databinding F2F 27-28 February 2006 (from paul.downey@bt.com on 2006-02-27)
  8. Minutes from XML Schema Patterns for Databinding F2F 27-28 Feb 2006 (from paul.downey@bt.com on 2006-03-12)
  9. ISSUE-38: xs:any processContents value of \\'skip\\' (from dean+cgi@w3.org on 2006-04-25)
  10. Re: ISSUE-38: xs:any processContents value of \\'skip\\' (from Paul.V.Biron@kp.org on 2006-04-26)
  11. Re: ISSUE-38: xs:any processContents value of \\'skip\\' (from petexmldev@tech-know-ware.com on 2006-04-26)
  12. RE: ISSUE-38: xs:any processContents value of \\'skip\\' (from paul.downey@bt.com on 2006-04-28)
  13. ISSUE-46: fixed value attributes (from dean+cgi@w3.org on 2006-05-05)
  14. Minutes from XML Schema Patterns for Databinding F2F 22-23 May 2006 (from paul.downey@bt.com on 2006-06-02)
  15. Minutes: XML Schema Patterns for Databinding F2F 31st July - 1st August 2006 (from paul.downey@bt.com on 2006-08-01)

Related notes:

2006-08-01: we have issue related to xs:default already. No Pattern associated with this issue.

2006-10-11: closed with no action