[OASIS Issue Tracker] (OSLCCORE-26) Linking from Service resource to read-only LDPC

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCORE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60383#comment-60383 ] 

James Amsden commented on OSLCCORE-26:
--------------------------------------

I'm not sure what the ACLs standards are for HTTP, but WebDAV ACLs specifies that OPTIONS requires read privilege. That would mean that a client without read privilege on an LDPC would not be able to discover anything about that LDPC. However, if that same client did have read access on a ServiceProvider resource, then they could read that file, and potentially discovery things about that LDPC, unless the server generated the ServiceProvider resource based on the clients access rights. This wouldn't work if the ServiceProvider resource were a static document.

This probably requires some discussion in the specs regarding consistency between what a client can discover through the different approaches to discovery - it should be the same.

> Linking from Service resource to read-only LDPC
> -----------------------------------------------
>
>                 Key: OSLCCORE-26
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-26
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: Martin Pain 
>            Assignee: James Amsden
>
> In OSLC v3 discovery, I think we need to think about how the links from a Service resource work.
> Particularly, if you have an LDPC that contains resources for a service, and that LDPC is read-only, and it doesn't support the OSLC v2 query capability, then what predicate would you use to link from the Service to the LDPC?
> If it supported creation, then listing is using oslc:creationFactory would probably be appropriate (and v3 clients could detectit's an LDPC using its 'rel=type' Link response header). If it supported the OSLC v2 query capability, then oslc:queryCapability would work. But if it's read-only, and can only be read using the means defined by LDP (plain GET, responding with ldp:contains; LDP Prefer headers; possibly LDP paging) then how do we link to it?



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)