ISO/IEC 23005-7:2014

Information technology — Media context and control — Part 7: Conformance and reference software

ISO/IEC 23005-7:2014 specifies the conformance and reference software implementing the normative clauses of all parts of ISO/IEC 23005. The information provided is applicable for determining the reference software modules available for the parts of ISO/IEC 23005, understanding the functionality of the available reference software modules, and utilizing the available reference software modules. The available reference software modules are specified in the form of application programming interfaces (API) according to ISO/IEC 23006-1. Furthermore, ISO/IEC 23005-7:2014 provides means for conformance testing, i.e. bit-streams - XML descriptions - that conform or do not conform to the normative clauses of the other parts of ISO/IEC 23005 and informative descriptions thereof.

Technologies de l'information — Contrôle et contexte de supports — Partie 7: Conformité et logiciel de référence

General Information

• Status: Withdrawn
• Publication Date: 12-Jan-2014
• Withdrawal Date: 12-Jan-2014
• ICS: 35.040 - Information coding
• ICS: 35.040.40 - Coding of audio, video, multimedia and hypermedia information
• Technical Committee: ISO/IEC JTC 1/SC 29 - Coding of audio, picture, multimedia and hypermedia information
• Drafting Committee: ISO/IEC JTC 1/SC 29 - Coding of audio, picture, multimedia and hypermedia information
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 06-Jan-2017
• Completion Date: 14-Feb-2026

Relations

• Revised: ISO/IEC 23005-7:2017 - Information technology — Media context and control — Part 7: Conformance and reference software
• Effective Date: 01-Nov-2014
• Revises: ISO/IEC 23005-7:2011 - Information technology — Media context and control — Part 7: Conformance and reference software
• Effective Date: 06-Jul-2012

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 23005-7
Second edition
2014-01-15
Information technology — Media context
and control —
Part 7:
Conformance and reference software
Technologies de l'information — Contrôle et contexte de supports —
Partie 7: Conformité et logiciel de référence

Reference number
©
ISO/IEC 2014
©  ISO/IEC 2014
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any
means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission.
Permission can be requested from either ISO at the address below or ISO’s member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2014 – All rights reserved

Contents Page
Foreword . iv
Introduction . v
1 Scope . 1
2 Normative references . 1
3 Terms, definitions, and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Abbreviated terms . 2
4 Reference software for ISO/IEC 23005 . 2
4.1 Introduction . 2
4.2 ISO/IEC 23005-2 APIs . 3
4.3 ISO/IEC 23005-3 APIs . 4
4.4 ISO/IEC 23005-4 APIs . 4
4.5 ISO/IEC 23005-5 APIs . 5
4.6 Binary representation APIs for ISO/IEC 23005 . 6
5 Conformance for ISO/IEC 23005 . 7
5.1 Introduction . 7
5.2 Rule-based Conformance for ISO/IEC 23005 . 7
5.3 Schema-based Conformance for ISO/IEC 23005 . 42
Bibliography . 46

© ISO/IEC 2014 – All rights reserved iii

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/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
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/IEC 23005-7 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia information.
This second edition cancels and replaces the first edition (ISO/IEC 23005-7:2011), which has been technically
revised.
ISO/IEC 23005 consists of the following parts, under the general title Information technology — Media context
and control:
 Part 1: Architecture
 Part 2: Control information
 Part 3: Sensory information
 Part 4: Virtual world object characteristics
 Part 5: Data formats for interaction devices
 Part 6: Common types and tools
 Part 7: Conformance and reference software
iv © ISO/IEC 2014 – All rights reserved

Introduction
This part of ISO/IEC 23005 specifies the conformance and reference software. The conformance and
reference software of ISO/IEC 23005 serves three main purposes:
 validation of the written specification of the several parts of ISO/IEC 23005;
 clarification of the written specification of the several parts of ISO/IEC 23005; and
 conformance testing for checking interoperability for the various applications against the reference
software which aims to be compliant with ISO/IEC 23005.

© ISO/IEC 2014 – All rights reserved v

INTERNATIONAL STANDARD ISO/IEC 23005-7:2014(E)

Information technology — Media context and control —
Part 7:
Conformance and reference software
1 Scope
This part of ISO/IEC 23005 specifies the conformance and reference software implementing the normative
clauses of all parts of ISO/IEC 23005. The information provided is applicable for determining the reference
software modules available for the parts of ISO/IEC 23005, understanding the functionality of the available
reference software modules, and utilizing the available reference software modules. The available reference
software modules are specified in the form of application programming interfaces (API) according to
ISO/IEC 23006-1.
Furthermore, this part of ISO/IEC 23005 provides means for conformance testing, i.e. bit-streams – XML
descriptions – that conform or do not conform to the normative clauses of the other parts of ISO/IEC 23005
and informative descriptions thereof.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 19757-3, Information technology — Document Schema Definition Languages (DSDL) — Part 3:
Rule-based validation — Schematron
ISO/IEC 23005-2, Information technology — Media context and control — Control information
ISO/IEC 23005-3, Information technology — Media context and control — Sensory information
ISO/IEC 23005-4, Information technology — Media context and control — Virtual world object characteristics
ISO/IEC 23005-5, Information technology — Media context and control — Data formats for interaction devices
ISO/IEC 23005-6, Information technology — Media context and control — Common types and tools
ISO/IEC 23006-1, Information technology — Multimedia service platform technologies — Architecture
3 Terms, definitions, and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 23006-1 apply.
© ISO/IEC 2014 – All rights reserved 1

3.2 Abbreviated terms
For the purposes of this document, the abbreviated terms given in the following apply.
API application programming interface
CIM control information metadata
MXM MPEG extensible middleware
SEM sensory effect metadata
VWOC virtual world object characteristics
IIM interaction information metadata
4 Reference software for ISO/IEC 23005
4.1 Introduction
This Clause specifies the reference software for ISO/IEC 23005. The ISO/IEC 23005 reference software is
written in Java and follows following package structure:
Name Definition
org Java package name for reference software provided by organizations
such as ISO/IEC, W3C, or similar.
org.iso
Java package name for reference software provided by ISO/IEC.
org.iso.mpeg Java package name for reference software provided by ISO/IEC JTC
1/SC 29/WG 11.
org.iso.mpeg.mpegv
Java package name for reference software provided in the course of the
development of ISO/IEC 23005.
NOTE 1 Subsequent packages for the individual ISO/IEC 23005 parts use the
uncapitalized abbreviations as defined in 3.2, e.g.,
 org.iso.mpeg.mpegv.cidl, org.iso.mpeg.mpegv.dcdv,
org.iso.mpeg.mpegv.sapv, org.iso.mpeg.mpegv.scdv
and org.iso.mpeg.mpegv.sepv for ISO/IEC 23005-2,
 org.iso.mpeg.mpegv.sedl and org.iso.mpeg.mpegv.sev
for ISO/IEC 23005-3,
 org.iso.mpeg.mpegv.vwoc for ISO/IEC 23005-4, or
 org.iso.mpeg.mpegv.iidl, org.iso.mpeg.mpegv.dcv and
org.iso.mpeg.mpegv.siv for ISO/IEC 23005-5.
 org.iso.mpeg.mpegv.ct for ISO/IEC 23005-6.
NOTE 2 Code included within these packages can be generated automatically by
using tools such as JAXB.
2 © ISO/IEC 2014 – All rights reserved

Name Definition
org.iso.mpeg.mpegv.{part}
Java package name for binary representation of reference software
.binary provided in the course of the development of ISO/IEC 23005.
the {part} placeholder is replaced by the component of each part, i.e.,
cidl, dvdv, sapv, scdv, sepv, sedl, sev, vwoc, iidl, dcv, siv and
ct.
org.iso.mpeg.mxm
Java package name for reference software provided in the course of the
development of ISO/IEC 23006-1. The actual API is defined within this
package.
4.2 ISO/IEC 23005-2 APIs
4.2.1 Introduction
This clause specifies the API to the ISO/IEC 23005-2 reference software. The API is defined in Java and
follows following package structure:
Name Definition
org.iso.mpeg.mxm.engine.cimengine
Java package name for API to the ISO/IEC 23005-2 reference
software.
4.2.2 CIM engine
The CIMEngine interface defines the methods for operating over data structures as defined within ISO/IEC
23005-2. Classes implementing the CIM engine interface act as factories creating instances of classes
performing the following functionalities:
 Classes to create data structures, by means of the CIM creation engine
 Classes to access data contained in data structures, by means of CIM parser engine

4.2.3 CIM creation
Creating CIM structures involves the following interfaces:
 CIMCreator: an interface defining the methods to create CIM structures.

4.2.4 CIM access
Accessing CIM structures involves the following interfaces:
 CIMParser: an interface defining the methods to parse CIM structures.

© ISO/IEC 2014 – All rights reserved 3

4.3 ISO/IEC 23005-3 APIs
4.3.1 Introduction
This clause specifies the API to the ISO/IEC 23005-3 reference software. The API is defined in Java and
follows following package structure:
Name Definition
org.iso.mpeg.mxm.engine.semengine
Java package name for API to the ISO/IEC 23005-3 reference
software.
4.3.2 SEM engine
The SEMEngine interface defines the methods for operating over data structures as defined within ISO/IEC
23005-3. Classes implementing the SEM engine interface act as factories creating instances of classes
performing the following functionalities:
 Classes to create data structures, by means of the SEM creation engine.
 Classes to access data contained in data structures, by means of SEM parser engine.

4.3.3 SEM creation
Creating SEM structures involves the following interfaces:
 SEMCreator: an interface defining the methods to create SEM structures.

4.3.4 SEM access
Accessing SEM structures involves the following interfaces:
 SEMParser: an interface defining the methods to parse SEM structures.

4.4 ISO/IEC 23005-4 APIs
4.4.1 Introduction
This clause specifies the API to the ISO/IEC 23005-4 reference software. The API is defined in Java and
follows following package structure:
Name Definition
org.iso.mpeg.mxm.engine.vwocengine
Java package name for API to the ISO/IEC 23005-4
reference software.
4 © ISO/IEC 2014 – All rights reserved

4.4.2 VWOC engine
The VWOCEngine interface defines the methods for operating over data structures as defined within ISO/IEC
23005-4. Classes implementing the VWOC engine interface act as factories creating instances of classes
performing the following functionalities:
 Classes to create data structures, by means of the VWOC creation engine.
 Classes to access data contained in data structures, by means of VWOC parser engine.

4.4.3 VWOC creation
Creating VWOC structures involves the following interfaces:
 VWOCCreator: an interface defining the methods to create VWOC structures.

4.4.4 VWOC access
Accessing VWOC structures involves the following interfaces:
 VWOCParser: an interface defining the methods to parse VWOC structures.

4.5 ISO/IEC 23005-5 APIs
4.5.1 Introduction
This clause specifies the API to the ISO/IEC 23005-5 reference software. The API is defined in Java and
follows following package structure:
Name Definition
org.iso.mpeg.mxm.engine.iidengine
Java package name for API to the ISO/IEC 23005-5 reference
software.
4.5.2 IID engine
The IIDEngine interface defines the methods for operating over data structures as defined within ISO/IEC
23005-2. Classes implementing the IID engine interface act as factories creating instances of classes
performing the following functionalities:
 Classes to create data structures, by means of the IID creation engine
 Classes to access data contained in data structures, by means of IID parser engine

4.5.3 IID creation
Creating IID structures involves the following interfaces:
© ISO/IEC 2014 – All rights reserved 5

 IIDCreator: an interface defining the methods to create IID structures.

4.5.4 IID access
Accessing IID structures involves the following interfaces:
 IIDParser: an interface defining the methods to parse IID structures.

4.6 Binary representation APIs for ISO/IEC 23005
4.6.1 Introduction
This clause specifies the API to the ISO/IEC 23005 reference software for binary representation. The API is
defined in Java and follows following package structure:
Name Definition
org.iso.mpeg.mpegv.binary.core
Java package name for API to the ISO/IEC 23005 reference
software for binary representation.

4.6.2 BinaryIO
The BinaryIO interface defines the methods for operating over data structures as defined within ISO/IEC
23005. Classes implementing the BinaryIO interface act as factories creating instances of classes performing
the following functionalities:
 Classes to generate a binary structure from a MXM object tree, by means of the construct binary structure
function.
 Classes to generate a binary file from a binary structure, by means of the write binary function.
 Classes to generate a binary structure from a binary structure, by means of the read binary function.
 Classes to restore a MXM object tree from a binary structure, by means of the create MXM object
function.
4.6.3 DefaultBinaryIO
DefaultBinaryIO class defines function “Encode” and “Decode”. Root elements of other parts (e.g. Part 2, 3, 4)
can be extended from this DefaultBinaryIO class. DefaultBinaryIO involves the following functions:
 encode: a function defining the methods to create binary file from a MXM object tree.
 decode: a function defining the methods to restore a MXM object tree from a binary file.

6 © ISO/IEC 2014 – All rights reserved

5 Conformance for ISO/IEC 23005
5.1 Introduction
This clause defines conformance for ISO/IEC 23005. A bit-stream is compliant to ISO/IEC 23005 if it conforms
to the conformance definitions specified in 5.2 and 5.3.
5.2 Rule-based Conformance for ISO/IEC 23005
5.2.1 Introduction
This clause defines a validation schema based on ISO/IEC 19757-3 to check the conformance bit-streams –
XML descriptions – that conform or do not conform to the normative clauses of the other parts of ISO/IEC
23005 and descriptions thereof. In particular, the additional validation rules as specified in the other parts of
ISO/IEC 23005 are checked with this validation schema. The actual schema can be found in 5.2.2 and a more
readable version of the rules and assertion messages is provided in 5.2.3. The actual conformance bit-
streams – XML descriptions – are defined in 5.2.4. The actual conformance bit-streams and corresponding
code can be found attached to this document.
For transforming the validation schema according to ISO/IEC 19757-3 and for validating the examples
Saxon [1] is used.
5.2.2 Validation schema
xmlns="http://purl.oclc.org/dsdl/schematron"
xmlns:sedl="urn:mpeg:mpeg-v:2010:01-SEDL-NS"
xmlns:sev="urn:mpeg:mpeg-v:2010:01-SEV-NS"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:si="urn:mpeg:mpeg21:2003:01-DIA-XSI-NS"
xmlns:cidl="urn:mpeg:mpeg-v:2010:01-CIDL-NS"
xmlns:dcdv="urn:mpeg:mpeg-v:2010:01-DCDV-NS"
xmlns:scdv="urn:mpeg:mpeg-v:2010:01-SCDV-NS"
xmlns:sepv="urn:mpeg:mpeg-v:2010:01-SEPV-NS"
xmlns:mpegvct="urn:mpeg:mpeg-v:2010:01-CT-NS"
xmlns:mpeg7="urn:mpeg:mpeg7:schema:2004"
xmlns:dia="urn:mpeg:mpeg21:2003:01-DIA-NS"
xmlns:iidl="urn:mpeg:mpeg-v:2010:01-IIDL-NS"
xmlns:dcv="urn:mpeg:mpeg-v:2010:01-DCV-NS"
xmlns:siv="urn:mpeg:mpeg-v:2010:01-SIV-NS"
queryBinding='xslt' schemaVersion='ISO19757-3'>














Schema for validating SEDL/CIDL/IIDL descriptions


© ISO/IEC 2014 – All rights reserved 7






A minValue shall be less than or equal to a maxValue.







A minValue shall be less than or equal to a maxValue.







A minValue shall be less than or equal to a maxValue.







A minValue shall be less than or equal to a maxValue.







A minValue shall be less than or equal to a maxValue.







A minValue shall be less than or equal to a maxValue.







8 © ISO/IEC 2014 – All rights reserved

A minValue shall be less than or equal to a maxValue.








An XminValue shall be less than or equal to an XmaxValue.



An YminValue shall be less than or equal to an YmaxValue.



A ZminValue shall be less than or equal to a ZmaxValue.








An YawMin shall be less than or equal to an YawMax.



A PitchMin shall be less than or equal to a PitchMax.



A RollMin shall be less than or equal to a RollMax.










The SEM element shall have a timeScale attribute.







© ISO/IEC 2014 – All rights reserved 9


A GroupOfEffects outside of a Declarations shall have a timestamp (i.e.,
pts, ptsDelta, or absTime).



A GroupOfEffects outside of a Declarations shall not have both a pts and
an absTime at the same time.



A GroupOfEffects within a Declarations shall have only a ptsDelta for a
timestamp.








At least activate, duration, or fade shall be defined.



An effect outside of a GroupOfEffects shall have a timestamp (i.e., pts,
ptsDelta, or absTime).



An effect within a GroupOfEffects shall not have a timestamp (i.e., pts,
ptsDelta, or absTime).



If duration is defined activate may not be defined.



If fade and duration are defined activate may not be defined.



If fade is defined intensity-value and intensity-range shall be defined.



10 © ISO/IEC 2014 – All rights reserved

If two (or more) consecutive Effect elements of the same type share the
same timestamp (i.e., pts, ptsDelta, or absTime) and location only the latest in
their order of appearance shall be used.



If intensity-value is present, intensity-range must be present and vice
versa.



The intensity-value must be within the intensity-range.



A number of trajectory samples at an update period must have a
timeSamples attribute, but duration attribute must not be described.



Passive kinesthetic force effect element must have a timeSamples
attribute in parent element, but duration attribute must not be described.



Passive kinesthetic force effect element must not be described with
active kinesthetic effect at the same time.



If fade and duration are defined fade must be less or equal to duration.



An Effect shall not have both a pts and an absTime at the same time.



An Effect within a Declarations shall have only a ptsDelta for a
timestamp.





© ISO/IEC 2014 – All rights reserved 11



A number of trajectory samples must be in multiples of 6 since 6 samples
include three positions and three orientations at each period Therefore number of
rows are fixed to 6.







Rows indicate 3 forces and 3 torques. Therefore, the number of row must be
'6'.







Wave effect element must have duration attribute in parent element.







Shake effect element must have duration attribute in parent element.







Spin effect element must have duration attribute in parent element.







At least directionH or directionV shall be defined.






12 © ISO/IEC 2014 – All rights reserved



At least pitch, roll, or yaw shall be defined.



If pitch is defined pitchSpeed or pitchAcceleration shall be defined.



If yaw is defined yawSpeed or yawAcceleration shall be defined.



If roll is defined rollSpeed or rollAcceleration shall be defined.








The number of RGB_value must be 3(red, green, blue). Therefore the length
of vector is fixed to 3.





The size of REG2XYZ_LUT matrix shall be 3 by 3. Therefore the number of
rows is fixed to 3 and the number of columns is fixed to 3.





The number of RGBScalar_Max must be 3(red, green, blue). Therefore the
length of RGBScalar_Max vector is fixed to 3.





The number of Offset_Value must be 3(red offset, green offset, blue
offset). Therefore the length of Offset_Value vector is fixed to 3.





© ISO/IEC 2014 – All rights reserved 13

The size of Gain, Offset, and Gamma is 3, respectively. The size of
matrix Gain_Offset_Gamma is 3 by 3. Therefore the number of rows is fixed to 3
and the number of columns is fixed to 3.





The size of Inverse_LUT matrix is 3 by 3. Therefore the number of rows is
fixed to 3 and the number of columns is fixed to 3.





The size of IDCG_Value matrix is 3 by 2. Therefore the number of rows is
fixed to 3 and the number of columns is fixed to 2.








A ReferenceEffect outside of a GroupOfEffects shall have a timestamp
(i.e., pts, ptsDelta, or absTime).



A ReferenceEffect within a GroupOfEffects shall have only a ptsDelta for
a timestamp.



A ReferenceEffect shall not have both a pts and an absTime at the same
time.



A ReferenceEffect within Declarations shall have only a ptsDelta for a
timestamp.







14 © ISO/IEC 2014 – All rights reserved





A MotionSensor shall contain at least one element in addition to a
timestamp element.



An IntelligentCamera shall contain at least one element in addition to a
timestamp element.




5.2.3 Description
5.2.3.1 Description for ISO/IEC 23005-2
Description for SensorDeviceCapability:
No. Rule Description
R1.0 if (@minValue and @maxValue) then if A minValue shall be less than or equal to a
(@minValue > @maxValue) then false() maxValue.
else true() else true()
Description for PositionCapability:
No. Rule Description
R1.1 if (@minValue and @maxValue) then if A minValue shall be less than or equal to a
(@minValue > @maxValue) then false() maxValue.
else true() else true()
Description for OrientationCapability:
No. Rule Description
R1.2 if (@minValue and @maxValue) then if A minValue shall be less than or equal to a
(@minValue > @maxValue) then false() maxValue.
else true() else true()
Description for VelocityCapability:
© ISO/IEC 2014 – All rights reserved 15

No. Rule Description
R1.3 if (@minValue and @maxValue) then if A minValue shall be less than or equal to a
(@minValue > @maxValue) then false() maxValue.
else true() else true()
Description for AngularVelocityCapability:
No. Rule Description
R1.4 if (@minValue and @maxValue) then if A minValue shall be less than or equal to a
(@minValue > @maxValue) then false() maxValue.
else true() else true()
Description for AccelerationCapability:
No. Rule Description
R1.5 if (@minValue and @maxValue) then if A minValue shall be less than or equal to a
(@minValue > @maxValue) then false() maxValue.
else true() else true()
Description for AngularAccelerationCapability:
No. Rule Description
R1.6 if (@minValue and @maxValue) then if A minValue shall be less than or equal to a
(@minValue > @maxValue) then false() maxValue.
else true() else true()
Description for Range:
No. Rule Description
R2.0 if (child::scdv:XminValue > An XminValue shall be less than or equal to an
child::scdv:XmaxValue) then false() else XmaxValue.
true()
R2.1 if (child::scdv:YminValue > An YminValue shall be less than or equal to an
child::scdv:YmaxValue) then false() else YmaxValue.
true()
R2.2 if (child::scdv:ZminValue > A ZminValue shall be less than or equal to a
child::scdv:ZmaxValue) then false() else ZmaxValue.
true()
Description for OrientationRange:
16 © ISO/IEC 2014 – All rights reserved

No. Rule Description
R3.0 if (child::scdv:YawMin > An YawMin shall be less than or equal to an
child::scdv:YawMax) then false() else true() YawMax.
R3.1 if (child::scdv:PitchMin > A PitchMin shall be less than or equal to a
child::scdv:PitchMax) then false() else true() PitchMax.
R3.2 if (child::scdv:RollMin > child::scdv:RollMax) A RollMin shall be less than or equal to a RollMax.
then false() else true()
5.2.3.2 Description for ISO/IEC 23005-3
Description for SEM:
No. Rule Description
R1.0 @si:timeScale The SEM element shall have a timeScale attribute.

Description for GroupOfEffects:
No. Rule Description
R2.0 if ( not(parent::sedl:Declarations) and A GroupOfEffects outside of a Declarations shall
not(@si:pts or @si:ptsDelta or have a timestamp (i.e., pts, ptsDelta, or absTime).
@si:absTime) ) then false() else true()
R2.1 if ( not(parent::sedl:Declarations) and A GroupOfEffects outside of a Declarations shall
(@si:pts and @si:absTime) ) then false() not have both a pts and an absTime at the same
else true() time.
R2.2 if ( parent::sedl:Declarations and (@si:pts A GroupOfEffects within a Declarations shall have
or @si:absTime) ) then false() else true() only a ptsDelta for a timestamp.

Description for Effects:
No. Rule Description
R3.0 @fade or @activate or @duration At least activate, duration, or fade shall be defined.
R3.1 if ( not(ancestor::sedl:Declarations) and An effect outside of a GroupOfEffects shall have a
not(parent::sedl:GroupOfEffects) and timestamp (i.e., pts, ptsDelta, or absTime).
not(@si:pts or @si:ptsDelta or
@si:absTime) ) then false() else true()
R3.2 if ( not(ancestor::sedl:Declarations) and An Effect within a GroupOfEffects shall have only a
(parent::sedl:GroupOfEffects and (@si:pts ptsDelta for a timestamp.
or @si:absTime)) ) then false() else true()
R3.3 if (@duration and @activate) then false() If duration is defined activate may not be defined.
© ISO/IEC 2014 – All rights reserved 17

No. Rule Description
else true()
R3.4 if (@duration and @fade) then if If fade and duration are defined activate may not be
(not(@activate)) then true() else false() else defined.
true()
R3.5 if(@fade and not(@intensity-value and If fade is defined intensity-value and intensity-range
@intensity-range)) then false() else true() shall be defined.
R3.6 if (some $retVal in (for $siblings in If two (or more) consecutive Effect elements of the
following-sibling::sedl:Effect return same type share the same timestamp (i.e., pts,
@xsi:type = $siblings/@xsi:type and ptsDelta, or absTime) and location only the latest in
((@si:pts = $siblings/@si:pts or their order of appearance shall be used.
@si:ptsDelta = $siblings/@si:ptsDelta or
@si:absTime = $siblings/@si:absTime) or
NOTE The other Effect elements can be removed
parent::sedl:GroupOfEffects) and @location from th
...