[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [wsrp][wsia][wsrp-wsia joint interfaces][Draft Spec 0.43]Terminology
I'm not sure why we distinguish between a type "handle" and a type "sessionID"? The session ID could be viewed as a transient wrapper around the persistent entity if there is a many to one relationship between sessions and persistent entities (as I assume). The markup could then be as well requested directly from the "session entity". So I would propose not to distinguish them from an identifier point of view: handle createEntity(handle, propertyValues) handle createSession(handle, propertyValues) Best regards Carsten Leue ------- Dr. Carsten Leue Dept.8288, IBM Laboratory Böblingen , Germany Tel.: +49-7031-16-4603, Fax: +49-7031-16-4401 |---------+----------------------------> | | Rich | | | Thompson/Watson/I| | | BM@IBMUS | | | | | | 05/22/2002 09:25 | | | PM | | | Please respond to| | | Rich Thompson | | | | |---------+----------------------------> >---------------------------------------------------------------------------------------------------------------------------------------------| | | | To: wsia@lists.oasis-open.org, wsrp@lists.oasis-open.org | | cc: | | Subject: Re: [wsrp][wsia][wsrp-wsia joint interfaces][Draft Spec 0.43] Terminology | | | | | >---------------------------------------------------------------------------------------------------------------------------------------------| Presuming the 2nd case to get dropped relative to the previous set of emails, I would propose this section call out how we will refer to these things throughout the remainder of the document/API. In particular, I would suggest: Session Information - This is carried opaquely in the interface as a "sessionID". => goes away Persistent Information - This is carried opaquely in the interface as a "handle". Rather than "Manifestation", I would propose using "Entity" to describe the thing from which markup may be requested. I think it has the right level of opacity (Consumer has no idea what kind of entity it is) while carrying appropriate semantics (a thing that may be interacted with). Using these terms, there was also an open question at the end of our last call related to whether there were both persistent and transient entities ... If we are going to support explicit lifecycle for both of these, I would propose: handle createEntity(handle, propertyValues) sessionID createSession(handle, propertyValues) ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC