Re: LDP WG Rechartering

Here are a few suggestions: (should I update them on my own?)

<#scope>
This statement is not needed as we already have this in LDP-Paging
 "How can a client specify the size of a page when paging?"

Perhaps it would be good to add a technical issue that motivates the shape
linkage:
"How can a client learn what property constraints there are when creating
or updating a resource?"

One item that I'd like to consider adding to the scope is how we can do
efficient transfer of LDP resources, either some initial set or rolling
updates (feed) of changes.  Such as RDF Data Streams  [1] or OSLC Tracked
Resource Set [2], to name a couple.

[1]: http://dataweb.infor.uva.es/wp-content/uploads/2014/07/iswc14.pdf
[2]: http://open-services.net/wiki/core/TrackedResourceSet-2.0/

Thanks,
Steve Speicher
http://stevespeicher.me

On Mon, Oct 20, 2014 at 1:06 PM, Arnaud Le Hors <lehors@us.ibm.com> wrote:

> As discussed on today's call, I put together a first draft of what a new
> charter for the LDP WG could look like.
> I would appreciate if you could have a look, especially regarding the
> scope and deliverables, and comment by responding to this email.
> Thank you.
>
> .https://www.w3.org/2012/ldp/wiki/LDPNext2015_Charter
> --
> Arnaud  Le Hors - Senior Technical Staff Member, Open Web Standards - IBM
> Software Group
>