W3C home > Mailing lists > Public > public-ldp-wg@w3.org > February 2013

Use-Cases for Issue-48 required

From: Henry Story <henry.story@bblfish.net>
Date: Mon, 4 Feb 2013 15:47:55 +0100
Cc: Sergio Fernández <sergio.fernandez@salzburgresearch.at>, Raúl García Castro <rgarcia@fi.upm.es>, "Linked Data Platform (LDP) Working Group" <public-ldp-wg@w3.org>
Message-Id: <F8B51AA7-E059-4F0E-B21F-0068E272D116@bblfish.net>
To: Pierre-Antoine Champin <pierre-antoine.champin@liris.cnrs.fr>

On 4 Feb 2013, at 15:42, Pierre-Antoine Champin <pierre-antoine.champin@liris.cnrs.fr> wrote:

> Henry,
> 
> On Mon, Feb 4, 2013 at 2:44 PM, Henry Story <henry.story@bblfish.net> wrote:
> 
>  
> If you want mechanisms to advertise restrictions on graphs for particular purposes 
> then you should work on ISSUE-48 "Profile mechanism is Needed", and find some 
> good use cases for it, so that we can then open it, with an idea as to what it would
> be to close it.
> 
> http://www.w3.org/2012/ldp/track/issues/48
> 
> I like the idea of profiles. Whether we should or not design a language to formally describe them, I'm not sure... I like Erik's idea that 'formally describe for [him] usually means "spec language is good enough"' [1].

I think that if you like the idea of profiles it is worth at least adding use cases to that issue
so that we can find out if simple spec language will be good enough or not. If there is to
be a general mechanism by which clients can find out what type of resource they can 
POST to a container that has profile restrictions then simple spec language won't do. On the other hand it may not be as difficult as it seems: it may already have been defined somewhere in the W3C or on the web, it may be just a matter of defining a few relations,
it may be that a WG or Community group can do that while this group is progressing. It may be that these restrictions are not needed at all.

Whatever: putting forward use cases for Issue-48 will be the only way to tell.

Henry





Received on Monday, 4 February 2013 14:48:31 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 9 May 2013 13:44:29 UTC