[OASIS Issue Tracker] (OSLCCORE-1) Ian to add scenario to https://wiki.oasis-open.org/oslc-core/DelegatedUIUseCases

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCORE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61148#comment-61148 ] 

James Amsden commented on OSLCCORE-1:
-------------------------------------

Ok, I get it. A client might want to control what's available on a selection dialog. For example, consider a project that has 12000 requirements. If a client wanted to select a requirement, they likely wouldn't want to have to choose from all 12000. They need some way to narrow down the selection list to something more manageable.

Sam's answers are correct. The server could organize requirements in different LDPCs (or Services creationFactories), and the client could choose one of those. 

But ultimately its up to the server creating the selection dialog to decide how best to support their client needs. For example, a selection dialog can be designed to display folders of requirements, use tags to focus the selection, provide regular expression matching, or even some server supported query mechanism. This is all outside the scope of OSLC which only specifies how the client discovers the dialog, and how the client interacts with the dialog to resize, cancel, or get the selected resource URIs. What's in the dialog iframe is entirely up the the server and should be transparent to the client application, but visible to the user.

We can discuss this, but I think it can probably be closed.


> Ian to add scenario to https://wiki.oasis-open.org/oslc-core/DelegatedUIUseCases
> --------------------------------------------------------------------------------
>
>                 Key: OSLCCORE-1
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-1
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>            Reporter: Steve Speicher
>            Priority: Minor
>              Labels: action-item
>




--
This message was sent by Atlassian JIRA
(v6.2.2#6258)