- From: Hallam-Baker, Phillip <pbaker@verisign.com>
- Date: Wed, 25 Sep 2002 14:08:30 -0700
- To: www-xkms@w3.org
- Message-ID: <2F3EC696EAEED311BB2D009027C3F4F40E6B2472@vhqpostal.verisign.com>
Issue #30 Another schema design question, where should the policy identifier go in the KeyBinding hierarchy? I think that it is clear that we need to be able to return the Policy identifier in responses. It is also clear that we need to be able to specify it in a locate request. I think it would be useful to be able to specify the Policy Identifier in a locate request as well. In fact it could well provide a locate service with critical scope information to help limit the search. <!-- KeyBindingAbstractType--> <complexType name="KeyBindingAbstractType" abstract="true"> <sequence> <element ref="xkms:KeyInfo" minOccurs="0"/> <element ref="xkms:KeyUsage" minOccurs="0" maxOccurs="3"/> <element ref="xkms:UseKeyWith" minOccurs="0" maxOccurs="unbounded"/> <element ref="xkms:PolicyIdentifier" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribute name="Id" type="ID" use="optional"/> </complexType> <!-- /KeyBindingAbstractType--> <!-- PolicyIdentifier --> <element name="PolicyIdentifier" type="xkms:PolicyIdentifierType"/> <complexType name=" PolicyIdentifierType"> <attribute name="Policy" type="anyURI"/> </complexType> <!-- /PolicyIdentifier -->
Received on Wednesday, 25 September 2002 17:06:46 UTC