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: WSDM & OGSA cross WG discussion on August 18


Hi all,

Per Heather's request, I send proposed agenda items for WSDM & OGSA 
cross WG discussion on August 18.

Your comments are very welcome. 
----
Hiro Kishimoto

<Date/time>
August 8th, 3pm-6pm
Due to an arrangement for other sessions, I would start this
corss WG session from 3pm. Is it OK for WSDM folks?

<Venue>
Intel facility in Santa Clara
Address: 2200, Mission College Blvd., Santa Clara, CA 95052
Directions to Intel: http://tinyurl.com/644su
Meeting room is at the main lobby of the main building (RNB), next to the
Intel museum. 

Entrance Procedure:
All visitors will need to sign-in in at a security desk, show a picture ID
and obtain a visitor badge before entering the meeting room. All visitors
will also be subject to bag searches during sign-in.

<Dial in information>
Domestic - 1-888-452-0308
International 1-484-644-0505
the pass code for both is 13729

<Agenda>
(1) OGSA and WSDM taxonomies fit?
     - Start with comparison of what OGSA expects and what WSDM
       defines. Expect that it is one part of collaboration between
       the two groups. 

(2) OGSA usecase/scenario
    Extract EMS and data service usecase/scenario from v1 doc
    which utilizes WSDM as its management interface.
    
(3) Naming: Might want to have unique identifiers that are
       unique across domains.
       - To some extent uniqueness is addressed (identity
         comparison). But different identities do not preclude that it
         is the same resource.
       - No rules to define unique identities
       - Work on data management might be relevant here

(4) operational state diagram
  - MUWS defines a very basic operational state diagram. As already
    stated resources are not restricted to this; it can be extended or
    something else can be defined instead.
    - OGSA also expects to define some state diagrams (e.g., job). Not
      sure how good a fit exists between OGSA and WSDM.

(5) Event format
    - WSDM is defining common event format.
    - (Hiro) Grid would also need some common event format; and we have to
      discuss whether requirements match.

(6)  Policy and Negotiation (less sure about negotiation)
    - Future work. Probably not addressed until 2.0 or later
    - [Q] Relationship with WS-Agreement?
    - [A] Still not sure how negotiation applies to WSDM
      - Initially thought to allow for negotiation of policy (but is
        somewhat unclear at the moment)

(7) CMM and WSDM





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