[whatwg] Fwd: <INCLUDE> and links with @rel=embed

bjartur svartman95 at gmail.com
Wed May 19 06:48:31 PDT 2010

> This all seems way too abstract - I think you are arguing for the
> wrong case with the right reasons. But in any case, you should try and
> make an example markup with your ideas and check if it really gives
> you what you think it will. I have sincere doubts.
Yeah, maybe my crazy idealism and tendency to reuse existing things don't mix up in this case.
The main purpose of <video> and <audio> is to create a scripting interface to online video.
But they also add new linking capabilities which should be available to any content whatsoever.
OK, letting me loose and only using current draft as a vague guideline.

<include href="./gpl" title="GNU General Public License> <!-- URI of general resource -->
	<include rel="alternate" href="./gpl.en" hreflang="en_US" title="GPL"> <!-- Some other way of marking alternatives would be better -->
		<!-- may add hreflang to all links herein for maximum compatibility -->
		<a rel="embed" href="./gpl.en.text" type="text/plain">...</a>
		<a rel="embed" href="./gpl.en.html" type="text/html" charset="..">...</a>
	<include rel="alternate" href="./gpl.fr" hreflang="fr" title="GPL">
		<!-- similiar to above -->
	<include href="./gpl-notes" title="Some secondary resource that should be bundled with the GPL">
		<a rel="alternate embed" href="./gpl-notes.en" hreflang="en_US">Notes on GPL</a>
		<a rel="alternate embed" href="./gpl-notes.fr" hreflang="is" lang="is">Um GPL</a>

More sane rewrite:

<choose href="./gpl" title="GNU General Public License" id="gpl">
	<choose href="./gpl.en" hreflang="en_US">
		<a rel="embed" href="./gpl.en.text" type="text/plain">...</a>
		<a rel="embed" href="./gpl.en.html" type="text/html" charset="..">...</a>
	<choose href="./gpl.fr" hreflang="fr">
		<!-- ... -->
<choose href="./gpl-notes" tilte="Notes on GPL" id="notes">
	<!-- ... -->

Note: choose states relationship between alternative resources, not that the UA
must choose to render only one of them. Element might be named <alt>.

Note: Requires more metadata to state relationship between #gpl and #notes.

I think that making one of those elements a media element might make some sense.
Also, I think that <a rel="embed"> should be substituted for <source> and @src
of <video> and <audio> should be removed, and <a rel="embed"> used instead.
If that brakes scripting, ignore my suggestion.

Radically changing <link> might also fulfill these use cases.
That's not compatible with existing implementations though,
and that might require allowing <link> inside of <body>.

Do you think that <link rdf:about="./gpl" rel="alternate" hreflang="fr" href="./gpl.fr">
is better? Or
<div rdf:about="./gpl">
	<div rdf:about="./gpl.en" about-/href-lang="en_US">
		<link rel="alternate" type="text/plain"	href="./gpl.en.text">
		<link rel="alternate" type="text/html"	href="./gpl.en.html">
	<link rel="alternate" hreflang="fr" href="./gpl.fr">
Although it brakes compatibility with browsers it expresses the desired info.
This feels like something that might be in a XHTML+XLink document.

More information about the whatwg mailing list