proposed resolution to issue 290

[Ron Monzillo <Ronald.Monzillo@Sun.COM>]

This message contains the proposed addition to the core errata
to allow for more flexible representation of encoding type.

-------- Original Message --------
Subject: 	Re: [wss] proposed resolution to issue 290
Date: 	Fri, 02 Jul 2004 19:20:04 -0400
From: 	Ron Monzillo <Ronald.Monzillo@Sun.COM>
To: 	Michael McIntosh <mikemci@us.ibm.com>
CC: 	wss@lists.oasis-open.org
References: 
<OF340C115A.E27ADBA8-ON85256EC5.007C21F6-85256EC5.007C9DDB@us.ibm.com>



Michael McIntosh wrote:

>
>
>Ron,
>
>Sorry I missed this the first time. I would prefer either a) retaining the
>current default (Base64Binary) or b) eliminating the default for
>EncodingType.
>Having the default value for one attribute of an element change based on
>the value of another attribute of that element seems to prevent the use of
>XML Schema to provide the default.
>
The "default" is currently not  represented in the schema, so we are
certainly not using the schema to enforce the default. 

Of your suggestions I prefer choice b. Can we do the following?

change it to read:

757: /wsse:SecurityTokenReference/wsse:KeyIdentifier/@EncodingType
758: The optional EncodingType attribute is used to indicate, using a
URI, the encoding
759: format of the KeyIdentifier value. This specification defines the
EncodingType URI values appearing in the following table. A token
specific profile MAY define additional token specific EncodingType URI values.
A KeyIdentifier MUST include an EncodingType attribute when its ValueType
is not sufficient to identify its encoding type.

also remove "(default) "from the description of Base64Binary in the table
beginning at line 761.

also remove "(the default)" from the end of the sentence at line 1834.

Ron




To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wss/members/leave_workgroup.php.