Fw: [Bug 10339] New: All: check for old references

FYI - Only reason I opened an issue instead of just doing it is because 
this falls into a category that's bigger than a "typo" - so a bit more 
formal tracking seemed appropriate.
Is there any objection to us accepting this issue, and proposal, thru 
email? 


Refs to be removed:

WS-Transfer:
- RFC 3986
- WS-SecureConversation
- WS-Security
- WS-SecurityPolicy

WS-MEX:
- RFC 3986
- WS-SecureConversation
- WS-Security
- WS-SecurityPolicy
- WS-Trust

WS-Eventing:
- RFC 3986
- WS-SecureConversation
- WS-Security
- WS-SecurityPolicy
- WS-Trust

WS-EVD:
- all ok

WS-Enum:
- RFC 3986
- WS-SecureConversation
- WS-Security
- WS-SecurityPolicy

WS-Fragment:
- RFC 3986

WS-SoapAssertions:
- all ok

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.
----- Forwarded by Doug Davis/Raleigh/IBM on 08/10/2010 07:51 AM -----

bugzilla@jessica.w3.org 
Sent by: public-ws-resource-access-notifications-request@w3.org
08/10/2010 07:50 AM

To
public-ws-resource-access-notifications@w3.org
cc

Subject
[Bug 10339] New: All: check for old references






http://www.w3.org/Bugs/Public/show_bug.cgi?id=10339

           Summary: All: check for old references
           Product: WS-Resource Access
           Version: PR
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: All
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: dug@us.ibm.com
         QAContact: public-ws-resource-access-notifications@w3.org


Some specs have references that are never used in the body of the spec.
See:
http://lists.w3.org/Archives/Public/public-ws-resource-access-comments/2010Aug/0004.html


Proposal: remove them from the references sections

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.