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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsdm message

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


Subject: Notes from the wsdm meeting on 8/5/2004


Here are some terse notes from the meeting last week.  Thank god we have 
John :)

Cheers,
H.
--

- Roll call (Winston)

We discussed two main issues:

Review of the MOWS document
---------------------------

Section 3.2.5 - The last state model did not distinguish between how
the incoming request behaved (processed something or failed) before
exiting.  The new model includes two states that make that
distinction.  "Request Model" state in the old model is broken into
Processed and Failed states that lead to a Request Complete state. 

Action Item: Igor to rewrite the text to include the input provided.

Section 3.2.5.1 - Use expressions to define subscription of
notifications.  The schema also should also expression of selectors on
the information.

With regard to the RequestProcessingNotification schema tag do:

Action Item: Include the previous state info.
Action Item: Describe the full context of all the elements.

Action Item: It is not clear how this can be implemented and reflected
in the state diagram.  Include an example to clarify things.

Action Item: Allow flexibility for sub-events.

Question: Should Top level state and request be required or should
they be optional?

Relationships
-------------

Both Igor and William did a high level description of the proposals
that they have submitted.  The TC has setup two dedicated calls for
discussions around relations on Fridays from 10-11 PDT. 

William's proposal introduces a new definition for
RelationshipProperties in WS-Resource.  He also defines new relation
notification topics for use by mgrs.

There was a discussion on the taxonomy of relationships and Igor
suggested that he will send out something on the subject.

Igor's proposal uses the notion of references to describe the actors
(source or the target) of a relation.  Actors can have multiple
references.

Both proposals assume relations as binary associations between a
source and a target -- which assumes directionality. 

Andrea disagreed with this and mentioned some use cases where this may
not work.

Action Item: Andrea will provide us with more relation use cases from
CIM that contradicts the directionality assumption difficult.

End of meeting --

begin:vcard
fn:Homayoun Pourheidari
n:Pourheidari;Homayoun
org:WebLogic Integration
adr;dom:;;2315 North First St.;San Jose;CA;95131
email;internet:homayoun@bea.com
tel;work:+1 408.570.8175
version:2.1
end:vcard



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