Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need a means to specify how OSLC clients/servers access incoming links #582

Open
jamsden opened this issue Sep 1, 2022 · 0 comments
Open
Assignees
Labels
linking-profiles Issues associated with OSLC Linking Profiles

Comments

@jamsden
Copy link
Member

jamsden commented Sep 1, 2022

The proposed Basic and Bi-Directional profiles currently specify OSLC Query as a MUST in order to get incoming links. In order to include the config profile, we will need to consider how to introduce the OSLC Link Discovery Service. There are two aspects of this Link Discovery Service: 1. How to make the links a server owns discoverable by other servers 2. How to discover incoming links a server doesn't own

ELM tools mostly require a server to contribute their own links through a TRS provider when config enabled. There is a special case for DOORS Next that uses OSLC query for incoming AM links. So it may be necessary to provide an additional ResourceShape constraint to specify which incoming link discovery API should be used to get specific incoming links. Even if this implementation detail is abstracted into the OSLC Link Discovery Service, a mediatory will need to be able to discover how to delegate the request for incoming links.

@jamsden jamsden added the linking-profiles Issues associated with OSLC Linking Profiles label Sep 1, 2022
@jamsden jamsden self-assigned this Sep 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
linking-profiles Issues associated with OSLC Linking Profiles
Projects
None yet
Development

No branches or pull requests

1 participant