- From: <noah_mendelsohn@us.ibm.com>
- Date: Tue, 26 Aug 2008 10:43:40 -0400
- To: "Steven Pemberton" <steven.pemberton@cwi.nl>
- Cc: "Ben Adida" <ben@mit.edu>, "Mark Baker" <distobj@acm.org>, "Norman Walsh" <ndw@nwalsh.com>, "Stuart Williams" <skw@hp.com>, "Tim Berners-Lee" <timbl@w3.org>, www-tag@w3.org
Steven Pemberton writes: > M12N specifies modules that can be combined in different ways. The > resulting host language need not be XHTML, and therefore, the Media > type used to describe it need not be an xhtml related one. > For instance, Jabber uses M12N to define message formats that can > include embedded XHTML, RDDL uses M12N. OK. > However, many host languages *are* XHTML (such as XHTML 1.1, XHTML > Basic, XHTML Print), and so use the xhtml media type. Good. So, let's say I use M12N to extend a host language, say XHTML, and I retrieve using HTTP a representation that includes markup defined in that extension. What normative specifications, presumably starting with the media type registration, give the user agent (browser) permission to infer the intended semantics from the new markup? That's the question on the table for the Self-describing Web finding. -------------------------------------- Noah Mendelsohn IBM Corporation One Rogers Street Cambridge, MA 02142 1-617-693-4036 --------------------------------------
Received on Tuesday, 26 August 2008 14:43:26 UTC