- From: Jonathan Marsh <jonathanMarsh@dev.w3.org>
- Date: Mon, 02 Aug 2004 14:52:51 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/issues
In directory hutz:/tmp/cvs-serv30312/issues
Modified Files:
wsd-issues-condensed.html
Log Message:
8/2 FTF update
Index: wsd-issues-condensed.html
===================================================================
RCS file: /sources/public/2002/ws/desc/issues/wsd-issues-condensed.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** wsd-issues-condensed.html 1 Aug 2004 16:47:11 -0000 1.10
--- wsd-issues-condensed.html 2 Aug 2004 14:52:49 -0000 1.11
***************
*** 42,82 ****
</tr>
<tr>
! <td><a href="#x161">161</a></td><td>Active</td><td>Media type description</td><td></td><td>Design</td><td></td><td>Should media-type values allow wild cards</td>
! </tr>
! <tr>
! <td><a href="#x162">162</a></td><td>Active</td><td>Media type description</td><td></td><td>Design</td><td></td><td>Allowing other choices for mediaType values</td>
! </tr>
! <tr>
! <td><a href="#x198">198</a></td><td>Active</td><td>Media type description</td><td></td><td>Design</td><td></td><td>mismatch between value of media type attribute and pattern</td>
! </tr>
! <tr>
! <td><a href="#x199">199</a></td><td>Active</td><td>Media type description</td><td></td><td>Design</td><td></td><td>mismatch between the media type attribute and the actual data</td>
! </tr>
! <tr>
! <td><a href="#x200">200</a></td><td>Active</td><td>Media type description</td><td></td><td>Design</td><td></td><td>Where should appInfo go?</td>
! </tr>
! <tr>
! <td><a href="#x201">201</a></td><td>Active</td><td>Media type description</td><td></td><td>Design</td><td></td><td>Name of mediaType</td>
! </tr>
! <tr>
! <td><a href="#x202">202</a></td><td>Active</td><td>Media type description</td><td></td><td>Editorial</td><td></td><td>More examples</td>
! </tr>
! <tr>
! <td><a href="#x203">203</a></td><td>Active</td><td>Media type description</td><td></td><td>Design</td><td></td><td>Limited to base64encoded?</td>
! </tr>
! <tr>
! <td><a href="#x204">204</a></td><td>Active</td><td>Media type description</td><td></td><td>Design</td><td></td><td>Why default to */* instead of to "no effect"?</td>
! </tr>
! <tr>
! <td><a href="#x205">205</a></td><td>Active</td><td>Media type description</td><td></td><td>Design</td><td></td><td>Explain priority</td>
! </tr>
! <tr>
! <td><a href="#x206">206</a></td><td>Active</td><td>Media type description</td><td></td><td>Design</td><td></td><td>Annotations and schema component model.</td>
! </tr>
! <tr>
! <td><a href="#x242">242</a></td><td>Active</td><td>Media type description</td><td></td><td>Design</td><td></td><td>Binding accepts header and output serialization </td>
! </tr>
! <tr>
! <td><a href="#x245">245</a></td><td>Active</td><td>Media Type Description</td><td></td><td>Design</td><td></td><td>Define expectedMediaTypeItem to be RFC 2616 Accepts header</td>
</tr>
<tr>
--- 42,46 ----
</tr>
<tr>
! <td><a href="#x252">252</a></td><td>Active</td><td>Media type description</td><td></td><td>Design</td><td></td><td>Syntax of media type annotation</td>
</tr>
<tr>
***************
*** 237,286 ****
<tbody class="Active">
<tr>
- <td valign="top" rowspan="5"><b><a name="x161">161</a></b></td><td>Media type description</td><td></td><td></td><td>Design</td><td>Active</td><td>Media Type TF</td><td></td>
- </tr>
- <tr>
- <td colspan="7"><b>Title:</b> Should media-type values allow wild cards</td>
- </tr>
- <tr>
- <td colspan="7"><b>Description:</b>
- <p>HTTP/MIME allow wildcards for declaring accepted media-types. Should this specification also allow wildcards for acceptedMediaTypes and/or mediaType attribute values, such as "image/*"?. There is already an issue recorded for this problem by XMLP as stated in XMLP Issue 443.</p>
-
- [<a href="http://www.w3.org/Search/Mail/Public/search?type-index=www-ws-desc&index-type=t&keywords=%22Issue+161%22&search=Search">Search</a> or
- <a href="http://www.google.com/search?num=50&hl=en&ie=UTF-8&as_qdr=all&q=%2Bwww-ws-desc+%2B%22issue+161%22+site%3Alists.w3.org&btnG=Search">Google</a> WG archive for relevant posts.]
-
- </td>
- </tr>
- <tr>
- <td colspan="7"><b>Proposal:</b> </td>
- </tr>
- <tr>
- <td colspan="7"><b>Resolution:</b> </td>
- </tr>
- </tbody>
- <tbody class="Active">
- <tr>
- <td valign="top" rowspan="5"><b><a name="x162">162</a></b></td><td>Media type description</td><td></td><td></td><td>Design</td><td>Active</td><td>Media Type TF</td><td></td>
- </tr>
- <tr>
- <td colspan="7"><b>Title:</b> Allowing other choices for mediaType values</td>
- </tr>
- <tr>
- <td colspan="7"><b>Description:</b>
- <p>Should other choices be allowed to represent media-type values? Even if allowed, should this specification utilize them?</p>
-
- [<a href="http://www.w3.org/Search/Mail/Public/search?type-index=www-ws-desc&index-type=t&keywords=%22Issue+162%22&search=Search">Search</a> or
- <a href="http://www.google.com/search?num=50&hl=en&ie=UTF-8&as_qdr=all&q=%2Bwww-ws-desc+%2B%22issue+162%22+site%3Alists.w3.org&btnG=Search">Google</a> WG archive for relevant posts.]
-
- </td>
- </tr>
- <tr>
- <td colspan="7"><b>Proposal:</b> </td>
- </tr>
- <tr>
- <td colspan="7"><b>Resolution:</b> </td>
- </tr>
- </tbody>
- <tbody class="Active">
- <tr>
<td valign="top" rowspan="5"><b><a name="x178">178</a></b></td><td>Test suite</td><td></td><td>SOAP/HTTP</td><td>Design</td><td>Active</td><td>TAG</td><td></td>
</tr>
--- 201,204 ----
***************
*** 306,545 ****
<tbody class="Active">
<tr>
- <td valign="top" rowspan="5"><b><a name="x198">198</a></b></td><td>Media type description</td><td></td><td></td><td>Design</td><td>Active</td><td>WG</td><td></td>
- </tr>
- <tr>
- <td colspan="7"><b>Title:</b> mismatch between value of media type attribute and pattern</td>
- </tr>
- <tr>
- <td colspan="7"><b>Description:</b>
- <p>[19 May FTF] Mismatch between value of media type attribute and pattern -- says nothing about the data.</p>
-
- [<a href="http://www.w3.org/Search/Mail/Public/search?type-index=www-ws-desc&index-type=t&keywords=%22Issue+198%22&search=Search">Search</a> or
- <a href="http://www.google.com/search?num=50&hl=en&ie=UTF-8&as_qdr=all&q=%2Bwww-ws-desc+%2B%22issue+198%22+site%3Alists.w3.org&btnG=Search">Google</a> WG archive for relevant posts.]
-
- </td>
- </tr>
- <tr>
- <td colspan="7"><b>Proposal:</b> </td>
- </tr>
- <tr>
- <td colspan="7"><b>Resolution:</b> </td>
- </tr>
- </tbody>
- <tbody class="Active">
- <tr>
- <td valign="top" rowspan="5"><b><a name="x199">199</a></b></td><td>Media type description</td><td></td><td></td><td>Design</td><td>Active</td><td>WG</td><td></td>
- </tr>
- <tr>
- <td colspan="7"><b>Title:</b> mismatch between the media type attribute and the actual data</td>
- </tr>
- <tr>
- <td colspan="7"><b>Description:</b>
- <p>[19 May FTF] Possible error conditions: mismatch between the media type
- attribute and the actual data.</p>
-
- [<a href="http://www.w3.org/Search/Mail/Public/search?type-index=www-ws-desc&index-type=t&keywords=%22Issue+199%22&search=Search">Search</a> or
- <a href="http://www.google.com/search?num=50&hl=en&ie=UTF-8&as_qdr=all&q=%2Bwww-ws-desc+%2B%22issue+199%22+site%3Alists.w3.org&btnG=Search">Google</a> WG archive for relevant posts.]
-
- </td>
- </tr>
- <tr>
- <td colspan="7"><b>Proposal:</b> </td>
- </tr>
- <tr>
- <td colspan="7"><b>Resolution:</b> </td>
- </tr>
- </tbody>
- <tbody class="Active">
- <tr>
- <td valign="top" rowspan="5"><b><a name="x200">200</a></b></td><td>Media type description</td><td></td><td></td><td>Design</td><td>Active</td><td>WG</td><td></td>
- </tr>
- <tr>
- <td colspan="7"><b>Title:</b> Where should appInfo go?</td>
- </tr>
- <tr>
- <td colspan="7"><b>Description:</b>
- <p>[19 May FTF] Where should the annotation appear, on the type and/or the element?</p>
-
- [<a href="http://www.w3.org/Search/Mail/Public/search?type-index=www-ws-desc&index-type=t&keywords=%22Issue+200%22&search=Search">Search</a> or
- <a href="http://www.google.com/search?num=50&hl=en&ie=UTF-8&as_qdr=all&q=%2Bwww-ws-desc+%2B%22issue+200%22+site%3Alists.w3.org&btnG=Search">Google</a> WG archive for relevant posts.]
-
- </td>
- </tr>
- <tr>
- <td colspan="7"><b>Proposal:</b> </td>
- </tr>
- <tr>
- <td colspan="7"><b>Resolution:</b> </td>
- </tr>
- </tbody>
- <tbody class="Active">
- <tr>
- <td valign="top" rowspan="5"><b><a name="x201">201</a></b></td><td>Media type description</td><td></td><td></td><td>Design</td><td>Active</td><td>WG</td><td></td>
- </tr>
- <tr>
- <td colspan="7"><b>Title:</b> Name of mediaType</td>
- </tr>
- <tr>
- <td colspan="7"><b>Description:</b>
- <p>[19 May FTF] Consider changing name from mediaType to contentType</p>
-
- [<a href="http://www.w3.org/Search/Mail/Public/search?type-index=www-ws-desc&index-type=t&keywords=%22Issue+201%22&search=Search">Search</a> or
- <a href="http://www.google.com/search?num=50&hl=en&ie=UTF-8&as_qdr=all&q=%2Bwww-ws-desc+%2B%22issue+201%22+site%3Alists.w3.org&btnG=Search">Google</a> WG archive for relevant posts.]
-
- </td>
- </tr>
- <tr>
- <td colspan="7"><b>Proposal:</b> </td>
- </tr>
- <tr>
- <td colspan="7"><b>Resolution:</b> </td>
- </tr>
- </tbody>
- <tbody class="Active">
- <tr>
- <td valign="top" rowspan="5"><b><a name="x202">202</a></b></td><td>Media type description</td><td></td><td></td><td>Editorial</td><td>Active</td><td>WG</td><td></td>
- </tr>
- <tr>
- <td colspan="7"><b>Title:</b> More examples</td>
- </tr>
- <tr>
- <td colspan="7"><b>Description:</b>
- <p>[19 May FTF] Would like more examples:
- e.g using a static type -- i'm always going to use an
- image/jpeg. What would that look like?</p>
-
- [<a href="http://www.w3.org/Search/Mail/Public/search?type-index=www-ws-desc&index-type=t&keywords=%22Issue+202%22&search=Search">Search</a> or
- <a href="http://www.google.com/search?num=50&hl=en&ie=UTF-8&as_qdr=all&q=%2Bwww-ws-desc+%2B%22issue+202%22+site%3Alists.w3.org&btnG=Search">Google</a> WG archive for relevant posts.]
-
- </td>
- </tr>
- <tr>
- <td colspan="7"><b>Proposal:</b> </td>
- </tr>
- <tr>
- <td colspan="7"><b>Resolution:</b> </td>
- </tr>
- </tbody>
- <tbody class="Active">
- <tr>
- <td valign="top" rowspan="5"><b><a name="x203">203</a></b></td><td>Media type description</td><td></td><td></td><td>Design</td><td>Active</td><td>WG</td><td></td>
- </tr>
- <tr>
- <td colspan="7"><b>Title:</b> Limited to base64encoded?</td>
- </tr>
- <tr>
- <td colspan="7"><b>Description:</b>
- <p>[19 May FTF] Explain why this proposal is limited to base64encoded?</p>
-
- [<a href="http://www.w3.org/Search/Mail/Public/search?type-index=www-ws-desc&index-type=t&keywords=%22Issue+203%22&search=Search">Search</a> or
- <a href="http://www.google.com/search?num=50&hl=en&ie=UTF-8&as_qdr=all&q=%2Bwww-ws-desc+%2B%22issue+203%22+site%3Alists.w3.org&btnG=Search">Google</a> WG archive for relevant posts.]
-
- </td>
- </tr>
- <tr>
- <td colspan="7"><b>Proposal:</b> </td>
- </tr>
- <tr>
- <td colspan="7"><b>Resolution:</b> </td>
- </tr>
- </tbody>
- <tbody class="Active">
- <tr>
- <td valign="top" rowspan="5"><b><a name="x204">204</a></b></td><td>Media type description</td><td></td><td></td><td>Design</td><td>Active</td><td>WG</td><td></td>
- </tr>
- <tr>
- <td colspan="7"><b>Title:</b> Why default to */* instead of to "no effect"?</td>
- </tr>
- <tr>
- <td colspan="7"><b>Description:</b>
- <p>[19 May FTF] Explain why */* AND absence means this is opaque
- application data (i.e. application/octet-stream.</p>
-
- [<a href="http://www.w3.org/Search/Mail/Public/search?type-index=www-ws-desc&index-type=t&keywords=%22Issue+204%22&search=Search">Search</a> or
- <a href="http://www.google.com/search?num=50&hl=en&ie=UTF-8&as_qdr=all&q=%2Bwww-ws-desc+%2B%22issue+204%22+site%3Alists.w3.org&btnG=Search">Google</a> WG archive for relevant posts.]
-
- </td>
- </tr>
- <tr>
- <td colspan="7"><b>Proposal:</b> </td>
- </tr>
- <tr>
- <td colspan="7"><b>Resolution:</b> </td>
- </tr>
- </tbody>
- <tbody class="Active">
- <tr>
- <td valign="top" rowspan="5"><b><a name="x205">205</a></b></td><td>Media type description</td><td></td><td></td><td>Design</td><td>Active</td><td>WG</td><td></td>
- </tr>
- <tr>
- <td colspan="7"><b>Title:</b> Explain priority</td>
- </tr>
- <tr>
- <td colspan="7"><b>Description:</b>
- <p>[19 May FTF] Pattern includes use of priority -- either explain
- relationship or get rid of it.</p>
-
- [<a href="http://www.w3.org/Search/Mail/Public/search?type-index=www-ws-desc&index-type=t&keywords=%22Issue+205%22&search=Search">Search</a> or
- <a href="http://www.google.com/search?num=50&hl=en&ie=UTF-8&as_qdr=all&q=%2Bwww-ws-desc+%2B%22issue+205%22+site%3Alists.w3.org&btnG=Search">Google</a> WG archive for relevant posts.]
-
- </td>
- </tr>
- <tr>
- <td colspan="7"><b>Proposal:</b> </td>
- </tr>
- <tr>
- <td colspan="7"><b>Resolution:</b> </td>
- </tr>
- </tbody>
- <tbody class="Active">
- <tr>
- <td valign="top" rowspan="5"><b><a name="x206">206</a></b></td><td>Media type description</td><td></td><td></td><td>Design</td><td>Active</td><td>WG</td><td></td>
- </tr>
- <tr>
- <td colspan="7"><b>Title:</b> Annotations and schema component model.</td>
- </tr>
- <tr>
- <td colspan="7"><b>Description:</b>
- <p>[19 May FTF] How do annotations show up in component model? (currently
- limited to a "binary information element")</p>
-
- [<a href="http://www.w3.org/Search/Mail/Public/search?type-index=www-ws-desc&index-type=t&keywords=%22Issue+206%22&search=Search">Search</a> or
- <a href="http://www.google.com/search?num=50&hl=en&ie=UTF-8&as_qdr=all&q=%2Bwww-ws-desc+%2B%22issue+206%22+site%3Alists.w3.org&btnG=Search">Google</a> WG archive for relevant posts.]
-
- </td>
- </tr>
- <tr>
- <td colspan="7"><b>Proposal:</b> </td>
- </tr>
- <tr>
- <td colspan="7"><b>Resolution:</b> </td>
- </tr>
- </tbody>
- <tbody class="Active">
- <tr>
- <td valign="top" rowspan="5"><b><a name="x242">242</a></b></td><td>Media type description</td><td></td><td></td><td>Design</td><td>Active</td><td>Hugo</td><td></td>
- </tr>
- <tr>
- <td colspan="7"><b>Title:</b> Binding accepts header and output serialization </td>
- </tr>
- <tr>
- <td colspan="7"><b>Description:</b>
- <p>[<a href="http://lists.w3.org/Archives/Public/www-ws-desc/2004Jul/0005.html">email</a>]</p>
-
- [<a href="http://www.w3.org/Search/Mail/Public/search?type-index=www-ws-desc&index-type=t&keywords=%22Issue+242%22&search=Search">Search</a> or
- <a href="http://www.google.com/search?num=50&hl=en&ie=UTF-8&as_qdr=all&q=%2Bwww-ws-desc+%2B%22issue+242%22+site%3Alists.w3.org&btnG=Search">Google</a> WG archive for relevant posts.]
-
- </td>
- </tr>
- <tr>
- <td colspan="7"><b>Proposal:</b> </td>
- </tr>
- <tr>
- <td colspan="7"><b>Resolution:</b> </td>
- </tr>
- </tbody>
- <tbody class="Active">
- <tr>
<td valign="top" rowspan="5"><b><a name="x244">244</a></b></td><td>SOAP 1.1</td><td></td><td></td><td>Design</td><td>Active</td><td>Asir</td><td></td>
</tr>
--- 224,227 ----
***************
*** 565,579 ****
<tbody class="Active">
<tr>
! <td valign="top" rowspan="5"><b><a name="x245">245</a></b></td><td>Media Type Description</td><td></td><td></td><td>Design</td><td>Active</td><td>Hugo</td><td></td>
</tr>
<tr>
! <td colspan="7"><b>Title:</b> Define expectedMediaTypeItem to be RFC 2616 Accepts header</td>
</tr>
<tr>
<td colspan="7"><b>Description:</b>
! <p>[<a href="http://lists.w3.org/Archives/Public/www-ws-desc/2004Jun/0263.html">email</a>]</p>
! [<a href="http://www.w3.org/Search/Mail/Public/search?type-index=www-ws-desc&index-type=t&keywords=%22Issue+245%22&search=Search">Search</a> or
! <a href="http://www.google.com/search?num=50&hl=en&ie=UTF-8&as_qdr=all&q=%2Bwww-ws-desc+%2B%22issue+245%22+site%3Alists.w3.org&btnG=Search">Google</a> WG archive for relevant posts.]
</td>
--- 247,262 ----
<tbody class="Active">
<tr>
! <td valign="top" rowspan="5"><b><a name="x252">252</a></b></td><td>Media type description</td><td></td><td></td><td>Design</td><td>Active</td><td>Jonathan marsh</td><td></td>
</tr>
<tr>
! <td colspan="7"><b>Title:</b> Syntax of media type annotation</td>
</tr>
<tr>
<td colspan="7"><b>Description:</b>
! <p>Should the expected media type be an attribute instead of an appinfo annotation?
! WG substantially in favor of this if tooling doesn't prevent it.</p>
! [<a href="http://www.w3.org/Search/Mail/Public/search?type-index=www-ws-desc&index-type=t&keywords=%22Issue+252%22&search=Search">Search</a> or
! <a href="http://www.google.com/search?num=50&hl=en&ie=UTF-8&as_qdr=all&q=%2Bwww-ws-desc+%2B%22issue+252%22+site%3Alists.w3.org&btnG=Search">Google</a> WG archive for relevant posts.]
</td>
Received on Monday, 2 August 2004 10:53:21 UTC