- From: Arthur Ryman <arthur.ryman@gmail.com>
- Date: Fri, 13 Nov 2015 13:31:25 -0500
- To: Nick Crossley <ncrossley@us.ibm.com>
- Cc: "public-data-shapes-wg@w3.org" <public-data-shapes-wg@w3.org>
- Message-ID: <CAApBiOnxbg0gC_hfodDSzRxq+3OM2cpbvV7kh6j0N4bbQshFCQ@mail.gmail.com>
Nick, Thx. I'll have a look at the OSLC fork before re-inventing the wheel. -- Arthur On Fri, Nov 13, 2015 at 11:54 AM, Nick Crossley <ncrossley@us.ibm.com> wrote: > Arthur, > > > There exists XSLT for transforming RDFS vocabularies > > [4].This transform could be reimplemented in Javascript and integrated > > with ReSpec. > > We already have this in the OSLC fork of ReSpec, and a merge back to the > W3C fork should not be hard. > > The OSLC fork of ReSpec also has equivalent Javascript to produce HTML > tables from OSLC shapes. That > part would need a rewrite to work from SHACL. > > Nick. > > [image: Inactive hide details for Arthur Ryman ---11/11/2015 08:05:07 > PM---I propose the following: 1. We should publish two normative]Arthur > Ryman ---11/11/2015 08:05:07 PM---I propose the following: 1. We should > publish two normative files: shacl-vocab.ttl and shacl-shacl.t > > From: Arthur Ryman <arthur.ryman@gmail.com> > To: "public-data-shapes-wg@w3.org" <public-data-shapes-wg@w3.org> > Date: 11/11/2015 08:05 PM > Subject: ISSUE-87: Shall we publish RDF files for the SHACL namespace? > ------------------------------ > > > > I propose the following: > > 1. We should publish two normative files: shacl-vocab.ttl and > shacl-shacl.ttl > > 2. shacl-vocab.ttl should be a simple RDFS vocabulary that does not > contain any shape information. It should be readable by anyone > knowledgeable in RDFS, but not SHACL > > 3. shacl-shacl.ttl should use SHACL to define the shape of valid SHACL > documents > > 4. both files should also be automatically transformed to HTML, e.g. > as in [3]. There exists XSLT for transforming RDFS vocabularies > [4].This transform could be reimplemented in Javascript and integrated > with ReSpec. A similar transform could be developed for SHACL > documents. > > 5. W3C should host these files and support Turtle/HTML content > negotiation as per [1] and [2]. > > [1] http://www.w3.org/TR/cooluris/ > [2] http://www.w3.org/TR/swbp-vocab-pub/ > [3] https://jazz.net/wiki/bin/view/LinkedData/JazzProcessVocabulary > [4] https://jazz.net/wiki/bin/view/LinkedData/PublishingRdfVocabularies > > -- Arthur > > > >
Attachments
- image/gif attachment: graycol.gif
Received on Friday, 13 November 2015 18:31:53 UTC