- From: <noah_mendelsohn@us.ibm.com>
- Date: Wed, 10 Nov 2004 23:58:03 -0500
- To: Chris Lilley <chris@w3.org>
- Cc: "Williams, Stuart (HP Labs, Bristol)" <skw@hp.com>, www-tag@w3.org
Chris Lilley writes: > - xml 1.1 or 1.0 (soap 10 only as schema is 1.0 only) > unclear areas Having missed this week's call, I'm not really sure what the context is for this discussion of 3023. I did some coordination months ago with Murata-san as to treatment of xml 1.0 and xml 1.1 in 3023, and I believe the resolution we agreed was workable for SOAP 1.2. I have not checked lately whether that resolution is in fact reflected in latest 3023 drafts, and given that I'm on an airplane at the moment I can't check just now. Is this something on which I need to follow up for Tag purposes? Presumably XMLP can take a first cut at any issues relating directly to SOAP. I'm cc:'ing David Fallside, XMLP chair, to keep him in the loop. Thanks. -------------------------------------- Noah Mendelsohn IBM Corporation One Rogers Street Cambridge, MA 02142 1-617-693-4036 -------------------------------------- Chris Lilley <chris@w3.org> Sent by: www-tag-request@w3.org 11/08/2004 03:01 PM Please respond to Chris Lilley To: "Williams, Stuart (HP Labs, Bristol)" <skw@hp.com> cc: www-tag@w3.org, (bcc: Noah Mendelsohn/Cambridge/IBM) Subject: 3023 update (was Re: Agenda TAG Telcon: 8th Nov 2004) On Saturday, November 6, 2004, 12:30:00 AM, Stuart wrote: WSHLB> 2.2.1 Media-Types Issues WSHLB> 1. RFC3023 WSHLB> + Update on progress with RFC3023 revision (CL) WSHLB> + Related Issues: WSHLB> [15]RFC3023Charset-21and finding "[16]Internet Media Type WSHLB> registration, consistency of use" Here is a summary of where things stand: agreement: - deprecation of text/xml and xml-external-parsed-entity (in current -00 draft) - the addition of XPointer as fragment identifiers (in current -00 draft) - addition of XML Base (in current -00 draft) - transcoding proxies can detect +xml and either fix up the XML encoding declaration, or leave it alone. Making well formed XML not well formed considered harmful (not in -00 draft, but agreed) tentative agreement - seems therefore to be agreement that the xml encoding declaration and the charset (if supplied) should match. disagreement - charset. Still says optional but strongly recommended, TAG wants optional and only supplied if correct. TAG wants default to be 'see xml encoding declaration'. So, some media types could omit the parameter entirely. However, attempt to register image/svg+xml without a charset (backed up by pointing to TAG findings) met resistance. Still therefore a conflict with TAG findings. http://www.imc.org/ietf-xml-mime/mail-archive/msg00978.html - xml 1.1 or 1.0 (soap 10 only as schema is 1.0 only) unclear areas - extent to which dispatching on media types really happens discussion - some on www-tag, moved to ietf-xml-mime document publishing http://www.ietf.org/internet-drafts/draft-murata-kohn-lilley-xml-00.txt is published draft-murata-kohn-lilley-xml-01.txt is created but we are discussing what else it should say :) so its not published. -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group Member, W3C Technical Architecture Group
Received on Thursday, 11 November 2004 05:09:06 UTC