Whitehouse.gov has not implemented any of the [[CC REL]] license metadata specification. The code below generates the license mark above:
10 KB (1,578 words) - 18:44, 13 October 2012
...fication, but excluding any claims that are not necessary to implement the Specification as written.}'''
...ns the specification, if any, set forth in the License Data Record by the "Specification" entry.}'''
20 KB (3,013 words) - 17:29, 19 October 2010
...application itself which is being licensed, and thus there is no separate specification or software code which serves to limit the scope of the license.
...rosoft's Open Specification Promise, which specifically defines a "Covered Specification" in technical terms)
12 KB (1,830 words) - 17:20, 19 October 2010
{{DiscoverEd Specification
1 KB (217 words) - 23:59, 1 September 2010
{{DiscoverEd Specification
1 KB (167 words) - 15:28, 9 June 2010
{{DiscoverEd Specification
1,018 bytes (152 words) - 21:55, 7 June 2010
{{DiscoverEd Specification
...the overhead or restrictions of providing feeds or OAI-PMH support. This specification describes a linked, structured data model for curating resources for Discov
2 KB (270 words) - 19:52, 10 June 2010
{{DiscoverEd Specification
2 KB (229 words) - 17:55, 18 June 2010
{{DiscoverEd Specification
1 KB (207 words) - 19:59, 16 June 2010
{{DiscoverEd Specification
3 KB (457 words) - 20:24, 30 August 2010
{{DiscoverEd Specification
3 KB (610 words) - 05:26, 23 June 2010
* Like CC, MC will provide three readings: computational (a RDF specification like CC REL), in-depth (descriptive material about the 4 categories) and us
...iatives do not depend on us. That is, as MC in essence would be just a RDF specification in the collective webpage (gathered by semantic searches), there could be o
22 KB (3,397 words) - 03:34, 1 July 2010
|participants=At a minimum, we expect 5-10 people to be involved in the specification, design, development, and testing. Once Eleversion is ready for initial pro
12 KB (1,740 words) - 06:39, 1 July 2010
* Metadata specification (norms, CC0+PDM) draft [NRY: August 16]
8 KB (1,108 words) - 23:22, 5 January 2011
...ring subject matter that is not set forth or specifically described in the Specification.
...ns the specification, if any, set forth in the License Data Record by the "Specification" entry.
22 KB (3,438 words) - 22:01, 2 November 2010
...because a computer is eventually needed to run the software. However, if a Specification has both specific hardware and software teachings, then both types of claim
...licensee that it has indeed licensed all necessary claims by taking the “Specification” route. Thus, these two approaches should be seen as representing two way
27 KB (4,298 words) - 00:40, 22 June 2011
...ring subject matter that is not set forth or specifically described in the Specification.
...ns the specification, if any, set forth in the License Data Record by the "Specification" entry.
3 KB (501 words) - 17:19, 19 October 2010
...tion Against Open Software, the Eco-Patent Commons, and the Microsoft Open Specification Promise, all of which rely on estoppel.
4 KB (571 words) - 17:21, 19 October 2010
{{DiscoverEd Specification
A complete implementation of this specification would provide the following things.
2 KB (361 words) - 19:47, 8 September 2010
{{DiscoverEd Specification
...r ''category'' from their wiki aggregated into a DiscoverEd instance. This specification describes:
3 KB (508 words) - 15:56, 14 October 2010
...e site itself and for CC licensed resources, 3) a subset of the [[CC REL]] specification, and 4) search for CC-licensed resources.
IssueLab has implemented a subset of the [[CC REL]] specification by using the [[RelLicense|rel="license"]] attribute in links to the license
4 KB (559 words) - 17:44, 5 September 2011
...licensed/copyright waived with CC, 3) a subset of the [[CC REL]] metadata specification, and 4) a way to search for CC licensed content.
Archive.org has implemented a subset of the [[CC REL]] specification by including the [[RelLicense|rel="license"]] attribute in links to the CC
5 KB (752 words) - 13:43, 8 February 2014
...e itself and for individual videos, 2) a subset of the [[CC REL]] metadata specification for the site itself, and 3) links to the Creative Commons brand and web ass
Al Jazeera has implemented a subset of the [[CC REL]] specification with the [[RelLicense|rel="license"]] attribute in some of its links to the
4 KB (619 words) - 18:01, 13 September 2011
'''Creative Commons Rights Expression Language (CC REL)''' is a specification describing how license information may be described using RDF and how licen
3 KB (386 words) - 13:42, 27 April 2011
== Phase 1: Specification Development ==
The LRMI Specification was developed with a strong [[LRMI/Technical_Working_Group|Technical Workin
2 KB (313 words) - 02:39, 21 December 2013
''Skip to [[#Specification specific questions|specification specific questions]], [[#Technology questions|technology questions]], or [[
==Specification specific questions==
20 KB (3,174 words) - 23:57, 15 June 2012
== LRMI Specification version 1.1 ==
528 bytes (77 words) - 17:23, 7 February 2013
== LRMI Draft Specification ==
This is the 0.5 version of the Learning Resources Metadata Initiative specification as created by the [[LRMI/Technical Working Group|LRMI Technical Working Gro
6 KB (756 words) - 20:32, 21 November 2011
...fic research. The Creative Commons Rights Expression Language (ccREL) is a specification for how license information is described using RDF and how licensing inform
...e via the liberal CC BY license. Both CC0 and CC BY metadata include ccREL specification for machine-readable expression of copyright licensing terms and related in
17 KB (2,628 words) - 21:47, 13 January 2012
== LRMI Specification version 0.7 ==
3 KB (449 words) - 21:33, 14 May 2012
...machine readable producers of standards that are referenceable in the LRMI specification.
2 KB (250 words) - 15:26, 23 November 2015
...ces will be made available in at least one open technical format (with its specification made available without legal or technical constraints)
4 KB (611 words) - 04:37, 11 November 2015
...p a suite of best practices references for others wishing to implement the specification themselves. Most of these implementation projects have now been completed a
Mappings are created to "map" the LRMI specification to the currently in-use metadata schema on each platform or registry. This
6 KB (854 words) - 18:02, 12 May 2014
