remember to disable your video too btw

<scribe> scribenick: deiu

[Ashock is going over the agenda]

[people discussion lunch options]

[introductions]

[Arnaud going over the last 2 years of LDP]

[Arnaud is going over LD paging]

Arnaud: the LD paging will most likely be published as a note

[Arnaud is going over LD Patch history]

Arnaud: LD Patch’s future is brighter…and we hope it will reach REC soon (we meet the exit criteria)

[Arnaud talking about the wishlist]

Arnaud: so we’re here today to answer the big question: what do we do next?

…the WG has slown down, we’ve also lost a few members recently

…we can try to recharter the WG right away, but what do we need for that?

…W3C wants to see a draft charter and to see who is interested

…we can also do nothing, meaning that the WG will close in a few months

…Sandro pushed for the idea that we have a good basis, and we should experiment with what we have now

…people agreed that we should wait a bit, though we may lose momentum

…W3C management also has some constraints

…so the bar is quite high if we want to recharter

[Ashock proposes an around the table session]

[Ashok asking who wants to speak today]

3-4 people rised their hands

oshani: I can go first

[Oshani is presenting how Oracle uses LDP internally]

gkellogg_: there was some discussions in the Hydra group about paging

…not knowing a lot about LDP, the group prefers using HTTP headers instead of using URI queries

[MiguelAraCo presenting Carbon LDP]

Please note that today’s presentations (pdf) are also available on the mailing list

<oshani> Sent my presentation to public-ldp@w3

[Andrew talking a bit about Fedora 4]

<gkellogg> davidwood’s position paper: https://lists.w3.org/Archives/Public/public-ldp/2015Apr/0017.html

<gkellogg> davidwood: looks like you’re recommending including a reference to the VoID description of the dataset with each response, seems like a good idea.

<gkellogg> The HydraAPI takes a similar position on reference the apiDocumentation endpoint with a Link header.

<betehess> http://io.pellucid.com/blog/exposing-resources-in-datomic-using-linked-data

<betehess> http://io.pellucid.com/blog/exposing-resources-in-datomic-using-linked-data

<gkellogg> Link and Unlink HTTP method proposal: http://tools.ietf.org/html/draft-snell-link-method-01

[ betehess now preseting ]

[ Arnaud presenting next ]

[ Arnaud discussing the wishlist: https://www.w3.org/2012/ldp/wiki/LDPNext ]

<Arnaud> https://www.w3.org/2012/ldp/wiki/LDPNext2015_Charter

<Arnaud> https://www.w3.org/2012/ldp/wiki/LDPNext

<Arnaud> http://open-services.net

[ Ashok about to present davidwood’s paper ]

<azaroth> (link to davidwood's paper?)

<bshambaugh> yes

[ link to davidwood’s paper: https://lists.w3.org/Archives/Public/public-ldp/2015Apr/att-0017/3_Round_Stones_LDP-Next_Position_Paper_20150421.pdf ]

<azaroth> Thank you!

<bshambaugh> thanks

<gkellogg> VoID: http://www.w3.org/TR/void/

[ bshambaugh presenting next ]

<azaroth> Queuing up URLs for my talk:

<azaroth> http://www.w3.org/TR/annotation-model/

<azaroth> http://w3c.github.io/web-annotation/protocol/wd/

<gkellogg> And for signatures/normalization:

<gkellogg> http://json-ld.org/spec/latest/rdf-dataset-normalization/

<gkellogg> https://web-payments.org/specs/source/ld-signatures/

[ azaroth presenting next ]

<Arnaud> http://www.w3.org/TR/annotation-model/

<Arnaud> http://w3c.github.io/web-annotation/protocol/wd/

<brent> Gregg: Provenance is here: http://bshambaugh.org/eispp/ch_1_2_OPM/OPM_transcript.txt

<gkellogg> RDF Dataset Normalization:

<gkellogg> http://json-ld.org/spec/latest/rdf-dataset-normalization/

<gkellogg> LD Signatures: https://web-payments.org/specs/source/ld-signatures/

<Arnaud> https://www.w3.org/2012/ldp/wiki/LDPNext2015_Charter

<gkellogg> VoID use cases: http://semanticweb.org/wiki/VoID

<Arnaud> http://www.w3.org/TR/2014/NOTE-ldp-acr-20140916/

<betehess> http://www.w3.org/TR/2014/NOTE-ldp-acr-20140916/

<gkellogg> Shortlist:

<Ashok> Points for LDP Next

<gkellogg> 1. Extensibility & Discovery

<Ashok> 1. Extensibility and Discovery

<gkellogg> 2. Inlining on Get

<gkellogg> 3. Query...

<Ashok> 2. Inlining on GET

<gkellogg> 4. Client-based paging

<gkellogg> 5. Access Controll usage policies

<Ashok> Also, review LDP 1.0 in view of interoperability analysis of existing implementations

<Ashok> Re. 5 ... start with the LDP Wiki Access Control note

<betehess> 3.1 SPARQL on LDP

<betehess> 3.2 resource-centric

<betehess> 3.3 RDFSource-scoped

<betehess> 3.4 paging

<Ashok> trackbot, ACTION: deiu update LDPNext charter and announce on mailing list

<betehess> ACTION: deiu to update LDPNext and announce it to the mailing list [recorded in http://www.w3.org/2015/04/21-ldp-minutes.html#action01]

<trackbot> Created ACTION-161 - Update ldpnext and announce it to the mailing list [on Andrei Sambra - due 2015-04-28].

<azaroth> ACTION: azaroth to send implementation comparison to public list [recorded in http://www.w3.org/2015/04/21-ldp-minutes.html#action02]

<trackbot> Created ACTION-162 - Send implementation comparison to public list [on Robert Sanderson - due 2015-04-28].

<betehess> adjourned

<Ashok> rrsagaent, draft minutes

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found ScribeNick: deiu
Inferring Scribes: deiu

WARNING: No "Topic:" lines found.

Present: TB_Dinesh

WARNING: Fewer than 3 people found for Present list!


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 21 Apr 2015
Guessing minutes URL: http://www.w3.org/2015/04/21-ldp-minutes.html
People with action items: azaroth deiu

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report