Steffen asked \nme if I could also provide a few examples on how to actually put RDF triples in the HTML, as the\ntemplate I gave yesterday is a mere empty canvas to draw the\ntriples on. There are actually various examples \nin my blog, which I will summarize here.
\n\nBefore I start, I like to put some emphasize on the following RDFa pattern. An RDF\nresource that serves as subject is always mapped to a HTML element. This can be a div element, but also other elements, as we\nwill see in the example.
\n\nThe oldest RDFa example in my blog is from
\nThis example shows how to embed the SMILES string CCO semantically. This example shows that the outer most span element is\nused to define the subject of the RDF triple, using the @about\nattribute to define the URI of the resource: #ethanol.\nNote that this URI is relative to the URI of the HTML page in which it is embedded. Later we will see an example with a full URI.
\n\nYeah, fair point. Just make a point with your publisher when you submit a new paper. It is the duty of the publisher and\nyour software vendor to do this right. In 2008 I wrote a small Ubiquity script\nto automagically\nconvert an InChI into semantified HTML content .\nBut I am not sure this script still works. If interesting, let me know, and I will revive the Firefox thingy.
\n\nBecause software can more easily understand what you mean. This is why Google is now pushing\nrich snippets.\nChemical blogspace understands them too, allowing you to see\nblog posts about molecules on other webpages .\nWith a simple bit of JavaScript you can link from your webpages, you can\nenrich your HTML sites with semantic chemistry yourself.\nBioclipse also has no problem with extracting\nthe RDF from HTML .\nEven Firefox can understand it .\nReally, there is no end to it.
\n\nOf course, why you should do this comes basically down to Molecular Chemometrics Principle #2, but I have not written that\non up yet (see also McPrinciple #1).
\n\nMore recently, I reported about using RDFa in human readable log file for computations I am doing (see\nScripts logs as HTML+RDFa: mix free text reporting with CSV ). \nThat code looks like:
\n\n\n\nThis example uses a div element to host the subject resource. Again, the resource URI is relative to the URI of\nthe document, e.g. this one. We can also note a new attribute,\n@typeof, which is here used to define the rdf:type of the #200234 resource.
\n\nThis code snippet does not define the um namespace, which was done elsewhere in the HTML. Moreover, this\ncode snippet does not actually reuse existing ontologies, which is highly recommended. The\nupcoming RDF symposium in Boston \nwill tell you all about chemical ontologies in the RDF world (see this detailed program,\nwhich itself is HTML+RDFa!). But, if you would just overlook the ad hoc namespaces used, you might appreciate the\nnesting: besides the compound (#200234), a second resource is defined (#error0). In total, this example contains six triples.
\n\nMeanwhile, the output simply looks like:
\n\nThis third, and for now last, example shows several other features. This HTML snippet show a one entry\nmolecule table, very much like those molecular spreadsheets in Excel, but than right here in your webbrowser.\n(Can you imagine what happens if we mash this up with\nJavaScript molecular viewers
\n\n\n\nFirst of all, the rdf.openmolecules.net project\nis used to construct an absolute URI for the molecule. The table then gives some properties of the molecule:\nits name (using Dublin Core, though perhaps rdfs:label\nis better), the boiling point (nicely encoded as t0 in this 1947 paper),\ntwo cheminformatics descriptors, and the SMILES, using the same approach as the first example in this post.
\n\nThe output of this table looks like:
\n\n| n-Butane | \n-0.5 | \n10 | \n1 | \nCCCC | \n
I will shortly blog about the source of the above code snippet, but you are invited to go ahead and checkout\nmy GitHub activity (RSS).
\n\nSteffen, I think these examples should get you pretty far, but please let me know if you have further questions!
\n\n