Design III

Design II Table-of-Contents Requirements: Model and Syntax
Change-size

Principles and Scope

  1. An XML-Signature application must be able to use and understand
    1. XML-namespaces [XML-namespaces] within its own signature syntax. Applications may optionally choose C14N algorithms which do or do not process namespaces within XML content.
    2. XLink [Xlink]. Applications will use XLink locators within the signature manifest to reference signed resources. Signature applications will not embed or expand XLink references in the signed content, though applications may optionally choose C14N algorithms which provide this feature.
    3. XML-Pointers [XPointer]. Applications will reference/select parts of XML documents using XML-Pointer within an XLink locator. [Reagle, WS-list(1)]
  2. Implementation/Design Philosophy
    1. XML Signatures will be developed as part of the broader Web design philosophy of decentralization, URIs, Web data [WebData], modularity/layering/extensibility, and assertions as statements about statements. [Reagle]
    2. The ability to leverage existing cryptographic provider (and infrastructure) primitives is desirable.  [List(Solo)]

Joseph Reagle, XML Signature Co-Chair

W3C Logo IETF Logo

7 of 11