OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: FW: schema




-----Original Message-----
From: Nick Pope [mailto:nick.pope@compliantsoftware.com]
Sent: 03 October 2005 17:13
To: OASIS DSS TC
Subject: FW: schema



> > - Schema

I'd go for this version suggested by Tommy with minor amendments and a
reuse of Document as an XMLSchema is itself an xml document.
A Document should indicate what schemas it depends on via a uri and
Schemas themselves can depend on other Schemas via an uri and those can
be identified by the namespace URI. Hence the SchemaRefs in
documentBasetype are thus redundant, how ever they can be understood as
a hint (shortcut) for efficient schema retrieval, but are clearly optional.

<xs:element name="Document" type="dss:DocumentType"/>
<xs:complexType name="DocumentType">
<xs:complexContent>
<xs:extension base="dss:DocumentBaseType">
<xs:choice>
<xs:element name="InlineXML" type="dss:InlineXMLType"/>
<xs:element name="Base64XML" type="xs:base64Binary"/>
<xs:element name="EscapedXML" type="xs:string"/>
<xs:element ref="dss:Base64Data"/>
</xs:choice>
</xs:extension>
</xs:complexContent>
</xs:complexType>

<xs:element name="Schema" type="dss:DocumentType"/>

Some suggestions for explanatory text for Schema :

RefUri: This uri if present MUST match the targetNamespace of the
contained Schema if present otherwise the uri extracted from the
targetNamespace is used.

Base64Data can be used for other not yet defined forms of verification
for CMS or whatever or an error can be thrown.

<xs:element name="Schemas" type="dss:SchemasType"/>
<xs:complexType name="SchemasType">
<xs:sequence>
<xs:element ref="dss:Schema" minOccurs="1" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="ID" type="xs:ID" use="required"/>
</xs:complexType>

<xs:complexType name="DocumentBaseType" abstract="true">
<xs:attribute name="ID" type="xs:ID" use="optional"/>
<xs:attribute name="RefURI" type="xs:anyURI" use="optional"/>
<xs:attribute name="RefType" type="xs:anyURI" use="optional"/>
<xs:attribute name="SchemaRefs" type="xs:IDREFS" use="optional"/>
</xs:complexType>

Amended Text for 2.5.1 Type DocumentBaseType:

...

SchemaRefs [Optional]

This may be used when the document contains XML documents or signatures.
It transfers an XML Schema [Schema1] which gives the ID attributes of
elements within the input document, which may be necessary if the
included signatures’ <ds:Reference> elements use XPointer expressions or
<ds:Transforms> require it. Referred <Schemas>, <Schema> or combinations
of those are to be used during parsing in sections 2.5.2, 3.3.1 1.a and
4.3 and for XPath evaluation in sections 2.6, 3.5.7, 4.3.1 if they are
supplied.
If anything else but <Schemas>, <Schema> are referred to from here the
server MUST report an Error.
If a referred Schema is not used by the document this MAY be ignored or
reported to the client in the <Result>/<ResultMessage>.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]