RE: Comments on Primer Sections 4 - 6.5

Hi Paul,

I don't have access to an xml editor that does validation right at this
moment, but the errors below look like simple. 

> wsdl20-primer.xml:1397: element gitem: validity error : 
> Element gitem content does not follow the DTD, expecting 
> (label , def), got (label def p example )
>                 </gitem>

Can you please  move the ending </def> tag to the end of the example,
right before the </gitem> tag?

> wsdl20-primer.xml:2364: element item: validity error : 
> Element item content does not follow the DTD, expecting (p | 
> ulist | olist | slist | glist | orglist | blist | note | 
> issue | wfcnote | vcnote | constraintnote | eg | graphic | 
> scrap | table | definitions | proto | example | ednote)+, got (CDATA)
>  </item>

Not sure which section causes this complaint. The CDATA section should
be enclosed inside <example>...<eg></eg></example>. Not sure how it can
got inserted directly under <item>. Can you please check and make sure
there is <eg> around the section?

Best Regards,
Kevin
  

> -----Original Message-----
> From: paul.downey@bt.com [mailto:paul.downey@bt.com] 
> Sent: Monday, Jun 20, 2005 1:32 PM
> To: ryman@ca.ibm.com; Liu, Kevin
> Cc: w3c-ws-desc@w3.org; w3c-ws-desc-request@w3.org
> Subject: RE: Comments on Primer Sections 4 - 6.5
> 
> i wanted to checkin DaveO's examples, but when I finally managed to
> find ssh internet access and checked out the whole 2002/ws/desc tree
> on Sunday afternoon (UK), the primer in CVS fails to make:
> 
> """
> $ make primer
> make -f Makefile.primer
> Validating wsdl20-primer.xml
> wsdl20-primer.xml:1397: element gitem: validity error : 
> Element gitem content does not follow the DTD, expecting 
> (label , def), got (label def p example )
>                 </gitem>
>                         ^
> wsdl20-primer.xml:2364: element item: validity error : 
> Element item content does not follow the DTD, expecting (p | 
> ulist | olist | slist | glist | orglist | blist | note | 
> issue | wfcnote | vcnote | constraintnote | eg | graphic | 
> scrap | table | definitions | proto | example | ednote)+, got (CDATA)
>  </item>
> 
> etc
> """
> 
>  <!ENTITY document.status "Editors' copy $Date: 2005/06/17 
> 23:32:32 $">
> 
> any ideas?
> 
> Paul
> 
> 
> -----Original Message-----
> From:	w3c-ws-desc-request@w3.org on behalf of Arthur Ryman
> Sent:	Mon 6/20/2005 3:18 PM
> To:	Liu, Kevin
> Cc:	w3c-ws-desc@w3.org; w3c-ws-desc-request@w3.org
> Subject:	RE: Comments on Primer Sections 4 - 6.5
> 
> Kevin,
> 
> Looks fine.
> 
> Arthur Ryman,
> Rational Desktop Tools Development
> 
> phone: +1-905-413-3077, TL 969-3077
> assistant: +1-905-413-2411, TL 969-2411
> fax: +1-905-413-4920, TL 969-4920
> mobile: +1-416-939-5063, text: 4169395063@fido.ca
> intranet: http://labweb.torolab.ibm.com/DRY6/
> 
> 
> 
> "Liu, Kevin" <kevin.liu@sap.com> 
> Sent by: w3c-ws-desc-request@w3.org
> 06/16/2005 06:50 PM
> 
> To
> Arthur Ryman/Toronto/IBM@IBMCA, <w3c-ws-desc@w3.org>
> cc
> 
> Subject
> RE: Comments on Primer Sections 4 - 6.5
> 
> 
> 
> 
> 
> 
> Hi Arthur,
>  
> >7. Section 5.4.1 Update this section to reflect the change to the 
> {safety} property 
> 
> [Kevin] I looked at your edits for this particular item while 
> investigating how to reflect part 1 changes to  @safe in the primer. 
> Instead of simply removing the attribute from this section, I 
> would agree 
> with DaveO that we still need to explain how the @wsdlx:safe 
> extension 
> maybe used here. so I added back some text here. 
>  
> Have a look at the text and let me know if you have concerns.
> Best Regards,
> Kevin
>   
>  
> 
> From: w3c-ws-desc-request@w3.org 
> [mailto:w3c-ws-desc-request@w3.org] On 
> Behalf Of Arthur Ryman
> Sent: Wednesday, Jun 15, 2005 6:42 PM
> To: w3c-ws-desc@w3.org
> Subject: Fw: Comments on Primer Sections 4 - 6.5
> 
> 
> DONE. 
> 
> Kevin, 
> 
> I tagged the primer as 
> 
> before-removing-transitive-2005-06-15 
> 
> before the changes and as 
> 
> after-removing-transitive-2005-06-15 
> 
> after so you can revert the document if you don't like my edits. 
> 
> Arthur Ryman,
> Rational Desktop Tools Development
> 
> phone: +1-905-413-3077, TL 969-3077
> assistant: +1-905-413-2411, TL 969-2411
> fax: +1-905-413-4920, TL 969-4920
> mobile: +1-416-939-5063, text: 4169395063@fido.ca
> intranet: http://labweb.torolab.ibm.com/DRY6/ 
> ----- Forwarded by Arthur Ryman/Toronto/IBM on 06/15/2005 
> 09:31 PM ----- 
> Arthur Ryman/Toronto/IBM 
> 06/15/2005 05:09 PM 
> 
> 
> To
> "Liu, Kevin" <kevin.liu@sap.com> 
> cc
> 
> Subject
> RE: Comments on Primer Sections 4 - 6.5Link
> 
> 
> 
> 
> 
> 
> 
> Kevin, 
> 
> Will do. 
> 
> Arthur Ryman,
> Rational Desktop Tools Development
> 
> phone: +1-905-413-3077, TL 969-3077
> assistant: +1-905-413-2411, TL 969-2411
> fax: +1-905-413-4920, TL 969-4920
> mobile: +1-416-939-5063, text: 4169395063@fido.ca
> intranet: http://labweb.torolab.ibm.com/DRY6/ 
> 
> 
> "Liu, Kevin" <kevin.liu@sap.com> 
> Sent by: www-ws-desc-request@w3.org 
> 06/15/2005 01:49 PM 
> 
> 
> To
> Arthur Ryman/Toronto/IBM@IBMCA, <www-ws-desc@w3.org> 
> cc
> 
> Subject
> RE: Comments on Primer Sections 4 - 6.5
> 
> 
> 
> 
> 
> 
> 
> 
> Hi Arthur, 
>   
> My comments below.  For those items we agree, please make the edits. 
> Best Regards,
> Kevin
>  
> 
> 
> From: www-ws-desc-request@w3.org 
> [mailto:www-ws-desc-request@w3.org] On 
> Behalf Of Arthur Ryman
> Sent: Monday, Jun 13, 2005 12:35 PM
> To: www-ws-desc@w3.org
> Subject: Comments on Primer Sections 4 - 6.5
> 
> 
> 1. Section 4. The text: 
> 
> A WSDL description must NOT refer to XML Schema components that are 
> neither imported nor embedded into that WSDL description. In 
> other words, 
> the use of xs:import and/or xs:schema is a necessary 
> condition for making 
> XML Schema components available to a WSDL Description component. 
> 
> should be stated positively, e.g. 
> 
> A WSDL description must use either xs:import or xs:schema to 
> define XML 
> Schema components that are refered to by WSDL components. 
> 
> 
> [Kevin] I am OK either way. 
>  
> 2. Section 4.2 The text: 
> 
> The xs:import mechanism is not transitive. Only components 
> defined in the 
> imported schema itself and components the schema includes via 
> xs:include 
> are available to the containing WSDL document. Specifically, 
> components 
> that the schema imports via xs:import are NOT available to WSDL. 
> 
> should be rewritten to avoid the use of the term "transitive". e.g. 
> 
> A WSDL document must define XML Schema components (within the types 
> element using either xs:import or xs:schema) that are refered 
> to by WSDL 
> components. The XML Schema components defined within xs:schema may be 
> defined using xs:include. In constrast, within xs:schema an 
> xs:import does 
> not define any components, but only declares a namespace. 
> 
> [Kevin] I personally think the current text is easier to 
> understand. why 
> we have to avoid the term "tranisitive"? I think the last two 
> sentences in 
> the paragraph qualifies what we mean by "transitive" pretty well. 
>  
>  
> 3. Section 4.3, Table 4-1 
> 
> The transitive column should be eliminated. The Meaning 
> column should be 
> rewriten to avoid the notion of merging. It should use the notion of 
> declaring namespaces and defining components. 
> 
> [Kevin] if you can come up with better text, I am OK with the change 
>  
> The last row should be labelled xs:include. 
> [Kevin] good catch. it should  be changed 
>  
> 4. Section 5.1 The code example has bad alignment: 
> 
>      <input messageLabel="xs:NCName"? 
>                                         element="union of xs:QName, 
> xs:Token"? >
>     </input>*
> 
>     <output messageLabel="xs:NCName"? 
>                                         element="union of xs:QName, 
> xs:Token"? >
>     </output>*
> 
> [Kevin] oops. should be fixed 
>  
> 5 Section 5.2. The following text is wrong: 
> 
> Finally, since faults, features and properties can also be defined as 
> children of the interface element (as described in the following 
> sections), the same name-collision rules apply to those constructs. 
> 
> The name collision rule only applies to faults. For features and 
> properties, you can special those you inherit via the 
> composition rules. 
> 
> [Kevin] please remove f&P from the list of constructs 
>  
> 6 Section 5.3. This text is wrong: 
> 
> The fault element has a required name attribute that must be 
> unique within 
> the WSDL document's target namespace, and permits it to be 
> referenced from 
> operation declarations. 
> 
> The name attribute is only required to be unique within the 
> Interface. It 
> is like <operation>. 
> 
> [Kevin] hmm, I remember having an ed note in this section asking for 
> clarification on the scope of  fault uniqueness since the 
> text in part 1 
> makes it sounds it has to be unique within the ns. So part 1 
> is clarified? 
> if so, I agree we should fix it here too. 
>   
> 7. Section 5.4.1 Update this section to reflect the change to 
> the {safety} 
> property 
> 
> [Kevin] yeap 
>  
> 8. Section 5.4.2 Update this text to describe #other 
> 
> The element attribute is also optional. If it is not 
> specified, then @@@@. 
> 
> 
> Should be: 
> 
> The element attribute is also optional. If it is not specified, then 
> #other. 
> 
> [Kevin] yeap 
>  
> 9. Section 6.1. Shouldn't this lisitng include <infault> and 
> <outfault>? 
> 
>    <operation ref="xs:QName" >
>     <input messageLabel="xs:NCName"? > </input>*
>     <output messageLabel="xs:NCName"? > </output>*
>   </operation>*
> 
> [Kevin] yes. 
> 
> Arthur Ryman,
> Rational Desktop Tools Development
> 
> phone: +1-905-413-3077, TL 969-3077
> assistant: +1-905-413-2411, TL 969-2411
> fax: +1-905-413-4920, TL 969-4920
> mobile: +1-416-939-5063, text: 4169395063@fido.ca
> intranet: http://labweb.torolab.ibm.com/DRY6/ 
> 
> 
> 
>

Received on Tuesday, 21 June 2005 01:36:50 UTC