Planet RDF

It's triples all the way down

May 28

Bob DuCharme: Reuse? Ha!

Reuse is Good, especially when you reuse my work.

Posted at 18:10

Norm Walsh: Rail trail photowalk

This afternoon, I had a little wander down the rail trail with my camera.

Posted at 10:56

May 27

Norm Walsh: XML Calabash 1.0.3 released

Announcing a new release of XML Calabash.

Posted at 19:24

Norm Walsh: Top of Sugarloaf

An unsuccessful attempt at a half century.

Posted at 12:10

May 26

Semantic Web Company (Austria): Re-vamped PoolParty Knowledge Discoverer has been released

PoolParty team has released a brandnew version of its knowledge discoverer to showcase the power of knowledge models in combination with linked data and text mining.

First of all: PoolParty Knowledge Discoverer is more about collecting context information about documents which deal with domain-specific ‘things’ like persons, places, companies etc. than a search engine in a ‘classical’ sense.

PoolParty Knowledge Discoverer

Don´t expect to find a pizzeria in your neighbourhood with this kind of tool. If you want to build a similar tool like this, take a look at the PoolParty product family.

How does it work?

Provide some text either by

  • typing your topic or
  • by retrieving text from a URL or
  • by entering a text directly into the editor

PoolParty will analyse your text.

Now you will get smart recommendations and context information:

  • related contents from Wikipeda
  • categories related to the text
  • images related to the text
  • tags relevant for the text

For example: If you want to get a quick overview over an interesting article of ‘The Guardian’ about open data, just click on the bookmarklet which can be installed to use the Knowledge Discoverer instantly, and you will be redirected to the following page.

The tool is a blueprint for many use cases in different sectors, here are some examples:

  • find relations between open positions and applicants in your recruiting database
  • find those pieces of your technical documentation which are related to a concrete description of a customer´s problem
  • save time when analysing new markets by collecting and linking information about your target market from different databases

Interested? Wanna see how this could work in established platforms like Confluence? Come to Atlassian Summit or SemTechBiz (both to be held in San Francisco) next week and visit us at the PoolParty booth!

Posted at 18:57

May 25

Dublin Core Metadata Initiative: DC-2012 pre-conference semantic metadata tutorials

2012-05-25, The two DC-2012 full-day pre-conference tutorials will each provide information professionals with beginning knowledge and skills necessary to design and development of semantic metadata including design of ontologies and controlled vocabularies useful in linked data on the open Web. The tutorials will also focus on design of metadata application profiles to meet an organization or company's needs to publish to the open Web using OWL and topic maps ontologies. Presenters Karen Coyle and Sam Oh have extensive experience teaching and working with professionals practicing in all forms of memory institutions (libraries, museums and archives) as well as the private sector. The tutorials are designed to address the needs of professionals with either minimal technical skills or those with extensive skills in non-semantic metadata wanting to develop knowledge and skills in the context of linked data and the Semantic Web.

Posted at 23:59

Dublin Core Metadata Initiative: DC-2012 online registration now open

2012-05-25, Online registration for DC-2012 is now open at http://ktw.mimos.my/registration2012/. DC-2012 is part of the Knowledge Technology Week 2012 activities.

Posted at 23:59

AKSW Group - University of Leipzig: Sorry, I don’t speak SPARQL – A Survey

Many Semantic Web applications are currently based on SPARQL. In particular, an increasing number of systems, such as question answering systems, keyword search or search by example internally construct SPARQL queries. However, lay users do not understand this language, so it is difficult to give the user feedback on what queries the system constructed. To address the gap between SPARQL and natural language, the AKSW and CITEC groups have devised an approach for transforming SPARQL queries to natural language.

You (yes, you!) can help us by judging the quality of the translations we present in this survey:

http://sparql2nl.aksw.org/eval

The survey can be done by both – SPARQL experts and lay users. For lay users, it takes 5 minutes to complete and 15 minutes for experts. In addition to the interesting (sometimes challenging) questions, there are also great prizes to win. 10 randomly selected participants will receive Amazon vouchers:

1st prize: 200 Euro
2nd prize: 100 Euro
3rd prize: 50 Euro
4th – 10th prize: 25 Euro

If you want to win a prize, you need to fill in your name at the end of the survey.

Enjoy the survey,

The SPARQL2NL Team

Posted at 09:54

AKSW Group - University of Leipzig: Sorry, I don’t speak SPARQL – A Survey

Many Semantic Web applications are currently based on SPARQL. In particular, an increasing number of systems, such as question answering systems, keyword search or search by example internally construct SPARQL queries. However, lay users do not understand this language, so it is difficult to give the user feedback on what queries the system constructed. To address the gap between SPARQL and natural language, the AKSW and CITEC groups have devised an approach for transforming SPARQL queries to natural language.

You (yes, you!) can help us by judging the quality of the translations we present in this survey:

http://sparql2nl.aksw.org/eval

The survey can be done by both – SPARQL experts and lay users. For lay users, it takes 5 minutes to complete and 15 minutes for experts. In addition to the interesting (sometimes challenging) questions, there are also great prizes to win. 10 randomly selected participants will receive Amazon vouchers:

1st prize: 200 Euro
2nd prize: 100 Euro
3rd prize: 50 Euro
4th – 10th prize: 25 Euro

If you want to win a prize, you need to fill in your name at the end of the survey.

Enjoy the survey,

The SPARQL2NL Team

Posted at 09:54

Ora Lassila: Death of Apps

Together with my colleague Ian Oliver I have been revisiting our old, favorite topic: The Death of Applications. This is continuation of the work we did at NRC with M3, and of the thinking I describe in my IdeasProject interview. Ian has also recently blogged about this.

So far, the thinking goes like this: "apps" are the concrete manifestation of locking data, logic and/or presentation in a proverbial "silo", and as such contribute to the fragmentation of information space. "There's an app for that" should be thought of as a curse, not as something positive.

Read Ian's blog entry on this, it goes more into details about our idea of "isolation", how apps isolate data and prevent access, reuse and integration.

I will give a keynote talk at the CIDOC 2012 conference in June, and will discuss these thoughts. This has been long time coming, and I look forward to discussing/debating this with folks.

Posted at 00:39

May 23

W3C Blog Semantic Web News: Interview: IBM on the Linked Data Platform

Arnaud Le Hors

Shortly after W3C announced the launch of the Linked Data Platform Working Group, I spoke with Arnaud Le Hors about IBM's interest in linked data and their decision to co-chair the Working Group.

IJ: Why did IBM get involved in organizing the Linked Enterprise Data Patterns Workshop in December 2011 and now the Linked Data Platform Working Group?

ALH: IBM has been involved in Semantic Web activities from the beginning, but primarily from a research perspective. Until recently we had no products using the technology. Now we have IBM Rational, which develops a set of tools for application and product lifecycle management (requirements, bugs, etc.). Other parts of IBM are actively exploring it for complementary purposes. Customers typically use tools from more than one vendor and require integration; this is a problem IBM addresses.

Over the years Rational has seen and tried a variety of approaches, but they have had limitations. For instance, if your tools interact through proprietary, language-specific APIs, you end up with an exponential number of APIs and versioning issues. The API approach doesn't scale. Another approach has been for all tools to converse with a central database. But this usually depends on a schema that is acceptable to all parties, which is more difficult to achieve and proves fragile as needs change.

Though there are supporters of these approaches; IBM was not satisfied. We realized that many characteristics we sought were present in the Internet and Linked Data. We have moved from a "tool-centric" approach to a "data-centric approach" based on Web standards. In this decentralized and scalable model, every piece of information that we have (e.g., a bug report) is addressable with a URI and can be accessed with HTTP.

IJ: Please describe a scenario.

ALH: Suppose someone files a bug report on a piece of software. The bug report is available at a URI. Another person then registers a change request, and an engineer is assigned to fix the code. The change request includes the URI of the bug report. The engineer changes the code and registers the URI of the change request in the source code management system. This chain of links gives fine-grained accountability. We store the information as linked data, which enables the communication among the tools.

So we are using linked data for application integration. I think this is fairly uncommon today. Most people are using linked data to create virtual data stores. A lot of linked data is read-only; our approach is inherently read-write.

IJ: Have you encountered any issues with updates when writing?

ALH: Yes. HTTP PUT is not enough. We need a PATCH method. There is a draft standard HTTP extension for PATCH, and I know that the SPARQL update community has a particular view of how PATCH should work. W3C needs to work on how PATCH would work in the context of RDF.

PATCH is a good example of a topic that motivated us to hold the Workshop in December. In adopting linked data in products, we have found that there may be multiple ways to achieve the same end, and no clear guidance or consensus on which to use where. So we are seeking guidance on how to use various technologies and we look for the W3C to organize discussions with industry on linked data good practices. Some examples of constructs where we would like to see industry converge include containers, lists, and pagination (requesting a piece of a representation). The Workshop was about these sorts of linked data "patterns" and we are looking forward to formally addressing these issues in the new Linked Data Platform Working Group.

IJ: Are there other projects using linked data within IBM? Or other parts of the Semantic Web stack?

ALH: Yes, for example IBM Watson. Watson uses a triple-store but also ontologies and inference. Watson downloads data from the Web (e.g., from dbpedia) that is curated and added to the triple store. Watson reasons over the data, using Semantic Web technology in a major way. We also have products from Tivoli (for help desk tickets) and Information Management (DB2) using linked data.

IJ: What do you see as barriers to RDF adoption?

ALH: A big one has been the XML syntax. I know the history of the XML syntax, but I think it obscures the otherwise simple RDF model. Turtle or some other simple syntax will help. Turtle is not yet a standard; we would like it to become one.

IJ: Is IBM creating tools to manipulate linked data?

ALH: IBM just released DB2 version 10 which provides support for RDF with a SPARQL engine on top of DB2. This was driven by demand from our products.

IJ: What else should W3C be doing in the linked data space?

ALH: Although the full Semantic Web stack is general and elegant, there may be too much going on, which raises obstacles for many engineers. Practical guidance (how to solve classes of problems, for instance) would help a lot. The linked open data movement has been very helpful for advocacy.

We think the industry will benefit from a clear definition of a linked data platform (or profile). Tim Berners-Lee listed four principles in his writing on linked data, but that view has no formal standing. With the Linked Data Platform Working Group we will enumerate the necessary standards, and provide guidance on conventions and good practices. We need big players to join the Working Group and agree on what it means to have a linked data platform. This will simplify deployment (reducing options), increase interoperability, and move the industry forward.

IJ: What do you consider core to a linked data platform?

ALH: IBM submitted a specification in March to try and answer that question. This is just a start though. We want to engage industry on the question.

IJ: Thank you for your time, Arnaud.

Posted at 22:03

Norm Walsh: Notice of upcoming downtime

There's another, much longer, maintenance window coming.

Posted at 21:16

May 20

Peter Shaw: Visualising RDF with Incontext

Surfing around the internet I recently discovered SURF‘s InContext Visualiser, which I think is a neat way to visualise of RDF relationships, especially OAI-ORE aggregated publications

I also discovered that people have already created a set of WordPress plugins (see: http://ep-books.ehumanities.nl/ ) to visualise books and other similar publications. However blogs do not fit into a book/chapter model.

However given there is already a schema for publishing blog data and my lh-rdf plugin already exposes most publicly available WordPress blog data as RDF using that format. It was an obvious next step to get the visualiser working with the LH RDF output. I have done so and hopefully you think the output is cool.

http://shawfactor.com/wp-content/plugins/lh-rdf/visualisation.php

I have bundled this visualiser with the lh rdf plugin, and in time I will polish it up and add shortcode support so it can be more easily be embedded in posts and pages.

Posted at 15:16

May 19

Norm Walsh: Numbered program listings

Putting line numbers in program listings is harder than it looks.

Posted at 20:38

Ebiquity research group UMBC: Google releases dataset linking strings and concepts

Yesterday Google announced a very interesting resource with 175M short, unique text strings that were used to refer to one of 7.6M Wikipedia articles. This should be very useful for research on information extraction from text.

“We consider each individual Wikipedia article as representing a concept (an entity or an idea), identified by its URL. Text strings that refer to concepts were collected using the publicly available hypertext of anchors (the text you click on in a web link) that point to each Wikipedia page, thus drawing on the vast link structure of the web. For every English article we harvested the strings associated with its incoming hyperlinks from the rest of Wikipedia, the greater web, and also anchors of parallel, non-English Wikipedia pages. Our dictionaries are cross-lingual, and any concept deemed too fine can be broadened to a desired level of generality using Wikipedia’s groupings of articles into hierarchical categories.

The data set contains triples, each consisting of (i) text, a short, raw natural language string; (ii) url, a related concept, represented by an English Wikipedia article’s canonical location; and (iii) count, an integer indicating the number of times text has been observed connected with the concept’s url. Our database thus includes weights that measure degrees of association.”

The details of the data and how it was constructed are in an LREC 2012 paper by Valentin Spitkovsky and Angel Chang, A Cross-Lingual Dictionary for English Wikipedia Concepts. Get the data here.

Posted at 16:02

Ebiquity research group UMBC: Google Knowledge Graph: first impressions

The Google’s Knowledge Graph showed up for me this morning — it’s been slowly rolling out since the announcement on Wednesday. It builds lots of research from human language technology (e.g., entity recognition and linking) and the semantic web (graphs of linked data). The slogan, “things not strings”, is brilliant and easily understood.

My first impression is that it’s fast, useful and a great accomplishment but leaves lots of room for improvement and expansion. That last bit is a good thing, at least for those of us in the R&D community. Here are some comments based on some initial experimentation.

GKG only works on searches that are simple entity mentions like people, places, organizations. It doesn’t do products (Toyota Camray), events (World War II), or diseases (diabetes) but does recognize that ‘Mercury’ could be a planet or an element.

It’s a bit aggressive about linking: when searching for “John Smith” it zeros in on the 17th century English explorer. Poor Professor Michael Jordan never get a chance, and providing context by adding Berkeley just suppresses the GKG sidebar. “Mitt” goes right to you know who. “George Bush” does lead to a disambiguation sidebar, though. Given that GKG doesn’t seem to allow for context information, the only disambiguating evidence it has is popularity (i.e., pagerank).

Speaking of context, the GKG results seem not to draw on user-specific information, like my location or past search history. When I search for “Columbia” from my location here in Maryland, it suggests “Columbia University” and “Columbia, South Carolina” and not “Columbia, Maryland” which is just five miles away from me.

Places include not just GPEs (geo-political entities) but also locations (Mars, Patapsco river) and facilities (MOMA, empire state building). To the GKG, the White House is just a place.

Organizations seem like a weak spot. It recognizes schools (UCLA) but company mentions seem not to be directly handled, not even for “Google”. A search for “NBA” suggests three “people associated with NBA” and “National Basketball Association” is not recognized. Forget finding out about the Cult of the Dead Cow.

Mike Bergman has some insights based on his exploration of the GKG in Deconstructing the Google Knowledge Graph

The use of structured and semi-structure knowledge in search is an exciting area. I expect we will see much more of this showing up in search engines, including Bing.

Posted at 14:43

Semantic Web Company (Austria): Has Google hi-jacked the Semantic Web?

Just recently Google has launched the ‘Knowledge Graph‘ (GKG) which “understands real-world entities and their relationships to one another: things, not strings.” Has Google hi-jacked the idea of the ‘Semantic Web’ or at least its vocabulary?

Sean Golliher has compared the most central concepts of the SemWeb community to the wording of Google in his blog post, for instance: Google doesn´t talk about ‘Linked data’ or ‘URIs’ but rather about ‘things and their relationships’. We don´t know if Google uses standards like RDF but obviously a lot of concepts and ideas developed by the SemWeb community in recent years were implemented in GKG. Some people complain that Google should clearly state that this is an implementation of the ‘Semantic Web’ (which was not invented by Google), others say that most concepts like ‘taxonomies’ have been around for hundreds of years anyway.

I believe that both sides have now a great chance to work together: Whether Google’s goal, to “build the next generation of search, which taps into the collective intelligence of the web and understands the world a bit more like people do”, can be reached or not is a matter of the intelligence of the employees. A lot of potential can be found within the semantic web community: If Google gives credit where it is due, semantic web people will be a bit more inspired to support an eco-system built around GKG – and it won´t last long until an ‘Open Knowledge Graph’ will fit together with Google´s revenue model.

Posted at 08:51

May 18

Leigh Dodds:

Posted at 15:33

May 17

Ebiquity research group UMBC: Google Knowledge Graph: things, not string

Google announced its “knowledge graph” today and describes it as “an intelligent model—in geek-speak, a ‘graph’ — that understands real-world entities and their relationships to one another: things, not strings. … It currently contains more than 500 million objects, as well as more than 3.5 billion facts about and relationships between these different objects. And it’s tuned based on what people search for, and what we find out on the web.” Information from the knowledge graph will initially augment search results — the feature is already being rolled out to US English users. A short video explains more.

A CNET article quotes KG project manager Jack Menzel: Menzel pitches Knowledge Graph without using the word “semantic” even once. While he says, “I dream of the semantic Web,” he takes pains to point out that what Google is announcing today is not what people talk about when they discuss semantic Web concepts. “We do continue to work on how to make search semantic,” he says, “but talking about it brings out the crazy people.” I hope this did not come out the way he intended it to.

Posted at 03:54

May 16

W3C Blog Semantic Web News: Interview: BBC on Publishing and Linked Data

I chatted recently with Olivier Thereaux, Yves Raimond (senior technologist in R&D), and Silver Oliver (data architect) of the BBC about the Web, publishing, and linked data.

Ian: The BBC is prolific and large. How do you view yourselves?

Silver: The BBC is primarily a broadcasting organization. Content is developed or commissioned within different editorial domains (such as News or Music or Sports) then distributed through diverse channels (TV, Radio, web, apps, etc). This fragmentation exists also on the web, with development of individual sites being largely delegated to dedicated teams.

Ian: How do you move beyond silos?

Yves: We have a lot of data that we are now using to draw connections among various BBC TV and radio programs and entities in other domains, like music or nature. We also expose the corresponding data. For example the programmes site exposes data views giving details about all the music tracks played in a given radio programme, and those details link to (and draw from) artist profiles on the BBC's music site… which themselves are also available as data views.

Olivier: We also reuse data that's available on the Web (e.g., from musicbrainz and wikipedia). Because the public is curating the information they can update it more rapidly than we could on our own. In a way, the Web is our Content Management System.

Ian: What are you using to aggregate and expose the data?

Yves: For the programmes and music site we use a relational database internally but then we expose the information in RDF.

Olivier: And we benefit from the ways that people have innovated around the RDF data we expose. When people play with the interfaces and massage the data, we can build on their experience.

Ian: Why not use RDF internally?

Yves: I think the main reason is that the people who originally built these sites site were unaware of RDF, or were concerned about using an unfamiliar technology on such a big project. But we use it with other projects.

Ian: How has your uses of data affected reporting?

Silver: In the past our editorial efforts have been captured in whole HTML documents. This causes problems for reuse in new data views and across platforms and applications (including IPTV). The key is in working with existing editorial workflows to capture a sub-set of machine readable information. In its simplest form this might be a byline and small number of tags the story is about.

Ian: How do reporters use the data to make connections between stories?

Silver: Connections have always happened, but it didn't scale. Linking between sports and news was a manual process and reliant on a journalist's knowledge of BBC output. But now we have rich data models behind the scenes. These models help the BBC editorial staff represent their understanding of the world and our audience's interests, and let us make connections in a scalable fashion.

Olivier: The data is a substrate that pre-populates a lot of the site, and then journalists can focus on the stories and not re-entering the data bits.

Silver: In sport, for example, we pay for the sport data (fixtures, results and statistics) then we write stories about match reports, and tagging ensures that everything gets linked properly. That's how we built the sites for the 2010 world cup or the 2012 olympics.

Ian: Do the reporters add data to the system directly?

Silver: Yes, we ask them to tag the stories they pull together so that we can put those stories into different contexts (or aggregations). We were quite happy to realize the natural curatorial process was already happening, we just needed to give people a way to capture data.

Ian: You mentioned buying and using data from various sources, including commercial ones. Do you make use of data provenance information?

Yves: We need to be very transparent about where our data comes from. Our reporters, partners, official organisations, sometimes our audience too.

Olivier: There is an interesting tension between making use of provenance information and ensuring user privacy. These days people expect to receive personalized content. To achieve that we make use of "attention data": what you watch or like. We have been looking at how to guarantee that we uphold privacy while at the same time asking for the minimal amount of information to tailor the best experience. That's probably less about "Do Not Track" and closer to the spirit of W3C's older P3P technology. On the other hand, we want to know whether information is reliable. This is challenging for user-generated content in particular: who is the user? how much do we trust them?

Ian: Do you think making provenance information available to readers can help digital literacy?

Silver: We had an interesting debate internally whether to include links from health stories to the journals that published the original research. Some felt that readers would not be interested in the links or would find the research complex. Others encouraged the links so that the community could respond to our articles with their own interpretations, including challenging the articles from various angles. This, in turn, would generate more discussion and perspectives from a much larger audience.

Ian: How did it turn out?

Silver: In stories about politics we have begun to include links to relevant legislation. And we are exploring how to extend the linking to pull in data from these sources to weave into BBC story-telling. For example data about committees that commented on bills, which members of parliament commented, and so on. These data models allow us to make more connections among stories, as we discussed earlier.

Ian: This sounds like a linked data project!

Silver: Internally we have wholesale signed up for and understood the value of linked data as way to manage our organizational complexity. We will draw data from various sources and use RDF to stitch them together. We can make use of the information in ways we could not do before because it was either too costly or unmanageable. Semantic Web technology is now core to our strategy as an enterprise.

Ian: Have you measured cost savings by using Semantic Web technology?

Silver: It's still too early to say. There were costs associated with our initial projects, since we needed to acquire expertise. But we have since been able to roll out highly trafficked BBC content using Semantic Web technology.

Ian: Thank you all so much for your time!

Posted at 08:24

May 11

schema.org: Schema.org markup for external lists


The world is too rich, complex and interesting for a single schema to describe fully on its own. With schema.org we aim to find a balance, by providing a core schema that covers lots of situations, alongside extension mechanisms for extra detail. There are many situations where the use of existing controlled vocabularies, standards and datasets would improve schema.org markup. This is the role of the schema.org "external enumerations" mechanism.

We introduce "external enumerations" with a simple example - countries - and encourage implementors to join the schema.org community in W3C's 'Web Schemas' group where the full details are being discussed.

Each schema.org type (such as Person, PostalAddress) is associated with a set of properties, such as
"nationality", "addressCountry". In turn, each property has one or more expected types; in this case, both the "nationality" of a Person, and the "addressCountry" of a PostalAddress expect to have a Country value. Rather than adding large lists of specific countries to schema.org, instead we encourage the use of external lists.  We will publish a set of well-known authority lists, linked to the types and properties they are used with. To get started, we take simple Wikipedia links as an example of such an authority. Other more specialist examples (such as IPTC codes) will follow.

Taking our existing Movie example in Microdata, let's add nationality details for one of the actors. To do this, we simply add a link:


<div itemscope itemtype="http://schema.org/Movie">
<h1 itemprop="name">Pirates of the Carribean: On Stranger Tides (2011)</h1>
<span itemprop="description">Jack Sparrow and Barbossa embark on[...]</span>
<div itemprop="actor" itemscope itemtype="http://schema.org/Person">
  <span itemprop="name">Johnny Depp</span>
  <link itemprop="nationality" href="http://en.wikipedia.org/wiki/United_States"/>
</div>
</div>
 
Here we use  'http://en.wikipedia.org/wiki/United_States' to stand for the specific country. Other authorities also publish useful structured data about countries and have stable URLs that could be used. For example, we could use the UN FAO's GeoPolitical Ontology, and their URL for the USA. From a schema.org perspective, we do not take account of any types and properties defined by these external sites, since it is important to support a variety of quite different authority lists, who often have different ways of modeling things. Each external authority essentially supplies a set of URI/URL item identifiers that can be dropped into schema.org markup.

We've shown here the use of Wikipedia links for identifying members of the Country type. Take a look at the detailed document for discussion on how to use this with Microdata's 'itemid' attribute, if you want to describe the Country (or other object) in further detail. The W3C wiki also gives other examples, and shows how the markup would look in RDFa Lite

While there are more details to work out as we start to apply this idea across schema.org, we wanted to share this initial example.  The basic idea is very simple: everywhere in schema.org where external lists will help, we will need to have a specific schema.org type (like Country), for which the external authority supplies identifiers. In some cases, we will have to add new types to support this. Beyond the basics presented here, there are various technical details of syntax, discussion of exactly which authorities and URI identifiers to use, and so on. We welcome suggestions (here or via the Web Schemas group) for existing enumerations that would be useful additions, and feedback on the general approach.

Posted at 20:49

May 10

Dave Beckett: Undugg

Digg just announced that Digg Engineering Team Joins SocialCode and The Washington Post reported SocialCode hires 15 employees from Digg.com

This acquihire does NOT include me. I will be changing jobs shortly but have nothing further to announce at this time.

I wish my former Digg colleagues the best of luck in their new roles. I had a great time at Digg and learned a lot about working in a small company, social news, analytics, public APIs and the technology stack there.

Posted at 15:20

Michael Hausenblas: Turning tabular data into entities

Two widely used data formats on the Web are CSV and JSON. In order to enable fine-grained access in an hypermedia-oriented fashion I’ve started to work on

Posted at 15:03

W3C Semantic Web News: Linked Data Platform Working Group Launched

The W3C launched the new Linked Data Platform (LDP) Working Group to promote the use of linked data on the Web. Per its charter, the group will explain how to use a core set of services and technologies to build powerful applications capable of integrating public data, secured enterprise data, and personal data. The platform will be based on proven Web technologies including HTTP for transport, and RDF and other Semantic Web standards for data integration and reuse. The group will produce supporting materials, such as a description of uses cases, a list of requirements, and a test suite and/or validation tools to help ensure interoperability and correct implementation.

Posted at 09:57

May 08

W3C Semantic Web News: Three RDFa Specifications are Proposed Recommendations

The RDF Web Applications Working Group has published three Proposed Recommendations for RDFa Core 1.1, RDFa Lite 1.1 and XHTML+RDFa 1.1.

Together, these documents outline the vision for RDFa in a variety of XML and HTML-based Web markup languages. RDFa Core 1.1 specifies the core syntax and processing rules for RDFa 1.1 and how the language is intended to be used in XML documents. RDFa Lite 1.1 provides a simple subset of RDFa for novice web authors. XHTML+RDFa 1.1 specifies the usage of RDFa in the XHTML markup language. The group also published a draft of the RDFa 1.1 Primer today.

Posted at 17:14

May 07

Dublin Core Metadata Initiative: Presentations Available for "Five Years On" Seminar at the British Library

2012-05-07, Presentations from the successful DCMI-UK regional meeting "Five Years On" at the British Library on 26-27 April 2012 are available at http://dcevents.dublincore.org/index.php/BibData/fyo. Additional resources from the Seminar and the collocated meetings of the DCMI Bibliographic Metadata Task Group and the Vocabulary Management Community will be added to the website over the next several weeks.

Posted at 23:59

Copyright of the postings is owned by the original blog authors. Contact us.