tutorial program

some airline will be exporting reservation services interfaces via web services.
amazon too (considering it)

mentioned N different interfaces problem (every WS is different so no standard way to talk to them).

how EDI worked for 30 years without ontologies
  people have talked about the terms enough to know what they mean
    a mentions EDI 850-470 and B understands
    doens't happen with resetta

VAN: EDI-specific network

EDIINT: transport non-XML EDI over the internet.

send message
wait for 2 hrs
resend

[EGP:
merge transport-level resend/ACK with those in the high-level state machines being transported.
PO is an ACK for a req
]

composite web services provide a fallback for partially failed web service
  don't cancel the hotel and plane res 'cause Hertz is down

web service definition:
  I/O
    formal parms are called ports and are asynchronous
      during service execution B says "Hertz is down." A says "try Avis."
  distinguish abstraction of booking a hotel from booking at hotels.com

data flow
  tie data R/W to parties.
    enables question: is every input satisfiable.
    enables optimizations like `find cheapest hotel`

Q: picture is complex, what will industry adopt first/when?

A: complex is done today (for instance, via VAN) but not in one framework
   internet hype made people aware of this integration problem.

Mclraith's talk

performative information/query

DAML-S

Q: what is a T-model?
A: template model -- construct used within UDDI to provide instanceOf classification

functionality description:
  precondition, input, output, effect

rating services: NAIC, Dun and Bradstreet xxx for companies

"need onotologies and description logics to reason about this."
  Q: what does the desc logic contribte?
  A: subsumption reasoning for services

a particular aggregation of located services could be stored as a process model

"atomic process: non-decomposable process"

"ultimate goal: semantic SQL."

Q: flexible matching -- do a flex match with google and take the first hit
   analogous to taking the first hit on google
A: we are using a series of filters and our constraints are not text, they are
   formally specified capabilities and effects.

Q: what about W3C and OWL?
A: DAML-S may become OWL-S. Also, in 18 months, we should have the architecture web services model.
   Also industry instituted WSI, to go more quickly than W3C. Composed of mostly the same comapianies.
   Other issue, patents -- companies must relinquish rights to patents to partisipate.


Q (harold boley): is DAML-S a provable superset of WSDL and UDDI?
A: we'd like to do some expriments.
   another compatibility issue -- UDDI servers sync at night.
   another diff -- trying multiple