OASIS Open: Committees

Interest in creating well-known holders for simple and array types

Are you interested in defining well-known value type for single and array values of the following types:
xsd:string
xsd:integer
xsd:int
xsd.long
xsd:short
xsd:decimal
xsd:float
xsd:double
xsd:boolean
xsd:byte
xsd:QName
xsd:dateTime
xsd:hexBinary
xsd:time
xsd:date

Amendment Posted on Thursday, 5 November 2009:
This is intended to be used for non-spec defined types for:
* event payloads (existing defined type: NamedStringArray)
* portlet properties (existing defined type: string)
* registration properties (existing defined type: string)

[ ]	Yes
[ ]	No
[ ]	Abstain

Opening:		Thursday, 5 November 2009 @ 04:00 pm EST
Closing:		Sunday, 22 November 2009 @ 04:00 pm EST
Group:		WSRP Interfaces SC

Ballot has closed.

Voting Details

Voting Summary

Options with highest number of votes are bold

Option	# Votes	% of Total
Yes	4	80%
No	1	20%
Abstain	0

Eligible members who have voted:	5 of 5	100%
Eligible members who have abstained:	0 of 5	0%
Eligible members who have not voted:	0 of 5	0%

Voting Details

Voter	Company	Vote	Reference Document and/or Comment
Rich Thompson	IBM	Yes	I will want to work through a concrete set of examples illustrating the use cases before we actually do the definitions. As part of that we should consider how we leverage other specs (e.g. xsi-type)
Nader Oteifa	NetUnity Software	No	Which ones must have values and which ones can be nil? What about just two primitive types? How about primitive types with a condition: an int only in the 1 - 100 range? How about me make "duration"
Kevin Frender	Oracle Corporation	Yes
Dina Steeve	Oracle Corporation	Yes
Nathan Lipke	Oracle Corporation	Yes	We have had a number of issues with portlet and registration values in WSRP 1.0 and expect likewise in 2.0 with events. This also may be useful for other consumer/producer data transfers.