Just an oversight...Needs to be
wsdm-muws-1.1-spec-cd-02.
Thanks,
Vaughn
From: Wilson, Kirk D
[mailto:]
Sent: Thursday, March 09, 2006 10:15
AM
To: Heather Kreger
Cc:
Subject: RE: [wsdm] WSDM MUWS 1.1 Part 2,
Final review and vote for CD
I find the “cd-02”
misleading, then. I thought that was supposed to be the Revision number
related to the stage of development of the doc. Based on the way I read
the Artifact Identification spec. WSDM-MUWS-1.1…-cd-02 would supersede
WSDM-MUWS-1.1…cd-01 by being a later version of the latter
document.
Changes to the schema
can be directly in the text of Appendix A, since it is just a matter of
deleting a set of lines (lines 1814-1823 in A.hk to be
precise).
Kirk
Wilson
Architect,
Development
Office of the
CTO
603
823-7146
-----Original
Message-----
From: Heather
Kreger [mailto:]
Sent: Thursday, March 09, 2006 10:04
AM
To: Wilson,
Kirk D
Cc:
Subject: RE: [wsdm] WSDM MUWS 1.1 Part 2,
Final review and vote for CD
cd-02 indicates its Committee
Draft of Part 2, the *A.,doc document is Vaughns edits.
In the A.hk.doc I addressed
the issues in my note (additional changes) and left it as markup so everyone
could see and we can review what I've done. I implemented Tom's
SequenceNumber and made some changes to how Vaughn addressed some of your
comments on the WS-Addressing reference parameters and the relationship
events.
Whew! We should review
and approve the A.hk.doc document today.
Do you need to update the
schema appendix in MUWS Part 1 or 2 to fix the copy/paste error?
Heather Kreger
STSM,
Web Services Lead Architect for SWG Emerging Technologies
Author of "Java
and JMX: Building Manageable Systems"
919-543-3211
(t/l 441) cell:919-496-9572
"Wilson,
Kirk D" <>
03/09/2006 07:04
AM
To
Heather
Kreger/Raleigh/IBM@IBMUS,
<>
cc
Subject
RE: [wsdm] WSDM
MUWS 1.1 Part 2, Final review and vote for
CD
I must say I’m
thoroughly confused by what version of what MUWS Part I need to review.
What is the relationship between the file ending in “A.hk” and the one
uploaded ending just in “A”? Are they the same? The situation is
not helped by the fact that the file names don’t designate the MUWS part (or
is that what the “cd-02” is meant to do?
Kirk
Wilson
Architect,
Development
Office of the
CTO
603
823-7146
-----Original
Message-----
From: Heather
Kreger [mailto:]
Sent: Thursday, March 09, 2006 12:38
AM
To:
Subject: [wsdm] WSDM MUWS 1.1 Part 2,
Final review and vote for CD
Hi,
Its taken a
little longer than expected to finish up the CD candidate for MUWS 1.1. Part 2
due to technical difficulties. I believe this draft to include all
agreed on changes and responses to Kirks comments on the previous draft.
Here's our agenda for
todays call:
1. Roll
2. Review naming
conventions for documents
3. MUWS 1.1 Part 2
changes review
4. Vote MUWS 1.1 to
Committee Draft
CELEBRATE!
Changes made in this
draft of MUWS 1.1:
Changes approved from
last call:
1.
replace section 2.5.1.2 470-519 with those
in Tom Studwells posting 470-519 for Correlation Properties with fixes in
schema.
2.
Rename to CorrellationProperties to
EventCorrellationProperties
3.
Font size 508-520
4. Deleting diagram
at 623
5.
Fix notification references
6. 1404 – add
statement ‘For releationships as a stand alone resource, Self should not be
specified.’ (Heather)
7.
2002 make Sequence an attribute
(Heather)
8.
Remove *PropertiesType declarations (Kirk to
change)
9.
Add CopySection with element declarations in WSDL (Kirk to
change)
10.
GED for Self element (Kirk to change)
Other changes made based
on Kirks editorial commentts:
1. Rewrote 136-142 to align with current
WS-RF and WS-A (I readded a paragraph I think was mistakenly
deleted)
2. Reformatted 2.5.1.4
Message Catalog section
3. 4.1.3 removed
ref to 'manageaable relationships' and put description of topics back in, I
think I've fixed Kirk's origional concern about the topic name.
4 minor space and
'.' removal throughout.
The XML schema and WSL
were correct and did not need to be updated or reverified.
Heather Kreger
STSM,
Web Services Lead Architect for SWG Emerging Technologies
Author of "Java
and JMX: Building Manageable Systems"
919-543-3211
(t/l 441) cell:919-496-9572
