W3C home > Mailing lists > Public > www-html@w3.org > June 2001

Re: URIs For XHTML Terms

From: Charles McCathieNevile <charles@w3.org>
Date: Fri, 15 Jun 2001 11:58:49 -0400 (EDT)
To: "Sean B. Palmer" <sean@mysterylights.com>
cc: <www-html@w3.org>, <w3c-wai-pf@w3.org>
Message-ID: <Pine.LNX.4.30.0106151156500.31803-100000@tux.w3.org>
Right, but this is just adding a layer of indirection for the sake of easy
readable N3, which strikes me as not justifying the effort. For machine
processing it is just as easy to use the full URIs anyway.

Chaals

On Fri, 15 Jun 2001, Sean B. Palmer wrote:

  > http://www.w3.org/TR/REC-html40-971218/struct/text.html#edef-ACRONYM

  I'd use that URL to point to the definition of the XHTML term in
  question, so that:-

  [[[
  @prefix xhtmle: <http://www.w3.org/1999/xhtml#elements.> .
  @prefix htmldfn:
  <http://www.w3.org/TR/REC-html40-971218/struct/text.html#edef-> .
  @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .

  xhtmle:acronym rdfs:isDefinedBy htmldfn:ACRONYM .
  ]]]

  Doing it in that way in which I recently outlined has advantages other
  any other "hack" system (e.g. in that the types are all grouped
  properly). For example, you can use:-

     http://www.w3.org/1999/xhtml#

  as an RDF namespace alias for all XHTML types, and:-

     http://www.w3.org/1999/xhtml#elements.

  as the RDF namespace alias for all XHTML elements, and so on.

  --
  Kindest Regards,
  Sean B. Palmer
  @prefix : <http://webns.net/roughterms/> .
  :Sean :hasHomepage <http://purl.org/net/sbp/> .


-- 
Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1 617 258 5999
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Friday, 15 June 2001 11:58:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:48 GMT