Re: [ws-caf] next set of issues

From
Mark Little <>
Date
2004-01-20T17:23:10+00:00
ID
000a01c3df7b$39a14e70$f501080a@ebchester
Thread
Re: [ws-caf] next set of issues
Given what was decided yesterday, it seems like 
issue 16 should be closed as it is covered by issue 45.

 

Mark.

  
----- Original Message ----- 

  
From: 
  Mark 
  Little 

  
To:  
  

  
Sent: Tuesday, January 20, 2004 4:02 
  PM

  
Subject: [ws-caf] next set of 
issues

  

  
Concentrating on general and WS-Context issues 
  for now, I want to propose we try to tidy up the following 
issues:

  
 

  
    
    

      12 
      
      nor 
      P2 
      All 
       
      
      NEW 
      
      clarify reply-to address in schema (and possibly the text) 

    

      13 
      
      maj 
      P2 
      All 
       
      
      NEW 
      
      UserActivityServicePortType the "completionStatus" operat... 

    

      14 
      
      nor 
      P2 
      All 
       
      NEW 
      
      StatusType is a restriction but is extended in WS-TXM. Is... 

    

      15 
      
      cri 
      P2 
      All 
       
      NEW 
      
      CompleteWithStatus has the wrong type 

    

      16 
      
      nor 
      P2 
      All 
       
      NEW 
      
      None of the WS-CAF schemas are WSI BP compliant. 

    

      17 
      
      nor 
      P2 
      All 
       
      NEW 
      
      wsc4c is referenced in parts of WS-CF schema. Is it elsew... 

    

      18 
      
      maj 
      P2 
      All 
       
      NEW 
      
      Incorrect WSDL import statement. 

    

      19 
      
      cri 
      P2 
      All 
       
      NEW 
      
      No "part" attribute. 

    

      20 
      
      nor 
      P2 
      All 
       
      NEW 
      
      Missing portType operations 

  
 

  
In line with something Alastair (I think) 
  mentioned yesterday about possible sharing implications of context, this came 
  up at the face-to-face and is

  
 

  

  
    
    

      46 
      
      nor 
      P2 
      All 
       
      NEW 
      
      Context sharing 

  
 

  
So maybe we want to discuss it too, though I 
  suspect it won't be resolved quickly.

  
 

  
Mark.