hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 3 Definition of terms, symbols and abbreviations | |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 3.1 Terms | For the purposes of the present document, the following terms apply: application: specific set of functions running on the PDR NOTE: Some applications use metadata, either automatically or under consumer control. ATSC-DASE: set of application programming interfaces currently being standardized by the Advanced Televisio... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 3.2 Symbols | Void. ETSI ETSI TS 102 822-3-1 V1.11.2 (2019-06) 14 |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAC Advanced Audio Coding (audio coding scheme) AMR Adaptive Multi Rate (audio coding scheme) ARIB Association of Radio Industries and Businesses ATSC Advanced Television Systems Committee AV Audio-Visual BSL British Sign Language CRID Content... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 4 Introduction to metadata | Metadata is generally defined as "data about data". Within the TV-Anytime environment, the most visible parts of metadata are the attractors/descriptors or hyperlinks used in electronic programme guides, or in Web pages. This is the information that the consumer or agent will use to decide whether or not to acquire a p... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 5 TV-Anytime Metadata Data Model | |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 5.1 TV-Anytime Metadata Process Model | Create Metadata aggregation Metadata editing Content creation Publish Content publishing Metadata publishing Search and selection metadata Location resolution metadata Segmentation metadata Select & Present Search & Selection Location Resolution Storage Metadata Content User Interaction Figure 1: Metadata and content f... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 5.2 TV-Anytime Metadata Structure Model | Two modelling approaches are used in the following clauses. A simple data modelling methodology (see figure 2) is first introduced to describe metadata structure at a high level in a manner independent of any particular representation. This syntax allows relationships between TV-Anytime entities to be clearly stated (e... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 5.3 CRID and Metadata | The cornerstone of TV-Anytime metadata is the CRID, described in ETSI TS 102 822-4 [9]. As a content reference identifier, the CRID refers to a piece of content, though in some cases it may refer to one or more other CRIDs. The CRID also acts as the link that connects different content-related metadata descriptions (se... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6 Metadata definitions | |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.0 XML as a representation format | For the purpose of interoperability, the TV-Anytime Forum has adopted XML as the common representation format for metadata. XML offers many advantages: it allows for extensibility, supports the separation of data from the application and is widely used. XML schema is mainly used to represent the data model. TV-Anytime ... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.1 Use of MPEG-7 | A metadata schema is the formal definition of the structure and type of metadata. TV-Anytime uses the MPEG-7 Description Definition Language (DDL) (see ISO/IEC 15938-5 [2]) to describe metadata structure as well as the XML encoding of metadata. DDL is based on XML schema as recommended by W3C in XML Schema, W3C Recomme... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.2 TV-Anytime Metadata Namespace | TV-Anytime metadata Description Schemes (DS) that have been developed under the auspices of the TV-Anytime Forum are associated with the TV-Anytime metadata XML namespace. The TV-Anytime XML schema is contained in archive ts_1028220301v011102p0.zip which accompanies the present document. It contains the complete set of... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.3 Content Description Metadata | |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.3.1 Content Description Requirements | The content description model shall be able to represent the following concepts: 1) A simple programme. 2) A programme with a number of different versions (e.g. edits for sex/violence/language, director's cut, etc.). 3) A programme that has been divided into a number of parts for publication (e.g. a 3 h film shown in 2... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.3.2 TV-Anytime Content Description model | Figure 5: TV-Anytime Content Description Model Entity definitions • "Programme" - the programme represents an editorially coherent piece of content, which may itself aggregate other programmes. • "Programme group" - the programme group entity simply represents a grouping of programmes. A number of different types of gr... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.3.3 Basic types | The simple and complex utility types defined below are used throughout the TV-Anytime schema specification. <simpleType name="TVAIDType"> <restriction base="string"> </restriction> </simpleType> <simpleType name="TVAIDRefType"> <restriction base="string"> </restriction> </simpleType> <simpleType name="TVAIDRefsType"> <... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.3.4 Description | The following simple and complex types define descriptive attributes of content. <complexType name="KeywordType"> <simpleContent> <extension base="mpeg7:TextualType"> <attribute name="type" use="optional" default="main"> <simpleType> <restriction base="NMTOKEN"> <enumeration value="main"/> <enumeration value="secondary... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.3.5 Audio and video information | The following simple and complex types define technical attributes of audio and video. <complexType name="BitRateType"> <simpleContent> <extension base="nonNegativeInteger"> <attribute name="variable" type="boolean" use="optional" default="false"/> <attribute name="minimum" type="unsignedLong" use="optional"/> <attribu... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.3.6 Programme information | <complexType name="AggregationOfType"> <sequence> <element name="AggregatedProgram" type="tva:CRIDRefType" minOccurs="2" maxOccurs="unbounded"/> </sequence> <attribute name="type" use="required"> <simpleType> <restriction base="string"> <enumeration value="omnibus"/> <enumeration value="magazine"/> <enumeration value="... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.3.7 Group Information | <complexType name="BaseProgramGroupTypeType" abstract="true"/> <complexType name="ProgramGroupTypeType"> <complexContent> <extension base="tva:BaseProgramGroupTypeType"> <attribute name="value" use="required"> <simpleType> <restriction base="string"> <enumeration value="series"/> <enumeration value="show"/> <enumeratio... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.3.8 Media Review DS | The MediaReview DS provides third-party reviews of AV content, such as a critic's review of a movie. Independent programme reviews can be presented to users to aid them in programme selection. <complexType name="ReviewerType"> <complexContent> <extension base="tva:TVAAgentType"> <sequence> <element name="Publication" t... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.3.9 Rights and usage restriction information | The RightsStatement element is used to provide information on rights and associated usage restrictions (e.g. geographical use, usage time windows, user actions, type of device). RightsStatements can be associated to programs or segments. A set of RightsStatements is aggregated in a RightsInformationTable. ETSI ETSI TS ... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.3.10 Common core set of metadata | |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.3.10.0 Three compliance levels | Descriptive metadata has been defined to be associated with content. Because TV-Anytime metadata will be processed on a variety of devices, including devices with extremely limited resources, metadata is classified into required, recommended and optional metadata elements. |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.3.10.1 Required | Name Requirement Title All ProgramInformation and GroupInformation objects shall contain a meaningful Title field. |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.3.10.2 Recommended | Name Guideline Synopsis It is recommended that all ProgramInformation and GroupInformation objects contain a meaningful Synopsis element. Genre It is recommended that all ProgramInformation and GroupInformation objects contain a meaningful set of classification elements. Language/CaptionLanguage/ SignLanguage It is rec... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.3.11 Optional metadata (informative) | All other metadata defined in the present document are optional. |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.4 Instance description metadata | |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.4.0 Instance vs. descriptive metadata | The previous clause addressed content description metadata, which associates metadata with a piece of content. The key for linking content metadata to content is the CRID. The present clause covers instance description metadata. Instance description metadata is useful in cases where there are meaningful differences bet... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.4.1 Programme location entities | A programme location contains information about one instance (or "publication event") of a programme. Multiple programme locations from the same service provider can be grouped to form e.g. a broadcast schedule, an on-demand service or a push-download package. A metadata provider aggregates a set of programme locations... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.4.2 Programme Location | Figure 7 is useful in understanding how the abstract model above has been implemented in the present document. Figure 7: ProgramLocationType and related types ProgramLocationType has a number of related types, some of them being used as entries in a programme location table (see clause 6.7.1). ProgramLocationType is an... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.4.3 Service information | <simpleType name="serviceInformationNameLengthType"> <restriction base="string"> <enumeration value="short"/> <enumeration value="medium"/> <enumeration value="long"/> </restriction> </simpleType> <complexType name="ServiceInformationNameType"> <simpleContent> ETSI ETSI TS 102 822-3-1 V1.11.2 (2019-06) 72 <extension ba... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5 Consumer metadata | |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.1 Usage history DS | |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.1.0 Introduction to the notion of usage history | The present clause presents a DS for describing usage history information gathered over extended periods of time. The collected usage history provides a list of the actions carried out by the user for an observation period, which can subsequently be used by automatic analysis methods to generate user preferences. A sta... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.1.1 Usage history DS | <complexType name="UsageHistoryType"> <complexContent> <extension base="mpeg7:DSType"> <sequence> <element name="UserIdentifier" type="mpeg7:UserIdentifierType" minOccurs="0"/> <element name="UserActionHistory" type="tva:UserActionHistoryType" maxOccurs="unbounded"/> </sequence> <attribute name="allowCollection" type="... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.1.2 UserActionHistory DS | <complexType name="UserActionHistoryType"> <complexContent> <extension base="mpeg7:DSType"> <sequence> <element name="ObservationPeriod" type="mpeg7:TimeType" minOccurs="0" maxOccurs="unbounded"/> <element name="UserActionList" type="tva:UserActionListType" maxOccurs="unbounded"/> </sequence> <attribute name="protected... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.1.3 UserActionList DS | <complexType name="UserActionListType"> <complexContent> <extension base="mpeg7:DSType"> <sequence minOccurs="0"> <element name="ActionType" type="mpeg7:TermUseType"/> <element name="UserAction" type="tva:UserActionType" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribute name="numOfInstances" type="nonNegativ... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.1.4 UserAction DS | The UserAction DS provides detailed information about individual user actions, including the time of occurrence, duration, associated CRID of the programme, location of the programme and references to related content descriptions and material. The TV-Anytime Forum UserAction DS is an extension of the UserAction DS spec... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.1.5 Informative examples | Informative examples of the usage history DSs presented in the present clause are provided in clause 15.2 of ISO/IEC 15938-5 [2]. |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.2 User preferences DS | |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.2.0 Introduction to the concept of user preference | The present clause contains DSs that facilitate description of user's preferences pertaining to consumption of multimedia material. User preference descriptions can be correlated with media descriptions to search, filter, select and consume desired content. Correspondence between user preference and media descriptions ... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.2.1 Basic user preference elements | The PreferenceCondition DS is used to specify a combination of time and/or place to be associated with a particular set of user preferences. The userChoice datatype is used to indicate the value of a condition set by a user, with respect to actions taken by a processor of descriptions. The preferenceValue datatype is u... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.2.2 UserPreferences DS | The UserPreferences DS is used to describe a user's preferences for consumption of multimedia material. Correspondence between user preference information and media descriptions allows personalization of content access and content consumption. The specification of the UserPreferences DS is given in clause 15.2.3 of ISO... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.2.3 UserIdentifier DS | The UserIdentifier DS may be used to associate a specific user (or set of users) with a particular user preference description, or to identify a particular user preference description, or to distinguish multiple user preference descriptions. The specification of the UserPreference DS is given in clause 15.2.4 of ISO/IE... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.2.4 FilteringAndSearchPreferences DS | The FilteringAndSearchPreferences DS specifies a user's filtering and/or searching preferences for audio-visual content. These preferences can be specified in terms of creation-, classification- and source-related properties of the content. The FilteringAndSearchPreferences DS is a container of CreationPreferences, Cla... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.2.5 CreationPreferences DS | The CreationPreferences DS specifies a user's preferences about the creation-related properties of AV content, such as favourite actors, etc. The specification of the CreationPreferences DS is given in clause 15.2.6 of ISO/IEC 15938-5 [2]. Syntax of the CreationPreferences DS is specified in clause 15.2.6.2 in ISO/IEC ... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.2.6 ClassificationPreferences DS | The ClassificationPreferences DS is used to convey a user's preferences about various classifications of the content, such as preferred genre or language. The specification of the ClassificationPreferences DS is given in clause 15.2.7 of ISO/IEC 15938-5 [2]. Syntax of the ClassificationPreferences DS is specified in cl... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.2.7 SourcePreferences DS | The SourcePreferences DS is used to convey preferences on the source of the AV content, such as publisher or channel of distribution. The specification of the SourcePreferences DS is given in clause 15.2.8 of ISO/IEC 15938-5 [2]. Syntax of the SourcePreferences DS is specified in clause 15.2.8.2 in ISO/IEC 15938-5 [2].... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.2.8 PreferenceCondition DS | ETSI ETSI TS 102 822-3-1 V1.11.2 (2019-06) 89 |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.2.9 BrowsingPreferences DS | The BrowsingPreferences DS is used to specify a user's preferences for navigating and accessing multimedia content. The BrowsingPreferences DS is a container of SummaryPreferences. The specification of the BrowsingPreferences DS is given in clause 15.2.9 of ISO/IEC 15938-5 [2]. Syntax of the BrowsingPreferences DS is s... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.5.2.10 SummaryPreferences DS | The SummaryPreferences DS describes a user's preferences for nonlinear navigation of media especially with respect to visualization and audio rendering of AV content. The specification of the SummaryPreferences DS is given in clause 15.2.10 of ISO/IEC 15938-5 [2]. Syntax of the BrowsingPreferences DS is specified in cl... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.6 Segmentation metadata | |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.6.0 Introduction to segmentation | Segmentation refers to the ability to define, access and manipulate temporal intervals (i.e. segments) within an AV stream. By associating metadata with segments and segment groups, it is possible to restructure and re-purpose an input AV stream to generate alternative consumption and navigation modes. Such modes could... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.6.1 Segmentation metadata: definitions and requirements | The present clause introduces an overview of segmentation, including definitions of terminology and a list of requirements for common applications. An entity-relationship diagram of the various components of a (segmented) programme is shown in figure 8. The properties and relationships of each entity are provided in mo... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.6.2 Basic segment description | The following complex type defines descriptive properties of segments. <complexType name="BasicSegmentDescriptionType"> <sequence> <element name="Title" type="mpeg7:TitleType" minOccurs="0" maxOccurs="unbounded"/> <element name="Synopsis" type="tva:SynopsisType" minOccurs="0" maxOccurs="unbounded"/> <element name="Genr... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.6.3 TVAMediaTime Type | The TVAMediaTime Type is used to describe a time point relative to a known origin and with an optional duration. This type is used extensively by the Segmentation data types. <complexType name="TVAMediaRelIncrTimePointType"> <simpleContent> <restriction base="mpeg7:MediaRelIncrTimePointType" > <attribute name="mediaTim... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.6.4 TimeBaseReference Type | The following type is used within the Segment structures to define a time base, which segments are authored against. <complexType name="TimeBaseReferenceType"> <sequence> <choice> <element name="MediaTimePoint" type="mpeg7:mediaTimePointType"/> <element name="MediaRelIncrTimePoint" type="mpeg7:MediaRelIncrTimePointType... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.6.5 Segment Information | The following element and complex type define a segment. <complexType name="SegmentInformationType"> <sequence> <element name="ProgramRef" type="tva:CRIDRefType" minOccurs="0"/> <element name="InstanceMetadataIdRef" type="tva:InstanceMetadataIdType" minOccurs="0" maxOccurs="unbounded"/> <element name="TimeBaseReference... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.6.6 Segment Group Information | The following element and complex types define segment grouping. <complexType name="GroupIntervalType" > <attribute name="ref" type="tva:TVAIDRefType" use="optional"/> </complexType> <complexType name="SegmentsType"> <attribute name="refList" type="tva:TVAIDRefsType" use="required"/> </complexType> <complexType name="G... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.6.7 Segment information table | The following element and complex type define a structure for holding all segmentation-related metadata. <complexType name="SegmentListType"> <sequence> <element name="SegmentInformation" type="tva:SegmentInformationType" minOccurs="0" maxOccurs="unbounded"/> </sequence> </complexType> <complexType name="SegmentGroupLi... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.7 TV-Anytime documents | |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.7.0 Introduction | TV-Anytime metadata is structured into self-contained documents. Each document has a single top-level element that encloses all other TV-Anytime metadata. |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.7.1 Information tables | <complexType name="ProgramInformationTableType"> <sequence> <element name="ProgramInformation" type="tva:ProgramInformationType" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> <attribute ref="xml:lang" use="optional"/> </complexType> <com... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 6.7.2 TV-Anytime metadata document | <!-- ################################################ --> <!-- Definition of TVAMain DS --> <!-- ################################################ --> <element name="TVAMain" type="tva:TVAMainType"/> <complexType name="TVAMainType"> <sequence> <element name="CopyrightNotice" type="mpeg7:TextualType" minOccurs="0" maxOcc... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 7 The TVA metadata framework (informative) | |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 7.1 The XML-based TV-Anytime metadata framework | There are different contexts where it might be preferred to continuously use XML in its textual form. Binarization allows saving bandwidth and maximizing the performance of the system (parsing at the binary level is more efficient). The transport and extraction of textual or binarized XML it out of the scope of TV-Anyt... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 7.2 Metadata security considerations | The TV-Anytime specification provides a rich set of metadata. This metadata can be considered as an asset requiring protection. Therefore, a protection scheme may be required to handle the usage of such data. Definition of a "proper" protection scheme depends on the nature of the metadata. For example, a critical secur... |
df6468f47ef292db5611a8a4e885226d | 102 786 | 1 Scope | The present document defines a grid testing framework based on existing testing and validation methodologies, best practices and tools used, in IT and Telecom sectors to obtain ICT Interoperability. |
df6468f47ef292db5611a8a4e885226d | 102 786 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
df6468f47ef292db5611a8a4e885226d | 102 786 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. Not applicable. |
df6468f47ef292db5611a8a4e885226d | 102 786 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI EG 202 237 (V1.1.2): "Methods for Testing a... |
df6468f47ef292db5611a8a4e885226d | 102 786 | 3 Definitions and abbreviations | |
df6468f47ef292db5611a8a4e885226d | 102 786 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: deployment manager: entity which converts deployment information into infrastructure specific service calls or commands to perform resource reservation and application deployment |
df6468f47ef292db5611a8a4e885226d | 102 786 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AD GCM Application Descriptor ADL Architecture Description Language CCS Compute Cluster Server DD GCM Deployment Descriptor GCM Grid Component Model ICS Implementation Conformance Statement IPT Internet Protocol Testing LSF Load Sharing Facili... |
df6468f47ef292db5611a8a4e885226d | 102 786 | 4 Testing framework for the Grid Component Model | |
df6468f47ef292db5611a8a4e885226d | 102 786 | 4.1 Introduction | EG 202 237 [i.1] describes a generic approach to interoperability testing for Internet Protocol Testing (IPT). In this guide, interoperability testing is defined as the "activity of proving that end-to-end functionality between (at least) two communicating systems is as required by the base standard(s) on which those s... |
df6468f47ef292db5611a8a4e885226d | 102 786 | 4.2 Grid Component Model | The Grid Component Model (GCM) standard contains three parts: the GCM Application Description [i.2], GCM Interoperability Deployment [i.3], and GCM Fractal Architecture Description Language (ADL) [i.4]. A generic GCM test architecture which focuses on the GCM Application Descriptor (AD) and Deployment Descriptor (DD) h... |
df6468f47ef292db5611a8a4e885226d | 102 786 | 4.3 Goals | The main purpose of the tests is the assessment of the standardized GCM Deployment Descriptor (DD) and Application Descriptor (AD). The general test objective is to check that applications can be deployed and executed on a given infrastructure based on the information provided in GCM DD and AD. An infrastructure can ei... |
df6468f47ef292db5611a8a4e885226d | 102 786 | 4.4 Test architecture | Figure 2: A test architecture for GCM-based deployment An example test architecture is shown in figure 2. The System Under Test (SUT) consists of the Deployment Manager and one or more infrastructures. The different types of entities that compose the means of testing handle provision of GCM DD and AD files to the deplo... |
df6468f47ef292db5611a8a4e885226d | 102 786 | 4.5 Test suite structure and test purposes | |
df6468f47ef292db5611a8a4e885226d | 102 786 | 4.5.1 Test suite structure | The test suite structure should be based on the requirements specified in GCM DD and AD standards. Firstly, test groups should distinguish tests to be relevant to GCM DD vs. AD. For the GCM DD groups should differentiate between indirect and direct resource access. For the GCM AD groups should differentiate between vir... |
df6468f47ef292db5611a8a4e885226d | 102 786 | 4.5.2 Test purposes | A test purpose (TP) specifies how a requirement specified in a specification can be assessed in a given test architecture. Therefore, each TP should at least include a reference to the clause in a specification where the requirement assessed in the test is stated in the standard. In addition, a TP should be dedicated t... |
df6468f47ef292db5611a8a4e885226d | 102 786 | 4.5.3 Test descriptions | A test description is a detailed but informal specification of the pre-conditions and test steps needed in order to cover one or more given test purposes. A test description shall contain the following information: • Identifier: Each TD has a unique identifier that relates a test to its group and sub-group. • Summary: ... |
df6468f47ef292db5611a8a4e885226d | 102 786 | 4.5.4 Test execution | Test execution requires the evaluation of the applicability of each test (description) to all of the equipment part of the SUT. To speed up this process a GCM Implementation Conformance Statement (ICS) should be established to allow infrastructure providers to specify supported features prior to a test execution and su... |
55830bb2142e344429b649b761595809 | 102 778-6 | 1 Scope | The present document specifies requirements and recommendations for the visual representations of advanced electronic signatures (AdES) in PDFs. This covers: a) Signature appearance: The visual representation of the human act of signing placed within a PDF document at signing time and linked to an advanced electronic s... |
55830bb2142e344429b649b761595809 | 102 778-6 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
55830bb2142e344429b649b761595809 | 102 778-6 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ISO 32000-1: "Document management - Portable document format - Part 1: PDF 1.7". [2] ETSI TS 102 778-1: "Electronic Signatures and Infrastructures (ESI); PDF Advanced Electronic Signature Profiles; Part 1: PAdES Overview -... |
55830bb2142e344429b649b761595809 | 102 778-6 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ISO/IEC 10181-4 (1997): "Information technology - Open Systems Interconnection - Security frameworks for open systems: Non-repudiation framework". |
55830bb2142e344429b649b761595809 | 102 778-6 | 3 Definitions and abbreviations | |
55830bb2142e344429b649b761595809 | 102 778-6 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in [1] and the following apply: certificate image: image that is part of a X509 certificate as specified in draft-ietf-pkix-certimage-04 [5] certified identity: information about the signer certified by a trusted source claimed signing time: time... |
55830bb2142e344429b649b761595809 | 102 778-6 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AdES Advanced Electronic Signature (as specified in Directive 1999/93/EC [8]) AP Appearance Dictionary CMS Cryptographic Message Syntax (as specified in RFC 3852 [9]) CN Common Name CRL Certificate Revocation List FT Field Type OCSP Online Cer... |
55830bb2142e344429b649b761595809 | 102 778-6 | 4 General concepts | An advanced electronic signature (AdES) included within an electronic document is based on a sequence of bytes obtained by applying a cryptographic algorithm, and serving to protect the integrity of the electronic document as well as the identity of the signatory. Signatures that can be applied to a PDF document, as de... |
55830bb2142e344429b649b761595809 | 102 778-6 | 5 The signature appearance | |
55830bb2142e344429b649b761595809 | 102 778-6 | 5.1 Recommended information in signature appearances | The following requirements are applicable to a conforming signature handler when creating a visual representation of the signature inserted in document at the signing time. A signature appearance represents elements of the AdES signature and other attributes of the signature such as signing time and location. A conform... |
55830bb2142e344429b649b761595809 | 102 778-6 | 5.2 Encoding of signature appearances in PDF | Signatures are stored inside a PDF document using a Signature Field (ISO 32000-1 [1], section 12.7.4.5). A signature field is the type of form field that contains the signature and its field type (FT) shall be Sig, and the field value (V), which is added at the time of signing, shall be a signature dictionary containin... |
55830bb2142e344429b649b761595809 | 102 778-6 | 6.2 Summary representation of certified identity verification | If the certified identity has been successfully validated the following information shall also be displayed at top level: • If the signatories certificate contains a certificate image then the certificate image as defined in draft-ietf-pkix- certimage-04 [5]. • If the signatories certificate contains no certificate ima... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.