OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (OSLCCORE-20) Service provider should describe domain/scope

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

Martin Pain commented on OSLCCORE-20:

As for my view on whether we should change anything or not:
- I certainly don't think any RDF content type should be a MUST. Not all servers have this problem.
- Actually, I can't see why a generic client would be doing this - we might have covered this before, but why would it have the URI of the (vendor-specific) project area if it wasn't written with knowledge of that vendor's specifics? Therefore, the vendor could solve this with a vendor-specific link, or any other vendor-specific way (or even oslc:serviceProvider from the project area resource to its service provider).
- In any case, I would still support widening the definition of oslc:details to allow for RDF resources at the other end. (Then use of oslc:details could be the "vendor-specific way" of solving this problem).
- If we did that, then my preference for our resolution of this issue would be: Ideally servers would make that other resource (the project area) the same resource as the SP. But if they don't want to do that, they can use oslc:details to link from the SP to the vendor-specific resource for which it provides services.

> Service provider should describe domain/scope
> ---------------------------------------------
>                 Key: OSLCCORE-20
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-20
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Improvement
>            Reporter: David Honey
>            Assignee: James Amsden
>              Labels: ready-for-vote
> OSLC 2.0 supports a service declaring a domain or scope using oslc:domain and oslc:usage. Jazz applications frequently declare a service provider for each project area. However, there is no standard way for a client to determine which service provider to use for a known project area.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]