RE: Proposed Changes to Core-12 (with renaming)

["Orchard, David" <dorchard@jamcracker.com>]

Title: RE: Proposed Changes to Core-12 (with renaming)

Bob,

Welcome to the same problems that XML Namespaces has in XML.  Is there a default namespace, a null namespace (namespace present but no value), or a non-namespace (namespace not present) when a namespace is not present?  I'm not even sure that I know the answer to my question on XML Namespaces, let alone have an opinion for SAML.

Dave

> -----Original Message-----
> From: George Robert Blakley III [mailto:blakley@us.tivoli.com]
> Sent: Tuesday, August 14, 2001 11:53 AM
> To: Mishra, Prateek
> Cc: McLaren, Christopher; 'pbaker@verisign.com'; Orchard, David;
> 'security-services@lists.oasis-open.org'
> Subject: Re: Proposed Changes to Core-12 (with renaming)
>
>
> Prateek,
>
> In the AttributeNameType structure, AttributeNamespace has minimum
> cardinality zero; does this mean that
> the AttributeName is drawn from a canonical default namespace
> (if so, do we
> specify what this namespace is)?
> Or does it permit ambiguity of reference.  If the latter, I'm
> nervous....
>
> Here's the structure I'm referring to:
>
> <complexType name="AttributeNameType">
>     <element ref="AttributeName">
>     <element ref="AttributeNamespace" minOccurs="0">
> </complexType>
>
>
> --bob
>
> Bob Blakley (email: blakley@us.tivoli.com   phone: +1 512 436 1564)
> Chief Scientist, Security, Tivoli Systems, Inc.
>
>
> "Mishra, Prateek" <pmishra@netegrity.com> on 08/14/2001 12:39:14 PM
>
> Please respond to "Mishra, Prateek" <pmishra@netegrity.com>
>
> To:   "McLaren, Christopher" <cmclaren@netegrity.com>,
>       "'pbaker@verisign.com'" <pbaker@verisign.com>,
>       "'dorchard@jamcracker.com'" <dorchard@jamcracker.com>,
>       "'security-services@lists.oasis-open.org'"
>       <security-services@lists.oasis-open.org>
> cc:
> Subject:  Proposed Changes to Core-12 (with renaming)
>
>
>
> This is from the August 14, Focus Group Call
>
> (1) Removal of <Object> element from (renamed)
> draft-sstc-schema-assertion-12 and
> replacement by its (literal) contents within
> <AuthorizationDecisionAssertionType> and
> <AuthorizationQueryType>.
>
> (2) Cardinality of element <AttributeValue> within
> <AttributeType> to be
> changed
> to minOccurs=1, maxOccurs=unbounded
>
> (3)  Removal of <Attribute> element from <AttributeQueryType> and its
> replacement
> by a new element <AttributeName> with cardinality minOccurs=0,
> maxOccurs=unbounded.
>
> <element name="saml:AttributeName" type="AttributeNameType">
> <complexType name="AttributeNameType">
>     <element ref="AttributeName">
>     <element ref="AttributeNamespace" minOccurs="0">
> </complexType>
>
>
> there is a need to promote to global level the following elements
>
> <element name="AttributeName" type="string">
> <element name="AttributeNamespace" type="uriReference">
>
> and update AttributeType to:
>
> <complexType name="AttributeType">
> <sequence>
> <element ref="AttributeName">
> <element ref="AttributeNamespace">
> <element name="AttributeValue" type="saml:AttributeValueType"
> maxOccurs="unbounded"/>
>
>
>
>
>
>
>
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to:
> security-services-request@lists.oasis-open.org
>
>
>