[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-1) Ian to add scenario to https://wiki.oasis-open.org/oslc-core/DelegatedUIUseCases
[ https://issues.oasis-open.org/browse/OSLCCORE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61172#comment-61172 ] Martin Pain commented on OSLCCORE-1: ------------------------------------ Use case from OSLC Automation: OSLC Automation has some related resources, two of which are AutomationPlans and AutomationRequests. An AutomationPlan can have zero or more AutomationRequests - and it is expected to increase over time. In this use case the UI consumer wants a user to select one AutomationRequest for a given AutomationPlan from the UI provider, without listing all AutomationRequests for all AutomationPlans on the server. Existing non-standard implemention: The UI consumer POSTs to the selection dialog URI some RDF that contains solely the triple "<> oslc_auto:executesAutomationPlan <the-URI-of-the-plan-to-filter-by>". (This is a copy of the pre-fill on creation dialogs.) The dialog then displays only the AutomationRequests that contain such a property. I'm not advocating this as a solution to standardise, but just as a data point of prior art. > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]