PUBLIC MARKS with tags data & websemantique

introduces schemas for more than a hundred new categories, including movies, music, organizations, TV shows, products, places and more.

Google Refine is a power tool for working with messy data, cleaning it up, transforming it from one format into another, extending it with web services, and linking it to databases like Freebase.

The very nature of RDF makes it somewhat annoying to work with. RDF data is always going to be a kind of frankenstein's data monster, patched together from bits and pieces that can just about be made to fit together.

The Provenance Vocabulary provides classes and properties to describe the provenance of data from the Web. Hence, this vocabulary enables providers of Web data to publish provenance-related metadata about their data. The Provenance Vocabulary Core Ontology provides the main classes and properties required to describe provenance of data on the Web. Notice, this vocabulary is not designed to describe provenance of other kinds of content such as documents.

And of course he has triggered the usual bunch of complaints about it. Tools are too technical, stuff is presented by geeks for geeks, data are boring, we need betteer user interfaces etc. Among many smart but technical proposals, basically adding to the general complexity issue they are supposed to solve, I will pick up this very simple one by Karl Dubost.

ACTION : Tell a story to people

LinkedGeoData is an effort to add a spatial dimension to the Web of Data / Semantic Web. LinkedGeoData uses the information collected by the OpenStreetMap project and makes it available as an RDF knowledge base according to the Linked Data principles. It interlinks this data with other knowledge bases in the Linking Open Data initiative.

Dave (Reynolds) raised the point that lists are an integral part of most APIs. This is another thing that we know we need to address in the UK linked government data project, but are unsure as yet how best to do so.

The non-RDF bits of the data Web are – roughly – going to be the leaves on the tree.

He discusses this further in his post on influencing the production of public data. So let me throw it open: what do you want your city/county/province/national government to put online for you to play with, and why?

No matter what user interfaces will drive the user interaction, the dream of being able to search the web of data following relational connections (say, somehow looking for “the height of all towers located in Paris”) dies miserably when it’s powered by a vastly sparse and unconnected graph.

We introduce pushback, a method that enables writing changes to non-RDF sources such as flickr, Twitter, Amazon, etc. from an RDF document.

The video explains our motivation, the architecture and the interaction between the components as well as RDForms. A demo (for Jira, a professional issue tracker system) is included in this video, where we show how to create, deploy and use an RDForm.

See esw.w3.org/topic/PushBackDataToLegacySources for further information.

In particular, making schema changes or adding indexes to a database with more than 10 - 20 million rows completely locks the database for hours at a time.

There is a lot of structured data in web pages. While this data is usually backed by structured storage of some sort, a lot of the semantics of the data are lost by the time the page is rendered in the web browser.

Apart from small differences (mainly concerning copy editing and figures), the online editions should have the same content as the print edition. However, we are planning to fix errata in the online editions every few months or so.

Google's Alon Halevy admitted that the search giant has "not been doing a good job" presenting the structured data found on the web to its users. By "structured data," Halevy was referring to the databases of the "deep web" - those internet resources that sit behind forms and site-specific search boxes, unable to be indexed through passive means.

Bear in mind that data integration and aggregation (whether large-scale or small-) are intrinsically, necessarily, kinds of data reuse. No data reuse, no data integration.