JSON-LD harmonizes the representation of Linked Data in JSON by describing a common JSON representation format for expressing directed graphs; mixing both Linked Data and non-Linked Data in a single document. The format has already been adopted by large companies such as Google in their Gmail product and is available to over 425 million customers around the world.
This is a 2nd Last Call publication for the JSON-LD 1.0 Algorithms and API specification. Changes since the previous publication include a shift to use a Future’s based API design approach, better base URL processing, and better translation of data from RDF.
All substantive technical work on the specification is complete. Feedback on both specifications is encouraged and should be sent to firstname.lastname@example.org. The 2nd Last Call period will end in 3 weeks, on June 06th 2013.
The Semantic Web Interest Group has published a new draft for the vCard-in-RDF Ontology, edited by Renato Iannella and James McKinney. The new draft updates the previous version by aligning it with the latest IETF vCard specification, ie, RFC6350.
This is a draft; If you wish to make comments regarding this document, please send them to email@example.com (subscribe, archives). The goal is to publish an Interest Group Note once there is a consensus in the community.
The W3C Provenance Working Group was chartered to develop a framework for interchanging provenance on the Web. The Working Group has now published the PROV Family of Documents as W3C Recommendations, along with corresponding supporting notes. You can find a complete list of the documents in the PROV Overview Note. PROV enables one to represent and interchange provenance information using widely available formats such as RDF and XML. In addition, it provides definitions for accessing provenance information, validating it, and mapping to Dublin Core.
JSON has proven to be a highly useful object serialization and messaging format. JSON-LD is a JSON-based format that can be used to serialize Linked Data. The syntax is designed to not disturb already deployed systems running on JSON, but provide a smooth upgrade path from JSON to JSON-LD. It is primarily intended to be a way to use Linked Data in Web-based programming environments, to build interoperable Web services, and to store Linked Data in JSON-based storage engines. JSON-LD is capable of serializing any RDF graph or dataset and most, but not all, JSON-LD documents can be directly transformed to RDF.
This is a Last Call publication for both specifications. All substantive technical work on each specification is complete. Feedback on both specifications is encouraged and should be sent to firstname.lastname@example.org. The Last Call period will end in 4 weeks, on May 10th 2013.
RDF 1.1 Semantics. This document describes a precise semantics for the Resource Description Framework 1.1 and RDF Schema. It defines a number of distinct entailment regimes and corresponding systems of inference rules. It is part of a suite of documents which comprise the full specification of RDF 1.1.
TriG. This document defines a textual syntax for RDF called TriG that allows an RDF dataset to be completely written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. TriG is an extension of the Turtle format.
On March 20th, 2013 members of the Provenance Working Group gave a tutorial on the PROV family of specifications at the EDBT conference in Genova, Italy. EDBT (“Extending Database Technology”) is widely regarded as one of the prime venues in Europe for dissemination of data management research.
The idea behind the tutorial was to provide a “database-centric” view of PROV, as a complement to the Semantic Web perspective offered by other tutorials, past and future, namely the ISWC’12 PROV tutorial (Boston, Nov. 2012) and the upcoming ESWC’13 PROV tutorial (Montpellier, France May 26-30).
The 1.5 hours tutorial was attended by about 26 participants, mostly from academia. It was structured into three parts of approximately the same length. The first two parts introduced PROV as a relational data model with constraints and inference rules, supported by a (nearly) relational notation (PROV-N). The third part presented known extensions and applications of PROV, based on the extensive PROV implementation report and implementations known to the presenter at the time.
This week we’ll hear from Maori Ito (National Institute of Biomedical Innovation, Osaka) on schema.org extensions for biomedical databases, with an opportunity to discuss these in depth.
Abstract: Lack of unified annotation makes it difficult to find specific information across a set of life science databases. Here, we discuss proposed extensions to schema.org to semantically annotate biological databases and their entries using the microdata format. We have applied this to Japanase biomedical data & resources to provide additional fields in our search results. We hope to finalize this proposal and encourage databases to adopt the extension, thereby improving the quality of search results.
W3C Wiki page : http://www.w3.org/wiki/WebSchemas/BioDatabases#BiologicalDatabaseEntry
Properties and example of markup are shown in this page.
BioHackathon2012 : https://github.com/dbcls/bh12/wiki/Schema.org-extension
How and why, discussions and useful links are shown in this link.
BH12.12 (Japanese) : http://wiki.lifesciencedb.jp/mw/index.php/BH12.12/schema.org Concrete examples of markup and search results, discussions and comments are shown in this link.
But why do we need a mapping between Dublin Core and PROV? Dublin Core has been typically used to describe document metadata in the Web. Many of its terms are directly related to provenance, which describe how the document has been modified, who participated in its creation, or when it was created, issued or published. Dublin Core is widely used and it has a strong community of users behind, so the alignment to a W3C specification for provenance is crucial for interoperability in the Web.
How can you use the mapping? If you are currently using Dublin Core terms and you want to derive direct PROV statements from your assertions, take a look at the direct mappings section. If you are interested in obtaining more refined qualified statements from your Dublin Core metadata, we suggest you to explore the Complex Mappings section.
How can you contribute? By sending us comments, suggestions and feedback. We aim to do a final release of the document before the end April and your comments would very appreciated.