Search results

Jump to: navigation, search

Page title matches

Page text matches

  • ...ses and formats with little commonality. For the Creative Commons metadata specification, we wanted to define a profile of the rights element that was more useful a
    10 KB (1,701 words) - 08:11, 25 April 2013
  • ...p://www.adobe.com/devnet/xmp/ defines] a rights management schema (see XMP Specification, p. 42). Creative Commons sets the following properties (example values):
    5 KB (735 words) - 05:58, 15 January 2015
  • See also: [http://www.adobe.com/devnet/xmp/ XMP Specification], p 36
    374 bytes (56 words) - 18:51, 4 March 2008
  • ...ationship is the Dublin Core "Type" attribute, and the href is the DC Text specification. Another document Type that could be specified with the href is http://purl
    13 KB (2,070 words) - 06:03, 28 October 2013
  • ...ts 9 standard keys in the dictionary. "License" is not among them, but the specification makes reference to the creation of new keys in two sentences in section 10.
    3 KB (447 words) - 16:58, 23 October 2009
  • ...are many video formats, each with its own ill-supported embedded metadata specification (if any). Creative Commons recommends adopting XMP across video formats, wi
    13 KB (2,030 words) - 14:31, 25 September 2014
  • ...currently stored in custom metadata fields; the next iteration of the ODF specification (not currently supported in tools) includes support for including arbitray
    1 KB (166 words) - 17:21, 4 March 2008
  • ...data Spec] is modified to include a "license" field in first class objects specification, [http://freedesktop.org/wiki/Software/Tracker Tracker] could be used to lo
    3 KB (405 words) - 23:55, 25 June 2009
  • A specification describing how license information may be described and attached to works.
    2 KB (283 words) - 23:49, 30 August 2016
  • * [[Companion File metadata specification]] [[Category:Specification]]
    3 KB (417 words) - 20:53, 23 September 2015
  • ...d December 6, 2000. A [http://web.resource.org/rss/1.0/modules/cc/ module specification] has been published for inclusion of licensing information in the feed.
    4 KB (553 words) - 19:26, 10 October 2007
  • [http://www.rssboard.org/rss-specification RSS 2.0] is a syndication (feed) format. A [http://cyber.law.harvard.edu/r The specification defines a namespace,
    2 KB (323 words) - 19:27, 3 December 2009
  • ...ommend and require [[RDFa]] for metadata transport, see the [[CC REL]] W3C specification and our [http://learn.creativecommons.org/wp-content/uploads/2009/07/discov ...sing Creative Commons licenses, we also recommend following the [[CC REL]] specification for identifying further CC license metadata.
    12 KB (1,855 words) - 18:10, 9 June 2010
  • '''Creative Commons Rights Expression Language (ccREL)''' is a specification describing how license information may be described using RDF and how licen
    3 KB (431 words) - 23:09, 28 November 2023
  • ..., probably this would have to be a [[parametric license]] to allow for the specification of [[expiry date]]s, [[price]], and other [[terms of use]] that might apply
    888 bytes (125 words) - 20:53, 12 June 2009
  • ...orking with Torrent consumers, indexers and publishers to develop a simple specification for embedding license metadata in a torrent file. We hope to publish a [ht
    804 bytes (110 words) - 22:02, 17 March 2008
  • Jamendo has implemented a subset of the [[CC REL]] specification by adding [[RelLicense|rel="license"]] tags into links to the CC license de
    16 KB (2,421 words) - 19:49, 16 December 2010
  • Flickr has implemented a subset of the [[CC REL]] specification by specifying the 'license' and 'cc:license'. Note that both names are cont
    10 KB (1,504 words) - 20:48, 25 July 2013
  • ...labs.creativecommons.org/~nathan/oscri/describing-registrations.html draft specification] for details.
    369 bytes (50 words) - 20:29, 24 September 2015
  • ...commons.org/~nathan/oscri/describing-registrations.html Draft Registration Specification]
    333 bytes (34 words) - 19:59, 25 June 2009
  • 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) - 17: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) - 16: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) - 16:20, 19 October 2010
  • {{DiscoverEd Specification
    1 KB (217 words) - 22:59, 1 September 2010
  • {{DiscoverEd Specification
    1 KB (167 words) - 14:28, 9 June 2010
  • {{DiscoverEd Specification
    1,018 bytes (152 words) - 20: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) - 18:52, 10 June 2010
  • {{DiscoverEd Specification
    2 KB (229 words) - 16:55, 18 June 2010
  • {{DiscoverEd Specification
    1 KB (207 words) - 18:59, 16 June 2010
  • {{DiscoverEd Specification
    3 KB (457 words) - 19:24, 30 August 2010
  • {{DiscoverEd Specification
    3 KB (610 words) - 04: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) - 02: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) - 05:39, 1 July 2010
  • * Metadata specification (norms, CC0+PDM) draft [NRY: August 16]
    8 KB (1,108 words) - 22: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) - 21: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) - 23:40, 21 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) - 16: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) - 16:21, 19 October 2010
  • {{DiscoverEd Specification A complete implementation of this specification would provide the following things.
    2 KB (361 words) - 18:47, 8 September 2010
  • {{DiscoverEd Specification ...r ''category'' from their wiki aggregated into a DiscoverEd instance. This specification describes:
    3 KB (508 words) - 14: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) - 16: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) - 12: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) - 17: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) - 12: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) - 01: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) - 22:57, 15 June 2012
  • == LRMI Specification version 1.1 ==
    528 bytes (77 words) - 16: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) - 19: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) - 20:47, 13 January 2012
  • == LRMI Specification version 0.7 ==
    3 KB (449 words) - 20:33, 14 May 2012

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)