Meetings:Telecon2013.11.04

Mondays at 10am US Eastern time for 60 minutes
  check your timezone -- http://www.timeanddate.com/worldclock/fixedtime.html?msg=LDP+meeting&iso=20130401T10&p1=43
Telephone US: +1.617.761.6200
  SIP: zakim@voip.w3.org
  Zakim code: LDPWG (53794)
IRC channel: #ldp on irc.w3.org on port 6665
Zakim instructions:  http://www.w3.org/2001/12/zakim-irc-bot.html
RRSAgent instructions: http://www.w3.org/2002/03/RRSAgent

1 Admin

• Chair: Arnaud Le Hors
• Scribe: First available on the scribe list.

1.1 Minutes of last meeting

Proposal: Approve the minutes of the October 28 teleconf:

http://www.w3.org/2013/meeting/ldp/2013-10-28

1.2 Next meeting

• Teleconference 2013.11.11

2 Tracking of actions and issues

Here's a link to the Tracker Summary Page; for the purpose of the agenda here are some more specific link:

• Actions:
  • Actions Pending Review: http://www.w3.org/2012/ldp/track/actions/pendingreview
  • Open Actions: http://www.w3.org/2012/ldp/track/actions/open
• Issues:
  • Issues Pending Review: http://www.w3.org/2012/ldp/track/issues/pendingreview
  • Raised Issues: http://www.w3.org/2012/ldp/track/issues/raised

3 Proposals regarding Paging & 209 vs 200

• Section 5.3.5.1
• Proposed: Eliminate 303 and indicate that a client can learn it received a Page based on the existence of Link rel="next/prev" headers.
• Proposed: Launch an effort to define 209 as a separate IETF RFC that applies in general to 303s and that we can use in LDPnext

4 Proposal regarding PUT Create: Leave spec as is

• Section 4.4.6
• Proposed: Leave spec unchanged - "servers MAY choose to allow the creation of new resources using HTTP PUT" - and defer how servers can advertise this to post LDP 1.0 until we get more feedback on best practices.

5 Proposal regarding ISSUE-81 Part I: ldp:container

• http://www.w3.org/2012/ldp/track/issues/81
• Proposals Part I
• We should change ldp:container to something else to avoid likely confusion with ldp:Container.
• Proposed: Change ldp:container to ldp:containingResource.

Container and containing resource are the same:

 <> a ldp:Container; 
   ldp:container <>;
   ldp:containsRelation rdf:member;
   ldp:insertedContentRelation ldp:MemberSubject.

becomes:

 <> a ldp:Container; 
   ldp:containingResource <>;
   ldp:containsRelation rdf:member;
   ldp:insertedContentRelation ldp:MemberSubject.

Container and containing resource are different:

 <assets/container> a ldp:Container;
   ldp:container <assets>;
   ldp:containsRelation rdf:member;
   ldp:insertedContentRelation ldp:MemberSubject.

becomes:

 <assets/container> a ldp:Container;
   ldp:containingResource <assets>;
   ldp:containsRelation rdf:member;
   ldp:insertedContentRelation ldp:MemberSubject.

6 Proposal regarding ISSUE-81 Part II: Keeping the simple case simple

• http://www.w3.org/2012/ldp/track/issues/81
• Proposals Part II
• Proposed: Make ldp:insertedContentRelation optional, default is ldp:MemberSubject

7 Discuss: ISSUE-81 Part I bis: ldp:membershipRule

• Proposals Part I bis

8 Status of disposition of Last Call comments

• Pending comments

9 AOB