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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xacml message

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


Subject: Re: [xacml] Re: [xacml-comment] Public review comments for xacml-json-http-v1.0-csprd03: 5.2.5 The StatusCode object representation


Yes of course, I had forgotten that. But then it begs the question: why a sequence?

On Oct 24, 2014 12:24 AM, "Steven Legg" <steven.legg@viewds.com> wrote:

Hi David,

On 24/10/2014 9:05 AM, David Brossard wrote:
Actually Steven, doesn't the schema allow this?

No. An absent maxOccurs is assumed to be one.

Regards,
Steven

That's the way I understand it. I just submitted the JSON profile before seeing your response. I would rather keep it as is.


<StatusCode ...>
   <StatusCode ...>
     <StatusCode ...>
       <StatusCode .../>
     </StatusCode>
   </StatusCode>
   <StatusCode ...>
     <StatusCode ...>
       <StatusCode .../>
     </StatusCode>
   </StatusCode>
</StatusCode>

On Thu, Oct 23, 2014 at 11:19 PM, Steven Legg <steven.legg@viewds.com <mailto:steven.legg@viewds.com>> wrote:


    Hi David,

    On 24/10/2014 12:27 AM, David Brossard wrote:

        Hi Glenn,

        I think you are wrong. I took the wording verbatim from the core XACML spec which says that StatusCode does contain a sequence of StatusCode.


    The core spec is badly worded also, but at least the core spec has an XML Schema
    to clarify the intent.

    Contains "an optional sequence of minor status codes" immediately suggests to me
    something like:

    <StatusCode ...>
       <StatusCode .../>
       <StatusCode .../>
       <StatusCode .../>
    </StatusCode>

    but the XML Schema tells me it is actually:

    <StatusCode ...>
       <StatusCode ...>
         <StatusCode ...>
           <StatusCode .../>
         </StatusCode>
       </StatusCode>
    </StatusCode>

    which I wouldn't naturally regard as a sequence. I think Glenn makes a fair point.
    The text description has to stand on its own in the JSON profile and I agree with
    his suggested rewording.

    Regards,
    Steven


        Am I missing the point?

        Cheers,
        David.


             5.55 Element <StatusCode>

        The <StatusCode> element contains a major status code value and an optional sequence of minor status codes.

        <xs:element name="StatusCode" type="xacml:StatusCodeType"/>

        <xs:complexType name="StatusCodeType">

             <xs:sequence>

                    <xs:element ref="xacml:StatusCode" minOccurs="0"/>

             </xs:sequence>

             <xs:attribute name="Value" type="xs:anyURI" use="required"/>

        </xs:complexType>

        The <StatusCode> element is of StatusCodeType complex type.

        The <StatusCode> element contains the following attributes and elements:

        Value [Required]

        See Section B.8 for a list of values.

        <StatusCode> [Any Number]

        Minor status code.  This status code qualifies its parent status code.


        On Thu, Jun 12, 2014 at 6:14 PM, GRIFFIN, GLENN (GLENN) <glenngriffin@research.att.com <mailto:glenngriffin@research.att.com> <mailto:glenngriffin@research.__att.com <mailto:glenngriffin@research.att.com>>> wrote:

             IMPORTANT NOTE: Please make sure that you are subscribed to the xacml-comment@lists.oasis-__open.org <mailto:xacml-comment@lists.oasis-open.org> <mailto:xacml-comment@lists.__oasis-open.org <mailto:xacml-comment@lists.oasis-open.org>> mailing list before submitting feedback with this form. For instructions on subscribing see https://www.oasis-open.org/__committees/comments/index.php?__wg_abbrev=xacml.____ <https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=xacml.____>

             Comment type [editorial | technical] ? editorial____

             Impact [major | minor] ? minor____

             The statement that ____

                          “.. the StatusCode object may contain a sequence of StatusCode objects..”____

             is confusing because a StatusCode may contain only one child StatusCode.  This may be a correct statement in an XML definition, but in general use the term “sequence” means a series, list, or array of multiple objects, so can be read as saying that the StatusCode can contain an array of StatusCodes.____

             It would be better to change this text to read____

                          “.. the StatusCode object may contain a StatusCode object..”____

             __ __




        --
        David Brossard, M.Eng, SCEA, CSTP
        VP of Customer Relations
        +46(0)760 25 85 75 <tel:%2B46%280%29760%2025%2085%2075>
        Axiomatics AB
        Skeppsbron 40
        S-111 30 Stockholm, Sweden
        Support: https://support.axiomatics.com
        Web: http://www.axiomatics.com <http://www.axiomatics.com/>
        Axiomatics for developers: http://developers.axiomatics.__com <http://developers.axiomatics.com>
        Connect with us on LinkedIn <http://www.linkedin.com/__companies/536082 <http://www.linkedin.com/companies/536082>> | Twitter <http://twitter.com/axiomatics__> | Google + <https://plus.google.com/u/1/__b/101496487994084529291/ <https://plus.google.com/u/1/b/101496487994084529291/>> | Facebook <https://www.facebook.com/__axiomatics <https://www.facebook.com/axiomatics>> | YouTube <http://www.youtube.com/user/__axiomaticsab <http://www.youtube.com/user/axiomaticsab>>





--
David Brossard, M.Eng, SCEA, CSTP
VP of Customer Relations
+46(0)760 25 85 75
Axiomatics AB
Skeppsbron 40
S-111 30 Stockholm, Sweden
Support: https://support.axiomatics.com
Web: http://www.axiomatics.com <http://www.axiomatics.com/>
Axiomatics for developers: http://developers.axiomatics.com
Connect with us on LinkedIn <http://www.linkedin.com/companies/536082> | Twitter <http://twitter.com/axiomatics> | Google + <https://plus.google.com/u/1/b/101496487994084529291/> | Facebook <https://www.facebook.com/axiomatics> | YouTube <http://www.youtube.com/user/axiomaticsab>



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