See also: IRC log
<ericP> http://www.w3.org/2002/ws/sawsdl/minutes/20060516
<ericP> PROPOSED, accept http://www.w3.org/2002/ws/sawsdl/minutes/20060516 as a true record of the last meeting
<ericP> SECOND: Joel
RESOLUTION: Minutes approved
<ericP> ACTION: 2006-05-09: EricP to make the HTML to override the schema at http://www.w3.org/2002/ws/sawsdl/spec/sawsdl [CONTINUED] [recorded in http://www.w3.org/2002/ws/sawsdl/minutes/20060523#action01]
<ericP> Problem manifects for Holger and Jack
<ericP> firefox 1.5 windows and galleon
<ericP> ACTION: 2006-05-16: JacekK to write an email trying to separate the different things in issue 6 [DONE] [recorded in http://www.w3.org/2002/ws/sawsdl/minutes/20060523#action02]
<ericP> ACTION: 2006-05-16: Holger to try and describe the use cases for category element [CONTINUED] [recorded in http://www.w3.org/2002/ws/sawsdl/minutes/20060523#action03]
<ericP> logistics page: http://www.w3.org/2002/ws/sawsdl/admin/meetings/200606Galway
<ericP> registration page: http://www.w3.org/2002/09/wbs/39001/200606galway/
<ericP> WSDL WG published last call of WSDL RDF mapping http://www.w3.org/TR/wsdl20-rdf/
<ericP> ACTION: Terry to review last call of WSDL RDF mapping http://www.w3.org/TR/wsdl20-rdf/ by beginning of July [recorded in http://www.w3.org/2002/ws/sawsdl/minutes/20060523#action04]
<ericP> ACTION: EricP to review last call of WSDL RDF mapping http://www.w3.org/TR/wsdl20-rdf/ by beginning of July [recorded in http://www.w3.org/2002/ws/sawsdl/minutes/20060523#action05]
Joel: I don't think we have a good reason for making it an NCName originally
Jacek: proposal is to xs:string
EricP: consensus for xs:string
RESOLUTION: make type of category name an xs:string
Laurent: there may be a need for all the ontologies (versioning)
Rama: in previous calls we talked about not specifying how to use the referenced models
Joel: what if they contradict each other?
EricP: we would need clear rules about what to use
Laurent: my proposal for conflicts is that the user defines a context for the annotation
... each modelReference would be in a different context
... if we don't do that, we would get many modelReferences on different elements, without consistency between them
... proposal is a context unique id
... this id would be local to the wsdl file
<laurenth> the idea is that any annotation to a wsdl file comes in a group, identified at the top of the specification. Then all model references are recalling this identifier. This solves the conflict issue declaratively
Joel: we already have a set of issues related to modelReference and SchemaMapping
... I don't really understand how it relates to those other issues
<JacekK> if annotations relate to others, shouldn't that be expressed in the ontology which contains the things that the annotations point to?
Laurent: the context id would define several annotations layers
joel: example?
Laurent: it could be different languages, different ontologies...
Rama: in WSDL-S there's schemaMapping only for complex types
... I think Laurent's proposal is good
Joel: it would introduce a lot of extra syntax in the WSDL file
... I'd like to see an example
EricP: I'm also interested in use cases
Holger: want to see syntax proposal
... note: we should not refer to wsdl 1.1 but wsdl 2.0
<ericP> ACTION: Laurent to propose specific textual changes for including multiple model references [recorded in http://www.w3.org/2002/ws/sawsdl/minutes/20060523#action06]
EricP: waiting for action completion
Holger: ongoing
<scribe> postponed
Laurent: complex types can't be annotated externally in the current spec
EricP: if I annotate Point X and you annotate Point Y, how do we deal with conflicting annotations?
... easier to annotate Point (as couple of coordinates X, Y)
Laurent: sometimes you have too complex types, like a group of points
... I'd like to be able to annotate where the type is used, not only where it's defined
EricP: like when the point is used, to say "this is the upper left hand corner of a rectangle"
<JacekK> conflicts in the annotations mean the document is invalid
<JacekK> we should note that and not care about how to handle such situation
<ericP> ACTION: Laurent to draft text to address annotations on complex types and "basic types" [recorded in http://www.w3.org/2002/ws/sawsdl/minutes/20060523#action07]
<ericP> ADJOURNED