W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > July to September 1999

DataModel Types and Values in Solo's Draft

From: Joseph M. Reagle Jr. <reagle@w3.org>
Date: Thu, 23 Sep 1999 18:15:27 -0400
Message-Id: <>
To: "IETF/W3C XML-DSig WG" <w3c-ietf-xmldsig@w3.org>
Some thoughts on the things I didn't work on much in Solo's draft.


 I was starting work on a manifest/package document and wanted to plug in and
 use syntax (particularly the references) from the Solo draft but I continue
 to find the lack of a data model behind it to be very frustrating. Why are
 somethings types and others values, and some values content? Was this
 purposeful? (I don't recall) One can ask this from the point of view
 syntactic consistency or from a datamodel point of view.
 (1) For instance:
   <dsig:signaturevalue value="dd2323dd"/>
 signaturevalue is a node/resource that is somehow (anonymously) related to
 signature with a property "value" and value "dd2323dd".
 But why not:
 Signature value is a property of signature with value "dd2323dd". Makes much
 more sense.
(2) Elsewhere:
  <dsig:keyinfodata type="keyname"> 3 </dsig:keyinfodata>
 keyinfodata is a resource that is somehow (anonymously) related to keyinfo.
 keyinfodata has a property of "type" with a value "keyname". KeyInfoData is
 also related to some literal "3" but I'm not sure how.
 But why not:
 keyinfo is a property that relates signature to keyattributes. keyattributes
 has numerous properties (keyname, keyvalue) all with different values.

Joseph Reagle Jr.   
Policy Analyst           mailto:reagle@w3.org
XML-Signature Co-Chair   http://w3.org/People/Reagle/
Received on Thursday, 23 September 1999 18:19:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:09:56 UTC