W3C home > Mailing lists > Public > public-xmlsec@w3.org > July 2010

ACTION-612: Schema addition to c14n 2 draft for qnameAware parameter

From: Scott Cantor <cantor.2@osu.edu>
Date: Wed, 28 Jul 2010 14:31:43 -0400
To: <public-xmlsec@w3.org>
Message-ID: <020201cb2e83$212f42d0$638dc870$@osu.edu>
Should we rename section 3 to "Use in XML Signature 2.0"?

The XsiTypeAware element should be removed, obviously.

Should we synchronize the parameter names in the table up above and in the
text with the element names in the schema? Seems like it's confusing to have
different case rules.

Also, there are missing xs: prefixes in the definition for
InclusiveNamespaces.

The proposed schema for the new QName option is as follows. It's a bit
confusing because it's using element and attribute names like Element and
Name. ;-)

<xs:element name="QNameAware">
  <xs:complexType>
    <xs:choice maxOccurs="unbounded">
      <xs:element ref="Element"/>
      <xs:element ref="QualifiedAttr"/>
      <xs:element ref="UnqualifiedAttr"/>
    <xs:sequence>
  </xs:complexType>
</xs:element>

<xs:element name="Element">
  <xs:complexType>
    <xs:attribute name="Name" type="xs:NCName" use="required"/>
    <xs:attribute name="NS" type="xs:anyURI"/>
  </xs:complexType>
</xs:element>

<xs:element name="QualifiedAttr">
  <xs:complexType>
    <xs:attribute name="Name" type="xs:NCName" use="required"/>
    <xs:attribute name="NS" type="xs:anyURI"/>
  </xs:complexType>
</xs:element>

<xs:element name="UnqualifiedAttr">
  <xs:complexType>
    <xs:attribute name="Name" type="xs:NCName" use="required"/>
    <xs:attribute name="ParentName" type="xs:NCName" use="required"/>
    <xs:attribute name="ParentNS" type="xs:anyURI"/>
  </xs:complexType>
</xs:element>

-- Scott
Received on Wednesday, 28 July 2010 18:32:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 28 July 2010 18:32:10 GMT