OASIS Web Services Interactive Applications TC

 View Only

Re: [wsrp][wsia][wsrp-wsia joint interfaces][Draft Spec 0.43]Terminology

  • 1.  Re: [wsrp][wsia][wsrp-wsia joint interfaces][Draft Spec 0.43]Terminology

    Posted 05-22-2002 15:28
     MHonArc v2.5.2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    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


    
    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)
    
    
    
    


    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


    Powered by eList eXpress LLC