If a element is referred to first by SchemaRefs the document is assumed to be valid against the Schemas first inside In both cases, the remaining schemas may occur in any order and are used Schema Schemas. either directly or indirectly by the first schema. If present, the server MUST use the schemas to identify the ID attributes and MAY also perform complete validation against the schemas. XML Syntax XML schema snippet defining DocumentBaseType: <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> Note: It is recommended to use xml:id as defined in [xml:id] as id in the payload referenced by a <ds:Reference>, because the schema then does not have to be supplied for identifying the ID attributes. JSON Syntax Element name mapping table: Element JSON member name ID ID RefURI refURI RefType refType SchemaRefs schemaRefs Type DocumentType The element contains the following element (in addition to the common ones listed in DocumentType section 2.1.1): [Required] Base64Data This element contains a base64 encoding of arbitrary data. The type of data is specified by its MimeType attribute. If the content of is expected to be XML (e.g. required by the usage context) the Base64Data decoded data will to be parsed. If in this case the content is not parseable XML data then the server MUST return a (section 2.6) issuing a of qualified by a Result ResultMajor RequesterError of ResultMinor NotParseableXMLDocument. For XML content the server MUST use the referred by for validation if specified. Schema SchemaRefs XML Syntax XML schema snippet defining DocumentType:
If a Schemas element is referred to first by SchemaRefs the document is assumed to be valid against the first Schema inside Schemas. In both cases, the remaining schemas may occur in any order and are used either directly or indirectly by the first schema. If present, the server MUST use the schemas to identify the ID attributes and MAY also perform complete validation against the schemas. XML Syntax XML schema snippet defining DocumentBaseType: <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> Note: It is recommended to use xml:id as defined in [xml:id] as id in the payload referenced by a <ds:Reference>, because the schema then does not have to be supplied for identifying the ID attributes. JSON Syntax Element name mapping table: Element JSON member name ID ID RefURI refURI RefType refType SchemaRefs schemaRefs Type DocumentType The DocumentType element contains the following element (in addition to the common ones listed in section 2.1.1): Base64Data [Required] This element contains a base64 encoding of arbitrary data. The type of data is specified by its MimeType attribute. If the content of Base64Data is expected to be XML (e.g. required by the usage context) the data will to be parsed. If in this case the content is not parseable XML data then the server MUST return a Result (section 2.6) issuing a ResultMajor of RequesterError qualified by a ResultMinor of NotParseableXMLDocument. For XML content the server MUST use the Schema referred by SchemaRefs for validation if specified. XML Syntax XML schema snippet defining DocumentType: decoded
dss-core-v2.0-wd01-2017-05-02_2017-05-02.docx