- From: Jose Kahan <jose.kahan@w3.org>
- Date: Tue, 5 Apr 2005 18:33:42 +0200
- To: www-xkms@w3.org
- Message-ID: <20050405163342.GA12512@rakahanga.inrialpes.fr>
Well, almost ready for the meeting with the director. Check it out at [1]. I need feedback to fix some last remaining points. I'm ready to attack part-2 when it's ready Shivaram. - Is Appendix B Non-Normative? - There is a reference to WSDL ([WSSL]) in the spec, although this reference is not used anywhere. The link that's included in that reference is broken now. If someone has a live link, proposed it. Otherwise, I suggest we update it to point to the WSDL 2.0 core WD (using the generic name for the spec, not the static one for the WD) and that we refer it from p. [352a]: <quote>... by reading a WSDL or metadata file. ....</quote> - Par. [373a] is missing some articles, but I'm unable to fix it without knowing what was it supposed to say originally. - I wonder if we need more text to say what is the meaning of "anyURI". I'm not sure if this is a known term or something we introduced in our schema. - The first header in the table below p.[104] seems a bit long. I think we could move that description to the text in p.104. (just a suggestion). - In the same table under p. 104, there are some starts in some cells of the the 2nd row (e.g. <X509Data>*. Is this a typo ro does it mean something special? Shivaram, You can continue editing your DRAFT document and I'll reflect the changes in the PUB one. Or just mail me your changes and I'll put them directly. I'm sorry for not updating the DRAFT and PUB ones, but it would have increased my workload :( I decided it was best to leave your DRAFT as it is and not commit my edited, but invalid XHTML file with the fixed ins and del. While waiting for part-2, I'll finish updating the issues list and make a final pass to the request for moving to PR and the implementation report. As soon as the edits in part-2 are ready we can send the request. I hope it happens this week or at latest next one :) Changes or things that I already did: - Rewrote the ack. section and added the CR contributors (see my previous message). - Moved the ack. section to Appendix E and put the Changes in Appendix F. This was a suggestion from the comm. team. It's the standard style spec style of both IETF and W3C> - Updated all the section links and numbers in section 1. to reflect the precedent change. - Marked appendix C thru E as Non-Normative in both the ToC and in the Appendixes titles. - Replaced "ex.," by "e.g.," throughout. Replaced "e.g. " by "e.g.," when it was missing (most of the times it was used correctly). - Slightly changed the phrasing in par. [112a], [128a], [132], [205] after checking with a native english speaker. For example, I changed [128a]RespondWith MUST NOT be present in CompoundRequest element. into [128a] The RespondWith element MUST NOT be present innside a CompoundRequest element. - Updated the Status of the Document section. - Deleted everything in the Change log except for the CR-PR section as proposed by Shivaram. - Verified all the links. Updated the link for the Stringprep AS profile to point to the RFC (published last Feb.). - Validated the HTML and went as far as possible thru the pubrules checker. -jose [1] http://www.w3.org/2001/XKMS/Drafts/XKMS-PR-PUB/PR-PUB-xkms-part-1.html#Acknowledgments
Received on Tuesday, 5 April 2005 16:33:46 UTC