On 21 May 2014 21:44, Rafael Chaves <raf...@abstratt.com> wrote: > > > At the moment, that's true, though in RO is starting to move in that > > direction. > > > > In RO v1.1 [3] (which .NET implements, not yet Isis) we have the concept > of > > property prompt and action parameter prompt. These enable conditional > > choices to be computed, eg Category/Subcategory. > > > > > I can see usefulness in that for sure, but the design probably looks > different than in a framework meant for local (in-process) clients (instead > of callbacks, you do a GET on some URL). In Kirra, for instance, there are > methods that Dan,can be invoked to determine the "domain" of a parameter > or of a relationship, i.e. candidate objects for a relationship or a > parameter (code API source [4] and live REST API [5] - look for slots named > domainUri). > > good stuff.. similar to RO's "domain-types" resources... exposing the metamodel.
> Also, now that I think about it, even in RO 1.0 we made the validate > > functionality available as a callback; hit the put/post resource, with an > > optional x-ro-validate-only argument. > > > > > Right, a dry-run mode, makes sense. But strictly speaking, not a callback, > right? (server doesn't invoke the client) > > True, wrong terminology. What I meant was simply that its a resource that's likely be to called from a client-side event callback (eg onBlur of some widget) websocket-y stuff is a whole different discussion! > > > > OK, what next? > > > > > > So, the short answer is: I don't know yet. :) > > Thanks for the conversation! > > No worries, any time... always happy to explore "synergies". Cheers Dan > Rafael >
