- From: Robin Berjon <robin@berjon.com>
- Date: Thu, 30 Aug 2012 12:48:50 +0200
- To: Larry Masinter <masinter@adobe.com>
- Cc: "spec-prod@w3.org Prod" <spec-prod@w3.org>
On Aug 29, 2012, at 21:41 , Larry Masinter wrote: > Define a URN scheme for spec references. In a world where URNs work, the source format would be better than the destination. Shane wrote: > Your "scheme" approach is very much like a CURIE - and I like that. I bet we could even do it in a way that was CURIE conforming... declare it as a 'prefix' and it would be dereferenced in the follow-your-nose manner that you would expect from RDF > > @prefix="spec: http://www.w3.org/URI_to_respec_bib/" somewhere in early in the spec, then transform the references. The one and only goal for ReSpec is to make the job of editing a spec as simple and straightforward as possible. This means having as little boilerplate as possible, as little syntax as possible, adherence to DRY and DWIM, and whenever possible a syntax that's as mnemonic as possible. In other words, it tries hard (and will keep trying harder) to ruthlessly be an authoring format. Irrespective of their merits in broader, distributed, loosely coupled systems that CURIEs and URNs may have and that can make them well suited to environments in which authorial needs are balanced by other considerations, I don't think that they make the cut in the face of those design principles :) -- Robin Berjon - http://berjon.com/ - @robinberjon
Received on Thursday, 30 August 2012 10:49:16 UTC