[security-services] ISSUE: Actions and Action elements

In my omnibus message
http://lists.oasis-open.org/archives/security-services/200202/msg00129.html,
I pointed out that the Actions and Action elements do their
namespace-qualifying differently than our other qualified elements. I
proposed removing Actions and changing Action to mirror the structure of
NameIdentifier. Note that when this schema was discussed at one of the F2F
meetings, it was argued that it would be relatively common for
AuthorizationDecisionQuerys to ask about more than one action from the same
namespace at the same time, and thus the existing schema would be more
concise. My feeling is that this isn't enough to justify a different style
of namespace/name structure.


Here's the proposal from my previous message, updated with Core-27 line and
section numbers:


Line 806: replace <element ref="saml:Actions"/> with <element
ref="saml:Action" maxOccurs="unbounded"/>

Line 817-819: Section 2.4.4.1, element <Action> (remove <Actions>)
The <Action> element specifies an action on the specified resource, for
which an authorization decision is sought. It has the following structure:

(Keep lines 820-824)

Lines 825-836:
string [required]: The action for which authorization is sought.

The following schema fragment defines the <Action> element and its Namespace
attribute:

<element name="Action" type="saml:ActionType"/>
<complexType name="ActionType">
  <simpleContent>
    <extension base="string">
      <attribute name="Namespace" type="anyURI"/>
    </extension>
  </simpleContent>
</complexType>



 - irving -
 


-----------------------------------------------------------------------------------------------------------------
The information contained in this message is confidential and is intended 
for the addressee(s) only.  If you have received this message in error or 
there are any problems please notify the originator immediately.  The 
unauthorized use, disclosure, copying or alteration of this message is 
strictly forbidden. Baltimore Technologies plc will not be liable for direct, 
special, indirect or consequential damages arising from alteration of the 
contents of this message by a third party or as a result of any virus being 
passed on.

 
This footnote confirms that this email message has been swept by 
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.