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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

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


Subject: XRDS text


Per my action item from the last telecon, following is proposed text for the XRDS section of the XRD 1.0 spec. Will, please edit this to follow the style/formatting conventions you have set for the rest of the spec.

 

Thanks,

 

=Drummond

 

*************************

XRDS (XRD Sequence)

 

In cases where an application requires a sequence of XRDs in a single XML document, this specification defines an alternate top-level element, XRDS. Its semantics are very simple: it contains a sequence of XRD elements, one optional attribute (ref, of type anyURI), and is not otherwise extensible. The ref attribute, if present, contains a URI identifying the resource described by the sequence of XRDs.

 

IMPORTANT: In past practice, XRDS was often used as the root element even if contained only a single XRD. That practice is now deprecated. The XRDS element SHOULD NOT be used unless it contains a sequence of two or more XRDs.

 

Following is the XSD schema

 

            [insert XSD schema for XRDS element here – see below for notes]

 

***************************

 

NOTES TO SCOTT ON THE XSD FOR THE XRDS ELEMENT

 

Following is the XSD for XRDS in the XRI Resolution 2.0 spec (http://docs.oasis-open.org/xri/2.0/specs/xri-resolution-V2.0.html). However this was for a fully-extensible XRDS element, which we decided two weeks ago was not necessary. Therefore we should replace it with very simple, non-extensible XRDS schema.

 

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xrds="xri://$xrds" targetNamespace="xri://$xrds" elementFormDefault="qualified">

   <!-- Utility patterns -->

   <xs:attributeGroup name="otherattribute">

       <xs:anyAttribute namespace="##other" processContents="lax"/>

   </xs:attributeGroup>

   <xs:group name="otherelement">

       <xs:choice>

          <xs:any namespace="##other" processContents="lax"/>

          <xs:any namespace="##local" processContents="lax"/>

       </xs:choice>

   </xs:group>

   <!-- Patterns for elements -->

   <xs:element name="XRDS">

       <xs:complexType>

          <xs:sequence>

              <xs:group ref="xrds:otherelement" minOccurs="0" maxOccurs="unbounded"/>

          </xs:sequence>

          <xs:attributeGroup ref="xrds:otherattribute"/>

          <!--XML Schema does not currently offer a means to express that only one of the following two attributes may be used in any XRDS element, i.e., an XRDS document may describe EITHER a redirect identifier or a ref identifier but not both.-->

          <xs:attribute name="redirect" type="xs:anyURI" use="optional"/>

          <xs:attribute name="ref" type="xs:anyURI" use="optional"/>

       </xs:complexType>

   </xs:element>

</xs:schema>

 

 

 



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