DWA OSLC get specific view
One answer
Hi,
I'm not entirely clear what you mean here.
Do you mean
1. "How do I get which requirements are visible in a view"
or
2. "How do I get requirements so that they look as they would in a view (i.e. with only the attributes that would be visible)?
In case 1 - there are no modules and no views in OSLC. These are quite simply not part of the specification. So what we have done, in an attempt to make as much information available as possible, is use Requirement Collections to describe the content of the module itself (as if standard view was applied) and the content of a view (which may have a filter applied).
If you are using the delegated user interface then when you pick a view the URI returned will be that of a Requirement Collection which contains the Requirements that the view would have.
If you are not using the DUI, how are you getting the resource URIs?
In case 2 - this cannot be done. A Requirement is a Requirement. If you ask for one you get the whole thing. Further view definitions/filters are not aviable via OSLC at all.
I'm not entirely clear what you mean here.
Do you mean
1. "How do I get which requirements are visible in a view"
or
2. "How do I get requirements so that they look as they would in a view (i.e. with only the attributes that would be visible)?
In case 1 - there are no modules and no views in OSLC. These are quite simply not part of the specification. So what we have done, in an attempt to make as much information available as possible, is use Requirement Collections to describe the content of the module itself (as if standard view was applied) and the content of a view (which may have a filter applied).
If you are using the delegated user interface then when you pick a view the URI returned will be that of a Requirement Collection which contains the Requirements that the view would have.
If you are not using the DUI, how are you getting the resource URIs?
In case 2 - this cannot be done. A Requirement is a Requirement. If you ask for one you get the whole thing. Further view definitions/filters are not aviable via OSLC at all.