[OASIS Issue Tracker] (OSLCCORE-9) Bootstrapping discovery

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

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

James Amsden commented on OSLCCORE-9:
-------------------------------------

If we require OSLC 3.0 to be backward compatible with OSLC 2.0, then discovery would need to continue to support Service Provider Catalog, Service Provider and Service resources. Its entirely likely that each of these would correspond to related LDP Containers. So a client could use the URI for the Service Provider Catalog, or its corresponding LDP container as the starting point for discovery using either OSLC 2.0 or 3.0 static/dynamic discovery techniques.

Do we agree that this would be sufficient to close this issue?


> Bootstrapping discovery
> -----------------------
>
>                 Key: OSLCCORE-9
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-9
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>            Reporter: Martin Pain 
>            Assignee: James Amsden
>
> See https://lists.oasis-open.org/archives/oslc-core/201503/msg00016.html
> See also a draft from Mark Nottingham about HTTP home documents: http://tools.ietf.org/html/draft-nottingham-json-home-03 (I haven't read it yet)



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