| CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 18:26:26 GMT
content-type: text/html
content-encoding: gzip
content-location: 0116.html
vary: negotiate,Accept-Encoding
tcn: choice
last-modified: Thu, 13 Jul 2023 17:54:10 GMT
cache-control: max-age=2592000, public
expires: Sat, 08 Nov 2025 20:48:46 GMT
access-control-allow-origin: *
x-request-id: 98c0bda48d941526
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: HIT
set-cookie: __cf_bm=h0F1oUaAzf7k0_Fcm78kiHma6IZL.u9HClzbM12mxj8-1760120786-1.0.1.1-Ft7.4KtV_eHZKgrOSaME16DE8QxwCrCkZV_qopparvqvSnBr3pbCHU1rNigDNhx0i1pSoOdjhNOnE38uJ7yhRg8N152n33FccLHKX_X7sGE; path=/; expires=Fri, 10-Oct-25 18:56:26 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c82a7e7b941f95-BLR
alt-svc: h3=":443"; ma=86400
XLINK, HLINK or neither? Possible new TAG issue from Tim Berners-Lee on 2002-06-14 (www-tag@w3.org from June 2002)
XLINK, HLINK or neither? Possible new TAG issue
- From: Tim Berners-Lee <timbl@w3.org>
- Date: Fri, 14 Jun 2002 15:00:43 -0400
- To: www-tag@w3.org
- Message-Id: <0711A419-7FC9-11D6-ABAE-000393914268@w3.org>
Martin D?rst mentioned, in response to the last call for the speech grammar draft, that there is a question as to whether for any URI parameter, xlink:href should be used. There was a note in later discussions that the HTML working group are working on a "HLINK" spec for describing xlink functionality as a schema annotation level solution to thius, just as several times we have looked at schema annotation as a compromise between RDF syntax and no semantics at all. For me this questions depends on whether the document type is a human-readable hypertext document, when generic hypertext xml tools would benefit from knowing what is a link, and whether significance of the URI in question is a hypertext link or something different. Maybe the TAG should give some direction in this area. Tim BL
Received on Friday, 14 June 2002 16:01:11 UTC