Towards a Global Infrastructure For Sharing Learning Resources - Revision history

Nathan Yergler at 00:18, 19 April 2010

2010-04-19T00:18:30Z

Nathan Yergler: Protected "Towards a Global Infrastructure For Sharing Learning Resources" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

2010-01-28T22:45:17Z

Protected "Towards a Global Infrastructure For Sharing Learning Resources" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

Nathan Yergler at 22:44, 28 January 2010

2010-01-28T22:44:59Z

Nathan Yergler at 19:47, 27 January 2010

2010-01-27T19:47:38Z

Nathan Yergler at 21:20, 13 January 2010

2010-01-13T21:20:23Z

Nathan Yergler at 22:22, 7 January 2010

2010-01-07T22:22:02Z

Nathan Yergler: /* Metadata */

2010-01-07T18:41:01Z

‎Metadata

Nathan Yergler at 18:39, 7 January 2010

2010-01-07T18:39:35Z

Nathan Yergler at 18:30, 7 January 2010

2010-01-07T18:30:21Z

Nathan Yergler at 18:26, 7 January 2010

2010-01-07T18:26:06Z

← Older revision		Revision as of 00:18, 19 April 2010
Line 63:		Line 63:
	If you want to make sure that the metadata you expose adhere to your self-imposed requirements, we strongly suggest leveraging a validation service, such as [http://ariadne.cs.kuleuven.be/validationService/ ARIADNE's validation service].		If you want to make sure that the metadata you expose adhere to your self-imposed requirements, we strongly suggest leveraging a validation service, such as [http://ariadne.cs.kuleuven.be/validationService/ ARIADNE's validation service].

−	[[Category:Learn]][[Category:~~DiscoverEd~~]][[Category:OER]]	+	[[Category:Learn]][[Category:OER Search]][[Category:OER]]

← Older revision		Revision as of 22:44, 28 January 2010
Line 1:		Line 1:
−	~~{{Draft}}~~
−
	''This document was developed by the participants of the [[OER Discovery 2009\|OER Search and Discovery meeting]], based on discussions at the meeting.''		''This document was developed by the participants of the [[OER Discovery 2009\|OER Search and Discovery meeting]], based on discussions at the meeting.''

@@ Line 1: / Line 1: @@
 {{Draft}}
-''This document was developed by the participants of the [http://opened.creativecommons.org/OER_Discovery_2009 OER Search and Discovery meeting], based on discussions at the meeting.''
+''This document was developed by the participants of the [[OER Discovery 2009|OER Search and Discovery meeting]], based on discussions at the meeting.''
 = Introduction =

← Older revision		Revision as of 21:20, 13 January 2010
Line 1:		Line 1:
		+	{{Draft}}
		+
	''This document was developed by the participants of the [http://opened.creativecommons.org/OER_Discovery_2009 OER Search and Discovery meeting], based on discussions at the meeting.''		''This document was developed by the participants of the [http://opened.creativecommons.org/OER_Discovery_2009 OER Search and Discovery meeting], based on discussions at the meeting.''

← Older revision		Revision as of 22:22, 7 January 2010
Line 1:		Line 1:
		+	''This document was developed by the participants of the [http://opened.creativecommons.org/OER_Discovery_2009 OER Search and Discovery meeting], based on discussions at the meeting.''
		+
	= Introduction =		= Introduction =

← Older revision	Revision as of 22:45, 28 January 2010
(No difference)

@@ Line 57: / Line 57: @@
 * [http://www.w3.org/XML/ XML]: the Extensible Markup Language that is at the heart of many Web document formats (like HTML).
-* [http://www.w3.org/RDF/ RDF]: the Resource Description Framework allows you to describe relationships and properties about your resources. The information is commonly written as XML.  If you are publishing XHTML content, we recommend using [http://en.wikipedia.org/wiki/RDFa RDFa] to include the metadata with the contentSee "ccREL: The Creative Commons Rights Expression Language" (http://wiki.creativecommons.org/ccREL) for a discussion of applications enabled by co-locating metadata and content. See "[[ccREL|ccREL: The Creative Commons Rights Expression Language]]" for a discussion of applications enabled by co-locating metadata and content.
+* [http://www.w3.org/RDF/ RDF]: the Resource Description Framework allows you to describe relationships and properties about your resources. The information is commonly written as XML.  If you are publishing XHTML content, we recommend using [http://en.wikipedia.org/wiki/RDFa RDFa] to include the metadata with the content. See [[ccREL|"ccREL: The Creative Commons Rights Expression Language"]] for a discussion of applications enabled by co-locating metadata and content.
 If you want to make sure that the metadata you expose adhere to your self-imposed requirements, we strongly suggest leveraging a validation service, such as [http://ariadne.cs.kuleuven.be/validationService/ ARIADNE's validation service].

← Older revision		Revision as of 18:39, 7 January 2010
Line 42:		Line 42:

	We strongly encourage you to register your repository in with ARIADNE or [http://oerfeeds.info OERfeeds.info].		We strongly encourage you to register your repository in with ARIADNE or [http://oerfeeds.info OERfeeds.info].
		+
		+	= Metadata =
		+
		+	Metadata describe the content. We strongly suggest that you use either one of the following two metadata schemas, that define an extensive set of metadata elements:
		+
		+	* [http://en.wikipedia.org/wiki/Learning_object_metadata LOM]: The IEEE Learning Object Metadata standard defines circa 70 elements that can be used to describe general, technical, educational and other aspects.
		+	* [http://dublincore.org/ DC]: Dublin Core metadata are more generic in nature. Specific extensions for learning content are discussed in the [http://dublincore.org/groups/education/index.shtml DCMI Education Community].
		+
		+	By adopting one of these common schemas, it is easy for software to process the metadata. For specific niche content, standards such as MPEG (for audio-visual material) and others, special purpose formats may be more appropriate. In that case, a mapping to LOM or DC enables interoperability with learning specific tools and infrastructures.
		+
		+	In order to enforce your requirements, you can define an "application profile". This typically involves making some metadata elements mandatory, or imposing constraints on the values that they can hold, etc.
		+
		+	Finally, the metadata are typically expressed in a machine-readable format, sometimes called a "binding". Common bindings includes:
		+
		+	* [http://www.w3.org/XML/ XML]: the Extensible Markup Language that is at the heart of many Web document formats (like HTML).
		+	* [http://www.w3.org/RDF/ RDF]: the Resource Description Framework allows you to describe relationships and properties about your resources. The information is commonly written as XML. If you are publishing XHTML content, we recommend using [http://en.wikipedia.org/wiki/RDFa RDFa] to include the metadata with the contentSee "ccREL: The Creative Commons Rights Expression Language" (http://wiki.creativecommons.org/ccREL) for a discussion of applications enabled by co-locating metadata and content. See "[[ccREL\|ccREL: The Creative Commons Rights Expression Language]]" for a discussion of applications enabled by co-locating metadata and content.
		+
		+	If you want to make sure that the metadata you expose adhere to your self-imposed requirements, we strongly suggest leveraging a validation service, such as [http://ariadne.cs.kuleuven.be/validationService/ ARIADNE's validation service].

← Older revision		Revision as of 18:30, 7 January 2010
Line 27:		Line 27:

	We suggest that you adopt OAI-PMH if you have no strong reason to prefer RSS, as OAI-PMH offers more features that can be important for third party developers. If you also want to provide feeds of new objects that are deposited in your repository, then an additional RSS feed is quite useful.		We suggest that you adopt OAI-PMH if you have no strong reason to prefer RSS, as OAI-PMH offers more features that can be important for third party developers. If you also want to provide feeds of new objects that are deposited in your repository, then an additional RSS feed is quite useful.
		+
		+	= Registration =
		+
		+	In order to enable harvesting software to contact a provider of content and metadata, this software must be aware of
		+
		+	* the location of the provider (typically a URL), as well as
		+	* the protocol(s) that the provider supports (OAI-PMH, RSS).
		+
		+	This information is typically maintained in a so-called '''registry'''. In a way, a registry is a meta-repository: a repository with information about repositories. Its main goal is to enable other services to discover repositories. To this effect, it sometimes also includes additional information about the content repositories, such as data about
		+
		+	* the collections they hold: their domain, the number of resources, etc.
		+	* when the repository was last updated,
		+	* etc.
		+
		+	We strongly encourage you to register your repository in with ARIADNE or [http://oerfeeds.info OERfeeds.info].

@@ Line 3: / Line 3: @@
 This document aims to help those who ask, "What should I be doing when I publish my OER's so that they are searchable and discoverable by the OER community and (perhaps) the whole world?". More specifically, this document aims to help those with a collection of such OER's.
 There are several options for many of the fundamental questions. Luckily, the number of options is actually quite limited. For nearly all producers we recommend adopting one of the choices outlined below.  These have significant adoption and deployment, increasing the reach and exposure of your OER.  We will develop bridges between the different approaches; indeed, many of these bridges already exist.
@@ Line 11: / Line 12: @@
 * For your content, we make no specific assumptions: HTML documents, OpenOffice documents, Microsoft Office documents, MPEG video clips, PDF documents, MP3 sound files, etc.; anything goes.  Of course, in the spirit of ''open'' educational resources, we certainly encourage you to publish in as open a format as feasible.
 * For the '''metadata''', we strongly suggest to use either [http://en.wikipedia.org/wiki/Learning_object_metadata Learning Object Metadata] or [http://en.wikipedia.org/wiki/Dublin_Core Dublin Core]. For specific niche domains, other formats like for instance MPEG apply as well. You may also define a so-called 'application profile' that defines your specific requirements your repository imposes with respect to metadata, so that you can enforce them. In concrete terms, such metadata can be expressed as XML or RDF.