OSLC Integration Wishlist

[james.e.hopper@leidos.com]

I would really love to be able to work with JIRA

[james.ciarcia@navy.mil]

According to both TWC 19.0 and 19.0 SP1 documentation @ https://docs.nomagic.com/display/TWCloud190SP1/OSLC+API there are only 4 properties exposed, making the conformance to the AM technically correct, but still very minimal. When would we expect to see some resourceShapes defined for the UML metaclasses? Is there any way to access the MOF associations that define each metaclass properties and relationships?

I would love to see something similar to the rdf mapping that was experimentally done for SysML 1.3 as documented @ http://www.omgwiki.org/OMGSysML/doku.php?id=sysml-oslc:oslc4mbse_working_group#sysml_rdf_vocabulary. Has any further work been done toward that end? Or are you waiting for some OMG standards to be released such as https://www.omg.org/cgi-bin/doc.cgi?ad/2009-12-9 the MOF to RDF Structural Mapping in Support of Linked Open Data RFP or SysML v2 services?

While Cameo is superior to other tools, the support for OSLC appears to be lagging a little. While I really like the idea of making the OSLC implementation as open specification as possible, it would be good to see a roadmap. That way customers can start developing their own OSLC clients for TWC.

[amarish.garud@gmail.com]

Please note that OSLC implementations of various OSLC providers are rather fickle (especially in the authentication aspect), so there may be some small quirks and/or impediments
to correct connecting to the OSLC provider (with unclear attribution - whether problem lies on the OSLC consumer side or on the OSLC provider side).
If you have any problems connecting to some specific OSLC provider X, please report them and we will try to investigate where the problem lies and provide some guidance.

I am getting the error to connect OSLC provider X through CSM R19SP3, where I have already installed Cameo Datahub plugin. I do not have TWC installed.
So in my case CSM client shall be able to access the OSLC provider using "Root service URI/ OAuth credentials"

Please suggest what is missing from my installation setup OR how can I troubleshoot it to solve this problem?

Regards,
Amarish

[rotundas19@gmail.com]

Please note that OSLC implementations of various OSLC providers are rather fickle (especially in the authentication aspect), so there may be some small quirks and/or impediments
to correct connecting to the OSLC provider (with unclear attribution - whether problem lies on the OSLC consumer side or on the OSLC provider side).windows
If you have any problems connecting to some specific OSLC provider X, please report them and we will try to investigate where the problem lies and provide some guidance.

I am getting the error to connect OSLC provider X through CSM R19SP3, where I have already installed Cameo Datahub plugin. I do not have TWC installed.
So in my case CSM client shall be able to access the OSLC provider using "Root service URI/ OAuth credentials"

Please suggest what is missing from my installation setup OR how can I troubleshoot it to solve this problem?

Regards,
Amarish

Hi, have you had any luck solving this out? Would be great if you could share the solution with me.
Thanks,
Tomas

[Seb_C]

Will Cameo / MSOSA ever be a provider for OSLC, or only a consumer? I would love if Cameo was able to act as a provider as well, that would enable some great capability for my team.

[francesco.matraxia@hima.com]

Hello everyone,

i would like to know if it is possible to establish a traceability between a model stored in Teamwork Cloud and requirements in Polarion. I heard about Reqtify but i would like to see if it is also possible using OSLC. (i am not in interested in ReqIF)

Many thanks for your answers