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] | [List Home]


Subject: Suggested agenda item for focus call


At least one SAML user asked for some clarification and additional
capability in handling empty-valued vs. null vs. zero-valued Attributes.

Currently we explicitly indicate that an absence of <AttributeValue>
elements can be used to asserto an attribute with no values.

It's not clear whether it's acceptable to assert a value of "empty string"
because of the language up front about not permitting empty strings in
content. I don't think we intended that restriction to apply to attribute
values, but it's worth clarifying.

Finally, I note that while XML permits an element to be explicitly "nil"
using the xsi:nil attribute, this isn't permitted by our schema. If we
wanted to permit "nil" values to appear, we would need to add
nillable="true" to the schema for the AttributeValue element. By default,
anyType is not nillable.

-- Scott



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