What is the correct property for OSLC Automation providers to use in their root services documents when being consumed by RQM?
Our OSLC Automation provider has a root services document that uses an oslc_auto:autoServiceProviders property/predicate to point to our Service Provider Catalog. However, I now can't find that documented either in the Root Services spec, or in the OSLC Automation vocab. Is that still the current "best practice" (or only) property to use, or is there a more recent one (e.g. jd:oslcCatalogs, or oslc:serviceProviderCatalog)?
A colleague was asking about the best property to use for linking to CM catalogs - having seen both oslc_cm:cmServiceProviders and jd:oslcCatalogs properties - and that made me realise that the one that we're using isn't in the Jazz documentation that I'm looking at.
Is there anything that we ought to be changing to bring our implementation up-to-date with what RQM expects in that aspect?
A colleague was asking about the best property to use for linking to CM catalogs - having seen both oslc_cm:cmServiceProviders and jd:oslcCatalogs properties - and that made me realise that the one that we're using isn't in the Jazz documentation that I'm looking at.
Is there anything that we ought to be changing to bring our implementation up-to-date with what RQM expects in that aspect?