Minutes of Encoding Task Force, 28 January 2002.

Present

• Asir Vedamuthu
• Henrik Frystyk Nielsen (scribe)
• Marc Hadley

1. Outstanding action items:
   • HFN will propose changes to spec and primer to resolve ed issue #17
   • HFN to propose resolution for ed issue #55, will contact PaulC and JohnI to determine history of this action
   • DF to ping RDF/UML re issue #29
   • HFN to summarize the two options for solving 177, ETF prefers removing the distinction; for WG's consideration, CC it to DavidF so he can add it to the agenda
   • Asir: talk to DavidF to ask him what the status is.
   • Asir: write a note for the SOAP encoding section pointing out that a result of using anonymous types is that one can't refer to them from the SOAP encoding and send to dist-app
2. Discussion on when the next telcon should be

   Monday Mon Feb 4 2002, 8.30-9.30 PT
   Chair: Marc Hadley
   	

3. Discussion
   • Issue 167

     There are two questions:
     
     The first question is when to use itemtype but the rewrite of arracy
     encoding has changed that from MUST to MAY so the issue has gone away
     
     The other question is regarding the fact that one can't use anonymous
     types.
     
     ACTION: Asir: write a note for the SOAP encoding section pointing out
     that a result of using anonymous types is that one can't refer to them
     from the SOAP encoding and send to dist-app
     	    

   • Issue 163

     DavidF has an action item on this
     
     ACTION: Asir: talk to DavidF to ask him what the status is.
     
     Schema vs. Encoding:
     
     ACTION: Henrik: write a clarifying text of why we use the schemas as
     examples and then send that to the ETF and Gudge for first input.
     	    

4. Closed Issues

   Subsumed by Asir's item - DF contact Schema experts re issue #163 
   
   Done - JK contact Asir about i167 - whether it still stands and what it
   actually means 
   
   Done - MH write a response to Gudge's email; propose to remove Schema
   from Encoding examples, add C-style code; in connection with issue 17 
   
   ??? JK to write the proposal for 168 that if a receiver cannot get the
   type, it MAY fault with the subcode enc:UntypedValue 
   
   Done - HFN to change the "object" to "node" in data model text