[
https://issues.apache.org/jira/browse/MARMOTTA-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131408#comment-14131408
]
ASF subversion and git services commented on MARMOTTA-531:
----------------------------------------------------------
Commit 93caa0f613ba1978221f621fc541902cd086874a in marmotta's branch
refs/heads/ldp from [~jakob]
[ https://git-wip-us.apache.org/repos/asf?p=marmotta.git;h=93caa0f ]
MARMOTTA-531: Changed the constrainet relation link (rel="ldp:contrainedBy")
MARMOTTA-530: Added context (anchor="...") to rel="describedby" Links
MARMOTTA-519, MAROTTA-520: tests pass with the updated ldp-testsuite
> Change the constrained link relationship
> ----------------------------------------
>
> Key: MARMOTTA-531
> URL: https://issues.apache.org/jira/browse/MARMOTTA-531
> Project: Marmotta
> Issue Type: Sub-task
> Components: Platform
> Affects Versions: 3.2.1
> Reporter: Sergio Fernández
> Assignee: Jakob Frank
> Labels: ldp
> Fix For: 3.3.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Given the
> [conflict|http://www.w3.org/2013/meeting/ldp/2014-09-08#resolution_3] with
> the usage of {{describedby}} to describe implementation constraints, the
> latest draft are proposing a new custom relationship:
> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#h5_ldpr-gen-pubclireqs
> {quote}
> 4.2.1.6 LDP servers must publish any constraints on LDP clients’ ability to
> create or update LDPRs, by adding a Link header with an appropriate context
> URI, a link relation of http://www.w3.org/ns/ldp#constrainedBy, and a target
> URI identifying a set of constraints [RFC5988], to all responses to requests
> that fail due to violation of those constraints. For example, a server that
> refuses resource creation requests via HTTP PUT, POST, or PATCH would return
> this Link header on its 4xx responses to such requests. The same Link header
> may be provided on other responses. LDP neither defines nor constrains the
> representation of the link's target resource. Natural language constraint
> documents are therefore permitted, although machine-readable ones facilitate
> better client interactions. The appropriate context URI can vary based on the
> request's semantics and method; unless the response is otherwise constrained,
> the default (the effective request URI) should be used.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
