← Prev in month ← Prev in thread

[OASIS Issue Tracker] (OSLCCORE-85) How to discover TRS

From
OASIS Issues Tracker <>
Date
2017-03-02T15:19:44+00:00
ID
Thread
[OASIS Issue Tracker] (OSLCCORE-85) How to discover TRS
[ https://issues.oasis-open.org/browse/OSLCCORE-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65368#comment-65368 ] 

David Honey commented on OSLCCORE-85:
-------------------------------------

Should we declare a new capability that can be referenced in a service provider referenced in a SPC?

> How to discover TRS
> -------------------
>
>                 Key: OSLCCORE-85
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-85
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Improvement
>            Reporter: David Honey
>            Assignee: James Amsden
>
> https://tools.oasis-open.org/version-control/svn/oslc-core/trunk/specs/tracked-resource-set.html#discovery described discovery but does not state how an indexer finds that data. Current Jazz applications use rootservices, which is usually a static XML document at a known URI relative to the application context root. Applications that want to dynamically provide TRSs, such as ones for a project area or some other data partition, do not have a standard means of advertising them, and indexers have no means to determine which new ones might be of interest to add as a data source.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
← Prev in month ← Prev in thread