W3C home > Mailing lists > Public > public-swbp-wg@w3.org > October 2005

RE: [VM] Reminder for rescheduled telecon today (Friday)

From: Bernard Vatant <bernard.vatant@mondeca.com>
Date: Fri, 28 Oct 2005 15:02:02 +0200
To: "Thomas Baker" <tbaker@tbaker.de>, "SW Best Practices" <public-swbp-wg@w3.org>
Message-ID: <GOEIKOOAMJONEFCANOKCMECMHCAA.bernard.vatant@mondeca.com>


In a rush before the telecon.

I'm fully happy with the content negotiation approach, my only concern is that you don't
know what *aspect* of the resource will be retrieved under a certain protocol until you
get there, unless you can get beforehand some expression of the type-map file. Putting
that along with my current thoughts about aspects and perspectives (sorry to take this
same hammer again to hit this nail), if I look at:

> URI: core
>
> URI: core-latest-rdf
> Content-type: application/rdf+xml

strikes me that I could write that in SPEK

 <spek:Aspect rdf:about="http://www.w3.org/2004/02/skos/core-latest-rdf">
  <spek:about rdf:resource="http://www.w3.org/2004/02/skos"/>
  <spek:inPerspective rdf:resource="some_URI_defining_application/rdf+xml"/>
 </spek:Aspect>

Just a thought. More about it on the phone.

Bernard


> -----Message d'origine-----
> De : public-swbp-wg-request@w3.org
> [mailto:public-swbp-wg-request@w3.org]De la part de Thomas Baker
> Envoyé : vendredi 28 octobre 2005 09:12
> Ŕ : SW Best Practices
> Objet : [VM] Reminder for rescheduled telecon today (Friday)
>
>
>
> Vocabulary Management telecon - Fri Oct 28
>
> 1300 UTC (1500 Berlin)
>
> Zakim: +1.617.761.6200=20
> Conference code 8683# ('VMTF')
> irc://irc.w3.org:6665/vmtf
> http://www.w3.org/2005/07/05-swbp-irc
> See: http://www.w3.org/Guide/1998/08/teleconference-calendar#D20051028
>
> Agenda
>
> 1) Can we achieve the goal outlined below [1]?
> 2) Presenting VM work in Galway.
>
> [1] http://lists.w3.org/Archives/Public/public-swbp-wg/2005Oct/0186.html
>
> -----
>
> SWBPD VM Task Force - update
>
> Most recent telecon: http://www.w3.org/2005/09/27-vmtf-minutes.html
>
> The problem: What is returned when the URI of a vocabulary term
> is dereferenced?   SKOS, FOAF, and DC handle this differently,
> and the existing solutions are not optimal, but we are close
> to agreement on a common approach.
>
> Where we stand:
>
> -- We agree that the solution should lie with content
>    negotiation [3].  (Other options considered were embedded
>    RDF (XHMTL 2.0) and RDF/A syntax, which however does not
>    address deployed tools.)
>
> -- Alistair has described how SKOS currently handles
>    dereferencing URIs and proposed some changes to the current
>    policy [1, 2, and attached below].
>
> -- Tom has described how DCMI currently handles dereferencing
>    [4] and endorses the requirements articulated by Alistair (see
>    below).
>
> Tom
>
> [1] http://lists.w3.org/Archives/Public/public-swbp-wg/2005Sep/0116.html
> [2] http://lists.w3.org/Archives/Public/public-swbp-wg/2005Oct/0024.html
> [3] http://www.w3.org/TR/webarch/#def-coneg
> [4] http://lists.w3.org/Archives/Public/public-swbp-wg/2005Jul/0002.html
>
> ----------------------------------------------------------------------
> Date: Mon, 3 Oct 2005 17:44:10 +0100
> From: Alistair Miles <A.J.Miles@rl.ac.uk>
>
> Requirements for URI dereferencing of RDF(S) classes and props:
>
> (1) If a person tries to dereference the URI of a class or
>     property (i.e. via a web browser), they end up at the relevant
>     bit of human-readable documentation.
>
> (2) If a machine tries to dereference the URI of a class
>     or property, they end up with a serialisation of a set of
>     RDF statements describing that class or property, with
>     a provenance that allows differentiation of different
>     'versions' of an RDF schema/ontology.
>
> (3) The whole thing complies with TAG resolution on httpRange-14.
>
> E.g. Implementation with Apache 1.3 (probably works for 2.0 too although
> I haven't checked)for 'hash' namespace
> http://www.w3.org/2004/02/skos/core:
>
> In directory corresponding to URL /2004/02/skos/ there is a type-map
> file (e.g. 'core.var') containing the following...
>
> ---
> URI: core
>
> URI: core-latest-rdf
> Content-type: application/rdf+xml
>
> URI: core-latest-html
> Content-type: text/html
>
> URI: core-latest-html
> Content-type: text/xml
>
> URI: core-latest-html
> Content-type: application/xml
>
> URI: core-latest-html
> Content-type: application/xhtml+xml
> ---
>
> ... and in directory corresponding to URL /2004/02/skos/ there is a
> .htaccess file containing the following...
> ---
> Options -MultiViews
> RewriteEngine On
> RewriteRule ^core$ core.var
> RewriteRule ^core-latest-rdf$ /2004/02/skos/core/history/2005-03-31
> [R=3D303]
> RewriteRule ^core-latest-html$ /TR/2005/WD-swbp-skos-core-spec-20050510
> [R=3D303]
> ---
>
> N.B. this is not actually implemented for
> http://www.w3.org/2004/02/skos/core although it is proposed to do so.
> It is implemented for the dummy resource
> http://www.w3.org/2004/02/skos/bar to test that it works.
>
>
> --
> Dr. Thomas Baker                      baker@sub.uni-goettingen.de
> SUB - Goettingen State                            +49-551-39-3883
> and University Library                           +49-30-8109-9027
> Papendiek 14, 37073 Göttingen
>
>
Received on Friday, 28 October 2005 13:02:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:17:19 GMT