[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [xacml] QName questions
But then what do we do about DataType values such as xsi:string that are already defined as QNames? Anne On 25 October, Simon Godik writes: Re: [xacml] QName questions > From: Simon Godik <simon@godik.com> > To: xacml@lists.oasis-open.org > Subject: Re: [xacml] QName questions > Date: Fri, 25 Oct 2002 14:40:20 -0700 > > > 1. If an xml attribute is defined as Type="xs:QName", then do XML > > parsers like SAX and DOM do the resolution of those names? > > By looking at the sax api it does not seem that anything is done with > attribute values of qname type. > My guess is that an application is responsible for expanding qname. Problem > is that expanded name > is a pair: (URI, local_name) and there is no standard that says how this 2 > elements should be combined to > form one value. Some suggest URI+local_name, others URIlocal_name, and so > on. > > My preference would be not to use qnames for attribute values at all, and > use URI's instead. > > Simon > > ----- Original Message ----- > From: "Anne Anderson" <Anne.Anderson@Sun.com> > To: "XACML TC" <xacml@lists.oasis-open.org> > Sent: Friday, October 25, 2002 8:47 AM > Subject: [xacml] QName questions > > > > 1. If an xml attribute is defined as Type="xs:QName", then do XML > > parsers like SAX and DOM do the resolution of those names? > > > > Example: Assume AttributeDesignatorType is defined as follows: > > <xs:complexType name="AttributeDesignatorType"> > > <xs:attribute name="AttributeId" type="xs:QName" use="required"/> > > <xs:attribute name="DataType" type="xs:anyURI" use="required"/> > > <xs:attribute name="Issuer" type="xs:anyURI" use="optional"/> > > </xs:complexType> > > > > Then, if my Policy says > > <Policy xmlns="urn:oasis:names:tc:xacml:1.0:policy" > > xmlns:sun-attrs="urn:sun:names:attribute-ids" > > ... > > <SubjectAttributeDesignator AttributeId="sun-attrs:attr1" > > .../> > > > > And a Request says > > <Request xmlns="urn:oasis:names:tc:xacml:1.0:context" > > xmlns:sun-stuff="urn:sun:names:attribute-ids" > > ... > > <Subject> > > <Attribute AttributeId="sun-stuff:attr1"> > > ... > > > > Will the tools themselves resolve these, or do I have to > > expand the names and then perform a string match myself? > > > > 2. Does anyone have a reference from W3C on whether QNames MAY be > > used as "aliases" for any URI or whether they are ONLY for use > > in referring to URI's that represent schemas? > > > > I.e. are the uses of QNames for use in identifiers as in #1 > > and in our current schemas even allowed (or recommended)? > > > > 3. Is there a way to define aliases for shortcut names other than > > QNames? I.e. can I define an alias to be equal to some > > initial prefix of a long URI, and then have that expanded by > > XML parsing tools? > > > > Anne > > -- > > Anne H. Anderson Email: Anne.Anderson@Sun.COM > > Sun Microsystems Laboratories > > 1 Network Drive,UBUR02-311 Tel: 781/442-0928 > > Burlington, MA 01803-0902 USA Fax: 781/442-1692 > > > > > > ---------------------------------------------------------------- > > To subscribe or unsubscribe from this elist use the subscription > > manager: <http://lists.oasis-open.org/ob/adm.pl> > > > > > > > > > ---------------------------------------------------------------- > To subscribe or unsubscribe from this elist use the subscription > manager: <http://lists.oasis-open.org/ob/adm.pl> > -- Anne H. Anderson Email: Anne.Anderson@Sun.COM Sun Microsystems Laboratories 1 Network Drive,UBUR02-311 Tel: 781/442-0928 Burlington, MA 01803-0902 USA Fax: 781/442-1692
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC