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


Help: OASIS Mailing Lists Help | MarkMail Help

security-services message

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

Subject: RE: [security-services] Validation of simple attribute value fails?

Since my discussion with Scott I've been trying to look into the point
he raises--that instead of having AttributeValue typed as an any we type
it as a sequence of elements, each of which is an any, and thus we can't
do single values.

My research has turned up little either way, but I think what he says
makes sense. Anyone who knows more about XML Schema (Eve, I'm looking at
you!) speak up.

My inclination would be to remove the AttributeValue type and set the
type of AttributeValue directly to the anyType. This would removes
nothing functionally from the AttributeValue and allows us to do the
sort of direct xsi:type-ing that I mention in my earlier posts.


> -----Original Message-----
> From: Scott Cantor [mailto:cantor.2@osu.edu] 
> Sent: Tuesday, December 18, 2001 4:54 PM
> To: security-services@lists.oasis-open.org
> Subject: [security-services] Validation of simple attribute 
> value fails?
> I had a brief exchange with Chris McLaren on this, but I 
> think I need to open it up wider.
> I don't think the current core schema will validate a simple 
> AttributeValue of string type such as:
> <?xml version="1.0" encoding="UTF-8"?>
> 	<Attribute 
> xmlns="http://www.oasis-open.org/committees/security/docs/draf
> t-sstc-sch
> ema-assertion-21.xsd"
> 		xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>  		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://www.oasis-open.org/committees/secur
> ity/docs/d
> raft-sstc-schema-assertion-21.xsd draft-sstc-schema-assertion-21.xsd"
> 		AttributeName="foo" AttributeNamespace="http://osu.edu">
> 	<AttributeValue xsi:type="xsd:string">bar</AttributeValue>
> </Attribute>
> I'm pretty sure that's supposed to be valid, but the schema 
> doesn't allow AttributeValue to be of type anyType, it 
> specifies a complexType of saml:AttributeValueType and then 
> defines that as an element sequence.
> Chris' recent examples on usage, which I think everybody was 
> happy with, assumed that xsd:string was a legal xsi:type 
> value, but it's not in this case. I validated (or rather 
> didn't) using XMLSpy 4 and using the XSV tool.
> Based on my understanding, leaving AttributeValue entirely 
> untyped in the schema (or explicitly saying anyType) is the 
> intended goal here.
> Chris, am I still wrong, and if so, why doesn't that validate?
> -- Scott
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>

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

Powered by eList eXpress LLC