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: [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"?>
		AttributeName="foo" AttributeNamespace="http://osu.edu">
	<AttributeValue xsi:type="xsd:string">bar</AttributeValue>

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

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

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

Powered by eList eXpress LLC