SWBPD WG Resolution Regarding httpRange-14

Hi all,

Whereas the TAG have not yet resolved httpRange-14 [1], the Semantic 
Web Best Practices and Deployment WG have resolved unanimously that:

   - an http URI without a hash MAY be used to identify an RDF property.

where MAY is understood in terms of RFC 2119
and identify is understood in terms of RFC 3986

Our primary concerns are:
    - Deployed semantic web applications such as Dublin Core [2],
      Friend-of-a-friend [3], Creative Commons [4], Adobe XMP [5]
      and RSS 1.0 [6] that use such URIs.
    - The practical difficulty of using '#' namespace URIs for large
      vocabularies such as wordnet;
    - Server side processing of fragment identifier components
      (i.e. the impossibility of doing server side redirects on
      '#' URIs).

The lack of resolution of the httpRange-14 issue is impacting the work 
of the following SWBPD WG Task Forces:
    - Vocabulary Management
    - Porting Thesauri
    - WordNet
    - RDF/Topic Maps Interoperability
(see the SWBPD WG homepage for TF list and more information [7])

The SWBPD WG hopes that the TAG will be able to soon reach closure on 
the httpRange-14 issue, noting the current SW practice embodied in our 
resolution.  We offer to work with you as appropriate.

[1] http://www.w3.org/2001/tag/issues.html#httpRange-14
[2] http://dublincore.org/
[3] http://www.foaf-project.org/
[4] http://creativecommons.org/
[5] http://www.adobe.com/products/xmp/main.html
[6] http://purl.org/rss/1.0/
[7] http://www.w3.org/2001/sw/BestPractices/#Tasks

Dave Wood
Co-chair, Semantic Web Best Practices & Deployment Working Group

Received on Saturday, 26 March 2005 21:20:22 UTC