Hi All

Here is an initial draft of the outline, motivation, and solution requirements for the OSLC linking profiles supplement

Best regards,

Eran Gery – Global Industry Solutions Lead, IBM ELM

Hi,

Please find my comments attached! Great start!

/Andrew

Hi All

Here is an initial draft of the outline, motivation, and solution requirements for the OSLC linking profiles supplement

Best regards,

Eran Gery – Global Industry Solutions Lead, IBM ELM

I have added some tracked changes and comments to Andrew’s comments.

Overall, I think this is an excellent description of the interoperability challenge we are trying to address, the proposed solution scope, and its business value. This is a good foundation upon which OSLC-OP can proceed. Thank Eran for your contribution.

Key issues I think we will need to address:

1. Separating the specification of how profiles are defined, from the specification of linking profile instances that address a specific integration problem
2. Establishing some standard way of expressing link storage ownership (e.g., ResourceShape extension)
3. Maintaining a seamless shift from OSLC Query based approach to discovering incoming links vs. a possibly future Link Discovery Service – ideally a richer profile layers on additional capabilities without invalidating existing approaches or creating its own interoperability challenges
4. Establishing some standard way of expressing how incoming links are accessed if the approach depends on the link type (as it does in DOOR Next)
5. Ensuring the profile clauses are machine readable and testable to facilitate automation of profile compliance verification

Hi,

Please find my comments attached! Great start!

/Andrew

Hi All

Here is an initial draft of the outline, motivation, and solution requirements for the OSLC linking profiles supplement

Best regards,

Eran Gery – Global Industry Solutions Lead, IBM ELM