OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsia message

[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

Title: Message
Wouldn't you tend to think that "ID" hints towards persistence and "Handle" hints towards transience and not vice-versa?
-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Wednesday, May 22, 2002 3:26 PM
To: wsia@lists.oasis-open.org; wsrp@lists.oasis-open.org
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
      Session Information - This is carried opaquely in the interface as a
      => 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
   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