1、SMPTE STANDARD SMPTE 359M-2001 for Television and Motion Pictures - Dynamic Documents 1 Scope 1.1 There is a need in the field of information technology for the unambiguous identification of objects to provide interoperability among infor- mation systems. Individual standards committees have divined
2、, as part of their development of technical standards, classes of objects. Specific objects are the individual members of the class of objects. Registration is the process whereby unambiguous names are formally associated with objects. This may be done by an organiza- tion, a standard, or an automat
3、ed facility. 1.2 Within the television and motion-picture industries, there is a need for engineering docu- ments (standards, recommended practices, and engineering guidelines) which can easily and rapidly be extended to cover new requirements (dynamic documents). Such documents typically contain ta
4、bles of values, parameters, or other entities that cannot be fully defined at the time the document is written. 1.3 Through a process described in this standard, the dynamic tables described above are estab- lished as registers to be administered by the SMPTE Registration Authority (SMPTE RA). 1.4 D
5、ynamic documents are created using the same administrative practices as conventional SMPTE documents. Once a dynamic document is adopted as an engineering document, only designated entities within a dynamic document are subject to change by the dynamic document process. As with conventional engineer
6、ing docu- ments, the base document can be modified, but only in accordance with existing administrative practices. Page 1 of 14 pages 1.5 Four types of registers are defined. These types differ in their procedures for adding or modifying the data contained within the registers. 1.6 In this standard,
7、 shall denotes a mandatory provision of the standard, should denotes a pro- vision that is recommended but not mandatory, and may denotes a provision that is optional. 2 Normative references The following standards contain provisions which, through reference in this text, constitute provisions of th
8、is standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent edition of the standards indicated below. ISOAEC JTC 1 Directi
9、ves, Procedures for the Tech- nical Work of ISOAEC JTC 1 on Information Tech- nology, Third Edition, 1995 Society of Motion Picture and Television Engineers Administrative Practices, Section XIII, Engineering 3 Definitions 3.1 data: A representation of facts, concepts, or instructions in a formalize
10、d manner, suitable for communication, interpretation, or processing by humans or automatic means. 3.2 dataelement: A unit of data for which the definition, identification, representation, and permissible values are specified by means of a set of attributes. - Copyright O 2001 by ME SOCIITY OF MOTION
11、 PICTURE AND TELEVISION ENGINEERS 595 W. Hartedale Ave., white Plains, NY 10607 (914) 761-1100 Approved April 2,2001 SMPTE 359M-2001 33 engineering document: A SMPTE standard, recommended practice, or engineering guide- line, or equivalent document from another organization. 3.4 register: A set of f
12、iles (paper, electronic, or a combination) containing the assigned data elements and the associated information. (Defi- nition adapted after that in annex E of the ISO/I EC Directives.) 3.5 registered data element: A data e I em e n t that has been entered into a register kept by a registration auth
13、ority. 3.6 registration authority (RA): T h e o r g an i z a- tion established by the SMPTE Registration Authority, LLC which is authorized to register data elements. 3.7 regisnation authority board (RA Board): The registration authority board consists of the board of directors of the SMPTE Registra
14、tion Author- ity, LLC. 4 Types of data elements 4.1 Type Dynamic documents shall specrty the type to which each registered data element within that document belongs, together with the information that must be supplied with each request for registration. The Standards Committee shall specify which te
15、chnology committee or other body is charged with reviewing the request. 4.2 Dataset An engineering document establishing a dynamic document shall specify an original set of data to be entered into the register once the engineering docu- ment has been approved. 4.3 Extension or change Portions of the
16、 dynamic document that are subject to extension or change shall be clearly labeled as such, and shall be classified according to type as defined below. Assignment of registered data element type shall be subject to ballot and approval per applicable SMPTE administrative practices as is the rest of t
17、he document. 4.4 Maintenance An engineering document establishing a dynamic document shall speciy the RA responsible for mainte- nance and upkeep of any registered data elements specified in the engineering document. The engineer- ing document may also specify locations where registers and registere
18、d data elements may be found in electronic form. Table 1 outlines the difference among registered data element types. Table 1 - Characteristics of registered data element types Page 2 of 14 pages SMPTE 359M-2001 4.5 Type 1 registers Additions to atype 1 register shall be subject to review for techni
19、cal mer, adequacy of information provided, nonconflict with existing engineering documents, and compliance with type 1 requirements. Additions to a type 1 register shall require an underlying engineering document to support any addition (see figure 1). Example: If a document is extended to include a
20、 new type of ancillary data, at least a first drat of a SMPTE engineering document must exist describing the new ancillary data. 4.5.1 Information required for additions to type 1 registers The following information shall be provided by any organization, individual, or committee wishing to make addi
21、tions to a type 1 register: 1) Contact information for the organization, individ- ual, or committee requesting the addition; 2) The supporting engineering document used as the basis for the submission; 3) A request specifying the addition to the register; 4) Identification of the specific register t
22、o which the addition is to be made; 5) Detailed information regarding the purpose and use of the addition to the register; 6) Name of authorized representative of the organi- zation requesting the addition. 4.6 Type 2 registers Additions to a type 2 register shall be subject to review for adequacy o
23、f information, including technical description, nonconflict with existing engineering documents, and compliance with type 2 requirements. Additions to a type 2 register shall not be subject to review for technical merit. Additions to atype 2 register shall not require a supporting SMPTE engineering
24、document (see figure 2). During the ballot process for a change in a type 2 registered data element, negative votes based upon procedural issues, including adequacy of technical description, shall be accepted. Negative votes based upon technical merit shall not be considered. Exam- ple: The addition
25、 of a term to the metadata dictionary is an example of a type 2 data element. 4.6.1 Information required for additions to type 2 registers The following information shall be provided by any organization, individual, or Committee wishing to make additions to a type 2 register: 1) Contact information
26、for the organization, individ- ual, or committee requesting the addition; 2) A request specifying the addition to the register; 3) Detailed information regarding the purpose and use of the addition to the register; 4) Name of authorized representative of the organi- zation requesting registration. 4
27、.7 Type 3 registers Additions to a type 3 register shall be reviewed for adequacy of information and compliance with type 3 requirements. Additions to a type 3 register shall not be subject to due process review (see figure 3). Example: An example of a type 3 data element is an item in the portion o
28、f the metadata dictionary assigned for prototype purposes. 4.7.1 Information required for additions to type 3 registers The following information shall be provided by any organization, individual, or cornmittee wishing to make additions to a type 3 register: 1) Contact information for the organizati
29、on, individ- ual, or cornmittee requesting the addition; 2) A request specifying the addition to the register; 3) Detailed information regarding the purpose and use of the addition to the register; 4) A detailed description of the format specification may be required; 5) Statement of intention to ap
30、ply the registered data element, and intended date of first use; Page 3 of 14 pages SMPTE 359M-2001 6) Name of authorized representative of the organi- zation requesting the addition. 4.8 Type 4 registers Additions to a type 4 register shall be reviewed for adequacy of information and compliance wit
31、h type 4 requirements. Additions to a type 4 register may re- quire a fee payment before changes or additions will be accepted. Additions to a type 4 register shall not be examined for technical merk Additions to a type 4 register shall not be subject to consensus review or trial publication (see fi
32、gure 4). Example: The registration of an MPEG RID or UPID root number would be a type 4 data element. 4.8.1 Information required for additions to type 4 registers The following information shall be provided by any organization, individual, or committee wishing to make an addition to a type 4 registe
33、r: 1) Contact information for the organization, individ- ual, or committee requesting the addition; 2) Statement of intention to apply the registered data element, and intended date of first use; 3) Name of authorized representative of the organi- zation requesting the addition to the registry. 5 De
34、letion of registered data elements 5.1 Any request for deletion of a registered data element shall result in the posting of an appro- priate public notice giving the specifics of the proposed deletion. The following information shall be required before a deletion shall be con- sidered: 1) Contact in
35、formation for the organization, individ- ual, or committee requesting the deletion; 2) Any supporting document that may have been used as the basis for an original request for creation of the registered data element; 3) A request specifying the deletion of the registered data element along with acom
36、plete justification for the deletion; 4) Identification of the specific register to which the deletion is to be made; 5) Name of authorized representative of the organi- zation requesting the deletion. 5.2 To give users an opportunity to disagree with the deletion, the registered data element to be
37、deleted will be marked as such for a one-year period. If, after this period, nobody identifies himself as a user, the registered data element shall be deleted from the register. If even one objection is received concerning deletion of the registered data element, the data element shall not be delete
38、d. 5.3 In the event that it is discovered after the fact that an application for a registered data element contained false or misleading information, the registered data element may be immediately de- leted from the register at the sole discretion of the SMPTE Registration Authority. 5.4 With the ex
39、ception of 5.3 above, a registered data element shall not be deleted from a register earlier than one year from the time public notice is given of the deletion. 5.5 Individual engineering documents may im- pose restrictions on deletion of a registered data element that are more restrictive than thos
40、e specif ied here. 6 Deletion of a register 6.1 A register can only be deleted by a revision to a registers establishing engineering docu- ment, or through withdrawal of the engineering document establishing the register. 6.2 Any request for deletion of a registered data element shall result in the
41、posting of an appro- priate public notice giving the specifics of the proposed deletion. 6.3 To give users an opportunity to disagree with the deletion, the register to be deleted will be marked as such for a one-year period. If, after this period, nobody identifies himself as a user, the register s
42、hall be deleted. If even one objec- tion is received concerning deletion of the regis- ter, the register shall not be deleted. Page 4 ot 14 pages SMPTE 359M-2001 inlitban and Submission Via SMPTE-RA Web site I 1 :,: TC Chdnnan Il 1 Fiaca Mlot on TC agenda. AmLach mwling d (nolice) Ram (o Odghator (R
43、equtrer 8new standard) diatituted wih nolice) commenta ., c Reium (o odgiiutor wllh mmmcnb Nolig Enginewing I Infomutian raqulrd for Type 1 Enliy - Contact infoimalion ror organiznh, indvldml. Q committee requaling dynamic dmrnt enaty. - CupWihg SMPTE siandard for autnniuion - Request fu Wac regl8ta
44、red enlity (e.g. revised We fu erjalhg siandard). Note hat applicalions fora regirtered enaty hat conlain bsde maiks u oh infumah mat are aa$ociated wih anoher organizalion will be r-. - Detailed hfumah regang he piroor and use d m0 rwisied nlity. Note hat hccmplete u inlumcient sDplcaUm8 mey be - N
45、me of auhuized represenblhre of ihe orpanizalion requaling reglsballon. *WiIwli for Type 1 Enlliy - Frw-aianding SMPTE Siandard required - Rwimv for leehnical mait, non-conllct wih M$Ung atmdards etc. ia requked Figure 1 - Flow diagram for type 1 SMPTE dynamic document entity Page 5 of 14 pages I SM
46、PTE 359M-2001 Acsgn to appropriate Working Group if required Initiation and Submission via SMPTE Website (Document # Assigned by Website) TC Chairmar; 1 Issue Dynamic SMPTE Website Document Ballot on Assign to appropria Engineering I TC 1 VP HQ Place ballot on TC WGagenda. Attach submission to meeti
47、n call (Notice) Notice sent to all members including the TC Tc/wG 1 Originator Return toe e standa TCNG ,A meeting) ballot results special section of (Trial Publication) Return to Originator Information required tor Type 2 entity - Contact information for organization, individual, or committee reque
48、sting dynamic document entity. - Request for specific registered entity (e.g. revised table for existing standard). Note that applications for a registered entity that contain eade marks or other information that are associated with another organization will be rejected. - Detailed information regar
49、ding the purpose and use of the registered entity. Note that applications may be rejected if sufcient information is not supplied - Name of authorized representative of the organization requesting registration. “Criteria for Type 2 entity - Free-tanding SMPTE Standard not required - Review for technical ment not required or accepted - Review for nonconflict with existing standards etc. is required TC chairman and group discuss disposition of ballot Return to originator with comments received? for disposition Return to originator Notify Engineering with comments VP, TC Chair
