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
