W3C home > Mailing lists > Public > public-prov-wg@w3.org > July 2011

PAQ draft in W3C repository

From: Graham Klyne <GK@ninebynine.org>
Date: Thu, 21 Jul 2011 15:30:01 +0100
Message-ID: <4E2837E9.4030001@ninebynine.org>
To: W3C provenance WG <public-prov-wg@w3.org>, Sandro Hawke <sandro@w3.org>
I've lodged a working copy of my PAQ draft in the W3C mercurial repository
(http://dvcs.w3.org/hg/prov/summary)

The draft can be viewed at:
http://dvcs.w3.org/hg/prov/raw-file/d270587d6ad8/paq/provenance-access.html

I think that URI is version-specific, and will not track updates to the draft.

@Sandro:  is there an common process for assigning a URI to be the latest
version in the repository, that can be used for the document "latest version" link.

[Later] (on a whim)
http://dvcs.w3.org/hg/prov/raw-file/tip/paq/provenance-access.html seems to do it.

...

A note for other editors using ReSpec
(http://dev.w3.org/2009/dap/ReSpec.js/documentation.html):  if you look at the
source of my PAQ document (e.g.
http://dvcs.w3.org/hg/prov/file/tip/paq/provenance-access.html), I've figured a
mechanism to add bibliographic entries referenced that are not covered by the
standard ReSpec bibliography library at
http://dev.w3.org/2009/dap/ReSpec.js/bibref/biblio.js.

...

I noticed I was getting mercurial merge conflicts because MacOS .DS_Store files
were being pushed to the repository.  I'd suggest these not be included in
repository contents.

#g
Received on Thursday, 21 July 2011 14:31:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 13:06:37 GMT