[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-85) How to discover TRS
[ https://issues.oasis-open.org/browse/OSLCCORE-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Amsden updated OSLCCORE-85:
---------------------------------
Component/s: TRS
> 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
> Components: TRS
> 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]