Re: [Sipping] Pre pub-request feedback on draft-ietf-sipping-uri-list-message-05

[Jari Urpalainen <[e-mail]>]

ext Dean Willis wrote:

>
> On Jan 26, 2006, at 10:38 AM, Miguel Garcia wrote:
>
>
>
>>> Question: Did anybody formally validate the schema and XML doc in  
>>> the example? I'm not an XML guy. Somebody please tell me you've  
>>> validated it.
>>>
>>
>> Yes, I validated the schema with XMLSpy and it is valid.
>>
>> However, I also validated with the validator at http:// 
>> validate.openlaboratory.net/ and it complains about the Unique  
>> Particle Attribution rule of the resource-list XML Schema (not  about 
>> the MESSAGE exploder draft itself).  The issue has been  discussed in 
>> the SIMPLE mailing list, see http://www.ietf.org/mail- 
>> archive/web/simple/current/msg05954.html
>> Unfortunately, there is nothing I can do to solve this problem,  
>> since there is nothing wrong in the XML Schema or the example in  
>> this draft.
>
>
> Hmm. That's supposedly the validator we'll be tested against. Jari  
> should know about it . . .
>
> in fact, he said:
>
> "Good catch, yes this schema violates the infamous Unique Particle
> Attribution (UPA) constraint (well yet another example that we should
> switch using RELAX NG ;-)). It is not about recursion it is about
> overlapping wildcards. So the first definition should be removed. Also
> there are some processContents="lax" definitions that seem to be
> missing, 48hours ?"
>
> so perhaps Jari can now help us figure out what needs to be done.
>
> HELP! Please?
>
in order to be concrete I'll include a proposal to fix xcap-list schema, 
which can be fixed within author's 48 hours, I'll hope ?

xcap-list spec has an UPA bug, the listType has two overlapping 
wildcards (<xs:any>) and e.g the second one can be removed without 
loosing extensibility:

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:ietf:params:xml:ns:resource-lists"
    xmlns="urn:ietf:params:xml:ns:resource-lists"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="qualified" attributeFormDefault="unqualified">

    <xs:import namespace="http://www.w3.org/XML/1998/namespace"
     schemaLocation="http://www.w3.org/2001/xml.xsd"/>

    <xs:complexType name="listType">
     <xs:sequence>
      <xs:element name="display-name" type="display-nameType" 
minOccurs="0"/>
      <xs:sequence minOccurs="0" maxOccurs="unbounded">
       <xs:choice>
        <xs:element name="list">
         <xs:complexType>
          <xs:complexContent>
           <xs:extension base="listType"/>
          </xs:complexContent>
         </xs:complexType>
        </xs:element>
        <xs:element name="external" type="externalType"/>
        <xs:element name="entry" type="entryType"/>
        <xs:element name="entry-ref" type="entry-refType"/>
        <xs:any namespace="##other" processContents="lax" minOccurs="0"
                maxOccurs="unbounded"/>
       </xs:choice>
      </xs:sequence>

<!--      <xs:any namespace="##other" minOccurs="0" 
maxOccurs="unbounded"/> -->
     </xs:sequence>
     <xs:attribute name="name" type="xs:string" use="optional"/>
     <xs:anyAttribute namespace="##other"/>
    </xs:complexType>
...

However,  processContents="strict" is the default value. Attributes do 
not have UPA constraint and they are hardly ever namespace qualified, so 
my preference would be:

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:ietf:params:xml:ns:resource-lists"
    xmlns="urn:ietf:params:xml:ns:resource-lists"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="qualified" attributeFormDefault="unqualified">

    <xs:import namespace="http://www.w3.org/XML/1998/namespace"
     schemaLocation="http://www.w3.org/2001/xml.xsd"/>

    <xs:complexType name="listType">
     <xs:sequence>
      <xs:element name="display-name" type="display-nameType" 
minOccurs="0"/>
      <xs:sequence minOccurs="0" maxOccurs="unbounded">
       <xs:choice>
        <xs:element name="list">
         <xs:complexType>
          <xs:complexContent>
           <xs:extension base="listType"/>
          </xs:complexContent>
         </xs:complexType>
        </xs:element>
        <xs:element name="external" type="externalType"/>
        <xs:element name="entry" type="entryType"/>
        <xs:element name="entry-ref" type="entry-refType"/>
        <xs:any namespace="##other" processContents="lax" minOccurs="0"
                maxOccurs="unbounded"/>
       </xs:choice>
      </xs:sequence>
     </xs:sequence>
     <xs:attribute name="name" type="xs:string" use="optional"/>
     <xs:anyAttribute namespace="##any" processContents="lax"/>
    </xs:complexType>

    <xs:complexType name="entryType">
     <xs:sequence>
      <xs:element name="display-name" minOccurs="0">
       <xs:complexType>
        <xs:simpleContent>
         <xs:extension base="display-nameType"/>
        </xs:simpleContent>
       </xs:complexType>
      </xs:element>
      <xs:any namespace="##other" processContents="lax" minOccurs="0"
       maxOccurs="unbounded"/>
     </xs:sequence>
     <xs:attribute name="uri" type="xs:anyURI" use="required"/>
     <xs:anyAttribute namespace="##any" processContents="lax"/>
    </xs:complexType>

    <xs:complexType name="entry-refType">
     <xs:sequence>
      <xs:element name="display-name" type="display-nameType" 
minOccurs="0"/>
      <xs:any namespace="##other"processContents="lax" minOccurs="0" 
maxOccurs="unbounded"/>
     </xs:sequence>
     <xs:attribute name="ref" type="xs:anyURI" use="required"/>
     <xs:anyAttribute namespace="##any" processContents="lax"/>
    </xs:complexType>

    <xs:complexType name="externalType">
     <xs:sequence>
      <xs:element name="display-name" type="display-nameType" 
minOccurs="0"/>
      <xs:any namespace="##other" processContents="lax" minOccurs="0" 
maxOccurs="unbounded"/>
     </xs:sequence>
     <xs:attribute name="anchor" type="xs:anyURI"/>
     <xs:anyAttribute namespace="##any" processContents="lax"/>
    </xs:complexType>

    <xs:element name="resource-lists">
     <xs:complexType>
      <xs:sequence maxOccurs="unbounded">
       <xs:element name="list" type="listType"/>
      </xs:sequence>
     </xs:complexType>
    </xs:element>

    <xs:complexType name="display-nameType">
     <xs:simpleContent>
      <xs:extension base="xs:string">
       <xs:attribute ref="xml:lang"/>
      </xs:extension>
     </xs:simpleContent>
    </xs:complexType>
</xs:schema>

Then the services schema should import the list schema. However, I'd 
much prefer that the services and list schema would share the same 
targetNamespace (include reference then to services). 

These kind of bugs easily occur as this favorite tool does not (or want 
to) check UPA violations (at least versions that I am aware of). That 
was one reason for setting up the on-line tool 
<http://validate.openlaboratory.net/> which is based on Xerces which 
supports UPA checking.

br,
Jari

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [e-mail] for questions on current sip
Use [e-mail] for new developments of core SIP