Re: Suspect links


"Eran Gery"
 

Jad

Suspect links related to any oslc link. not specific to “parent/child”. A classical use case is a link between a requirement and a design element that refines it. 

Also, Suspect information depends on a configuration. A link can be suspect in one configuration and valid in another.

The way it is implemented in Jazz is based on a dedicated service. Applications need to interact with the service to retrieve and update the state of a link.

Eran




On 1 Nov 2022, at 1:25, Jad El-Khoury <jad@...> wrote:


Hi When creating links between applications, is there some OSLC mechanism to identify and tag “Suspect” OSC links? If not covered by OSLC, any good hints on some good practices? For example, ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd

Hi

 

When creating links between applications, is there some OSLC mechanism to identify and tag “Suspect” OSC links? If not covered by OSLC, any good hints on some good practices?

 

For example,

* how can an OSLC Application know that a resource it links to (in another application) has been changed?

* how can an OSLC Application inform another application that a resource it links to has been changed?

To my understanding

  1. suspect links are only relevant on a parent-child relationship when the parent has changed (to warn the child item that the parent has changed)
  2. And, with OSLC, we don’t really have the semantics of parent-child semantics (which is different from the link direction)

 

 

regards

______________________________

Jad El-khoury, PhD

KTH Royal Institute of Technology

School of Industrial Engineering and Management, Mechatronics Division

Brinellvägen 83, SE-100 44 Stockholm, Sweden

Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45

jad@..., www.kth.se

 

Join oslc-op@lists.oasis-open-projects.org to automatically receive all group messages.