[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-9) Bootstrapping discovery
[ https://issues.oasis-open.org/browse/OSLCCORE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59937#comment-59937 ]
Martin Pain commented on OSLCCORE-9:
-------------------------------------
(Sorry for the delay in replying)
Yes, that is what I mean. (I think you answered your own question about how that would work and provide v2 compatibility - are there any more details you'd want me to clarify my view on?)
I don't think we would need to say that the catalog and provider LDPCs can't contain anything else, but OSLC says nothing about those other things so anything else in those LDPCs would not be OSLC, and therefore not meaningful to OSLC clients.
> 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]