This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
2.2.5 Semantics FROM: Within a WS-CDL document, descriptions allow the recording of semantic definitions and other documentation. The OPTIONAL description sub-element is allowed inside any WS-CDL language element. WS-CDL parsers are not required to parse the contents of the description. The information provided by the description sub-element will allow for the recording of semantics in any or all of the following ways: * Text. This will be in plain text or possibly HTML and should be brief * Document Reference. This will contain a URI to a document that more fully describes the component * Machine Oriented Semantic Descriptions. This will contain machine processable definitions in languages such as RDF or OWL Descriptions that are text or document references can be defined in multiple different human readable languages. TO: Within a WS-CDL document, descriptions may reference semantic definitions and other documentation. The OPTIONAL description sub-element is allowed inside any WS-CDL language element. Descriptions MAY be text or document references defined in multiple different human readable languages. Where machine processable, WS-CDL parsers are not required to parse the contents of the description. The information provided by the description sub-element will reference the descriptions in any or all of the following areas: * Text: Plain text, HTML or other non-encoded text formats may apply (e.g. text/plain, text/html, text/sgml, text/xml, etc.). * Document Reference. This MAY contain a URI to a document that more fully describes the component. * Machine Oriented Semantic Descriptions. This MAY contain machine processable definitions in languages such as RDF or OWL. This description MAY contain a URI. The semantics of any element or attribute from the WS-CDL namespace SHOULD remain unchanged. =================================================== This change is based on working towards solidifying two items: a. Define which references MAY be accessible via a URI or other machine processable reference (not only documentation). b. Explicitly define whether or not these descriptions can affect the semantics. If not, explicitly limit or exclude whether these semantic references may change operational semantics or affect the development of a choreography description.
From 8-feb-05 concall: http://lists.w3.org/Archives/Member/member-ws-chor/2005Feb/att-0003/Minutes- 02082005-0.txt EDITORIAL - fix with text in proposal
Changed as suggested (added 'and MUST not be contradicted' at the end in line with the resolution of another issue.
group notification of status change: http://lists.w3.org/Archives/Member/member- ws-chor/2005Jul/0004.html
no comments from group so closed confirmed: http://lists.w3.org/Archives/Member/member-ws-chor/2005Jul/0004.html