ISO/IECJTC1/SC29
Date:2006-12-5
ISO/IECFCD21000-14
ISO/IECJTC1/SC29/WG11
Secretariat:ANSI
Information Technology— Multimedia framework (MPEG-21)— Part14: Conformance Testing
Technologie de l'Information— Cadre de Multimedia (MPEG-21)— Partie14: Conformance Testing
Warning
This document is not an ISO International Standard. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an International Standard.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.
ISO/IECFCD21000-14
Copyright notice
This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as permitted under the applicable laws of the user's country, neither this ISO draft nor any extract from it may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, photocopying, recording or otherwise, without prior written permission being secured.
Requests for permission to reproduce should be addressed to either ISO at the address below or ISO's member body in the country of the requester.
ISO copyright office
Case postale 56CH-1211 Geneva 20
Tel.+ 41 22 749 01 11
Fax+ 41 22 749 09 47
Web
Reproduction may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
ContentsPage
Foreword......
Introduction......
1Scope......
2Normative references......
3DID Conformance......
3.1DIDL Document Conformance:......
3.2DIDL Parser Conformance......
4DII Conformance......
4.1Digital Item Identification Document Conformance:
4.2Digital Item Identification Parser Conformance......
5IPMP Components Conformance
5.1Digital Item Declaration Document Conformance:
5.2IPMP Parser Conformance......
6REL Conformance......
6.1Rights Expression Conformance......
6.1.1General
6.1.2Rules extracted from subclause 6.3 of ISO/IEC 21000-5
6.1.3Rules extracted from subclauses 6.5.2 and 6.6 of ISO/IEC 21000-5
6.1.4Rules extracted from subclause 7.4.1 of ISO/IEC 21000-5
6.1.5Rules extracted from subclause 7.3.6 of ISO/IEC 21000-5
6.2REL Parser Conformance......
7RDD Conformance......
8DIA Conformance......
8.1DIA Description Conformance......
8.2Bitstream Syntax Schema Conformance......
8.3DIA Parser Conformance......
8.4DIA BintoBSD Parser Conformance......
8.5DIA BSDtoBin Parser Conformance......
8.6DIA gBSDtoBin Parser Conformance......
9File Format Conformance......
9.1Introduction......
9.2Process......
9.3Areas tested......
9.4File Documentation......
10DIP Conformance......
10.1Introduction......
10.2DIP schema conformance......
10.2.1Introduction......
10.2.2Testing DIP schema conformance......
10.3DIP engine conformance......
10.3.1Introduction......
10.3.2Testing DIP engine conformance......
10.4DIML syntax conformance......
10.4.1Introduction......
10.4.2Testing DIML syntax conformance......
10.5DIM engine conformance......
10.5.1Introduction......
10.5.2DIBOs with non-deterministic results......
10.5.3Testing DIM engine conformance......
10.6J-DIXO conformance......
10.6.1Introduction......
10.6.2J-DIXO inclusion in DID Conformance......
10.6.3J-DIXO conformance......
11DIP Amd/1 Conformance......
11.1Terminal conformance: C++ binding implementation
11.2C++ executable conformance
12Event Reporting Conformance......
12.1Event Report Request Description Conformance......
12.2Event Report Description Conformance......
12.3Event Report Request Parser Conformance......
12.4Event Report Parser Conformance......
12.5Draft List of Conformance Tests......
13Conformance for Binary Format......
14Conformance for Fragment Identification......
14.1Introduction......
14.2Syntax Conformance......
14.3FID Parser conformance......
14.4Logical Model conformance......
14.5Logical Model Parser conformance......
15Annex A – Tests for DIDL Documents......
15.1Test 1 Explanation: This test is for….......
15.1.1XML declaration......
15.1.2Validation result......
15.2Test 2 Explanation: This test is for….......
15.2.1XML declaration......
15.2.2Validation result......
15.3Test 3 Explanation: This test is for….......
15.3.1XML declaration......
15.3.2Validation result......
15.4Test 4 Explanation: This test is for….......
15.4.1XML declaration......
15.4.2Validation result......
15.5Test 5 Explanation: This test is for….......
15.5.1XML declaration......
15.5.2Validation result......
15.6Test 6 Explanation: This test is for….......
15.6.1XML declaration......
15.6.2Validation result......
15.7Test 7 Explanation: This test is for….......
15.7.1XML declaration......
15.7.2Validation result......
15.8Test 8 Explanation: This test is for….......
15.8.1XML declaration......
15.8.2Validation result......
15.9Test 9 Explanation: This test is for….......
15.9.1XML declaration......
15.9.2Validation result......
15.10Test 10 Explanation: This test is for….......
15.10.1XML declaration......
15.10.2Validation result......
15.11Test 11 Explanation: This test is for….......
15.11.1XML declaration......
15.11.2Validation result......
15.12Test 12......
15.12.1XML declaration......
15.12.2Validation result......
15.13Test 13......
15.13.1XML declaration......
15.13.2Validation result......
15.14Test 14......
15.14.1XML declaration......
15.14.2Validation result......
15.15Test 15......
15.15.1XML declaration......
15.15.2Validation result......
15.16Test 16......
15.16.1XML declaration......
15.16.2Validation result......
15.17Test 17......
15.17.1XML declaration......
15.17.2Validation result......
15.18Test 18......
15.18.1XML declaration......
15.18.2Validation result......
15.19Test 19......
15.19.1XML declaration......
15.19.2Validation result......
15.20Test 20......
15.20.1XML declaration......
15.20.2Validation result......
15.21Test 21......
15.21.1XML declaration......
15.21.2Validation result......
15.22Test 22......
15.22.1XML declaration......
15.22.2Validation result......
15.23Test 23......
15.23.1XML declaration......
15.23.2Validation result......
15.24Test 24......
15.24.1XML declaration......
15.24.2Validation result......
15.25Test 25......
15.25.1XML declaration......
15.25.2Validation result......
15.26Test 26......
15.26.1XML declaration......
15.26.2Validation result......
15.27Test 27......
15.27.1XML declaration......
15.27.2Validation result......
15.28Test 28......
15.28.1XML declaration......
15.28.2Validation result......
16Annex B – Tests for Digital Item Identification Documents......
16.1Test 1......
16.1.1XML declaration......
16.1.2Validation result......
16.2Test 2......
16.2.1XML declaration......
16.2.2Validation result......
16.3Test 3......
16.3.1XML declaration......
16.3.2Validation result......
16.4Test 4......
16.4.1XML declaration......
16.4.2Validation result......
17Annex C – Tests for DIDL Documents with protected elements......
17.1Test 1......
17.1.1XML declaration......
17.1.2Validation result......
17.2Test 2......
17.2.1XML declaration......
17.2.2Validation result......
17.3Test 3......
17.3.1XML declaration......
17.3.2Validation result......
17.4Test 4......
17.4.1XML declaration......
17.4.2Validation result......
17.5Test 5......
17.5.1XML declaration......
17.5.2Validation result......
18Annex D – Tests for Rights Expressions......
18.1Test 1......
18.1.1XML declaration......
18.1.2Validation result......
18.2Test 2......
18.2.1XML declaration......
18.2.2Validation result......
18.3Test 3......
18.3.1XML declaration......
18.3.2Validation result......
18.4Test 4......
18.4.1XML declaration......
18.4.2Validation result......
18.5Test 5......
18.5.1XML declaration......
18.5.2Validation result......
18.6Test 6......
18.6.1XML declaration......
18.6.2Validation result......
18.7Test 7......
18.7.1XML declaration......
18.7.2Validation result......
18.8Test 8......
18.8.1XML declaration......
18.8.2Validation result......
18.9Test 9......
18.9.1XML declaration......
18.9.2Validation result......
18.10Test 10......
18.10.1XML declaration......
18.10.2Validation result......
18.11Test 11......
18.11.1XML declaration......
18.11.2Validation result......
18.12Test 12......
18.12.1XML declaration......
18.12.2Validation result......
18.13Test 13......
18.13.1XML declaration......
18.13.2Validation result......
18.14Test 14......
18.14.1XML declaration......
18.14.2Validation result......
18.15Test 15......
18.15.1XML declaration......
18.15.2Validation result......
18.16Test 16......
18.16.1XML declaration......
18.16.2Validation result......
18.17Test 17......
18.17.1XML declaration......
18.17.2Validation result......
18.18Test 18......
18.18.1XML declaration......
18.18.2Validation result......
18.19Test 19......
18.19.1XML declaration......
18.19.2Validation result......
18.20Test 20......
18.20.1XML declaration......
18.20.2Validation result......
18.21Test 21......
18.21.1XML declaration......
18.21.2Validation result......
18.22Test 22......
18.22.1XML declaration......
18.22.2Validation result......
18.23Test 23......
18.23.1XML declaration......
18.23.2Validation result......
18.24Test 24......
18.24.1XML declaration......
18.24.2Validation result......
18.25Test 25......
18.25.1XML declaration......
18.25.2Validation result......
18.26Test 26......
18.26.1XML declaration......
18.26.2Validation result......
18.27Test 27......
18.27.1XML declaration......
18.27.2Validation result......
18.28Test 28......
18.28.1XML declaration......
18.28.2Validation result......
18.29Test 29......
18.29.1XML declaration......
18.29.2Validation result......
19Annex E – Tests for DIA Descriptions......
19.1gBSD test streams......
19.1.1Example 1......
19.1.2Example 2......
19.1.3Example 3......
19.1.4Example 4......
19.1.5Example 5......
19.1.6Example 6......
19.1.7Example 7......
19.1.8Example 8......
20Annex F – tests for File Format......
20.1a12......
20.211-did.m21......
21Annex G – tests for DIP......
21.1Tests for DIP engine......
21.2Tests for DIM engine......
21.3Tests for J-DIXO invocation......
21.4Tests for J-DIBO implementation......
22Annex H – tests for DIP Amd/1......
22.1C++ data type bindings for DIML object types.......
22.2C++ DIBO factory interface.......
22.3C++ global environment interface.......
22.4C++ interface bindings for DIBOs.......
23Annex I – tests for ER......
24Annex J – tests for FID......
24.1Test Fragment Identifiers......
24.1.1First test suite......
24.1.2Second test suite......
24.1.3Third test suite......
24.2Test Logical Model Schemas......
24.2.1Test 1......
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IECJTC1.
International Standards are drafted in accordance with the rules given in the ISO/IECDirectives, Part2.
The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75% of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC2100014 was prepared by Joint Technical Committee ISO/IECJTC1, Information technology, Subcommittee SC29, Multimedia framework (MPEG-21).
ISO/IEC21000 consists of the following parts, under the general title Information Technology— Multimedia framework (MPEG-21):
Part 1: Vision, Technologies and Strategy [Technical Report]
Part 2: Digital Item Declaration
Part 3: Digital Item Identification
Part 4: Intellectual Property Management and Protection Components
Part 5: Rights Expression Language
Part 6: Rights Data Dictionary
Part 7: Digital Item Adaptation
Part 8: Reference Software
Part 9: File Format
Part 10: Digital Item Processing
Part 11: Evaluation Tools for Persistent Association Technologies [Technical Report]
Part 12: Test Bed for MPEG-21 Resource Delivery [Technical Report]
Part 14: Conformance Testing
Part 15: Event Reporting
Part 16: Binary Format
Part 17: Fragment Identification of MPEG Resources
Part 18: Digital Item Streaming
Introduction
ISO/IEC 21000 contains a number of requirements. For any particular conformance point (such as DII Parser or a Rights Expression), only some of the requirements apply. As such, there is a need to specify various conformance points, identify the requirements that apply, and develop a way to ascertain whether a particular artefact (such as a piece of software or hardware or a document) meets all the requirements for a particular conformance point or not. This part of ISO/IEC 21000 is intended to fulfil this need.
©ISO/IEC2006— All rights reserved / 1ISO/IECFCD21000-14
Information Technology— Multimedia framework (MPEG-21)— Part14: Conformance Testing
1Scope
This International Standard specifies conformance points for ISO/IEC 21000. Clause 2 gives the normative references. Clauses 3 through 7 each contain a group of conformance points related to a particular part of ISO/IEC 21000. Each subclause in Clauses 3 through 7 specifies a conformance point. Conformance test cases are provided in Annexes.
2Normative references
The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 21000 (all parts), Information technology – Multimedia framework (MPEG-21)
Namespaces in XML, W3C Recommendation 14 January 1999
Extensible Markup Language (XML) 1.0 (Second Edition) W3C Recommendation, October 6th, 2000
XML Schema Part 1: Structures W3C Recommendation, May 2, 2001
XML Schema Part 2: Datatypes W3C Recommendation, May 2, 2001
XML Information Set, W3C Recommendation 24 October 2001XML Base, W3C Recommendation 27 June 2001
Canonical XML, Version 1.0, W3C Recommendation 15 March 2001
3DID Conformance
The following conformance points are defined:
3.1DIDL Document Conformance:
A DIDL Document is conformant only if
- It is a well-formed XML document that validates against the Digital Item Declaration Language Schema as specified in ISO/IEC 21000-2:2005, and
- All validation rules that are normatively defined in ISO/IEC 21000-2:2005 are met.
NOTE1Conformance of DIDL Documents can be checked by using the normative Digital Item Declaration parser that is part of the ISO/IEC 21000 Reference Software.
NOTE2A DID may contain descriptions defined in other parts of ISO/IEC 21000, such as a DIA description (ISO/IEC 21000-7). The conformance of a DID does not imply the conformance of these included descriptions.
3.2DIDL Parser Conformance
A DIDL Parser is defined as a module that takes a file as input and produces as output either 1 (if the input file is a conformant DIDL Document) or 0 (if the input file is not a conformant DIDL Document).
A DIDL Parser is conformant only if, given the inputs given in Annex B it produces the corresponding outputs from Annex B.
4DII Conformance
The following conformance points are defined:
4.1Digital Item Identification Document Conformance:
A Digital Item Identification Document is conformant only if it is a well-formed XML document that validates against the Digital Item Identification Schema as specified in ISO/IEC 21000-3.
4.2Digital Item Identification Parser Conformance
A Digital Item Identification Parser is defined as a module that takes a file as input and produces as output either 1 (if the input file is a conformant Digital Item Identification Document) or 0 (if the input file is not a conformant Digital Item Identification Document).
A Digital Item Identification Parser is conformant only if, given the inputs given in Annex C it produces the corresponding outputs from Annex C.
5IPMP Components Conformance
The following conformance points are defined:
5.1Digital Item Declaration Document Conformance:
A DIDL document with IPMP DIDL elements is conformant only if
- It is a well-formed XML document that validates against the DIDL Schema, IPMP DIDL Schema, IPMP Information Schema and IPMP General Information Schema as specified in ISO/IEC 21000-4, and
- All validation rules that are normatively defined in ISO/IEC 21000-4 are met, and
- Once unprotected the DIDL document shall be DID Conformant as specified in Clause 3.
5.2IPMP Parser Conformance
An IPMP Parser is defined as a module that takes a file as input and produces as output either 1 (if the input file is a conformant DIDL document with IPMP DIDL elements) or 0 (if the input file is not a conformant DIDL document with IPMP DIDL elements).
An IPMP Parser is conformant only if, given the inputs given in Annex C, it produces the corresponding outputs from Annex C.
6REL Conformance
The following conformance points are defined:
6.1Rights Expression Conformance
6.1.1General
A Rights Expression is conformant only if it meets all the Rights Expression constraints specified in ISO/IEC 21000-5. Some of these constraints are specified in various clauses and subclauses throughout ISO/IEC 21000-5 and many are specified in Annex A (REL Schemas) of ISO/IEC 21000-5. The text in 4.1.2 through 4.1.5 was copied from ISO/IEC 21000-5. The tables in 4.1.2 through 4.1.5 were tabulated from the information in ISO/IEC 21000-5. In the event of discrepancy between 4.1.2 through 4.1.5 and ISO/IEC 21000-5, ISO/IEC 21000-5 is authoritative.
NOTEThe License Validation Rules Checker Reference Software in ISO/IEC 21000-8 checks if an expression that only uses terms from ISO/IEC 21000-5 satisfies all the expression constraints given in ISO/IEC 21000-5.
6.1.2Rules extracted from subclause 6.3 of ISO/IEC 21000-5
The following provisions apply to r:License elements that contain r:LicensePart elements having the r:licensePartId or r:licensePartIdRef attributes.
a)R-REL-2100: An r:LicensePart shall not have both the r:licensePartId attribute and the r:licensePartIdRef attribute.
b)R-REL-2200: For a given r:LicensePartId value v and r:Licensel, l shall not contain more than one r:LicensePart having an r:licensePartId attribute with the value v.
c)R-REL-2300: If an r:LicensePart has an r:licensePartIdRef attribute, then it shall have empty content. As a corollary, types that are derivations of the type r:LicensePart should allow their content to be empty (for otherwise their r:licensePartIdRef attribute shall not be used).
d)If an r:LicenseParta has an r:licensePartIdRef attribute with a certain value v, then there shall exist some (other) r:LicensePartb in the same r:License as a such that all of the following are true:
1)R-REL-2401:b has an r:licensePartId attribute with value v,
2)R-REL-2402: the expanded element name of b exactly matches that of a, and
3)R-REL-2403:b is not an ancestor of a.
e)With the exception of signature verification and License issuer resolution (see 6.4), the following two processing steps shall be carried out before the other License processing steps defined in this part of ISO/IEC 21000. In particular, they shall be carried out before the evaluation of Variable references or the testing of equality.
1)If an r:LicenseParta has an r:licensePartIdRef attribute with a certain value v, and b is the r:LicensePart in the same r:License as a that has an r:licensePartId attribute with value v, then the semantics of the r:License containing a and b are as if
i)a were removed from the r:License and replaced with an element that is Equal to b,
ii)the r:licensePartId attributes were removed from and all of its descendants, and
iii)any preserved attributes that has were removed from , and any preserved attributes that a has were added to , where here a preserved attribute is
I)any attribute of type xsd:ID or
II)any attribute for which id is the local part of its Qualified Name.
2)If an r:License contains no r:LicensePartelements with an r:licensePartIdRef attribute, then the semantics of that r:License are as if the r:licensePartId attribute were removed from all r:LicensePart elements in that r:License with an r:licensePartId attribute.
NOTE1It is the intent of e)II) to enable the useful definition and incorporation of other identification systems on r:LicensePart elements beyond the document-global xsd:ID-typed identifiers.
NOTE2Circular references such as that shown in Example 1 are not allowed because, after one application of provision e), the semantics will be as shown in Example 2, which violates provision d)3).
EXAMPLE1
<r:license>
<r:grantGroup licensePartId="x">
<r:grantGroup licensePartIdRef="y"/>
</r:grantGroup>
<r:grantGroup licensePartId="y">
<r:grantGroup licensePartIdRef="x"/>
</r:grantGroup>
</r:license>
EXAMPLE2
<r:license>
<r:grantGroup licensePartId="x">
<r:grantGroup>
<r:grantGroup licensePartIdRef="x"/>
</r:grantGroup>
</r:grantGroup>
<r:grantGroup licensePartId="y">
<r:grantGroup>
<r:grantGroup licensePartIdRef="y"/>
</r:grantGroup>
</r:grantGroup>
</r:license>
6.1.3Rules extracted from subclauses 6.5.2 and 6.6 of ISO/IEC 21000-5
Let a be an r:LicensePart. If a/@r:varRef exists, then R-REL-3101:a shall have empty content and R-REL-3102: the value of a/@r:varRef shall be the name of some Variable whose scope includes a.
R-REL-3200: If a conceptually abstract element appears in an r:License, it shall either have a type that is not conceptually abstract or appear in the form of a Variable reference, as described in 6.5.2.
R-REL-3200 (continued): If a conceptually abstract type appears in an r:License, it shall belong to an element that either is not conceptually abstract or appears in the form of a Variable reference, as described in 6.5.2.
The following is a list of the conceptually abstract elements and types.
Conceptually abstract elements / Conceptually abstract typesr:licensePart
r:principal
r:right
r:resource
r:condition
r:anXmlPatternAbstract
r:principalPatternAbstract
r:rightPatternAbstract
r:resourcePatternAbstract
r:conditionPatternAbstract
r:dcConstraint
r:trustRoot
r:serviceDescription
r:propertyAbstract
sx:name / r:LicensePart
r:Principal
r:Right
r:Resource
r:Condition
r:AnXmlPatternAbstract
r:PrincipalPatternAbstract
r:RightPatternAbstract
r:ResourcePatternAbstract
r:ConditionPatternAbstract
r:DcConstraint
r:TrustRoot
r:ServiceDescription
r:PropertyAbstract
sx:Name
sx:StatefulCondition
6.1.4Rules extracted from subclause 7.4.1 of ISO/IEC 21000-5
R-REL-4100: If the syntax of a particular derivation of the type r:LicensePart declares its content model as optional, the semantics of that optional content model, unless specified otherwise, is that it shall not be omitted in an r:LicensePart of that derivation unless that r:LicensePart has an r:licensePartIdRef or r:varRef attribute.
The following is a list of types that cannot be empty unless used with r:licensePartIdRef or r:varRef.
Types / Elements using those types directlyr:Datum
r:DepthConstraint
r:DigitalResource
r:ExerciseMechanism
r:ExistsRight
r:Fulfiller
r:Grant
r:GrantGroup
r:GrantGroupPattern
r:GrantPattern
r:KeyHolder
r:PatternFromLicensePart
r:PrerequisiteRight
r:PropertyPossessor
r:Revocable
r:RevocationFreshness
r:ServiceReference
r:TrustedRootGrants
r:TrustedRootIssuers
sx:CallForCondition
sx:FeeFlat
sx:FeeMetered
sx:FeePerInterval
sx:FeePerUse
sx:FeePerUsePrePay
sx:Rate
sx:StateReferenceValuePattern
sx:Territory
sx:Uddi
sx:ValidityIntervalDurationPattern
sx:ValidityIntervalStartsNow
sx:ValidityTimePeriodic
sx:WsdlAddress
sx:WsdlComplete
anonymous type defined in mx:complement
mx:Destination
mx:DiCriteria
mx:DiItemReference
mx:DiPartOf
mx:DiReference
mx:IsMarked
mx:Mark
mx:ResourceSignedBy
mx:Source
mx:Transaction / r:datum
r:depthConstraint
r:digitalResource
and sx:WsdlAddress/sx:kind/sx:wsdl
and sx:WsdlComplete/sx:wsdl
r:exerciseMechanism
r:existsRight
r:fulfiller
r:grant
r:grantGroup
r:grantGroupPattern
r:grantPattern
r:keyHolder
r:patternFromLicensePart
r:prerequisiteRight
r:propertyPossessor
r:revocable
r:revocationFreshness
r:serviceReference
r:trustedRootGrants
r:trustedRootIssuers
sx:callForCondition
sx:feeFlat
sx:feeMetered
sx:feePerInterval
sx:feePerUse
sx:feePerUsePrePay
sx:rate
sx:stateReferenceValuePattern
sx:territory
sx:uddi
sx:validityIntervalDurationPattern
sx:validityIntervalStartsNow
sx:validityTimePeriodic
sx:wsdlAddress
sx:wsdlComplete
mx:complement
mx:destination
mx:diCriteria
mx:diItemReference
mx:diPartOf
mx:diReference
mx:isMarked
mx:mark
mx:resourceSignedBy
mx:source
mx:transaction
The following is a list of types that declare an optional content model but specify an exception to the rule of 7.4.1.
Types / Elements using those types directlyanonymous type defined in mx:union
anonymous type defined in mx:intersection
mx:RequiredAttributeChanges
mx:ProhibitedAttributeChanges / mx:union
mx:intersection
mx:requiredAttributeChanges
mx:prohibitedAttributeChanges
6.1.5Rules extracted from subclause 7.3.6 of ISO/IEC 21000-5
R-REL-5100: An r:EncryptedContent shall have an xenc:Type attribute with a value of
6.2REL Parser Conformance
An REL Parser is defined as a module that takes a file as input and produces as output either 1 (if the input file is a conformant Rights Expression) or 0 (if the input file is not a conformant Rights Expression).
An REL Parser is conformant only if, given the inputs given in Annex D it produces the corresponding outputs from Annex D.
7RDD Conformance
RDD Conformance is not defined at this time because there is no syntax.
8DIA Conformance
The following conformance points are defined:
8.1DIA Description Conformance
A DIA Description is conformant only if it is well-formed XML and meets all the description constraints specified in ISO/IEC 21000-7. These constraints are specified in text and schemas in various clauses and subclauses throughout ISO/IEC 21000-7.
In particular, when the DIA Description is a Bitstream Syntax Description (BSD), the following additional constraint applies: a BSD is conformant only if it is BSDL-1 valid, as specified in the sub clause 8.3.1.5 of ISO/IEC 21000-7.
8.2Bitstream Syntax Schema Conformance
A Bitstream Syntax Schema (BS Schema) is conformant only if it is BSDL-2 valid, as specified in the sub clause 8.4.6 of ISO/IEC 21000-7.
8.3DIA Parser Conformance
A DIA Parser is defined as a module that takes a file as input and produces as output either 1 (if the input file is a conformant DIA Description) or 0 (if the input file is not a conformant DIA Description).
A DIA Parser is conformant only if, given the inputs given in Annex E it produces the corresponding outputs from Annex E.