Information technology — Multimedia content description interface — Part 5: Multimedia description schemes — Amendment 2: Multimedia description schemes user preference extensions

Technologies de l'information — Interface de description du contenu multimédia — Partie 5: Schémas de description multimédia — Amendement 2: Extensions de préférence d'utilisateur des schémas de description multimédia

General Information

Status
Published
Publication Date
17-Feb-2005
Current Stage
6060 - International Standard published
Due Date
05-Nov-2005
Completion Date
18-Feb-2005
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 15938-5:2003/Amd 2:2005 - Multimedia description schemes user preference extensions
English language
38 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 15938-5
First edition
2003-05-15
AMENDMENT 2
2005-02-15


Information technology — Multimedia
content description interface —
Part 5:
Multimedia description schemes
AMENDMENT 2: Multimedia description
schemes user preference extensions
Technologies de l'information — Interface de description du contenu
multimédia —
Partie 5: Schémas de description multimédia
AMENDEMENT 2: Extensions de préférence d'utilisateur des schémas
de description multimédia




Reference number
ISO/IEC 15938-5:2003/Amd.2:2005(E)
©
ISO/IEC 2005

---------------------- Page: 1 ----------------------
ISO/IEC 15938-5:2003/Amd.2:2005(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.


©  ISO/IEC 2005
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing 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 copyright@iso.org
Web www.iso.org
Published in Switzerland

ii © ISO/IEC 2005 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 15938-5:2003/Amd.2:2005(E)
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.
Amendment 2 to ISO/IEC 15938-5:2003 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia
information.
© ISO/IEC 2005 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 15938-5:2003/Amd.2:2005(E)

Information technology — Multimedia content description
interface —
Part 5:
Multimedia description schemes
AMENDMENT 2: Multimedia description schemes user preference
extensions
Except where noted otherwise, add the corresponding subclauses of ISO/IEC 15938-5:2003 with the content
of the following subclauses hereafter:
6.5.7 LogicalUnitLocator datatype
6.5.7.1 Introduction
The locating of nested units is supported by defining an explicit structure to the LogicalUnitLocator that
allows media locators to be included as sub-units. Furthermore, by supporting hierarchical structures directly
through this nesting, the LogicalUnitLocator retains a clear semantics when multiple locators are
sequenced within a description to identify the union of logical units.
6.5.7.2 LogicalUnitLocator datatype syntax
Syntax of the LogicalUnitLocatorType:
 
 
 

 
 
  
   
    
     
      
       
        
       
        use="required"/>
       
      
     
     
      
       
        
       
© ISO/IEC 2005 – All rights reserved 1

---------------------- Page: 4 ----------------------
ISO/IEC 15938-5:2003/Amd.2:2005(E)
       
      
     
    
   
  
 

6.5.7.3 LogicalUnitLocator datatype semantics
Semantics of the LogicalUnitLocatorType:
Name Definition
LogicalUnitLocatorType
Describes the location of logical unit of a media resource, such as a “track”
of a CD or “chapter” of a DVD. The localization within a target resource
can be specified using either LogicalUnit or ReferenceUnit
elements. In the case that multiple instances of these elements are
included within the description, the result is the union of the individual
locator elements, e.g., chapter 1 and chapter 2 of a DVD. Nested logical
units should be described using the SubUnit elements of each locator
element.
LogicalUnit Describes the localization of a logical unit by identifying the name of the
logical unit, e.g., “chapter” and value, e.g., “2”.
unit
Identifies the unit, e.g., “chapter” using termReferenceType. The unit
name can belong to a classification scheme in order to enforce a
controlled vocabulary. The termReferenceType also allows names to
be used that do not belong to classification schemes when needed.
value
Describes the value of the unit, e.g., “2” using string.
SubUnit
Describes nested units located within the parent logical unit, e.g., “section
2” of “chapter 1”. SubUnit is of type MediaLocator to allow non-logical
sub-units to be described.
ReferenceUnit
Describes the localization of a logical unit by identifying reference of the
logical unit, such as by xpath expression.
referenceGrp
Identifies the reference of the logical unit using xpath, idref, etc.

6.5.7.4 Example (informative)
The following example describes the logical unit of a “chapter” of a DVD. This example assumes that a
classification scheme “urn:dvd:logicalunit” has been defined for DVDs that identifies the names of its logical
units, e.g., “chapter”.

 
  
   
    
     
    
   
2 © ISO/IEC 2005 – All rights reserved

---------------------- Page: 5 ----------------------
ISO/IEC 15938-5:2003/Amd.2:2005(E)
  
 


The following example describes the logical unit of a CD that corresponds to track 8 from disk 2. This example
assumes that a classification scheme has been defined for CDs that identifies the names of its logical units.
Furthermore, this example shows the explicit use of hierarchy of units to indicate that the track is from disk 2.
The LogicalUnitLocator describes the increasing granularity and nesting of logical units in the case of
hierarchical relationship using the SubUnit element.

 
  
   
    
     
      
       
      
     
    
   
  
 


The following example uses the ReferenceUnit xpath reference mechanism of LogicalUnitLocator
to address a fragment of an XML resource.

 
  
   
    
     
    
   
  
 


The following example uses the ReferenceUnit xpath reference mechanism of LogicalUnitLocator
to address a fragment of an XML resource.

 
  
   
    
     
    
   
  
 

© ISO/IEC 2005 – All rights reserved 3

---------------------- Page: 6 ----------------------
ISO/IEC 15938-5:2003/Amd.2:2005(E)
The following example describes a fragment that corresponds to a time point at 30 seconds from the
beginning of the third track of an Audio CD.


 
  
   
  
 


The following example describes the first 15 seconds of all the audio tracks of the second CD disk in a three
disk CD Audio package.

 
  
   
  
 



Except where noted otherwise, replace the corresponding subclauses of ISO/IEC 15938-5:2003 with the
content of the following subclauses hereafter:

7.5.3.2 Person DS syntax








 
 
  
  
     type="mpeg7:ControlledTermUseType"/>
  
  
  
   
    type="mpeg7:OrganizationType"/>
    type="mpeg7:ReferenceType"/>
    type="mpeg7:PersonGroupType"/>
    type="mpeg7:ReferenceType"/>
   
  
  
     minOccurs="0" maxOccurs="unbounded"/>
  
  
  
  
   type="mpeg7:ElectronicAddressType"
   minOccurs="0" maxOccurs="unbounded"/>
   minOccurs="0"/>
   minOccurs="0"/>
 
© ISO/IEC 2005 – All rights reserved 5

---------------------- Page: 8 ----------------------
ISO/IEC 15938-5:2003/Amd.2:2005(E)
 



7.5.3.3 Person DS semantics
Semantics of the PersonType:
Name Definition
PersonType Describes an individual person.
Name
Describes a name associated with this person. Multiple names are allowed. The
interpretation of different names is not defined in this standard.
NameTerm Describes a name associated with this person using a term from a classification
scheme.
Affiliation
Describes an organizations or person groups with which this person is affiliated.
For example, the company for which the individual works, the sports team on which
they place, and so on. A person may be affiliated with more than one organization
or group.
Organization
Describes an organization that this person is affiliated with.
OrganizationRef
Describes a reference to an organization that this person is affiliated with.
PersonGroup Describes a group that this person is affiliated with.
PersonGroupRef
Describes a reference to a person group that this person is affiliated with.
Citizenship
Describes the countries in which this person is a legal citizen. A person may hold
multiple citizenships. The legal definition of citizenship is not defined in this
standard and may vary from country to country.
Address
Describes a place that is the address where this person can be located.
AddressRef Describes a reference to a place that is the address where this person can be
located.
ElectronicAddress
Describes the electronic address information for this person.
PersonDescription Describes information about a person to distinguish them from other persons of the
same name - e.g. farmer, poet, American dentist
Nationality Describes the nationality of an individual by origin, birth, or naturalization

7.5.6 PersonName datatype
• The LinkingName element is Name Component that describes a link used between family, given and
other names (e.g. den, ten, van den, von)
6 © ISO/IEC 2005 – All rights reserved

---------------------- Page: 9 ----------------------
ISO/IEC 15938-5:2003/Amd.2:2005(E)
• The Salutation element is Name Component that describes an individual's salutation or title. Eg. Mr.,
Mrs., Sir. This is distinct fro the Title element which is reserved for terms used personal honours (e.g.,
F.R.S.) and qualifications (e.g., Professor).

7.5.6.1 Introduction
The PersonName datatype describes the name of a person, whether historical, existing, or fictional.
7.5.6.2 PersonName datatype syntax







 
 
  minOccurs="0"/>
  minOccurs="0"/>
 
  minOccurs="0"/>
 
 




 
 
  
  
  
 
 







 
 
 
 



© ISO/IEC 2005 – All rights reserved 7

---------------------- Page: 10 ----------------------
ISO/IEC 15938-5:2003/Amd.2:2005(E)
7.5.6.3 PersonName datatype semantics
Semantics of the PersonNameType:
Name Definition
PersonNameType
Describes the name of a person.
GivenName
Describes the given name(s) of a person. At least one given name shall be
specified in a name description. Given names include middle names and/or

middle initials, if known. Given names may be initials or abbreviation if only
these elements are known.
Linking Name
Describes a link used between family, given and other names (e.g. den, ten, van
den, von)
FamilyName
Describes the family name(s) of an individual. This may be a surname, clan
name, and so forth. The use of this element is optional since not all person
names include a family name.
Title
Indicates the titles that are part of the name of an individual, such as honorifics.
This part of a name is optional.
Salutation
Descries an individual's salutation or title. Eg. Mr., Mrs., Sir
Numeration
Indicates a roman numeral or other numeric designation that is part of the name
of an individual. For example, the "III" in "William James III."
dateFrom
Indicates the date starting from which this name came into use (e.g. date of
birth, date of change to a new name, and so forth). If not specified, then no so
such date is known.
dateTo
Indicates the date starting from which this name ceased to be used (death, old
name after name change, etc). If not specified, then use of the name is still
current.
type
Indicates the type of name using one of the following values:
• former – The name is no longer used.
• variant – The name is a variation of the official or most commonly used
name. For example, an abbreviated form of the official name, or an
informal nickname.
• main –The name is either the official one or is widely known and used.
xml:lang
Describes the language in which the name is described. This need not be the
same as the original language of the name. For example, a Japanese name can
be described in English.

Semantics of the NameComponentType:
Name Definition
NameComponentType
Describes a component of a name.
Initial
Indicates the initial for the name component. Initials are a truncated form of the of
the name component.
abbrev
Indicates an alternative shorter form for a name component. For example, "Bill" for
"William."
8 © ISO/IEC 2005 – All rights reserved

---------------------- Page: 11 ----------------------
ISO/IEC 15938-5:2003/Amd.2:2005(E)
7.5.7.2 ElectronicAddress datatype syntax








 
  
 
  
  
   
   
    
    
   
   
  
  
 
  
 
 
 
 



7.5.7.3 ElectronicAddress datatype semantics
Semantics of the ElectronicAddressType:
Name Definition
ElectronicAddressType Describes an electronic address.
Telephone
Describes a telephone number.
type
Indicates a particular type of phone number, if known:
• central – The telephone number of a central switchboard.
• secondary – The telephone number is a mobile number (e.g., cell
phone).
Fax Describes a fax number.
Email
Describes an E-mail address.
Url
Describes a URL address, such as a home page.

© ISO/IEC 2005 – All rights reserved 9

---------------------- Page: 12 ----------------------
ISO/IEC 15938-5:2003/Amd.2:2005(E)
7.6.2.2 Place DS syntax








 
 
      minOccurs="0" maxOccurs="unbounded"/>
      minOccurs="0" maxOccurs="unbounded"/>
                minOccurs="0" maxOccurs="unbounded"/>
      minOccurs="0"/>
  
  
   
   
   
   
  
  
      minOccurs="0" maxOccurs="unbounded"/>
      minOccurs="0" maxOccurs="unbounded"/>
      minOccurs="0" maxOccurs="unbounded">
  
   
   
    
   
   
  
  
  
  
   
   
          minOccurs="1" maxOccurs="unbounded"/>
     type="mpeg7:TextualType"
    minOccurs="0"/>
   
   
   
  
  
   
   
     ="0" />
10 © ISO/IEC 2005 – All rights reserved

---------------------- Page: 13 ----------------------
ISO/IEC 15938-5:2003/Amd.2:2005(E)
     ="0" />
     ="0" />
    
          minOccurs ="0" />
          minOccurs ="0" />
     type="mpeg7:TextualType"
         minOccurs="0"/>
   
   
  
  
  
   minOccurs="0"/>
  
   
   
     ="0" />
     />
     ="0" />
   
   
  
  
   type="mpeg7:ElectronicAddressType"
   minOccurs="0" maxOccurs="unbounded"/>
 
 
 



7.6.2.3 Place DS semantics
Semantics of the PlaceType:
Name Definition
PlaceType Describes a location.
Name
Describes a name of the place. Multiple values are allowed to support
multiple languages.
NameTerm Describes a name of the place using a term from a classification scheme.
PlaceDescription
The textual description of a place.
© ISO/IEC 2005 – All rights reserved 11

---------------------- Page: 14 ----------------------
ISO/IEC 15938-5:2003/Amd.2:2005(E)
Name Definition
Role
Indicates the role of the place, such as "real location," "fictional setting," or
"shooting location."
GeographicPosition
Describes the geographic position of the place.
Point
Describes a geographic point in the place.
datum Indicates the geodetic datum system used in the description of
GeographicPosition (optional). Possible values include "wgs84“ (World
Geodetic System 1984), "itrf“ (International Terrestrial Reference Frames),
"tokyo“ (Tokyo Datum) and so on.
AstronomicalBody
Describes the name of the astronomical body on which the location exists.
For example, "Earth."
Region
Describes the region of the place specified using the appropriate
ISO 3166-2 region code.
AdministrativeUnit Describes the name of the administrative units to which the place belongs-
e.g. a city, a town, a village, or even a fictional unit as the USS Enterprise.
The administrative unit is a place within the region specified. More than
one administrative unit may be specified. In this case the order of
administrative is interpreted as being from largest to smallest. In other
words, each administrative unit should contain the subsequent
administrative unit.
Type
Indicates the type of administrative unit being identified (e.g. "town," "city,"
"spaceship").
PostalAddress Describes the postal address including street (or square) and house
number or name of the place. The postal address does not need to include
the information specified by other elements of the Place DS, such as
country, region, or administrative unit. However, such information may be
included in this element.
AddressLine
Describes one line of the postal address of the place. The division of the
postal address into lines is not specified by this standard.
PostingIdentifier Describes the postal identifier for the place (optional). For example, a ZIP
code or Postal code.
StructuredPostalAddress Describes a postal address by division into individual structured elements.
StreetNumber Describes the alphanumeric street number of an address. (e.g. “1” in 1
Downing Street)
StreetName Describes street or thoroughfare name
PostalTown Describes the postal town name
City
Describes city of the address
StateProvinceCounty
Describes the state, province or county of the address
InternalCoordinates Describes the internal coordinates of the place within the specified postal
address (e.g. an apartment or room number, the drawing
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.