Notes of WSMO teleconference 2006/1/18 Notes taken by Jacek Present: John, Emilia, Sven, Jacek, Reto, Axel, James, Ioan, Cristina, Adina Topic: D3.4 - Amazon use case James: only minor changes - state signature introduced "concept" keyword James: and some updates in the transition rules John: are all listings validated? James: yes, only choreography lacks as the validator has to be updated James: unsure about the status of when WSMX will run this John: we need a deadline Axel: James should find out until next telcon when WSMX could have this use case running ACTION: James will find out until next telcon (Feb 1) when WSMX plans to have the use case running Axel: who are the reviewers? Axel: I can review it but need 3 weeks for it, not just two John: we should get someone from WSMX ACTION: Axel to review D3.4 by Feb 10 ACTION: James to find a WSMX reviewer for D3.4 Topic: D14 John: the deliverable is in good shape, but how would you do the actual invocation of the web services? Last answer I heard was "grounding", the deliverable (section 3.3 or 3.2) should say that, with at least a one-line summary and a link to the grounding deliverable John: comment on section 4: the OU is working on orchestration in IRS, it seems that in D14 you need something called "performative". John: In orchestration, you invoke goals, and you want to enable these invocations. Axel: I understand, ideally Barry should join us more actively John: he will implement it by end of January, then he can show it to us Axel: for example by presentation in the WSMO telcon? John: will add it to the agenda of an appropriate meeting John: is this deliverable now pretty much final? Axel: newer suggestions are in a KWeb deliverable, will have to be added to D14 - like non-determinism using choose construct etc. Axel: but first we need to prove the model with some examples James: I had problems modeling non-determinism in D3.4, as Amazon WSDL doesn't expose faults James: anyway, it seems we only have client-side non-determinism, we need something like OR on the updates that the rules effect John: we will have minor update, then ask Dieter about making it final Axel: and then we open version 0.3 to include orchestration? John: we need to see what Barry is doing Topic: SPARQL Axel: SPARQL is an RDF query language Axel: there's a protocol on top of it as well Axel: but apparently there are concerns about SPARQL following the RDF semantics Sven: but SPARQL is very simple, some parts seem to be missing, like nested queries; I might know by the next telcon Axel: we might postpone the topic and tell Martin, who raised the issue, to come to the next telcon - and should it be WSMO or WSML WG? John: OK, postponed SPARQL discussion postponed to the next telcon Meeting adjourned, we'll meet in 2 weeks