W3C home > Mailing lists > Public > public-xg-mmsem@w3.org > April 2007

RE: [MMSEM-Vocabulary] XGR 'Multimedia Vocabularies on the Semantic Web' available

From: Hausenblas, Michael <michael.hausenblas@joanneum.at>
Date: Tue, 24 Apr 2007 10:07:46 +0200
Message-ID: <768DACDC356ED04EA1F1130F97D29852010DF13B@RZJC2EX.jr1.local>
To: "Christian Timmerer \(ITEC\)" <christian.timmerer@itec.uni-klu.ac.at>, <erik.mannens@ugent.be>
Cc: <public-xg-mmsem@w3.org>

Christian, Erik,

Thank you for the help and the wording. I have now updated 
the Wiki [1] and the XGR [2] accordingly to reflect the changes.

@Erik: If possible, please make the changes in the Wiki directly,
rather than via mail - makes (my) life easier ;)

@Christian: If you can make it by next Monday that would be great -
the goal is to have the XGR [2] ready *before* 1 May 2007 ...

@All: I'm still awaiting feedback on the XGR [2] - typos, 
inconsistencies, etc. ... everything is welcome to make this
deliverable go live as planned :)

Please be aware of the fact that I can't make it to the telecon
due to a travel from 25 - 27 April.


[1] http://www.w3.org/2005/Incubator/mmsem/wiki/Vocabularies 
[2] http://www.w3.org/2005/Incubator/mmsem/XGR-vocabularies-20070419/

 Michael Hausenblas, MSc.
 Institute of Information Systems & Information Management
 JOANNEUM RESEARCH Forschungsgesellschaft mbH

>-----Original Message-----
>From: Christian Timmerer (ITEC) 
>Sent: Monday, April 23, 2007 7:24 PM
>To: erik.mannens@ugent.be; Hausenblas, Michael
>Cc: public-xg-mmsem@w3.org; christian.timmerer@itec.uni-klu.ac.at
>Subject: RE: [MMSEM-Vocabulary] XGR 'Multimedia Vocabularies 
>on the Semantic Web' available
>Dear Erik, Michael,
>  I'm happy to contribute but unfortunately I'm not able to 
>provide something by this week but until beginning of next 
>week seems to be doable. Recently, I've given a presentation 
>on MPEG-21 and information about this (incl. a set of slides) 
>can be found on [1] and [2].
>Best regards,
> -Christian
>[1] http://mpeg79.emi.ac.ma/workshop.htm#MPEG21
>[2] http://www-itec.uni-klu.ac.at/~timse/#pres
>:- Dipl.-Ing. Dr. Christian Timmerer
>:- Department of Information Technology (ITEC)
>:- Klagenfurt University, Austria
>:- http://research.timmerer.com
>>> Visit the IT Campus Carinthia
>>> http://www.it-campus.at
>From: public-xg-mmsem-request@w3.org 
>[mailto:public-xg-mmsem-request@w3.org] On Behalf Of Erik Mannens
>Sent: Monday, April 23, 2007 5:09 PM
>To: 'Hausenblas, Michael'; christian.timmerer@itec.uni-klu.ac.at
>Cc: public-xg-mmsem@w3.org
>Subject: [MMSEM-Vocabulary] XGR 'Multimedia Vocabularies on 
>the Semantic Web' available
>Dear Michael, Christian,
>hereby the MPEG-21 snippet that could replace the old one. 
>Christian, can you check if all your comments are taken care of?
>Sincere greetings,
>Erik Mannens
>Project Manager
>Ghent University - IBBT
>Faculty of Engineering
>Department of Electronics and Information Systems
>Multimedia Lab
>Gaston Crommenlaan 8 bus 201, B-9050 Ledeberg-Ghent, Belgium
>t: +32 9 33 14993
>f: +32 9 33 14896
>m: +32 473 27 44 17
>t sec: +32 9 33 14911
>e: erik.mannens@ugent.be <mailto:erik.mannens@ugent.be> 
>URL: http://multimedialab.elis.ugent.be 
>The MPEG-21 standard aims at defining a framework for 
>multimedia delivery and consumption which supports a variety 
>of businesses engaged in the trading of digital objects. 
>MPEG-21 is quite different to its predecessors, as it is not 
>focused on the representation and coding of content like 
>MPEG-1 to MPEG-7 do, but instead focusing on filling the gaps 
>in the multimedia delivery chain. MPEG-21 was developed with 
>the vision in mind that it should offer users transparent and 
>interoperable consumption and delivery of rich multimedia 
>content. The MPEG-21 standard consists of a set of tools and 
>builds on its previous coding and metadata standards like 
>MPEG-1, -2, -4 and -7, i.e., it links them together to produce 
>a protectable universal package for collecting, relating, 
>referencing and structuring multimedia content for the 
>consumption by users (the Digital Item). The vision of MPEG-21 
>is to enable transparent and augmented use of multimedia 
>resources (e.g. music tracks, videos, text documents or 
>physical objects) contained in digital items across a wide 
>range of networks and devices. 
>The two central concepts of MPEG-21 are Digital Items, a 
>fundamental unit of distribution and transaction, and the 
>concept of Users interacting with Digital Items: A User is any 
>entity that interacts in the MPEG-21 environment or makes use 
>of a Digital Item, and a Digital Item is a structured digital 
>object with a standard representation, identification and 
>metadata within the MPEG-21 framework. This entity is also the 
>fundamental unit of distribution and transaction within this 
>The MPEG-21standard consists of 18 parts (part 13, formerly 
>known as Scalable Video Coding, has been specified as an 
>amendment to MEPG-4 part 10; consequently, part 13 is 
>currently no longer in use): 
>*	Digital Item Declaration (DID) - provides a schema 
>consisting of a set of abstract terms and concepts to define 
>Digital Items. The DID Model defines digital items, 
>containers, fragments or complete resources, assertions, 
>statements and annotations on digital items. 
>*	Digital Item Identification and Description (DII) - is 
>concerned with the ability to identify and refer to complete 
>or partial Digital Items. 
>*	Intellectual Property Management and Protection (IPMP) 
>- specifies how to include IPMP information and protected 
>parts of Digital Items in a DIDL document. It declares a IPMP 
>Digital Item Declaration Language, which provides for a 
>protected representation of the DID model. Secondly, it 
>declares IPMP Information schemas, which define structures for 
>expressing protection-related information. 
>*	Rights Expression Language (REL) - provides a schema to 
>declare rights and permissions using the terms as defined in 
>the Rights Data Dictionary. 
>*	Rights Data Dictionary (RDD) - comprises of a set of 
>uniquely identified terms that can be used to declare rights 
>on items using the REL. 
>*	Digital Item Adaptation (DIA) - primarily specifies 
>metadata on which the adaptation of content across devices and 
>networks could be based. Additionally it specifies the 
>behavior and a framework for tools to assist the adaptation of 
>*	Reference Software: This part includes descriptions and 
>implementations of the normative parts of the standard (DID, 
>DII, REL, RDD and DIA). This part should ensure a fast 
>adaptation and implementation of compliant applications. 
>*	File Format: This part specifies how the MPEG-21 file 
>(container) format where a digital item and its references 
>content can be placed. The file format is an extension of the 
>ISO file format. 
>*	Digital Item Processing (DIP) - DIP should improve the 
>processing of 'static' Digital Items by providing tools that 
>allow Users to add functionality to a DID. One possible use of 
>DIP is to provide a Digital Item with a set of methods that 
>can are visible to users and could be performed on the DI. For 
>this purpose the DIP part specifies so called Digital Item 
>Methods (DIM) that can be expressed using the Digital Item 
>Method Language (DIML). 
>*	Vision, Technology and Strategy: This parts includes an 
>overview of the standard 
>*	Evaluation Methods for Persistent Associations: This 
>part deals with how resources and metadata can be persistently 
>linked and how especially IPMP protection can be ensured on 
>the content. 
>*	Test Bed for MPEG-21 Resource Delivery: This part 
>consists of a software framework including a streaming player, 
>a media server and a network emulator to test MPEG-21 tools. 
>*	Conformance Testing 
>*	Event Reporting 
>*	Binary Format 
>*	Fragment Identification for MPEG Media Types 
>*	Digital Item Streaming 
>MPEG-21 identifies and defines the mechanisms and elements 
>needed to support the multimedia delivery chain as described 
>above, as well as the relationships between and the operations 
>supported by them. Within the parts of MPEG-21, these elements 
>are elaborated by defining the syntax and semantics of their 
>characteristics, such as interfaces to the elements. 
Received on Tuesday, 24 April 2007 08:03:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:01:25 UTC