ISSUE-37
more than one way to express null, empty or missing content
- State:
- CLOSED
- Product:
- Basic
- Raised by:
- Paul Downey
- Opened on:
- 2006-04-25
- Description:
This issue stems from the resolution of ISSUE-7, and ACTION-29. We provide several methods for expressing missing, null or empty content: - minOccurs="0" - nillable="true" - an empty string - possibly a null type pattern (dependent upon ISSUE-15) - others? what advice (design considerations) should we offer to select between these patterns. Does each pattern have different semantics?
- Related emails:
- ISSUE-37: more than one way to express null, empty or missing content (from dean+cgi@w3.org on 2006-04-25)
- Minutes: XML Schema Patterns for Databinding F2F 31st July - 1st August 2006 (from paul.downey@bt.com on 2006-08-01)
- Minutes: XML Schema Patterns for Databinding F2F 5th-6th October 2006 (from paul.downey@bt.com on 2006-10-07)
- ACTION-80: review ISSUES list against the edtodo list (from paul.downey@bt.com on 2006-10-12)
Related notes:
2006-08-01: closed with no action