index.html 54.1 KB

Raw Blame History Permalink

<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
<html lang="en" dir="ltr">
<head>
    <title>XML Security RELAX NG Schemas</title>
    <meta http-equiv="Content-Type" content="text/html;charset=utf-8">

    <!--      <script src='../../../dap-dev/ReSpec.js/js/respec.js' -->
    <!--              class='remove'></script> -->


  <style type="text/css">
/*****************************************************************
 * ReSpec CSS
 * Robin Berjon (robin at berjon dot com)
 * v0.05 - 2009-07-31
 *****************************************************************/


/* --- INLINES --- */
em.rfc2119 {
    text-transform:     lowercase;
    font-variant:       small-caps;
    font-style:         normal;
    color:              #900;
}

h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
    border: none;
}

dfn {
    font-weight:    bold;
}

a.internalDFN {
    color:  inherit;
    border-bottom:  1px solid #99c;
    text-decoration:    none;
}

a.externalDFN {
    color:  inherit;
    border-bottom:  1px dotted #ccc;
    text-decoration:    none;
}

a.bibref {
    text-decoration:    none;
}

code {
    color:  #ff4500;
}


/* --- WEB IDL --- */
pre.idl {
    border-top: 1px solid #90b8de;
    border-bottom: 1px solid #90b8de;
    padding:    1em;
    line-height:    120%;
}

pre.idl::before {
    content:    "WebIDL";
    display:    block;
    width:      150px;
    background: #90b8de;
    color:  #fff;
    font-family:    initial;
    padding:    3px;
    font-weight:    bold;
    margin: -1em 0 1em -1em;
}

.idlType {
    color:  #ff4500;
    font-weight:    bold;
    text-decoration:    none;
}

/*.idlModule*/
/*.idlModuleID*/
/*.idlInterface*/
.idlInterfaceID {
    font-weight:    bold;
    color:  #005a9c;
}

.idlSuperclass {
    font-style: italic;
    color:  #005a9c;
}

/*.idlAttribute*/
.idlAttrType, .idlFieldType {
    color:  #005a9c;
}
.idlAttrName, .idlFieldName {
    color:  #ff4500;
}
.idlAttrName a, .idlFieldName a {
    color:  #ff4500;
    border-bottom:  1px dotted #ff4500;
    text-decoration: none;
}

/*.idlMethod*/
.idlMethType {
    color:  #005a9c;
}
.idlMethName {
    color:  #ff4500;
}
.idlMethName a {
    color:  #ff4500;
    border-bottom:  1px dotted #ff4500;
    text-decoration: none;
}

/*.idlParam*/
.idlParamType {
    color:  #005a9c;
}
.idlParamName {
    font-style: italic;
}

.extAttr {
    color:  #666;
}

/*.idlConst*/
.idlConstType {
    color:  #005a9c;
}
.idlConstName {
    color:  #ff4500;
}
.idlConstName a {
    color:  #ff4500;
    border-bottom:  1px dotted #ff4500;
    text-decoration: none;
}

/*.idlException*/
.idlExceptionID {
    font-weight:    bold;
    color:  #c00;
}

.idlTypedefID, .idlTypedefType {
    color:  #005a9c;
}

.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
    color:  #c00;
    font-weight:    normal;
}

.excName a {
    font-family:    monospace;
}

.idlRaises a.idlType, .excName a.idlType {
    border-bottom:  1px dotted #c00;
}

.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
    width:  45px;
    text-align: center;
}
.excGetSetTrue, .prmNullTrue, .prmOptTrue { color:  #0c0; }
.excGetSetFalse, .prmNullFalse, .prmOptFalse { color:  #c00; }

.idlImplements a {
    font-weight:    bold;
}

dl.attributes, dl.methods, dl.constants, dl.fields {
    margin-left:    2em;
}

.attributes dt, .methods dt, .constants dt, .fields dt {
    font-weight:    normal;
}

.attributes dt code, .methods dt code, .constants dt code, .fields dt code {
    font-weight:    bold;
    color:  #000;
    font-family:    monospace;
}

.attributes dt code, .fields dt code {
    background:  #ffffd2;
}

.attributes dt .idlAttrType code, .fields dt .idlFieldType code {
    color:  #005a9c;
    background:  transparent;
    font-family:    inherit;
    font-weight:    normal;
    font-style: italic;
}

.methods dt code {
    background:  #d9e6f8;
}

.constants dt code {
    background:  #ddffd2;
}

.attributes dd, .methods dd, .constants dd, .fields dd {
    margin-bottom:  1em;
}

table.parameters, table.exceptions {
    border-spacing: 0;
    border-collapse:    collapse;
    margin: 0.5em 0;
    width:  100%;
}
table.parameters { border-bottom:  1px solid #90b8de; }
table.exceptions { border-bottom:  1px solid #deb890; }

.parameters th, .exceptions th {
    color:  #fff;
    padding:    3px 5px;
    text-align: left;
    font-family:    initial;
    font-weight:    normal;
    text-shadow:    #666 1px 1px 0;
}
.parameters th { background: #90b8de; }
.exceptions th { background: #deb890; }

.parameters td, .exceptions td {
    padding:    3px 10px;
    border-top: 1px solid #ddd;
    vertical-align: top;
}

.parameters tr:first-child td, .exceptions tr:first-child td {
    border-top: none;
}

.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
    width:  100px;
}

.parameters td.prmType {
    width:  120px;
}

table.exceptions table {
    border-spacing: 0;
    border-collapse:    collapse;
    width:  100%;
}

/* --- TOC --- */
.toc a {
    text-decoration:    none;
}

a .secno {
    color:  #000;
}

/* --- TABLE --- */
table.simple {
    border-spacing: 0;
    border-collapse:    collapse;
    border-bottom:  3px solid #005a9c;
}

.simple th {
    background: #005a9c;
    color:  #fff;
    padding:    3px 5px;
    text-align: left;
}

.simple th[scope="row"] {
    background: inherit;
    color:  inherit;
    border-top: 1px solid #ddd;
}

.simple td {
    padding:    3px 10px;
    border-top: 1px solid #ddd;
}

.simple tr:nth-child(even) {
    background: #f0f6ff;
}

/* --- DL --- */
.section dd > p:first-child {
    margin-top: 0;
}

.section dd > p:last-child {
    margin-bottom: 0;
}

.section dd {
    margin-bottom:  1em;
}

.section dl.attrs dd, .section dl.eldef dd {
    margin-bottom:  0;
}

/* --- EXAMPLES --- */
pre.example {
    border-top: 1px solid #ff4500;
    border-bottom: 1px solid #ff4500;
    padding:    1em;
    margin-top: 1em;
}

pre.example::before {
    content:    "Example";
    display:    block;
    width:      150px;
    background: #ff4500;
    color:  #fff;
    font-family:    initial;
    padding:    3px;
    font-weight:    bold;
    margin: -1em 0 1em -1em;
}

/* --- EDITORIAL NOTES --- */
.issue {
    padding:    1em;
    margin: 1em 0em 0em;
    border: 1px solid #f00;
    background: #ffc;
}

.issue::before {
    content:    "Issue";
    display:    block;
    width:  150px;
    margin: -1.5em 0 0.5em 0;
    font-weight:    bold;
    border: 1px solid #f00;
    background: #fff;
    padding:    3px 1em;
}

.note {
    margin: 1em 0em 0em;
    padding:    1em;
    border: 2px solid #cff6d9;
    background: #e2fff0;
}

.note::before {
    content:    "Note";
    display:    block;
    width:  150px;
    margin: -1.5em 0 0.5em 0;
    font-weight:    bold;
    border: 1px solid #cff6d9;
    background: #fff;
    padding:    3px 1em;
}

/* --- Best Practices --- */
div.practice {
    border: solid #bebebe 1px;
    margin: 2em 1em 1em 2em;
}

span.practicelab {
    margin: 1.5em 0.5em 1em 1em;
    font-weight: bold;
    font-style: italic;
}

span.practicelab   { background: #dfffff; }

span.practicelab {
    position: relative;
    padding: 0 0.5em;
    top: -1.5em;
}

p.practicedesc {
    margin: 1.5em 0.5em 1em 1em;
}

@media screen {
    p.practicedesc {
        position: relative;
        top: -2em;
        padding: 0;
        margin: 1.5em 0.5em -1em 1em;
    }
}

/* --- SYNTAX HIGHLIGHTING --- */
pre.sh_sourceCode {
  background-color: white;
  color: black;
  font-style: normal;
  font-weight: normal;
}

pre.sh_sourceCode .sh_keyword { color: #005a9c; font-weight: bold; }           /* language keywords */
pre.sh_sourceCode .sh_type { color: #666; }                            /* basic types */
pre.sh_sourceCode .sh_usertype { color: teal; }                             /* user defined types */
pre.sh_sourceCode .sh_string { color: red; font-family: monospace; }        /* strings and chars */
pre.sh_sourceCode .sh_regexp { color: orange; font-family: monospace; }     /* regular expressions */
pre.sh_sourceCode .sh_specialchar { color: 	#ffc0cb; font-family: monospace; }  /* e.g., \n, \t, \\ */
pre.sh_sourceCode .sh_comment { color: #A52A2A; font-style: italic; }         /* comments */
pre.sh_sourceCode .sh_number { color: purple; }                             /* literal numbers */
pre.sh_sourceCode .sh_preproc { color: #00008B; font-weight: bold; }       /* e.g., #include, import */
pre.sh_sourceCode .sh_symbol { color: blue; }                            /* e.g., *, + */
pre.sh_sourceCode .sh_function { color: black; font-weight: bold; }         /* function calls and declarations */
pre.sh_sourceCode .sh_cbracket { color: red; }                              /* block brackets (e.g., {, }) */
pre.sh_sourceCode .sh_todo { font-weight: bold; background-color: #00FFFF; }   /* TODO and FIXME */

/* Predefined variables and functions (for instance glsl) */
pre.sh_sourceCode .sh_predef_var { color: #00008B; }
pre.sh_sourceCode .sh_predef_func { color: #00008B; font-weight: bold; }

/* for OOP */
pre.sh_sourceCode .sh_classname { color: teal; }

/* line numbers (not yet implemented) */
pre.sh_sourceCode .sh_linenum { display: none; }

/* Internet related */
pre.sh_sourceCode .sh_url { color: blue; text-decoration: underline; font-family: monospace; }

/* for ChangeLog and Log files */
pre.sh_sourceCode .sh_date { color: blue; font-weight: bold; }
pre.sh_sourceCode .sh_time, pre.sh_sourceCode .sh_file { color: #00008B; font-weight: bold; }
pre.sh_sourceCode .sh_ip, pre.sh_sourceCode .sh_name { color: #006400; }

/* for Prolog, Perl... */
pre.sh_sourceCode .sh_variable { color: #006400; }

/* for LaTeX */
pre.sh_sourceCode .sh_italics { color: #006400; font-style: italic; }
pre.sh_sourceCode .sh_bold { color: #006400; font-weight: bold; }
pre.sh_sourceCode .sh_underline { color: #006400; text-decoration: underline; }
pre.sh_sourceCode .sh_fixed { color: green; font-family: monospace; }
pre.sh_sourceCode .sh_argument { color: #006400; }
pre.sh_sourceCode .sh_optionalargument { color: purple; }
pre.sh_sourceCode .sh_math { color: orange; }
pre.sh_sourceCode .sh_bibtex { color: blue; }

/* for diffs */
pre.sh_sourceCode .sh_oldfile { color: orange; }
pre.sh_sourceCode .sh_newfile { color: #006400; }
pre.sh_sourceCode .sh_difflines { color: blue; }

/* for css */
pre.sh_sourceCode .sh_selector { color: purple; }
pre.sh_sourceCode .sh_property { color: blue; }
pre.sh_sourceCode .sh_value { color: #006400; font-style: italic; }

/* other */
pre.sh_sourceCode .sh_section { color: black; font-weight: bold; }
pre.sh_sourceCode .sh_paren { color: red; }
pre.sh_sourceCode .sh_attribute { color: #006400; }

</style><link href="http://www.w3.org/StyleSheets/TR/W3C-WD" rel="stylesheet" type="text/css" charset="utf-8"></head><body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">XML Security RELAX NG Schemas</h1><h2 id="w3c-working-draft-30-august-2011">W3C Working Draft 30 August 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-xmlsec-rngschema-20110830/">http://www.w3.org/TR/2011/WD-xmlsec-rngschema-20110830/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/xmlsec-rngschema/">http://www.w3.org/TR/xmlsec-rngschema/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://www.w3.org/2008/xmlsec/Drafts/xmlsec-rngschema/">http://www.w3.org/2008/xmlsec/Drafts/xmlsec-rngschema/</a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-xmlsec-rngschema-20110421/">http://www.w3.org/TR/2011/WD-xmlsec-rngschema-20110421/</a></dd><dt>Editors:</dt><dd><span>Makoto Murata</span>, Invited Expert</dd>
<dd><span>Frederick Hirsch</span>, Nokia</dd>
</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr></div>
    <div id="abstract" class="introductory section"><h2>Abstract</h2>
      <p>This document serves to publish RELAX NG schemas for XML
      Security specifications, including  XML Signature 1.0 and 1.1, XML Encryption 1.0 and 1.1, Exclusive Canonicalization, XML
      Signature Properties, XML-Signature XPath Filter 2.0, and XML Security Generic Hybrid Ciphers.
      </p>
    </div><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
      <p>
        This Working Draft collects non-normative RELAX NG Schemas for XML
        Security specifications, including XML Signature 1.0 and 1.1, XML Encryption
        1.0 and 1.1, Exclusive Canonicalization, XML
        Signature Properties, XML-Signature XPath Filter 2.0, and XML Security Generic Hybrid Ciphers. The
        normative description of the respective data formats are
        included in the Recommendation-track specifications.
      </p>
      <p>
        These schemas are drafts and subject to further revisions. This is a
        work in progress. This document is
        intended to evolve to include additional RELAX NG schemas.
        </p><p>This version of this specification is significantly different from
        the
        <a href="http://www.w3.org/TR/2011/WD-xmlsec-rngschema-20110421/">previous
        version</a>.  </p>

        <ul>
          <li>The prose has been completely rewritten.  In particular,
          <a href="#sec-Taxonomy">Taxonomy of schemas</a>,
          <a href="#sec-Techniques">Schema authoring techniques</a>, and
          <a href="#sec-Schema-Indexes">Schema indexes</a>  have been introduced.</li>
          <li>xmldsig-filter2.rnc for XML-Signature XPath Filter 2.0 has been added.</li>
          <li>xmldsig11-schema.rnc has been modified by adding X509Digest and
          invoking xmldsig-filter2.rnc.</li>
          <li>Small bugs in xenc-schema-11.rnc and xmlsec-ghc-schema.rnc have been fixed.</li>
          <li>any.rnc has been renamed as security_any.rnc</li>
          <li>exclusiveC14N.rnc has been renamed as exc-c14n.rnc</li>
          <li>Driver schemas have been thoroughly renamed.</li>
        </ul>

    <p>This document was published by the <a href="http://www.w3.org/2008/xmlsec/">XML Security Working Group</a> as a Working Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:public-xmlsec@w3.org">public-xmlsec@w3.org</a> (<a href="mailto:public-xmlsec-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-xmlsec/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. The group does not expect this document to become a W3C Recommendation. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/42458/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#sec-Introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#sec-Taxonomy" class="tocxref"><span class="secno">2. </span>Taxonomy of Schemas</a><ul class="toc"><li class="tocline"><a href="#sec-Taxonomy-Driver" class="tocxref"><span class="secno">2.1 </span>Driver Schemas</a></li><li class="tocline"><a href="#sec-Taxonomy-Strict" class="tocxref"><span class="secno">2.2 </span>Strict Schemas</a></li><li class="tocline"><a href="#sec-Taxonomy-Lenient" class="tocxref"><span class="secno">2.3 </span>Lenient Schemas</a></li><li class="tocline"><a href="#sec-Taxonomy-Supplementary" class="tocxref"><span class="secno">2.4 </span>Supplementary Schemas</a></li><li class="tocline"><a href="#sec-Taxonomy-Common" class="tocxref"><span class="secno">2.5 </span>Common schemas</a></li></ul></li><li class="tocline"><a href="#sec-Techniques" class="tocxref"><span class="secno">3. </span>Schema Authoring Techniques</a><ul class="toc"><li class="tocline"><a href="#sec-Techniques-Strict" class="tocxref"><span class="secno">3.1 </span>Strict Definitions</a></li><li class="tocline"><a href="#sec-Techniques-Lenient" class="tocxref"><span class="secno">3.2 </span>Lenient Definitions</a></li><li class="tocline"><a href="#sec-Techniques-Except" class="tocxref"><span class="secno">3.3 </span>Except Patterns</a></li><li class="tocline"><a href="#sec-Techniques-Wildcard" class="tocxref"><span class="secno">3.4 </span>Wildcard Patterns</a></li></ul></li><li class="tocline"><a href="#sec-Schema-Indexes" class="tocxref"><span class="secno">4. </span>Schema Indexes</a><ul class="toc"><li class="tocline"><a href="#sec-Strict-Lenient-Supplementary" class="tocxref"><span class="secno">4.1 </span>Strict, Lenient, and Supplementary Schemas</a></li><li class="tocline"><a href="#sec-Driver" class="tocxref"><span class="secno">4.2 </span>Driver schemas</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">A. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">A.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">A.2 </span>Informative references</a></li></ul></li></ul></div>

    <div id="sec-Introduction" class="section">
      <!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
      <p>The XML Security specifications include normative XML
      Schema  [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA-1">XMLSCHEMA-1</a></cite>], [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA-2">XMLSCHEMA-2</a></cite>].
      This note provides non-normative RELAX NG schemas in the compact syntax as well as the
      XML syntax [<cite><a class="bibref" rel="biblioentry" href="#bib-RELAXNG-SCHEMA">RELAXNG-SCHEMA</a></cite>].
      </p>
      <p>The biggest difference from the original XSD schemas is that these
      RELAX NG schemas provide co-occurrence constraints between the
      <code>Algorithm</code> attribute and child parameter elements.  Thus, RELAX NG
      validation can report an error when a <code>DigestMethod</code> element with
      <code>Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"</code> has an
      <code>HMACOutputLength</code> element, which is allowed only when
      <code>Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1"</code>.</p>

    </div>


    <div id="sec-Taxonomy" class="section">
      <!--OddPage--><h2><span class="secno">2. </span>Taxonomy of Schemas</h2>

      <div id="sec-Taxonomy-Driver" class="section">
        <h3><span class="secno">2.1 </span>Driver Schemas</h3>
        <p>Schemas in this group invoke other schemas, and further define the start
        pattern and wildcard patterns.  These driver schemas are written from
        scratch.</p>

        <p>A driver schema is required for each combination of strict,
        lenient, and supplementary schemas (see below).  This
        note provides some driver schemas, but does not cover all possible
        combinations.  It is believed that driver schemas for other
        combinations are easy to write.</p>

        <p>Moreover, the driver schemas in this note allow signature or encryption elements anywhere
        in the given XML document.  When one wants to allow signature or encryption elements at a certain location only,
        dedicated schemas are required.</p>
      </div>
      <div id="sec-Taxonomy-Strict" class="section">
        <h3><span class="secno">2.2 </span>Strict Schemas</h3>
        <p>Schemas in this group play the key role, and they are derived from the
        original XSD schemas.  Unlike the original XSD schemas, strict schemas
        allow specific values of the <code>Algorithm</code> attribute and further specify
        permissible child parameter elements for each of the values.  For
        example, a strict schema xmldsig-core-schema.rnc allows
        "http://www.w3.org/2000/09/xmldsig#sha1" as the value of the <code>Algorithm</code>
        attribute of the <code>DigestMethod</code> element and an empty sequence of child
        elements. </p>
      </div>
      <div id="sec-Taxonomy-Lenient" class="section">
        <h3><span class="secno">2.3 </span>Lenient Schemas</h3>
        <p>Schemas in this group complement strict schemas, and they are derived
        mainly from xsd:any in the original XSD schemas.  Lenient schemas are
        expected to be used together with strict schemas.</p>

        <p>Unlike strict schemas, lenient schemas allow any value for the
        <code>Algorithm</code> attribute and allow any child parameter elements.  For
        example, xmldsig-allowAnyForeign.rnc allows any value for the
        <code>Algorithm</code> attribute of the <code>DigestMethod</code> element and any child
        parameter element.  However, when the <code>Algorithm</code> attribute value is
        explicitly specified in strict schemas, child parameter elements
        continue to be tightly constrained.</p>
      </div>
      <div id="sec-Taxonomy-Supplementary" class="section">
        <h3><span class="secno">2.4 </span>Supplementary Schemas</h3>
        <p>Schemas in this group are derived from XSD schemas not constraining
        the <code>Algorithm</code> attribute.  These schemas are used together with strict
        schemas.  These schemas are intended to exactly capture the original
        XSD schemas.</p>
      </div>

      <div id="sec-Taxonomy-Common" class="section">
        <h3><span class="secno">2.5 </span>Common schemas</h3>
        <p>Schemas in this group define common patterns for RELAX NG.  These
        schemas are not derived from XSD schemas.  There is one common schema,
        namely <a href="security_any.rnc">security_any.rnc</a> (<a href="security_any.rng">security_any.rng</a>).  It defines
        <code>security_anyElement</code> and <code>security_anyAttribute</code>, which allow any element
        and attribute, respectively.</p>
      </div>
    </div>
    <div id="sec-Techniques" class="section">
      <!--OddPage--><h2><span class="secno">3. </span>Schema Authoring Techniques</h2>
      <div id="sec-Techniques-Strict" class="section">
        <h3><span class="secno">3.1 </span>Strict Definitions</h3>
        <p>Strict schemas provide strict definitions of the <code>Algorithm</code> attribute
        as well as permissible child elements.  For example, a strict schema
        xmldsig-core-schema.rnc has a definition shown below.  It specifies
        that "http://www.w3.org/2000/09/xmldsig#sha1" is allowed for the
        <code>Algorithm</code> attribute and an empty sequence of child elements are
        allowed.  This definition is used for defining attributes and contents
        of the <code>DigestMethod</code> element.</p>

        <pre class="xml-dtd">ds_DigestMethodType =
        attribute Algorithm {
        xsd:anyURI "http://www.w3.org/2000/09/xmldsig#sha1" }</pre>

        <p>Another definition (shown below) from the same schema specifies that either</p>
        <ul>
          <li>"http://www.w3.org/2000/09/xmldsig#hmac-sha1" is allowed for the <code>Algorithm</code>
          attribute and an optional <code>HMACOutputLength</code> element is allowed,</li>
          <li>"http://www.w3.org/2000/09/xmldsig#dsa-sha1" is allowed for the <code>Algorithm</code>
          attribute and no child elements are  allowed, or </li>
          <li>"http://www.w3.org/2000/09/xmldsig#rsa-sha1" is allowed for the <code>Algorithm</code>
        attribute and no child elements are  allowed.</li></ul>
        <p>Note that RELAX NG allow the use
        of attribute definitions in the choice construct.</p>

        <pre class="xml-dtd">ds_SignatureMethodType =
        (attribute Algorithm {
        xsd:anyURI "http://www.w3.org/2000/09/xmldsig#hmac-sha1" },
        element HMACOutputLength { ds_HMACOutputLengthType }?)
        | attribute Algorithm {
        xsd:anyURI "http://www.w3.org/2000/09/xmldsig#dsa-sha1" }
        | attribute Algorithm {
        xsd:anyURI "http://www.w3.org/2000/09/xmldsig#rsa-sha1" } </pre>

        <p>Furthermore, strict or supplementary schemas may extend definitions
        provided by other strict schemas.  This is done by the combine feature
        of [<cite><a class="bibref" rel="biblioentry" href="#bib-RELAXNG-SCHEMA">RELAXNG-SCHEMA</a></cite>].  For example, another strict schema,
        xmldsig11-schema.rnc, extends the definition <code>ds_DigestMethodType</code> in
        xmldsig-core-schema.rnc.</p>

        <pre class="xml-dtd">ds_DigestMethodType |=
        attribute Algorithm {
        xsd:anyURI "http://www.w3.org/2001/04/xmlenc#sha256"
        }
        | attribute Algorithm {
        xsd:anyURI "http://www.w3.org/2001/04/xmldsig-more#sha384"
        }
        | attribute Algorithm {
        xsd:anyURI "http://www.w3.org/2001/04/xmlenc#sha512"
        }</pre>

        <p>It specifies that "http://www.w3.org/2001/04/xmlenc#sha256",
        "http://www.w3.org/2001/04/xmldsig-more#sha384", and
        "http://www.w3.org/2001/04/xmlenc#sha512" are also allowed as
        values of the <code>Algorithm</code> attribute.</p>

        <p>Note that the original strict definition is NOT overshadowed.
        The value "http://www.w3.org/2000/09/xmldsig#sha1" continues
        to be allowed for the <code>Algorithm</code> attribute.</p>

      </div>
      <div id="sec-Techniques-Lenient" class="section">
        <h3><span class="secno">3.2 </span>Lenient Definitions</h3>
        <p>Lenient schemas provide lenient definitions of the <code>Algorithm</code> attribute as well
        as permissible child elements.  For example,
        xmldsig-allowAnyForeign.rnc has a definition shown below.  It
        specifies that any value except ds_DigestAlgorithms (see 3.1.3) is
        allowed for the <code>Algorithm</code> attribute and a possibly-empty sequence of
        foreign elements is allowed as the content.  Again, note that
        the combine feature of  RELAX NG is used to combine strict
        definitions and lenient definitions.</p>

        <pre class="xml-dtd">ds_DigestMethodType |=
        attribute Algorithm { xsd:anyURI - ds_DigestAlgorithms },
        ds_anyForeignElement*</pre>
      </div>
      <div id="sec-Techniques-Except" class="section">
        <h3><span class="secno">3.3 </span>Except Patterns</h3>
        <p>Lenient definitions do not allow any value except those explicitly allowed by strict
        schemas.  This is done by the except pattern of RELAX NG.</p>

        <p>The above lenient definition of ds_DigestMethodType contains "-
        ds_DigestAlgorithms".  It is an except pattern, and allows any value
        except those matching ds_DigestAlgorithms, which is defined by the
        strict schema xmldsig-core-schema.rnc.</p>

        <pre class="xml-dtd">ds_DigestAlgorithms =
        xsd:anyURI "http://www.w3.org/2000/09/xmldsig#sha1"</pre>

        <p>Since other strict schemas introduce other values for the Algorithm
        attribute, they also extend such definitions for the except pattern.
        For example, xmldsig11-schema.rnc, extends the above definition.</p>

        <pre class="xml-dtd">ds_DigestAlgorithms |=
        xsd:anyURI "http://www.w3.org/2001/04/xmlenc#sha256"
        | xsd:anyURI "http://www.w3.org/2001/04/xmldsig-more#sha384"
        | xsd:anyURI "http://www.w3.org/2001/04/xmlenc#sha512"</pre>
      </div>
      <div id="sec-Techniques-Wildcard" class="section">
        <h3><span class="secno">3.4 </span>Wildcard Patterns</h3>
        <p>Wildcard patterns, namely <code>ds_anyForeignElement</code>,
        <code>dsig11_anyForeignElement</code>, <code>xenc_anyForeignElement</code>, and
        <code>xenc11_anyForeignElement</code>, in driver schemas capture foreign elements.  These wildcard
        patterns are defined as elements not belonging to
        any of the known namespaces.</p>
      </div>
    </div>
    <div id="sec-Schema-Indexes" class="section">
      <!--OddPage--><h2><span class="secno">4. </span>Schema Indexes</h2>
      <div id="sec-Strict-Lenient-Supplementary" class="section">
        <h3><span class="secno">4.1 </span>Strict, Lenient, and Supplementary Schemas</h3>
        <dl>        <dt>XML Signature 1.0   [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLDSIG-CORE">XMLDSIG-CORE</a></cite>] </dt>
        <dd><dl><dt id="id-Strict-Schema-for-XML-Signature-1.0">strict</dt>  <dd><a href="xmldsig-core-schema.rnc">xmldsig-core-schema.rnc</a> (<a href="xmldsig-core-schema.rng">xmldsig-core-schema.rng</a>)</dd>
        <dt id="id-Lenient-Schema-for-XML-Signature-1.0">lenient</dt>  <dd><a href="xmldsig-allowAnyForeign.rnc">xmldsig-allowAnyForeign.rnc</a> (<a href="xmldsig-allowAnyForeign.rng">xmldsig-allowAnyForeign.rng</a>)</dd></dl></dd>
        <dt> XML Signature 1.1  [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLDSIG-CORE1">XMLDSIG-CORE1</a></cite>]</dt>
        <dd><dl><dt id="id-Strict-Schema-for-XML-Signature-1.1">strict</dt>  <dd><a href="xmldsig11-schema.rnc">xmldsig11-schema.rnc</a> (<a href="xmldsig11-schema.rng">xmldsig11-schema.rng</a>)</dd>
        <dt id="id-Lenient-Schema-for-XML-Signature-1.1">lenient</dt>  <dd><a href="xmldsig11-allowAnyForeign.rnc">xmldsig11-allowAnyForeign.rnc</a> (<a href="xmldsig11-allowAnyForeign.rng">xmldsig11-allowAnyForeign.rng</a>)</dd></dl></dd>
        <dt>Exclusive Canonicalization Algorithms [<cite><a class="bibref" rel="biblioentry" href="#bib-XML-EXC-C14N">XML-EXC-C14N</a></cite>]</dt>
        <dd><dl><dt id="id-Supplementary-Schema-for-Exclusive-Canonicalization-Algorithms">supplementary</dt>  <dd><a href="exc-c14n.rnc">exc-c14n.rnc</a> (<a href="exc-c14n.rng">exc-c14n.rng</a>)</dd></dl></dd>
        <dt>XML Signature Properties  [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLDSIG-PROPERTIES">XMLDSIG-PROPERTIES</a></cite>]  </dt>
        <dd><dl><dt id="id-Supplementary-Schema-for-XML-Signature-Properties">supplementary</dt>  <dd><a href="xmldsig-properties-schema.rnc">xmldsig-properties-schema.rnc</a> (<a href="xmldsig-properties-schema.rng">xmldsig-properties-schema.rng</a>)
        </dd></dl></dd>
        <dt>XML Encryption 1.0 [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLENC-CORE">XMLENC-CORE</a></cite>]</dt>
        <dd><dl><dt id="id-Strict-Schema-for-XML-Encryption-1.0">strict</dt>  <dd><a href="xenc-schema.rnc">xenc-schema.rnc</a> (<a href="xenc-schema.rng">xenc-schema.rng</a>)</dd>
        <dt id="id-Lenient-Schema-for-XML-Encryption-1.0">lenient</dt>  <dd><a href="xenc-allowAnyForeign.rnc">xenc-allowAnyForeign.rnc</a> (<a href="xenc-allowAnyForeign.rng">xenc-allowAnyForeign.rng</a>)</dd></dl></dd>
        <dt>XML Encryption 1.1 [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLENC-CORE1">XMLENC-CORE1</a></cite>]</dt>
        <dd><dl><dt id="id-Strict-Schema-for-XML-Encryption-1.1">strict</dt>  <dd><a href="xenc-schema-11.rnc">xenc-schema-11.rnc</a> (<a href="xenc-schema-11.rng">xenc-schema-11.rng</a>)</dd>
        <dt id="id-Lenient-Schema-for-XML-Encryption-1.1">lenient</dt>  <dd><a href="xenc11-allowAnyForeign.rnc">xenc11-allowAnyForeign.rnc</a> (<a href="xenc11-allowAnyForeign.rng">xenc11-allowAnyForeign.rng</a>)</dd></dl></dd>
        <dt>XML-Signature XPath Filter 2.0 [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLDSIG-XPATH-FILTER2">XMLDSIG-XPATH-FILTER2</a></cite>] </dt>
        <dd><dl><dt>supplementary</dt>  <dd><a href="xmldsig-filter2.rnc">xmldsig-filter2.rnc</a> (<a href="xmldsig-filter2.rng">xmldsig-filter2.rng</a>)</dd>
        <dd>This schema is directly invoked by xmldsig11-schema.rnc</dd></dl></dd>
        <dt>XML Security Generic Hybrid Ciphers [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSEC-GHCIPHERS">XMLSEC-GHCIPHERS</a></cite>] </dt>
        <dd><dl><dt id="id-Strict-Schema-for-XML-Security-Generic-Hybrid-Ciphers">strict</dt>  <dd><a href="xmlsec-ghc-schema.rnc">xmlsec-ghc-schema.rnc</a> (<a href="xmlsec-ghc-schema.rng">xmlsec-ghc-schema.rng</a>)</dd>
        <dt id="id-Lenient-Schema-for-XML-Security-Generic-Hybrid-Ciphers">lenient</dt>  <dd><a href="xmlsec-ghc-allowAnyForeign.rnc">xmlsec-ghc-allowAnyForeign.rnc</a> (<a href="xmlsec-ghc-allowAnyForeign.rng">xmlsec-ghc-allowAnyForeign.rng</a>)</dd></dl></dd>
        </dl>
      </div>
      <div id="sec-Driver" class="section">
        <h3><span class="secno">4.2 </span>Driver schemas</h3>
        <p>This subsection provides a list of driver schemas and also provides a list of included schemas  for each driver schema.</p>

        <dl><dt><a href="Strict-Signature.rnc">Strict-Signature.rnc</a> (<a href="Strict-Signature.rng">Strict-Signature.rng</a>)</dt>
        <dd>
          <ul>
            <li><a href="#sec-Taxonomy-Common">Common schema for any element and attribute</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Signature-1.0">Strict Schema for XML Signature 1.0</a></li>
          </ul>
        </dd>

        <dt><a href="Strict-Encryption.rnc">Strict-Encryption.rnc</a> (<a href="Strict-Encryption.rng">Strict-Encryption.rng</a>)</dt>
        <dd>
          <ul>
            <li><a href="#sec-Taxonomy-Common">Common schema for any element and attribute</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Signature-1.0">Strict Schema for XML Signature 1.0</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Encryption-1.0">Strict schema for XML Encryption 1.0</a></li>
          </ul>
        </dd>

        <dt><a href="Lenient-Signature11.rnc">Lenient-Signature11.rnc</a> (<a href="Lenient-Signature11.rng">Lenient-Signature11.rng</a>)</dt>
        <dd>
          <ul>
            <li><a href="#sec-Taxonomy-Common">Common schema for any element and attribute</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Signature-1.0">Strict Schema for XML Signature 1.0</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Signature-1.1">Strict Schema for XML Signature 1.1</a></li>
            <li><a href="#id-Lenient-Schema-for-XML-Signature-1.0">Lenient Schema for XML Signature 1.0</a></li>
            <li><a href="#id-Lenient-Schema-for-XML-Signature-1.1">Lenient Schema for XML Signature 1.1</a></li>
          </ul>
        </dd>

        <dt><a href="Lenient-Signature11-properties.rnc">Lenient-Signature11-properties.rnc</a> (<a href="Lenient-Signature11-properties.rng">Lenient-Signature11-properties.rng</a>)</dt>
        <dd>
          <ul>
            <li><a href="#sec-Taxonomy-Common">Common schema for any element and attribute</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Signature-1.0">Strict Schema for XML Signature 1.0</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Signature-1.1">Strict Schema for XML Signature 1.1</a></li>
            <li><a href="#id-Lenient-Schema-for-XML-Signature-1.0">Lenient Schema for XML Signature 1.0</a></li>
            <li><a href="#id-Lenient-Schema-for-XML-Signature-1.1">Lenient Schema for XML Signature 1.1</a></li>
            <li><a href="#id-Supplementary-Schema-for-XML-Signature-Properties">Supplementary schema for XML Signature Properties</a></li>
          </ul>
        </dd>

        <dt><a href="Lenient-Signature-exclusiveC14N.rnc">Lenient-Signature-exclusiveC14N.rnc</a> (<a href="Lenient-Signature-exclusiveC14N.rng">Lenient-Signature-exclusiveC14N.rng</a>)</dt>
        <dd>
          <ul>
            <li><a href="#sec-Taxonomy-Common">Common schema for any element and attribute</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Signature-1.0">Strict Schema for XML Signature 1.0</a></li>
            <li><a href="#id-Lenient-Schema-for-XML-Signature-1.0">Lenient Schema for XML Signature 1.0</a></li>
            <li><a href="#id-Supplementary-Schema-for-Exclusive-Canonicalization-Algorithms">Supplementary schema for Exclusive Canonicalization Algorithms</a></li>
          </ul>
        </dd>

        <dt><a href="Lenient-Signature11-properties-exclusiveC14N.rnc">Lenient-Signature11-properties-exclusiveC14N.rnc</a> (<a href="Lenient-Signature11-properties-exclusiveC14N.rng">Lenient-Signature11-properties-exclusiveC14N.rng</a>)</dt>
        <dd>
          <ul>
            <li><a href="#sec-Taxonomy-Common">Common schema for any element and attribute</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Signature-1.0">Strict Schema for XML Signature 1.0</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Signature-1.1">Strict Schema for XML Signature 1.1</a></li>
            <li><a href="#id-Lenient-Schema-for-XML-Signature-1.0">Lenient Schema for XML Signature 1.0</a></li>
            <li><a href="#id-Lenient-Schema-for-XML-Signature-1.1">Lenient Schema for XML Signature 1.1</a></li>
            <li><a href="#id-Supplementary-Schema-for-XML-Signature-Properties">Supplementary schema for XML Signature Properties</a></li>
            <li><a href="#id-Supplementary-Schema-for-Exclusive-Canonicalization-Algorithms">Supplementary schema for Exclusive Canonicalization Algorithms</a></li>
          </ul>
        </dd>

        <dt><a href="Lenient-Encryption11.rnc">Lenient-Encryption11.rnc</a> (<a href="Lenient-Encryption11.rng">Lenient-Encryption11.rng</a>)</dt>
        <dd>
          <ul>
            <li><a href="#sec-Taxonomy-Common">Common schema for any element and attribute</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Signature-1.0">Strict Schema for XML Signature 1.0</a></li>
            <li><a href="#id-Lenient-Schema-for-XML-Signature-1.0">Lenient Schema for XML Signature 1.0</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Encryption-1.0">Strict schema for XML Encryption 1.0</a></li>
            <li><a href="#id-Lenient-Schema-for-XML-Encryption-1.0">Lenient schema for XML Encryption 1.0</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Encryption-1.1">Strict schema for XML Encryption 1.1</a></li>
            <li><a href="#id-Lenient-Schema-for-XML-Encryption-1.1">Lenient schema for XML Encryption 1.1</a></li>
          </ul>
        </dd>

        <dt><a href="Lenient-Encryption11-ghc.rnc">Lenient-Encryption11-ghc.rnc</a> (<a href="Lenient-Encryption11-ghc.rng">Lenient-Encryption11-ghc.rng</a>)</dt>
        <dd>
          <ul>
            <li><a href="#sec-Taxonomy-Common">Common schema for any element and attribute</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Signature-1.0">Strict Schema for XML Signature 1.0</a></li>
            <li><a href="#id-Lenient-Schema-for-XML-Signature-1.0">Lenient Schema for XML Signature 1.0</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Encryption-1.0">Strict schema for XML Encryption 1.0</a></li>
            <li><a href="#id-Lenient-Schema-for-XML-Encryption-1.0">Lenient schema for XML Encryption 1.0</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Encryption-1.1">Strict schema for XML Encryption 1.1</a></li>
            <li><a href="#id-Lenient-Schema-for-XML-Encryption-1.1">Lenient schema for XML Encryption 1.1</a></li>
            <li><a href="#id-Strict-Schema-for-XML-Security-Generic-Hybrid-Ciphers">Strict schema for XML Security Generic Hybrid Ciphers</a></li>
            <li><a href="#id-Lenient-Schema-for-XML-Security-Generic-Hybrid-Ciphers">Lenient schema for XML Security Generic Hybrid Ciphers</a></li>
          </ul>
        </dd>
      </dl>
    </div>
  </div>
  <!--
       <section id="sec-Included-rngSchema" class="informative">
       <h2>Included RNG Schema files</h2>
       <p> The following are RELAX NG schema files that are included in other
       files described in this document.</p>

<dl>
  -->
  <!--     <dt>Define allowed element contents of XML Signature elements</dt> -->
  <!--     <dd><a href="allowAny.rnc">allowAny.rnc</a></dd> -->
  <!--     <dd> -->
  <!-- This schema allows any element as permissible contents of  -->
  <!-- <code>CanonicalizationMethod</code>, <code>SignatureMethod</code>, <code>Transform</code>, <code>DigestMethod</code>, -->
  <!-- <code>KeyInfo</code>, <code>KeyValue</code>, <code>X509Data</code>, <code>SPKIData</code>, <code>Object</code>, <code>SignatureProperty</code>,  -->
  <!-- <code>PGPData</code> elements. -->
  <!-- </dd> -->
  <!--
       <dt>Define <code>anyElement</code> and <code>anyAttribute</code></dt>
       <dd><a href="any.rnc">any.rnc</a> (<a href="any.rng">any.rng</a>)</dd>

<dt>Exclusive Canonicalization Algorithms RNG Schema Definitions</dt>
<dd>
<a href="exclusiveC14N.rnc">exclusiveC14N.rnc</a> (<a href="exclusiveC14N.rng">exclusiveC14N.rng</a>)
<p>RNG Schema to allow Exclusive Canonicalization algorithms.
</p>
</dl>
</section>
  -->
  <!--
      <section id="sec-Signature-rngSchema" class="informative">
      <h2>XML Signature 1.0 RNG Schema</h2>
      <p> The following are RELAX NG schemas for XML Signature 1.0
      [[XMLDSIG-CORE]].</p>
      <dl>
      <dt>XML Signature Core RELAX NG Schema Instance</dt>
      <dd><a href="xmldsig-core-schema.rnc">xmldsig-core-schema.rnc</a> (<a href="xmldsig-core-schema.rng">xmldsig-core-schema.rng</a>)</dd>
      <dd>This is the schema corresponding to XML Signature 1.0, Second
      Edition.</dd>

<dt>RELAX NG XML Signature 1.0 Top-Level Schema</dt>
<dd><a
href="any-containing-xmldsig.rnc">any-containing-xmldsig.rnc</a> (<a href="any-containing-xmldsig.rng">any-containing-xmldsig.rng</a>)</dd>
<dd>Any correct use of XML Signature 1.0 schema is expected be
valid against this top-level schema.
</dd>

<dt>RELAX NG XML Signature 1.0 schema, allowing Exclusive
Canonicalization</dt>
<dd><a
href="any-containing-xmldsig-exclusiveC14N.rnc">any-containing-xmldsig-exclusiveC14N.rnc</a> (<a href="any-containing-xmldsig-exclusiveC14N.rng">any-containing-xmldsig-exclusiveC14N.rng</a>)</dd>
<dd>Any correct use of XML Signature 1.0 schema is expected be
valid against this top-level schema, including use of the
Exclusive Canonicalization algorithm.
</dd>

<dt>RELAX NG Schema corresponding to <code>xsd:any</code></dt>
<dd><a
href="xmldsig-allowAnyForeign.rnc">xmldsig-allowAnyForeign.rnc</a> (<a href="xmldsig-allowAnyForeign.rng">xmldsig-allowAnyForeign.rng</a>)</dd>
<dd>This is used by the top-level schema to mimic <code>xsd:any</code>.</dd>
</dl>
</section>
<section id="sec-Signature11-rngSchema" class="informative">
<h2>XML Signature 1.1 RNG Schema</h2>
<p> The following are RELAX NG schemas for XML Signature 1.1
[[XMLDSIG-CORE1]].</p>
<dl>
<dt>XML Signature 1.1 RELAX NG Schema Instance</dt>

<dd><a href="xmldsig11-schema.rnc">xmldsig11-schema.rnc</a> (<a href="xmldsig11-schema.rng">xmldsig11-schema.rng</a>)</dd>

<dt>RELAX NG XML Signature 1.1 Top-Level Schema</dt>
<dd><a
href="any-containing-xmldsig11.rnc">any-containing-xmldsig11.rnc</a> (<a href="any-containing-xmldsig11.rng">any-containing-xmldsig11.rng</a>)</dd>
<dd>Any correct use of XML Signature 1.1 schema is expected be
valid against this top-level schema.
</dd>
<dt>RELAX NG Schema corresponding to <code>xsd:any</code></dt>
<dd><a
href="xmldsig11-allowAnyForeign.rnc">xmldsig11-allowAnyForeign.rnc</a> (<a href="xmldsig11-allowAnyForeign.rng">xmldsig11-allowAnyForeign.rng</a>)</dd>
<dd>This is used by the top-level schema to mimic <code>xsd:any</code>.</dd>
</dl>
</section>
<section id="sec-SignatureProperties-rngSchema" class="informative">
<h2>XML Signature Properties RNG Schema</h2>
<p> The following are RELAX NG schemas for XML Signature Properties [[XMLDSIG-PROPERTIES]].</p>
<dl>
<dt>Signature Properties RNG Schema Instance</dt>
<dd>
<a
href="xmldsig-properties-schema.rnc">xmldsig-properties-schema.rnc</a> (<a href="xmldsig-properties-schema.rng">xmldsig-properties-schema.rng</a>)
<p>Valid RNG Schema instance.
</p></dd>
<dt>RELAX NG XML Signature 1.1 with Properties Top-Level Schema</dt>
<dd><a
href="any-containing-xmldsig11-properties.rnc">any-containing-xmldsig11-properties.rnc</a> (<a href="any-containing-xmldsig11-properties.rng">any-containing-xmldsig11-properties.rng</a>)</dd>
<dd>Any correct use of XML Signature 1.1 schema containing
Signature Properties defined in this specification is expected be
valid against this top-level schema.
</dd>
<dt>RELAX NG XML Signature 1.1 with Properties Top-Level
Schema, allowing Exclusive Canonicalization</dt>
<dd><a
href="any-containing-xmldsig11-properties-exclusiveC14N.rnc">any-containing-xmldsig11-properties-exclusiveC14N.rnc</a> (<a href="any-containing-xmldsig11-properties-exclusiveC14N.rng">any-containing-xmldsig11-properties-exclusiveC14N.rng</a>)</dd>
<dd>Any correct use of XML Signature 1.1 schema containing
Signature Properties defined in this specification is expected be
valid against this top-level schema, including use of
Exclusive Canonicalization algorithm.
</dd>
</dd>
</dl>
</section>
<section id="sec-Encryption-rngSchema" class="informative">
<h2>XML Encryption 1.0 RNG Schema</h2>
<p> The following is a RELAX NG schema for XML Encryption 1.0 [[XMLENC-CORE]].</p>
<dl>
<dt>XML Encryption 1.0 RELAX NG Schema Instance</dt>
<dd><a href="xenc-schema.rnc">xenc-schema.rnc</a> (<a href="xenc-schema.rng">xenc-schema.rng</a>)</dd>
<dd>This is the schema corresponding to XML Encryption
1.0.</dd>
<dt>RELAX NG XML Encryption 1.0 Top-Level Schema</dt>
<dd><a
href="any-containing-encryption.rnc">any-containing-encryption.rnc</a> (<a href="any-containing-encryption.rng">any-containing-encryption.rng</a>)</dd>
<dd>Any correct use of XML Encryption schema is expected be valid
against this top-level schema.</dd>
<dt>RELAX NG Schema corresponding to <code>xsd:any</code></dt>
<dd><a
href="xenc-allowAnyForeign.rnc">xenc-allowAnyForeign.rnc</a> (<a href="xenc-allowAnyForeign.rng">xenc-allowAnyForeign.rng</a>)</dd>
<dd>This is used by the top-level schema to mimic <code>xsd:any</code>.</dd>
</dl>
</section>

<section id="sec-Encryption11-rngSchema" class="informative">
<h2>XML Encryption 1.1 RNG Schema</h2>
<p> The following are RELAX NG schemas for XML Encryption 1.1
[[XMLENC-CORE1]].</p>
<dl>
<dt>XML Encryption 1.1 RELAX NG Schema Instance</dt>

<dd><a href="xenc-schema-11.rnc">xenc-schema-11.rnc</a> (<a href="xenc-schema-11.rng">xenc-schema-11.rng</a>)</dd>

<dt>RELAX NG XML Encryption 1.1 Top-Level Schema</dt>
<dd><a
href="any-containing-encryption11.rnc">any-containing-encryption11.rnc</a> (<a href="any-containing-encryption11.rng">any-containing-encryption11.rng</a>)</dd>
<dd>Any correct use of XML Encryption 1.1 schema is expected be
valid against this top-level schema.
</dd>
<dt>RELAX NG Schema corresponding to <code>xsd:any</code></dt>
<dd><a
href="xenc11-allowAnyForeign.rnc">xenc11-allowAnyForeign.rnc</a> (<a href="xenc11-allowAnyForeign.rng">xenc11-allowAnyForeign.rng</a>)</dd>
</dl>
</section>
<section id="sec-GenericHybrid-rngSchema" class="informative">
<h2>XML Security Generic Hybrid Ciphers RNG Schema</h2>
<p> The following are RELAX NG schemas for
XML Security Generic Hybrid Ciphers
[[XMLSEC-GHCIPHERS]].</p>
<dl>
<dt>XML Security Generic Hybrid Ciphers RELAX NG Schema Instance</dt>

<dd><a href="xmlsec-gh-schema.rnc">xmlsec-gh-schema.rnc</a> (<a href="xmlsec-gh-schema.rng">xmlsec-gh-schema.rng</a>)</dd>

<dt>RELAX NG XML Security Generic Hybrid Ciphers Top-Level Schema</dt>
<dd><a
href="any-containing-encryption11-gh.rnc">any-containing-encryption11-gh.rnc</a> (<a href="any-containing-encryption11-gh.rng">any-containing-encryption11-gh.rng</a>)</dd>
<dd>Any correct use of XML Security Generic Hybrid Ciphers  is expected be
valid against this top-level schema.
</dd>
<dt>RELAX NG Schema corresponding to <code>xsd:any</code></dt>
<dd><a
href="xmlsec-gh-allowAnyForeign.rnc">xmlsec-gh-allowAnyForeign.rnc</a> (<a href="xmlsec-gh-allowAnyForeign.rng">xmlsec-gh-allowAnyForeign.rng</a>)</dd>

</dl>
</section>
  -->


<div id="references" class="appendix section"><!--OddPage--><h2><span class="secno">A. </span>References</h2><p>Dated references below are to the latest known or appropriate edition of the referenced work.  The referenced works may be subject to revision, and conformant implementations may follow, and are encouraged to investigate the appropriateness of following, some or all more recent editions or replacements of the works cited. It is in each case implementation-defined which  editions are supported.</p><div id="normative-references" class="section"><h3><span class="secno">A.1 </span>Normative references</h3><p>No normative references.</p></div><div id="informative-references" class="section"><h3><span class="secno">A.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-RELAXNG-SCHEMA">[RELAXNG-SCHEMA]</dt><dd><a href="http://standards.iso.org/ittf/PubliclyAvailableStandards/c052348_ISO_IEC_19757-2_2008(E).zip"><cite>Information technology -- Document Schema Definition Language (DSDL) -- Part 2: Regular-grammar-based validation -- RELAX NG</cite></a>. ISO/IEC 19757-2:2008. URL: <a href="http://standards.iso.org/ittf/PubliclyAvailableStandards/c052348_ISO_IEC_19757-2_2008(E).zip">http://standards.iso.org/ittf/PubliclyAvailableStandards/c052348_ISO_IEC_19757-2_2008(E).zip</a>
</dd><dt id="bib-XML-EXC-C14N">[XML-EXC-C14N]</dt><dd>Donald E. Eastlake 3rd; Joseph Reagle; John Boyer. <a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/"><cite>Exclusive XML Canonicalization Version 1.0.</cite></a> 18 July 2002. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/">http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/</a>
</dd><dt id="bib-XMLDSIG-CORE">[XMLDSIG-CORE]</dt><dd>Joseph Reagle; et al. <a href="http://www.w3.org/TR/2008/REC-xmldsig-core-20080610/"><cite>XML Signature Syntax and Processing (Second Edition).</cite></a> 10 June 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-xmldsig-core-20080610/">http://www.w3.org/TR/2008/REC-xmldsig-core-20080610</a>
</dd><dt id="bib-XMLDSIG-CORE1">[XMLDSIG-CORE1]</dt><dd>D. Eastlake, J. Reagle, D. Solo, F. Hirsch, T. Roessler, K. Yiu. <a href="http://www.w3.org/TR/2011/CR-xmldsig-core1-20110303/"><cite>XML Signature Syntax and Processing Version 1.1.</cite></a> 3 March 2011. W3C Candidate Recommendation. (Work in progress.) URL: <a href="http://www.w3.org/TR/2011/CR-xmldsig-core1-20110303/">http://www.w3.org/TR/2011/CR-xmldsig-core1-20110303/</a>
</dd><dt id="bib-XMLDSIG-PROPERTIES">[XMLDSIG-PROPERTIES]</dt><dd>Frederick Hirsch. <a href="http://www.w3.org/TR/2011/CR-xmldsig-properties-20110303/"><cite>XML Signature Properties.</cite></a> 3 March 2011. W3C Candidate Recommendation. (Work in progress.) URL: <a href="http://www.w3.org/TR/2011/CR-xmldsig-properties-20110303/">http://www.w3.org/TR/2011/CR-xmldsig-properties-20110303/</a>
</dd><dt id="bib-XMLDSIG-XPATH-FILTER2">[XMLDSIG-XPATH-FILTER2]</dt><dd>Merlin Hughes; John Boyer; Joseph Reagle. <a href="http://www.w3.org/TR/2002/REC-xmldsig-filter2-20021108/"><cite>XML-Signature XPath Filter 2.0.</cite></a> 8 November 2002. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2002/REC-xmldsig-filter2-20021108/">http://www.w3.org/TR/2002/REC-xmldsig-filter2-20021108/</a>
</dd><dt id="bib-XMLENC-CORE">[XMLENC-CORE]</dt><dd>Donald Eastlake; Joseph Reagle. <a href="http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/"><cite>XML Encryption Syntax and Processing.</cite></a> 10 December 2002. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/">http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/</a>
</dd><dt id="bib-XMLENC-CORE1">[XMLENC-CORE1]</dt><dd>J. Reagle; D. Eastlake; F. Hirsch; T. Roessler. <a href="http://www.w3.org/TR/2011/CR-xmlenc-core1-20110303/"><cite>XML Encryption Syntax and Processing Version 1.1.</cite></a> 3 March 2011. W3C Candidate Recommendation. (Work in progress.) URL: <a href="http://www.w3.org/TR/2011/CR-xmlenc-core1-20110303/">http://www.w3.org/TR/2011/CR-xmlenc-core1-20110303/</a>
</dd><dt id="bib-XMLSCHEMA-1">[XMLSCHEMA-1]</dt><dd>Henry S. Thompson; et al. <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>XML Schema Part 1: Structures Second Edition.</cite></a> 28 October 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/</a>
</dd><dt id="bib-XMLSCHEMA-2">[XMLSCHEMA-2]</dt><dd>Paul V. Biron; Ashok Malhotra. <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>XML Schema Part 2: Datatypes Second Edition.</cite></a> 28 October 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/</a>
</dd><dt id="bib-XMLSEC-GHCIPHERS">[XMLSEC-GHCIPHERS]</dt><dd>Magnus Nyström; Frederick Hirsch. <a href="http://www.w3.org/TR/2011/CR-xmlsec-generic-hybrid-20110303/"><cite>XML Security Generic Hybrid Ciphers.</cite></a> 3 March 2011. W3C Candidate Recommendation. (Work in progress.) URL: <a href="http://www.w3.org/TR/2011/CR-xmlsec-generic-hybrid-20110303/">http://www.w3.org/TR/2011/CR-xmlsec-generic-hybrid-20110303/</a>
</dd></dl></div></div></body></html>