- From: Ashok Malhotra <ashokma@microsoft.com>
- Date: Thu, 10 May 2001 09:49:40 -0700
- To: "Ed Shaya" <eshaya@katherine.physics.umd.edu>, <www-xml-schema-comments@w3.org>
Ed: You raise an interesting point. The XML Schema list datatype is space separated. I believe you are asking for a list datatype where the tokens are separated not by spaces but by number of characters. I don't see this as a bug but rather a requirement for a different type of list. All the best, Ashok =========================================================== Ashok Malhotra <mailto: ashokma@microsoft.com> Microsoft Corporation 212 Hessian Hills Road Croton-On-Hudson, NY 10520 USA Redmond: 425-703-9462 New York: 914-271-6477 -----Original Message----- From: Ed Shaya [mailto:eshaya@katherine.physics.umd.edu] Sent: Thursday, May 10, 2001 8:38 AM To: www-xml-schema-comments@w3.org Subject: Ambiguity in Lists Sirs: I wish to point out that the Schema Part 2 description of lists datatypes does not specify what happens in the circumstance that the atomic components are strings of a specified length (via a restriction of length="8", say) and some of these have spaces within them. Are parsers required to return these atomic components intact within a list? Do validators count them as a single atom? If so, it will requires extra complexity in the parser/validator to first locate PROPER S boundaries between proper atomic units before counting atomic units or parsing them. If not, then one looses an important functionality of lists. Ed Shaya Chief Scientist Astronomical Data Center/NASA
Received on Thursday, 10 May 2001 13:06:17 UTC