W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2012

[Bug 17183] [FO30] Constructors for list and union types

From: <bugzilla@jessica.w3.org>
Date: Wed, 13 Jun 2012 11:21:10 +0000
To: public-qt-comments@w3.org
Message-Id: <E1SeldO-0005vK-4m@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17183

--- Comment #1 from Michael Kay <mike@saxonica.com> 2012-06-13 11:21:09 UTC ---
The WG meeting on 2012-06-12 agreed with the general direction here, subject to
approval of detailed text. The WG decided not to attempt to specify a detailed
return type for constructor functions for union and list types, specifying it
instead as xs:anyAtomicType*.

The following changes have been applied, subject to final approval.

17.1 Mention xs:dateTimeStamp explicitly rather than referring vaguely to new
XSD 1.1 types.

New section 17.2 defining constructor functions for xs:NMTOKENS, xs:IDREFS, and
xs:ENTITIES. The return type of these is given as xs:NMTOKEN*, xs:IDREF*, and
xs:ENTITY* respectively. The argument type is xs:string? (the function returns
an empty sequence only if the input is an empty sequence; conversion of a
zero-length string fails because these types all specify minLength="1".

For user-defined simple types of variety list and union, the argument type is
xs:string? and the return type is xs:anyAtomicType*.

In the section on QName and Notation, a paragraph has been added explaining the
impact on function literals, partial function application, and function-lookup.

A revised draft containing these changes will be posted.

-- 
Configure bugmail: https://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 Wednesday, 13 June 2012 11:21:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:39 UTC