FYI
LDP is moving back in the W3C process, republishing as Last Call with a
3 week period, where there is room for some minor issues such as:
* context URIs on links
* find a better a link relation for the constraints
* switch to SHOULD for Turtle when Accept is not sent
* JSON-LD passes to MUST be supported
* putting ldp:IndirectContainer at risk
All feedback to the working group from the Marmotta community is welcomed.
-------- Forwarded Message --------
Subject: LDP edits for Monday's resolutions are live
Resent-Date: Wed, 10 Sep 2014 13:17:47 +0000
Resent-From: [email protected]
Date: Wed, 10 Sep 2014 09:16:39 -0400
From: John Arwe <[email protected]>
To: [email protected] Working Group <[email protected]>
Editor's draft [1] contains the following. Several of us agonized [3]
over the exact linguistic path through conneg for the revised Turtle words
(with a ripple effect on JSON-LD to handle the tie case), so the list of
changesets [2] is substantially longer than the set of resolutions [4].
Here's a list of direct links to affected sections to make things easier
than mentally merging the change sets.
Although we didn't resolve to have any WG review of these, seems like we
could shoehorn in 24 hours for sanity checks and still publish on Tuesday.
1: context URIs on links
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html
#ldpr-gen-pubclireqs
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-post-createbinlinkmetahdr
2: rel=describedby to rel=<some_LDP_URI>
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html
#ldpr-gen-pubclireqs
3: Change MUST on Turtle to SHOULD when Accept is ABSENT
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldprs-HTTP_GET
(first clause split into two; absent covered in second one)
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-post-turtle
(no change for this item; see below though)
4: Servers MUST support JSON-LD when requested by client, marked as a
feature at RISK
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#atrisk-ldpr-jsonld
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#atrisk-ldpc-jsonld
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#sotd
5: IndirectContainer as a feature at RISK
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#sotd
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#atrisk-indir-cont-ex
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#atrisk-indir-cont-ref1
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#atrisk-indir-cont-ref2
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#atrisk-indirect-containers
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpic-indirectmbr
(editorial: added final sentence to 5.5.2.1)
In the course of making the changes above, I found that some of the POST
clauses were making unwarranted assumptions (all POSTs are creates) so I
clarified those as well:
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-post-turtle (
from: must accept turtle [for any reason] if you support post/ to: ... [to
create a new member] ...)
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#atrisk-ldpc-jsonld
(same)
[1] https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html
[2] https://dvcs.w3.org/hg/ldpwg/shortlog
[3] https://susanlattwein.files.wordpress.com/2013/09/french-taunting.jpg
[4] https://www.w3.org/2013/meeting/ldp/2014-09-08
Best Regards, John
Voice US 845-435-9470 BluePages
Cloud and Smarter Infrastructure OSLC Lead
--
Sergio Fernández
Senior Researcher
Knowledge and Media Technologies
Salzburg Research Forschungsgesellschaft mbH
Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
T: +43 662 2288 318 | M: +43 660 2747 925
[email protected]
http://www.salzburgresearch.at
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 660 2747 925
e: [email protected]
w: http://redlink.co
