linked open data National Libraries and a Museum open up their data using CC0 CC0 has been getting lots of love in the last couple months in the realm of data, specifically GLAM data (GLAM as in Galleries, Libraries, Archives, Museums). The national libraries of Spain and Germany have released their bibliographic data using the CC0 public domain dedication tool. For those of you who don’t know what that means, it means that the libraries have waived all copyrights to the extent possible in their jurisdictions, placing the data effectively into the public domain. What’s more, the data is available as linked open data, which means that the data sets are available as RDF (Resource Description Framework) on the web, enabling the data to be linked with other data from different sources. “Open Data Stickers” / Copyright and related rights waived via CC0 by jwyg The National Library of Spain teamed up with the Ontology Engineering Group (OEG) to create the data portal: datos.bne.es. 2 Comments » 3 Comments »
Apache Jena - Home How to return SPARQL results in JSON-LD? Lignes de temps Le logiciel Lignes de temps met à profit les possibilités d’analyse et de synthèse offertes par le support numérique. Inspirées par les «timelines» ordinairement utilisées sur les bancs de montage numérique, Lignes de temps propose une représentation graphique d’un film, révélant d’emblée, et in extenso, son découpage. Lignes de temps offre en cela un accès inédit au film, en substituant à la logique du défilement contraint qui constitue l’expérience de tout spectateur de cinéma, et pour les besoins de l’analyse, la «cartographie» d’un objet temporel. Aussi, en sélectionnant un segment d’une ligne de temps, l’utilisateur a-t-il accès directement au plan ou à la séquence correspondante dans le film, séquence qui peut être décrite et analysée par des commentaires textuels, audio, vidéo, ou documentée par des images ou des liens Internet. Pour appareiller les pratiques « amateurs » Objectivation, subjectivation, communautisation Regards signés et formes de rendu FAQ (questions fréquentes)
Linked Data Platform Best Practices and Guidelines 2.1 Predicate URIs should be HTTP URLs URIs are used to uniquely identify resources and URLs are used to locate resources on the Web. That is to say that a URL is expected to resolve to an actual resource, which can be retrieved from the host. A URI, on the other hand, may also be a URL, but it does not have to be; it may refer to something that has no retrievable representation. One of the fundamental ideas behind Linked Data is that the things referred to by HTTP URIs can actually be looked up ("dereferenced"). Of course, it is also a common practice to reuse properties from open vocabularies that are publicly available. 2.2 Use and include the predicate rdf:type to represent the concept of type in LDPRs It is often very useful to know the type (class) of an LDPR, though it is not essential to work with the interaction capabilities that LDP offers. Example 1: Representation of an LDPR with explicit declaration of rdf:type @prefix rdf: <
RDF Translator How to create and publish a SKOS taxonomy in 5 minutes · AKSW/OntoWiki Wiki In a real world case you would have deployed OntoWiki on a server reachable by some specific URL. Lets assume that URL is After the following steps the resources created in this examples would then be resolvable by accessing them with a browser, for example by visiting This means that all resources created in OntoWiki are automatically published. The example taxonomy @prefix rdf: < . Note: In a real world case it would be better to reuse an existing product class. for example Create the knowledge base Open OntoWiki and log in as "Admin" or some other user that can create knowledge bases.Go to Knowledge Bases->Edit->Create Knowledge Base.Set the Knowledge Base URI to Now you have several options: Add classes and properties using dialogs On the right you should see the window "Properties of Product". Upload a file Paste source
curl and libcurl Data on the Web Best Practices Status of This Document This section describes the status of this document at the time of its publication. Other documents may supersede this document. This early version of the document shows its expected scope and future direction. This document was published by the Data on the Web Best Practices Working Group as an Editor's Draft. Publication as an Editor's Draft does not imply endorsement by the W3C Membership. This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. This document is governed by the 1 August 2014 W3C Process Document. Introduction The best practices described below have been developed to encourage and enable the continued expansion of the Web as a medium for the exchange of data. In broad terms, data publishers aim to share data either openly or with controlled access. This document sets out a series of best practices that will help publishers and consumers face the new challenges and opportunities posed by data on the Web. Context
The D2RQ Platform – Accessing Relational Databases as Virtual RDF Graphs The Quick Guide to GUIDs Our world is numbered. Books have ISBNs and products have barcodes. Cars have VINs, even people have social security numbers. Numbers help us reference items unambiguously. “John Smith” may be many people, but Social Security Number 123-45-6789 refers to one person exactly. A GUID (globally unique identifier) is a bigger, badder version of this type of ID number. Any way you title it, GUIDs or UUIDs are just big, gigantic ID numbers. The Problem With Counting “We don’t need no stinkin’ GUIDs,” you may be thinking between gulps of Top Ramen, “I’ll just use regular numbers and start counting up from 1.” Sure, it sounds easy. Who does the counting? The problem with counting is that we want to create ID numbers without the management headache. GUIDs to the Rescue GUIDs are large, enormous numbers that are nearly guaranteed to be unique. 30dd879c-ee2f-11db-8314-0800200c9a66 The format is a well-defined sequence of 32 hex digits grouped into chunks of 8-4-4-4-12. Here’s the thinking behind GUIDs:
LODE - Live OWL Documentation Environment Live OWL Documentation Environment (LODE), version 1.2 dated 3 June 2013, is a service that automatically extracts classes, object properties, data properties, named individuals, annotation properties, general axioms and namespace declarations from an OWL and OWL2 ontology, and renders them as ordered lists, together with their textual definitions, in a human-readable HTML page designed for browsing and navigation by means of embedded links. This LODE service is an open source development, and can be freely used, as described in this document. It may be used in conjunction with content negotiation to display this human-readable version of an OWL ontology when the user accesses the ontology using a web browser, or alternatively to deliver the OWL ontology itself when the user accesses the ontology using an ontology editing tool such as Protégé and NeOn Toolkit. The following pseudo-URL describes the way to call the LODE service: where: www.essepuntato.it/lode is the URL to call the service.
Globally Unique Identifier (GUID) Globally Unique Identifier (GUID) A GUID identifies a person. In a URI, the GUID identifies the person who is associated with the data of the resource. For example, the following URI refers to the contacts (acquaintances) of the person whose GUID is 6677. Using the YQL Contacts Table, you specify the user with the GUID value of 6677 with the guid key as seen in this example: SELECT * FROM social.contacts WHERE guid='6677' An application can obtain the GUID of the person who is running the application. The YQL Social Tables use the me variable to store the GUID of the user running the application. SELECT * FROM social.contacts WHERE guid=me GUIDs have the following characteristics: A GUID exists for every Yahoo ID and is never the same as the Yahoo ID. For syntax and other details, see the Introspective GUID section.