- From: Michael[tm] Smith <mike@w3.org>
- Date: Mon, 24 Aug 2015 10:24:38 +0900
- To: =JeffH <Jeff.Hodges@KingsMountain.com>
- Cc: W3C WebApps WG <public-webapps@w3.org>
- Message-ID: <20150824012438.GZ30733@sideshowbarker.net>
Hi =JeffH, =JeffH <Jeff.Hodges@KingsMountain.com>, 2015-08-23 14:51 -0700: > Archived-At: <http://www.w3.org/mid/55DA4071.2080809@KingsMountain.com> > > Hi, > > I notice in at least some specs produced by y'all, such as.. > > [1] http://www.w3.org/TR/workers/ > > [2] http://www.w3.org/TR/webmessaging/ > > > ..there are some terms that are underlined with lighter blue thick lines, > but which are not links, and are not explicitly defined within those specs. > > e.g, a few from [1] "absolute url", "tasks", "event loops"; and a few from > [2] "origin", "task source", "same". > > in looking at the source the specs are renderede from, in each case such > terms are enclosed by <span>...</span>, like so.. > > <span>origin</span> > > It seems like this markup is being used to signal that the term is defined > in another spec (eg HTML5, URL), Yeah, that’s exactly the case. The formatting of those specs is an artifact of a time when we were still using spec-production tools that didn’t support creating real hyperlinks to the correct specs in those cases. In fact both of those specs are somewhat just artifacts of earlier years, in that they’re just copies of specs published elsewhere, Abe while the Workers spec was officially a separate spec upstream as well, it was folded back into the HTML spec years ago. And the content of the Web Messaging spec has been, since it was first defined, part of the HTML spec. —Mike -- Michael[tm] Smith https://people.w3.org/mike
Received on Monday, 24 August 2015 01:25:05 UTC