oslc-core message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [oslc-core] Delegate UI use cases - Chained dialogs (wizards) and returning resource representations
- From: Ian Green1 <ian.green@uk.ibm.com>
- To: Martin P Pain <martinpain@uk.ibm.com>
- Date: Mon, 10 Mar 2014 13:51:51 +0000
Hi Martin
re postMessage offering a representation.
As I understand it, you are proposing
that the observer of the delegated UI will receive (via postmessage) a
representation of the newly created resource, rather than getting the URI
and having to do a GET.
Such a proposal raises for me lots of
questions because http protocol is being "bypassed". Can
you motivate when it would be necessary/desirable for the client to use
such a feature?
best wishes,
-ian
ian.green@uk.ibm.com (Ian Green1/UK/IBM@IBMGB)
IBM Rational
<oslc-core@lists.oasis-open.org> wrote on 05/03/2014
11:01:27:
> From: Martin P Pain/UK/IBM@IBMGB
> To: Arnaud Le Hors <lehors@us.ibm.com>
> Cc: oslc-core@lists.oasis-open.org
> Date: 05/03/2014 11:01
> Subject: [oslc-core] Delegate UI use cases -
Chained dialogs
> (wizards) and returning resource representations
> Sent by: <oslc-core@lists.oasis-open.org>
>
> I've submitted two delegated UI use cases to the wiki page [1]:
>
> * (mp) Chaining of dialogs (creating wizards from dialogs).
> Scenario: In OSLC Automation, a user might want to use a selection
> dialog to select an AutomationPlan, then be presented with an
> AutomationRequest creation dialog for that plan (or AutomationResult
> selection dialog, if appropriate). (One solution would be to
> encourage providers to include selection of those prior resources
in
> their later selection dialogs, but allowing composition on the
> client side allows more flexibility).
>
> * (mp) Should we allow creation dialogs to return an entire resource
> representation through the postMessage result (oslc:result)? e.g.
> this could be used by OSLC Automation 2.1 deferred-execution
> creation dialog - currently in draft. (If so, we might also want to
> consider moving this result value to be JSON-LD).
>
>
> [1] https://wiki.oasis-open.org/oslc-core/DelegatedUIUseCases
>
> Martin
>
>
> <oslc-core@lists.oasis-open.org> wrote on 04/03/2014 22:31:16:
>
> > From: Arnaud Le Hors <lehors@us.ibm.com>
> > To: oslc-core@lists.oasis-open.org,
> > Date: 04/03/2014 22:31
> > Subject: [oslc-core] Agenda for 6 March 2014
> > Sent by: <oslc-core@lists.oasis-open.org>
> >
> > Hi,
> >
> > The agenda for Thursday's call is now available:
> > https://wiki.oasis-open.org/oslc-core/Meetings/Telecon2014.03.06
> >
> > Please, note the new call-in info.
> >
> > Steve Speicher created a new document to capture the use cases
and
> > requirements for delegated UI. Please, add your own use cases
and
> > requirements as well as those for the Development and evolution
of
> > vocabularies which we already started.
> >
> > We'll discuss these this week.
> >
> > Best regards.
> > --
> > Arnaud Le Hors - Software Standards Architect - IBM Software
Group
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with
> number 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
PO6 3AU
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]