- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 17 Apr 2009 15:47:49 +0000
- To: www-xml-schema-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3264
David Ezell <David_E3@VERIFONE.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |David_E3@VERIFONE.com
Keywords|needsReview |decided
--- Comment #15 from David Ezell <David_E3@VERIFONE.com> 2009-04-17 15:47:48 ---
Decided:
- 3264 (XML Query and XSL WGs): xs:anyURI definition.
http://www.w3.org/XML/Group/2004/06/xmlschema-2/datatypes.b3264.html
Summary: the value space of anyURI needs to be specified.
Note: some discussion in Bugzilla, some amendments proposed. One
possible point of controversy: are base64Binary and hexBinary
intended to encode sequences of bits or of octets?
MSM's recommendations: fairly quick.
- Amend as described in comment 7: in hexBinary and
base64Binary, change
... the set of possibly empty finite-length sequences of
binary octets
to
... the set of finite-length sequences of zero or more
binary octets
- Amend as described in comment 9: in the new 3.3.18.1, read
The ·value space· of anyURI is the set of finite-length
sequences of zero or more characters (as defined in
[XML]) that ·match· the Char production from [XML].
- Amend as suggested in comment 5, in the light of comment 9:
in 3.3.18.2 (anyURI lexical mapping) for
The ·lexical space· of anyURI is the set of possibly
empty finite-length character sequences.
read
The ·lexical space· of anyURI is the set of finite-length
sequences of zero or more characters (as defined in
[XML]) that ·match· the Char production from [XML].
- And for the record, optionally reaffirm in the minutes that
base64Binary encodes octet sequences, not (by itself) bit
sequences.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 17 April 2009 15:48:01 UTC