[Fwd: [closed] chas-01 request to add aboutEachPrefix]

Hi Folks,

This issue got rejected by the RDF core group.

My feeling is that  aboutEachPrefix per se is indeed a nasty hack with 
lots of problems. On the other hand there is a huge need to be able to 
discuss a class of objects without enumerating every member of the class 
in advance. For example, pages produced by an organisation, or pages 
aproved by an individual for publication. (In fact there is no reason 
why these would all begin with the same fragment of URI anyway).

It may be that this is only possible by using OWL. This would mean that 
we cannot expect to meet these use cases except with systems which have 
the additional machinery, as far as I can tell. I would like to ask the 
grop for an explicit clarification of whether this is the case, and if 
so I will actually request something to this effect go in the primer 
(including at the least a link to an explanation of how it can be done 
using the full glory of the Framework)...



-------- Original Message --------
Subject:  [closed] chas-01 request to add aboutEachPrefix
Date:  Mon, 07 Apr 2003 16:44:13 +0100
From:  Dave Beckett <dave.beckett@bristol.ac.uk>
To:  Charles McCathieNevile <charles@sidar.org>
CC:  www-rdf-comments@w3.org


You made a last call comment captured in


The RDF Core WG has resolved


to reject this comment on the grounds that the original reasons for
removal remain valid:

 * We had good feedback that it lived badly in RDF and as such was
   little implemented or used.

 * It broke layering by looking inside URIs rather than dealing with
   them as identifiers.

 * Felt more like a RDF/XML syntax thing than part of the RDF model
   and as such it mixed badly with triples.

 * Worked badly with rdf:bagID - the interactions were never well

 * Experienced practitioners recommended against using it.

Please reply to this email, copying www-rdf-comments@w3.org
indicating whether this decision is acceptable.


Received on Wednesday, 9 April 2003 09:51:59 UTC