[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-26) Linking from Service resource to read-only LDPC
[ https://issues.oasis-open.org/browse/OSLCCORE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Amsden updated OSLCCORE-26: --------------------------------- Issue Type: Task (was: Bug) > 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: Task > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]