[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:comment-tabpanel&focusedCommentId=70100#comment-70100 ] Andrii Berezovskyi commented on OSLCCORE-85: -------------------------------------------- The link in the description is 404: https://tools.oasis-open.org/version-control/svn/oslc-core/trunk/specs/trs/tracked-resource-set.html#discovery > 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 > Priority: Major > > 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 (v7.7.2#77003)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]