I agree Ed. I would also note that OSLC Query is the only standard means available in OSLC to obtain the backlinks, regardless of how difficult or inefficient that might be.

GCs and project area associations used by jazz.net apps demonstrate a way of limiting the number of service providers that would need to be queried. The use of OSLC query for obtaining incoming links has been implemented and proven to work based on this approach.  I imagine there could be other implementations that would establish a meaningful search scope. This is an implementation detail the profile probably does not need to address.

If we feel TRS and some Link Query Service is required for a more useful approach to accessing incoming links, and is necessary for config-enabled situations, then we need to put that in our scope or do it in a separate profile.

Hello all,

At our last meeting it was asserted that using OSLC Query for back link discovery was completely untenable for larger installations because each and every IBM-ELM project area in every application must be queried. After some testing I would like to nuance this assertation. Recall that part of the issue here to what degree ProjectArea (aka ServiceProvider) association is required to create links.

GC mode

In GC compliant mode ProjectArea associates are not required to create links. Still it is only possible to create links to local configurations that are in the selected GC. For many cases the list of ProjectArea/ServiceProviders in a GC will be short.  

Non-GC mode

In non-GC mode ProjectArea is required to create links.

Conclusion

It is certainly true that we can imagine situations where using OSLC Query for back links might be untenable. I would suggest that there are many situations where OSLC query remains a workable options.

1. In non-GC mode with a limited number of ServiceProviders which is the usual case
2. In GC-mode with a smaller GCs

If an OSLC compliant application is integrated with IBM-ELM then an application can we can use LDX. If not then it is likely that one of the two conditions apply.

Cheers,

Ed

Ed Gentry
Product Owner

e.gentry@... | +49 0172 8867789 | Per Microsoft Teams anrufen

MID GmbH | Kressengartenstr. 10 | 90402 Nürnberg
Tel.: +49 911 968360 | www.mid.de
Sitz des Unternehmens: Nürnberg Handelsregister: Amtsgericht Nürnberg HRB Nr. 21108
Vorsitzender der Geschäftsführung: Dr. Martin Müller Geschäftsführer: Andreas Ditze
 .
   

Hello all,

At our last meeting it was asserted that using OSLC Query for back link discovery was completely untenable for larger installations because each and every IBM-ELM project area in every application must be queried. After some testing I would like to nuance this assertation. Recall that part of the issue here to what degree ProjectArea (aka ServiceProvider) association is required to create links.

GC mode

In GC compliant mode ProjectArea associates are not required to create links. Still it is only possible to create links to local configurations that are in the selected GC. For many cases the list of ProjectArea/ServiceProviders in a GC will be short.  

Non-GC mode

In non-GC mode ProjectArea is required to create links.

Conclusion

It is certainly true that we can imagine situations where using OSLC Query for back links might be untenable. I would suggest that there are many situations where OSLC query remains a workable options.

1. In non-GC mode with a limited number of ServiceProviders which is the usual case
2. In GC-mode with a smaller GCs

If an OSLC compliant application is integrated with IBM-ELM then an application can we can use LDX. If not then it is likely that one of the two conditions apply.

Cheers,

Ed

Ed Gentry
Product Owner

e.gentry@... | +49 0172 8867789 | Per Microsoft Teams anrufen

MID GmbH | Kressengartenstr. 10 | 90402 Nürnberg
Tel.: +49 911 968360 | www.mid.de
Sitz des Unternehmens: Nürnberg Handelsregister: Amtsgericht Nürnberg HRB Nr. 21108
Vorsitzender der Geschäftsführung: Dr. Martin Müller Geschäftsführer: Andreas Ditze
 .