OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

saml-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: RE: [saml-dev] Attribute Statement example

Thanks a lot for clarifying Ryan.


>Date: Fri, 10 May 2002 13:14:55 -0400
>From: Ryan Eberhard <ryan.eberhard@entegrity.com>
>Subject: RE: [saml-dev] Attribute Statement example
>To: "'Bhavna Bhatnagar'" <bhavna.bhatnagar@sun.com>, 
>MIME-version: 1.0
>Hop-count: 1
>X-MAILWATCH-INSTANCEID: 01020003d9744ee4-aad2-434c-a86c-d0caffcc25e5
>List-Owner: <mailto:saml-dev-help@lists.oasis-open.org>
>List-Post: <mailto:saml-dev@lists.oasis-open.org>
>List-Subscribe: <http://lists.oasis-open.org/ob/adm.pl>, 
>List-Unsubscribe: <http://lists.oasis-open.org/ob/adm.pl>, 
>List-Archive: <http://lists.oasis-open.org/archives/saml-dev/>
>List-Help: <http://lists.oasis-open.org/elists/admin.shtml>, 
>List-Id: <saml-dev.lists.oasis-open.org>
>X-OriginalArrivalTime: 10 May 2002 17:18:47.0987 (UTC) 
>I was originally responsible for that piece of verbiage... sorry for any
>What I meant was that because AttributeValue is an anyType, it seemed
>sensible to put some limits on what would be included in this element, but I
>wanted to suggest the least restrictive limit.  Therefore, the schema type
>of AttributeValue should be specified with an xsi:type attribute (rather
>than a substitution group), the type should extend "string", and it should
>remain a simple type.  In practice, this means that the AttributeValue
>schema could only be extended to include custom attributes.
>For example:
><AttributeValue xsi:type="string">Administrator</AttributeValue>
><AttributeValue xsi:type="vendor:MyAttributeValue" vendor:attr1="a"
>	Administrator
>-----Original Message-----
>From: Bhavna Bhatnagar [mailto:bhavna.bhatnagar@sun.com]
>Sent: Friday, May 10, 2002 12:18 PM
>To: saml-dev@lists.oasis-open.org
>Subject: [saml-dev] Attribute Statement example
>Hi Prateek/Anyone,
>I was revisiting Prateek's original proposal regarding the artifact profile
>testing and was wondering if you could give me an example of how an
>Statement might look like.
>I was having difficulty understanding these lines from the doc.:
>We suggest that AttributeValues be defined by a schema that has
>and derives from string (or is string), i.e. extra attributes only, and that
>xsi:type mechanism be used. This way, portal sites can be guaranteed of
>a string pair for AttributeName and AttributeValue.
>Thanks much.
>Bhavna Bhatnagar                		Sun Microsystems Inc.
>Identity Management group	 __o
>Tel: 408-276-3591              _`\<,_	
>                              (*)/ (*)
> ________________________________________________________________________ 
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.oasis-open.org/ob/adm.pl>

Bhavna Bhatnagar                		Sun Microsystems Inc.		 
Identity Management group	 __o
Tel: 408-276-3591              _`\<,_	
                              (*)/ (*)

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC