Talk:Metadata - Revision history

Martin.leese: /* IEEE Learning Object Metadata */ Tidied formatting (to make clearer who said what)

2012-06-05T19:39:27Z

IEEE Learning Object Metadata: Tidied formatting (to make clearer who said what)

← Older revision		Revision as of 19:39, 5 June 2012
Line 2:		Line 2:
	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.		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		Fred Kintanar ([[User:Fredkintanar05\|Fredkintanar05]]), 30 January 2006<br/>
	:Cebu City, Philippines		Cebu City, Philippines

	Having just looked at the [http://ltsc.ieee.org/wg12/ IEEE LOM page], I see they		: Having just looked at the [http://ltsc.ieee.org/wg12/ 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).
	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 [http://ltsc.ieee.org/wg12/ Annodex];		: What you want to do may already be possible with [http://ltsc.ieee.org/wg12/ Annodex]; try their [http://lists.annodex.net/cgi-bin/mailman/listinfo/ mailing lists], or the [http://lists.xiph.org/mailman/listinfo/ogg-dev Ogg-dev] mailing list.
	try their [http://lists.annodex.net/cgi-bin/mailman/listinfo/ mailing lists],
	or the [http://lists.xiph.org/mailman/listinfo/ogg-dev Ogg-dev] mailing list.

	:[[User:Imalone\|Imalone]] 05:48, 30 January 2006 (PST)		:[[User:Imalone\|Imalone]] 05:48, 30 January 2006 (PST)

Martin.leese: /* MDMF (now renamed M3F) replacing VorbisComments */ Put back attribution

2009-08-23T14:39:34Z

MDMF (now renamed M3F) replacing VorbisComments: Put back attribution

← Older revision		Revision as of 14:39, 23 August 2009
Line 32:		Line 32:
	::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". [[User:Martin.leese\|Martin Leese]] 12:01, 18 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". [[User:Martin.leese\|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		:::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!!!!!! [[User:Xpete\|Xpete]] 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. [[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)

Martin.leese: Zapped blank line + added attribution. Please use ~~~~.

2009-08-22T16:24:54Z

Zapped blank line + added attribution. Please use ~~~~.

← Older revision		Revision as of 16:24, 22 August 2009
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)

Vmol: /* Meta data files */

2009-08-22T14:25:57Z

Meta data files

← Older revision		Revision as of 14:25, 22 August 2009
Line 44:		Line 44:

	A general approach would make life very easy for a lot of people.		A general approach would make life very easy for a lot of people.
	Allowing Ogg to include files as meta data. 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).		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.		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.

Vmol: Added idea

2009-08-22T14:25:25Z

Added idea

← Older revision		Revision as of 14:25, 22 August 2009
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 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. 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: Fixed spelling mistake of mine

2009-05-04T17:28:12Z

Fixed spelling mistake of mine

← Older revision		Revision as of 17:28, 4 May 2009
Line 32:		Line 32:
	::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". [[User:Martin.leese\|Martin Leese]] 12:01, 18 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". [[User:Martin.leese\|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 ~~metadata~~ format and can't!!!!!! ~~[[User:Xpete\|Xpete]]~~ 29 January 2008		:::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. [[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)

Martin.leese: /* MDMF (now renamed M3F) replacing VorbisComments */ Added atribution

2008-04-13T02:32:46Z

MDMF (now renamed M3F) replacing VorbisComments: Added atribution

← Older revision		Revision as of 02:32, 13 April 2008
Line 32:		Line 32:
	::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". [[User:Martin.leese\|Martin Leese]] 12:01, 18 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". [[User:Martin.leese\|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 metadata format and can't!!!!!!		:::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 metadata format and can't!!!!!! [[User:Xpete\|Xpete]] 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. [[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)

Martin.leese: /* MDMF (now renamed M3F) replacing Vorbiscomments */ Response

2008-01-29T23:59:21Z

MDMF (now renamed M3F) replacing Vorbiscomments: Response

← Older revision		Revision as of 23:59, 29 January 2008
Line 20:		Line 20:
	:[[User:Imalone\|Imalone]] 05:48, 30 January 2006 (PST)		:[[User:Imalone\|Imalone]] 05:48, 30 January 2006 (PST)

	== MDMF (now renamed M3F) replacing ~~Vorbiscomments~~ ==		== MDMF (now renamed M3F) replacing VorbisComments ==

	The article read:		The article read:
	<blockquote>		<blockquote>
	"The format [MDMF] will possibly replace ~~Vorbis comments~~ altogether."		"The format [MDMF] will possibly replace VorbisComments altogether."
	</blockquote>		</blockquote>

	To which Imalone responded:		To which Imalone responded:
	:This seems unlikely, not least because ~~Vorbis comments~~ are much simpler to implement and interpret. Current consensus is that this will be supplementary or take precedence.--[[User:Imalone\|Imalone]] 06:21, 17 September 2007 (PDT)		: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.--[[User:Imalone\|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". [[User:Martin.leese\|Martin Leese]] 12:01, 18 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". [[User:Martin.leese\|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 metadata format and can't!!!!!!		:::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 metadata format and can't!!!!!!

			::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)

Xpete: /* MDMF (now renamed M3F) replacing Vorbiscomments */

2008-01-29T17:26:11Z

MDMF (now renamed M3F) replacing Vorbiscomments

← Older revision		Revision as of 17:26, 29 January 2008
Line 31:		Line 31:

	::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". [[User:Martin.leese\|Martin Leese]] 12:01, 18 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". [[User:Martin.leese\|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 metadata format and can't!!!!!!

Martin.leese: /* MDMF replacing Vorbiscomments */ Noted MDMF now renamed to M3F

2007-11-25T04:42:47Z

MDMF replacing Vorbiscomments: Noted MDMF now renamed to M3F

← Older revision		Revision as of 04:42, 25 November 2007
Line 20:		Line 20:
	:[[User:Imalone\|Imalone]] 05:48, 30 January 2006 (PST)		:[[User:Imalone\|Imalone]] 05:48, 30 January 2006 (PST)

	== MDMF replacing Vorbiscomments ==		== MDMF (now renamed M3F) replacing Vorbiscomments ==

	The article read:		The article read: