[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Text on multi-valued attributes in draft-4
As I mentioned in yesterday's email, I've been attempting to review the use of Attribute in the current specification with a fine-tooth comb - hence some of my questions from yesterday. After the call this morning, I thought it would be beneficial to post some comments on current text changes (with line numbers from oasis-xacml-2_0-core-spec-wd-04.pdf) that I've accumulated. For clarity on lines 2021-2024, I'd suggest placing meta-data first as well as inserting 'one or more': "The <Attribute> element is the central abstraction of the request context. It contains attribute meta-data and one or more attribute values..." 2196-2201: Why is there no sequence of xacml-context:Attribute elements that are defined as elements in StatusDetailType? Also, if any AttributeValues are listed, is that listing considered complete or simply a subset the PDP chooses to return Line 2443: AttributeValue is not a URI, but the way the section on extensibility reads, it seems as though it should be. Finally, I didn't see text that outlines that <Attribute attributeid="XX" datatype="YY"> <AttributeValue>1</AttributeValue> <AttributeValue>2</AttributeValue> </Attribute> is a syntactic shortcut for representing: <Attribute attributeid="XX" datatype="YY"> <AttributeValue>1</AttributeValue> </Attribute> <Attribute attributeid="XX" datatype="YY"> <AttributeValue>2</AttributeValue> </Attribute> with
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]