- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Fri, 17 Sep 2004 17:51:00 -0700
- To: <www-ws-desc@w3.org>
Tuesday
Media Type Description Note (new issues)
RESOLUTION: Consensus not to reopen 252 based on Umit's mail.
RESOLUTION: Consensus to remove sentence "the annotation should be
considered only as a hint."
RESOLUTION: Consensus on adding "When expectedMediaType is used and
has
a wild card or list, you SHOULD write your message schema
to
require a contentType."
Primer
RESOLUTION: DBooth to change "WSD" to "WSDL Document" throughout.
RESOLUTION: Accepted the proposal from DBooth to have more specific
References for the concepts you need to know.
RESOLUTION: Diagram revised to add "client" and "web service"
in parentheses.
RESOLUTION: Change "Web" to "Network" in diagram 2-1.
Various other suggestions to the authors to make the primer more
accessible to the intended audience (e.g. be more example-based.)
Media Type Description
RESOLUTION: Add two complex types to our XML MIME schema, one derived
from base64 and one from hexbinary.
Last Call Issues
Issue LC5d:
RESOLVED: Accept DBooth's proposed change in
http://lists.w3.org/Archives/Public/www-ws-desc/2004Sep/0008.html
ACTION: Editors to implement resolution to LC5d at
http://lists.w3.org/Archives/Public/www-ws-desc/2004Sep/0008.html
Issue LC5g:
RESOLVED: Accept the reviewer's proposal: "a conformant WSDL
processor MUST immediately cease processing (fault) if
it doesn't agree to fully abide ...."
ACTION: Editors to implement resolution for LC5g as proposed.
Issue LC5h:
RESOLUTION: reclassify as Editorial.
Issue LC5i:
RESOLVED: Delete the note from the conformance section (as
redundant),
and promote the material on optional extensions into its
own
section, and add "See section ___ for further
explanantion".
ACTION: Editors to implement resolution to LC5i.
Issue LC5j:
RESOLVED: Close LC5j as resolved by LC5i.
Issue LC5k:
RESOLVED: Delete the text, because it is only advice to implementers.
ACTION: Editors to implement resolution to LC5k.
ACTION: Arthur to submit proposal on conformance requirements for
XML serialization (of WSDL and schema documents)
Issue LC5l:
RESOLVED: Leave the Note, but change "processors" to "conformant
processors" (and link to the conformance section), and
explain this to the reviewer.
RESOLVED: Make the Note in 6.3 normative, and rephrase as
"Extensibility
elements SHOULD NOT alter the existing semantics in ways
that
are likely to confuse users."
ACTION: Editors to implement resolution to LC5l.
Issue LC6a:
RESOLVED: Change {name} in F&P to {uri}.
ACTION: Editors to implement resolution to LC6a.
Issue LC6b:
RESOLVED: Reject the reviewer's suggestion, explaining that an
element
Supports schema validation by allowing a co-constraint
between
'value' and 'constraint'.
Issue LC6c:
RESOLVED: Reject the reviewer's suggestion, and explain that we were
following XML Schema's convention and that it further
clarifies that it is the location of a WSDL document.
Issue LC6d:
ACTION: JMarsh to take issue LC6d to XML Core WG
RESOLVED: We should accept the reviewers point about making explicit
that we're defining a new scheme.
ACTION: Editors to make explicit that we're defining new XPointer
fragment schemes.
[Issue remains open.]
Issues LC7, LC10, LC12, LC15
ACTION: Editors to implement LC7, LC10, LC12, LC15 unless they find
problems that require additional group attention.
Wednesday:
Last Call Issues
Issue LC8:
ACTION: Editors update spec to clarify our using of anyURI is
actually
URI reference except targetNS
RESOLUTION: LC8 closed by allowing # everywhere but targetNamespace.
Issue LC9:
ACTION: Glen to respond to Tim saying yes to his first question,
and pointing out sections 6.
ACTION: Editors to clarify spec about operation name mapping
requirements by moving paragraph preceeding section 2.2.1.1
and whole 2.2.1.1 to service section, and clear up the text.
RESOLUTION: LC9 closed with above clarification.
Zed notation:
ACTION: Arthur to (re)write a subsection of the spec to show exactly
how
it looks with the Zed notation included before next telecon.
ACTION: Hugo to investigate potential options for get the Zed version
published in W3C web site.
Last Call Issues:
Issue LC29a:
RESOLUTION: Add a rationale to the spec explaining there is no good
default value for code and subcode.
ACTION: Editors to add rationale to spec to explain why no default
for
binding fault is defined (no good default codes)
Media Type Description re-review
ACTION: Media type editors to change the syntax to follow the http
spec,
drop the pattern facet from the schema, and say that the
format
of the string which follows the appropriate production in the
HTTP RFC (except for not supporting extensions).
ACTION: Tom and Anish to figure out the right words for a more
meaningful overview/introduction to the problem we're trying
to
solve.
ACTION: Media Type editor to remove last sentence of 2nd bullet,
combine
with previous occurrence (remove redundancy).
ACTION: Media Type editor to make requirements an OLIST.
ACTION: Media Type editor to clarify binary EII term, a la "a binary
EII
is an EII defined as follows"
ACTION: Media Type editor to have at least one example which uses the
Full syntax instead of the convenience types.
ACTION: Media Type editor to remove colon from 2nd para of 3.1.
Anish appointed as editor from WSDesc WG.
Last Call Issues
Issue 29c:
RESOLUTION: We will resolve this issue as before (no default for
WSDL
faults).
ACTION: Editors to implement a fix for LC29c similar to the fix
for LC29a.
Issue 29e:
RESOLUTION: It is an error for instance documents to have elements
with
xsi:nil=true.
ACTION: Editors to add as 1st bullet of 3.8.1.1 that it is an error
for
instance documents to have elements with xsi:nil=true.
RESOULTION: It is an error to have nil values when trying to
auto-generate parameters.
ACTION: Editors to change first bullet of section 3.8.1.1. to say
"Uncited non-nil elements with a possibly empty single value
are serialized ..."
Issue 29f:
RESOLUTION: close 29f with the same resolution as 29e (add bullet
to 3.8.3)
ACTION: Jonathan to ask XForms folks to review WSDL.
Issue 29g:
Issue split (see 29h) Reclassified as editorial.
ACTION: Jonathan to split 29g to two issues: first one to be
tagged editorial, 2nd (29h) to be closed as no need to do it.
Issue 29h:
RESOLUTION: 29h closed - no need.
Issues 29g, 32, 34a, 35, 36, 39 and 40:
ACTION: Editors to implement editorial issues 29g, 32, 34a, 35, 36,
39 and 40 or come back to the WG with questions.
Thursday
RDF Mapping questions
RESOLUTION: Move App C to RDF Mapping spec, except the frag-id which
will
move within media-type reg appendix.
ACTION: Editors to move App C to RDF Mapping spec, except the frag-id
which will move within media-type reg appendix.
RESOLUTION: Camel case is OK for RDF mapping constructed URIs.
ACTION: Editors to fix paragraph 6-9 of section 2.1.1 moved into 2.1.2
which talks about the syntax.
ACTION: Arthur to write up his proposal to rename 'defintions' to
'description'.
Administrative
ACTION: Glen to contact Bob Cunnings regarding planning for CR
bake-offs.
Last Call Issues
Issue LC34a
RESOLUTION: Add links to sections of specification where we note that
QName is insufficient to identify a component.
ACTION: Editors to add links to component designators to sections
Where we note QName is insufficient.
Issue LC34b
RESOLUTION: Close issue 34b - accept proposal in general, include F&P
additions too
ACTION: Arthur will scrub the proposed syntax and create Features and
properties syntax.
ACTION: Editors to implement the restriction that feature and
property
URIs must be unique in a scope.
Issue LC34c
RESOLUTION: Issue 34c Accept the proposal - change names to match
component names in table C-1.
ACTION: Arthur to revamp table C-1 with component names
Issue LC34d
RESOLUTION: Table will be reworked to be more readable when new
components are added.
ACTION: App C editors to rework table to be more readable when new
components are added.
Issue LC33
RESOLUTION: close issue 33 - Remove default from text in bullet item
"HTTP Method Selection"
ACTION: Editors to remove 'default' from text in bullet item "HTTP
Method
Selection"
Issue LC37
RESOLUTION: Accommodate the method default and input serialization
default in part 3, section 3.6.4
ACTION: Editors to redo Part 3 Section 3.6.4 to accommodate method
and input serialization defaults.
Issue LC38
RESOLUTION: close issue 38 - Assign a new namespace URI.
ACTION: Hugo to get a URI to use for DTD example in Appendix E.1
Issue LC12
RESOLUTION: close issue 12 - Add whttp:location to section 2.1, the
binding operation element (same place as
whttp:defaultTransferCoding)
ACTION: Editors to add whttp:location to section 2.1, the binding
operation element (same place as whttp:defaultTransferCoding)
Issue LC13
RESOLUTION: close issue 13 - change use of HTTP Operation Component
ACTION: Editors to change use of HTTP Operation Component to
something
like Binding Operation Component augmented by HTTP
properties.
Issue LC14
RESOLUTION: close issue 14 - Fix the mapping to say the value is the
component.
ACTION: editors fix the places described in issue 14 to say the
value is the component.
Issue LC16
RESOLUTION: close issue 16 - accept the proposal to remove the
sentence: "Thus, an interface defines the design of
the application."
ACTION: editors to remove the sentence "Thus, an interface defines
the design of the application" in section 2.2.1
Issue LC17
ACTION: Jonathan to record proposed resolution in the issues list.
Issue LC18
ACTION: Glen to CC Asir on mail to Marc re: SOAP modules and features
Received on Saturday, 18 September 2004 00:51:31 UTC