you're reading...
Idea, Linked Data, Proposal

Announcing Application Metadata on the Web of Data

I’m just about to release a new version of the voiD editor, called ve2. It’s currently located at http://ld2sd.deri.org/ve2/ (note that this is a temporary location; I gotta find some time setting up our new LiDRC lab environment).

Anyway, the point is really: every now and then one deploys a Web application (such as ve2; see, that’s why I needed the pitch) and likely wants to also tell the world out there a bit about the application. Some things you want to share with the Web at large that come immediately to mind are:

  • who created the app and who maintains it (creator, legal entity, etc.)
  • which software it has been created with (Java, PHP, jQuery, etc.)
  • where the source code of the app is
  • on which other services it depends on (such as Google calendar, flickr API, DBpedia lookup, etc.)
  • acknowledgments
  • usage conditions

Now, for most of the stuff one can of course use DOAP, the Description of a Project vocabulary, as we did (using RDFa) in the riese project, but some of the metadata goes beyond this, in my experience.

To save myself time (and hopefully you as well) I thought it might not hurt to put together an RDFa template for precisely this job: Announcing Application Metadata on the Web of Data . So, I put my initial proposal, based on Dublin Core and DOAP, at:


Creative Commons License

Note: The WebApp metadata template is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License. You may want to include a reference to this blog post.


About woddiscovery

Web of Data researcher and practitioner


2 thoughts on “Announcing Application Metadata on the Web of Data

  1. Hi Michael,

    I am interested in your Application Metadata vocabulary http://vocab.deri.ie/app-meta/html and in particular the rdf:Property “uses”. I have been sketching out the relationships between components for SOA applications, e.g. WSDL depending on XML Schemas plus other component dependencies, similar to your “uses”, and ended up defining these properties as owl:TransitiveProperty since I could then have each component define its own set of immediate dependencies and then infer the complete set of dependencies for the whole deployment.

    Would defining “uses” as an owl:TransitiveProperty also make sense in your context?



    Posted by Richard Hancock | 2010-01-10, 20:54
  2. Richard,

    Thanks for your feedback and yes, indeed, I think making am:uses transitive is a good idea as it is what one would naturally expect. If you have more ideas what should go into the voc or other enhancement suggestions, plz let me know (is your sketch available on the Web, maybe ?)


    Posted by woddiscovery | 2010-01-11, 06:28

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s


%d bloggers like this: