- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Sun, 09 Oct 2011 00:55:17 -0400
- To: www-tag@w3.org
> ashok malhotra wrote: > Thanks, Manu, good note! Good, I'm glad it made some sense. :) > Let me try and summarize where I think you are going and see whether you agree > and others see this as a promising direction: > > Currently, the specs say "fragment identifier semantics are defined by the media type". > We should amend this to say "fragment identifier semantics are defined by the media type and > the kind of agent that is making use of the markup". For example: Effectively, yes. > 1. In browsers without Javascript frag ids identify a place in a document. > 2. In browsers with Javascript and for media types that support active content, > frag ids may also be used to pass parameters to the Javascript > 3. For Semantic agents frag ids may also be used to identify a concept in a document That is correct. So, that is the edit that will need to be made to RFC 3986. There are another set of updates that will need to be made to the following documents in order to ensure follow-your-spec-nose jumps from Media Type -> Language Spec -> Semantics Spec: * The text/html and application/xhtml+xml Media Type registration will need to mention the existence of the HTML+RDFa spec and the HTML5 Microdata spec. Adding a sentence or two stating that fragment identifiers may have additional meaning if attributes from HTML+RDFa or HTML5 Microdata are used in the document would address the issue of fragment identifier meaning in HTML. * XML+RDFa is currently defined in RDFa Core 1.1, so we may need to update whatever document is the most recent successor to RFC 3023 to mention that fragment identifiers may have meaning when used with XML documents if the RDFa attributes are mixed into the document. So, with those edits made, we can follow our noses from the Media Type registration to the RDFa Core 1.1 specification for the following languages: * HTML4+RDFa 1.1 * HTML5+RDFa 1.1 * XHTML1+RDFa 1.0 * XHTML1+RDFa 1.1 * XHTML5+RDFa 1.1 * SVG Tiny 1.2 + RDFa 1.0 * ODF+RDFa 1.0 * XML+RDFa 1.1 -- manu -- Manu Sporny (skype: msporny, twitter: manusporny) Founder/CEO - Digital Bazaar, Inc. blog: Standardizing Payment Links - Why Online Tipping has Failed http://manu.sporny.org/2011/payment-links/
Received on Sunday, 9 October 2011 04:55:57 UTC