- From: Shane McCarron <shane@aptest.com>
- Date: Wed, 07 Jan 2009 10:59:35 -0600
- To: XHTML WG <public-xhtml2@w3.org>
As a quick follow up to this - I actually believe that the current RFC does a decent job of dealing with this. See http://www.ietf.org/rfc/rfc3236.txt section 8. We are not using it, but that doesn't mean it is wrong. Shane McCarron wrote: > > As per our discussion today, I wanted to briefly summarize the issues > relating to this action item... > > Essentially, this comes down to how a client can tell a server what > flavors of XHTML it supports. We had discussed in the past using the > profile parameter of the media type as a way of doing this. In the > end we recognized that what we should do is extend the RFC so that it > describes this convention, perhaps format rules for the value of the > profile parameter, and maybe even a reference to a w3c-hosted registry > of xhtml family markup languages. Such a registry would, of course, > use RDFa. > > I think this is the core of the issue. Mark Baker indicated he could > help us through the process once we know what we actually want. > -- Shane P. McCarron Phone: +1 763 786-8160 x120 Managing Director Fax: +1 763 786-8180 ApTest Minnesota Inet: shane@aptest.com
Received on Wednesday, 7 January 2009 17:00:11 UTC