Re: RDF WG minutes from 2011-05-18

I was looking at the minutes, and the section to recspec. One of the comments was that Sandro was concerned about consistent references. Although I may have misunderstood the minutes (or Sandro's concerns), I thought it worthwhile to give some info.

- It is easy to adopt an agreement on how to set all our (bibliography) references in a consistent manner if we all use recspec; see below.
- What is more difficult and, I believe, were Sandro's concerns are:
  - Have one place for common boilerplate text for, say, Abstract and Status: clearly, all documents will have to have some common texts. This is easier to handle on a wiki by using some mediawiki templates: the common text can be updated on the templates and that is fine. Unless somebody comes up with some extra javascript tricks and modifies recspec accordingly, we would have to do that by hand.
  - Have document A have a hyperlink to a specific place in document B, so that these hyperlinks remain valid along all the subsequent versions of the draft. That again will have to be made by hand, and is obviously the source of lots of problems if we are not careful. I believe Sandro had some tricks on the wiki (maybe Peter or some other former OWL2 editors may comment on that).

_Personally_ I am in favour of recspec, but I thought it is good to have these known from the beginning.

As for the ways to get the references: by default, recspec understands microsyntax like [[XHTML]]. References are automatically collected making use of a W3C wide bibliography file[1], which can be edited by anyone (it is an open cvs access document). Of course, it is not wise to add drafts to this document (but it is perfectly o.k. to add references to standards and other stable documents, unless they are already there; that file has over 800 entries today).

However, it is also possible to set up a local js file, common to all RDF drafts. 

1. Let us create a file, say, 'rdfbiblio.js'. The file looks as follows:

var preProc = {
  apply:  function(c) {
   // extend the bibliography entries
   berjon.biblio["HTML-RDFA"] = "Manu Sporny; et al. <a href=\"\"><cite>HTML+RDFa</cite></a> 04 March 2010. W3C Working Draft. URL: <a href=\"\"></a> ";
   berjon.biblio["RDFA-API"] = "Manu Sporny, Benjamin Adriaan, and Mark Birbeck; <a href=\"\"><cite>RDFa API</cite></a> Latest. W3C Working Draft. URL: <a href=\"\"></a>";

I use some examples I played with in the RDFWA WG; the format of the bibliography content is the same as for the central depository.

2. In the document's source file, add the entry

    <script src='rdfbiblio.js' class='remove'></script>

right before the recspec configuration script.

3. In the configuration script itself (which is, in fact, a dictionary) add or modify the line:
  preProcess: [ preProc ]

That is it. The trick is that recspec has a bunch of extension mechanisms, and this is one of those: as you guess, the functions in the array for preProcess are executed before anything else, and the function above adds to the bibliography list used run-time.

I hope this helps



On May 22, 2011, at 22:37 , Richard Cyganiak wrote:

> Seems like Wednesday's scribe didn't find time yet to generate the minutes, so I just did it:
> I recall that one more resolution was made after a vote, but it was not scribed: accept the proposal on ISSUE-40.
> Best,
> Richard

Ivan Herman, W3C Semantic Web Activity Lead
mobile: +31-641044153
PGP Key:

Received on Monday, 23 May 2011 07:58:48 UTC