Re: [humanmarkup-comment] Re: [uiml-discuss] RE: founding member

[cognite@zianet.com]

Thanks for drawing these strings together for us, Rex.

Could you make a quick sketch of the flows here, as far as they can be
imagined at this point?  IFF it isn't a big time-taker for you.  A rough
starting point is this below, though I don't know if I'm reading you right;
is this it? 

-----------------------------------------------------------------------------
From the WSIA point of view,
(where x is to indicate combination or  "cross-product"  and -> is an arrow
showing flow):
-----------------------------------------------------------------------------

primary producers [of discourses]

x  encoding for transmission and ultimately viewing/executing

-->

web services [markup-] language WSDL  

x  used in "portlet" software, e.g., Java with term space from JSR 168
established by Java Community Process group

--- --> via SOAP protocol pass-thru

 --> user lookup registries (e.g., UDDI)

 --> User

x browser or other client-side app for viewing/executing

-----------------------------------------------------------------------------

SC

At 10:30 AM 10-10-2002 -0700, you wrote:
>Hi Again Manos, et al,
>
I wanted to add a couple of interesting issues from today's meeting 
of the WSRP-WSIA Joint Interface  group, which is rapidly becoming 
indistinguishable from one larger TC, but which is getting 
hellaciously complicated, and those are that there are various kinds 
of ways in which UIs will be accommodated in that specification.
...
>One is as a set of properties (a list of markup types, mime types, 
>and specific contexts, one of which is userContext (user profile). 
>Another entire issue which will impact UIs is JSR 168 which is the 
>Java Community Process group that is dealing with Java-encoded 
>portlets, and this protcol is being synched with Web Services Remote 
>Portal so that those two protocols handle similar information the 
>same way, or at least do not invalidate or conflict with each other.
>
>Intermediary aggregators of what is called Web Services are the 
>agencies which will be handling the flow of these services from the 
>primary producers through SOAP using WSDL, and various look-up 
>registries such as UDDI to end users--the folks with which 
>HumanMarkup is most concerned in those contexts. (We also allow for 
>AI and various kinds of user agents which can use our schemata for a 
>multitude of purposes.)
>
>However, the point I am making is that it is simply impossible for 
>all of the different groups, and more, that I mentioned in my first 
>message this morning, to be taking accurate account of each other. 
>One service which I believe I heard some mention of, unless I am 
>imagining it, is some kind of inter-OASIS and/or 
>inter-Standards-Organizations liaison. If someone can direct me to 
>the list, I would like to represent the groups with which I am most 
>familiar.
>
>Some harmonization of this growing tangle of would-be standards is 
>going to be necessary.
>
>Ciao,
>Rex
>
>At 5:50 PM +0300 10/10/02, m batsis wrote:
>>Rex Brooks wrote:
>>>I am copying this to the Humanmarkup public comment list in the 
>>>hope that someone out there has the time to at least monitor this 
>>>UIML effort so that we will not be obliged to retrofit our 
>>>specifications to accommodate it if it becomes necessary, or to 
>>>actively liaise if it appears wise and possibly fruitful.
>>
>>Since I have an interest on UIs and am familiar with related 
>>vocabularies (XHTML/SVG, XForms, XUL, XBL etc) I'll be happy to 
>>establish a connection with the UIML TC.
>>
>>I have subscribed to uiml-discuss and will have comments on the v3 
>>spec by Monday.
>>
>>If anyone has any usefull pointers please do share.
>>
>>Manos
>
>
>-- 
>Rex Brooks
>Starbourne Communications Design
>1361-A Addison, Berkeley, CA 94702 *510-849-2309
>http://www.starbourne.com * rexb@starbourne.com
>
>
>----------------------------------------------------------------
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.oasis-open.org/ob/adm.pl>
>
>