Subject: [Simple] Bug in RFC 4826: resource-lists schema doesn't require anchor attribute

From: Byron Campen <[email-masked]>
Date: Tue, 22 Jul 2008 13:06:18 -0500

The resource-lists schema in RFC 4826 does not match the normative  
text wrt whether the "anchor" attribute is required in <external>  
elements.

The normative text reads:

"
    The <external> element has a single
    mandatory attribute, "anchor", which specifies the external list by
    means of an absolute HTTP URI.
"

The schema reads:

"
     <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="##other" processContents="lax"/>
     </xs:complexType>
"

	I looked in the rfc errata, but did see this mentioned. Should I go  
ahead and file a new erratum?

Best regards,
Byron Campen

_______________________________________________
Simple mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/simple