oslc-op / oslc-specs

OSLC OP specifications and notes
https://open-services.net/specifications/
25 stars 10 forks source link

Configuration management does not describe use of configuration context for OSLC query #526

Open DavidJHoney opened 3 years ago

DavidJHoney commented 3 years ago

The configuration management spec Part 3: Configuration Specification has a section 15. Query Support, but that section does not cover use of configuration context for OSLC Query. Section 7 describes usage of configuration context for versioned resources, but does not cover OSLC query.

This means that currently there is no OSLC defined mechanism for querying for versioned resources in a configuration context. However, we have some Rational ELM applications that DO implement this!

Section 8 says:

A configuration server must support the following operations on configuration items (versioned concept resources) in the context of a global configuration, or in the context of a configuration from this server: [config-res-106]

However, I learnt that DOORS Next only supports local configuration contexts for OSLC query and not global configuration contexts. Given the intent of [config-res-106], I regard that as a defect. However, because the configuration management specification is silent on configuration scoping of OSLC queries, one might argue that this is not a defect.

I think this omission is an oversight and needs to be fixed before we go to PSD.

Proposal: Update 15. Query Support to add the following conformance clause:

Servers that support query capabilities on versioned resources MUST support the use of a configuration context to limit the query results to the versions selected by that configuration context, or to unversioned resources. The configuration context MUST support reference of a global configuration, or a configuration from this server.

jamsden commented 3 years ago

Agree

DavidJohnHoney commented 2 years ago

I think this should be addressed before we go to PS. It's currently outstanding in the PSD.

berezovskyi commented 2 years ago

There is a potential for the ambiguity in "MUST support reference of a global configuration, or a configuration"