Talk:Metadata

From XiphWiki

(Difference between revisions)
Jump to: navigation, search
m (Meta data files)
m (Zapped blank line + added attribution. Please use ~~~~.)
Line 35: Line 35:
::An Ogg container can contain more than one logical stream. [[M3F]] will be a separate logical stream, and will be separate from the [[Vorbis]] stream. As [[M3F]] does not touch [[Vorbis]], backwards compatibility will not be a problem. [[User:Martin.leese|Martin Leese]] 15:59, 29 January 2008 (PST)
::An Ogg container can contain more than one logical stream. [[M3F]] will be a separate logical stream, and will be separate from the [[Vorbis]] stream. As [[M3F]] does not touch [[Vorbis]], backwards compatibility will not be a problem. [[User:Martin.leese|Martin Leese]] 15:59, 29 January 2008 (PST)
-
 
== Meta data files ==
== Meta data files ==
Line 48: Line 47:
This way Ogg doesn't have to make or support an complicated and advanced meta data file format for structuring the information itself. Ogg doesn't have to be able to decode them, only contain them which wouldn't be very difficult because it just holds files.  
This way Ogg doesn't have to make or support an complicated and advanced meta data file format for structuring the information itself. Ogg doesn't have to be able to decode them, only contain them which wouldn't be very difficult because it just holds files.  
Making Ogg more efficient, streamlined and powerful at the same time.  
Making Ogg more efficient, streamlined and powerful at the same time.  
-
 
How would this work?  
How would this work?  
Line 57: Line 55:
This then could show all the relevant files and folder.  
This then could show all the relevant files and folder.  
Enabling to browse the folder in the file as a normal folder in the file system would be a very good way of providing access for users and programs.
Enabling to browse the folder in the file as a normal folder in the file system would be a very good way of providing access for users and programs.
 +
 +
[[User:Vmol|Vmol]] 08:25, 22 August 2009 (MDT)

Revision as of 16:24, 22 August 2009

IEEE Learning Object Metadata

The proposed solution is RDF + Dublin Core. Has anybody looked into supporting IEEE LOM, the Learning Object Metadata standard that I believe can incorporate Dublin Core? This is being adopted by key players in the e-learning world (IMS Global Learning, and SCORM), and would be valuable for the applications I am interested in.

Fred Kintanar
Cebu City, Philippines

Having just looked at the IEEE LOM page, I see they have XML and RDF bindings defined. The current view seems to be that you package a RDF or RDF/XML description of the content into the Ogg stream, with Dublin Core being a minimum feature set (Dublin Core certainly doesn't provide everything one might want). Handlers would most likely ignore or "dumb-down" relations they don't understand. In that case this would certainly work, but at the moment there is no clear plan (details like references between and into logical streams haven't really been considered as far as I can tell).

What you want to do may already be possible with Annodex; try their mailing lists, or the Ogg-dev mailing list.

Imalone 05:48, 30 January 2006 (PST)

MDMF (now renamed M3F) replacing VorbisComments

The article read:

"The format [MDMF] will possibly replace VorbisComments altogether."

To which Imalone responded:

This seems unlikely, not least because VorbisComments are much simpler to implement and interpret. Current consensus is that this will be supplementary or take precedence.--Imalone 06:21, 17 September 2007 (PDT)
As I understand it, the purpose of MDMF is to replace VorbisComments for the use of structured metadata, allowing VorbisComments to revert to its orginally intended use of "short, text comments ... much like someone jotting a quick note on the bottom of a CDR." I will modify the article to say this. The Vorbis docs even state "arbitrary metadata belongs in a separate logical bitstream (usually an XML stream type) that provides greater structure and machine parseability". Martin Leese 12:01, 18 September 2007 (PDT)
Then Vorbis will have to be replaced by a successor because else you get backwards compatibility issues when players try to read vorbis with the new meta data format and can't!!!!!! 29 January 2008
An Ogg container can contain more than one logical stream. M3F will be a separate logical stream, and will be separate from the Vorbis stream. As M3F does not touch Vorbis, backwards compatibility will not be a problem. Martin Leese 15:59, 29 January 2008 (PST)

Meta data files

Meta data is handy and structured meta data handier.

However sometimes there is a lot of metadata and it's not handy to use some tagged metadata.

A general approach would make life very easy for a lot of people. Allowing Ogg to include files as meta data (and folders). Enabling those files to be added, deleted changed opened as normal files with external programs. Or viewed with file managers. e.g. ad a tab meta data files in the File Properties dialog that displays the meta data files and sub folder(s).

This way Ogg doesn't have to make or support an complicated and advanced meta data file format for structuring the information itself. Ogg doesn't have to be able to decode them, only contain them which wouldn't be very difficult because it just holds files. Making Ogg more efficient, streamlined and powerful at the same time.

How would this work? In the files, there would be a folder called meta data files. This folder would contain every meta data file as files.

The files could be made visible in the file system by adding a tab called meta data files. This then could show all the relevant files and folder. Enabling to browse the folder in the file as a normal folder in the file system would be a very good way of providing access for users and programs.

Vmol 08:25, 22 August 2009 (MDT)

Personal tools


Main Page

Xiph.Org Projects

Audio—

Video—

Text—

Container—

Streaming—