[foaf-dev] Proposal: deprecate pastProject and currentProject

Richard Cyganiak richard at cyganiak.de
Sat Dec 12 22:17:55 CET 2009


The properties are not used much because foaf:Project is not used  
much. If you deprecate them, it would only be consequent to deprecate  
that class along with the properties.

I use all three in my homepage and would find it sad to see those  
terms removed from the spec.


On 12 Dec 2009, at 21:04, Libby Miller wrote:

> hi all,
> I've being reading through the foaf spec and I want to make the
> following proposal: deprecate pastProject and currentProject.
> My reasoning is that they are nearly unused - I found only 179 and 648
> usages respectively when I looked through Sindice reasonably recently:
> http://planb.nicecupoftea.org/2009/09/08/163/
> I'm concerned also at the inclusion of time in the description of the
> property name, which is different to the 'present tense' form of the
> rest of the properties.
> Any thoughts? I'm wondering why they are not used much. Are they not
> useful? or is it that they have not been picked up by any large
> exporters but are useful to people making their own files? or perhaps
> marking something as unstable isn't much encouragement for people to
> use it?
> Anyone care to make a counter-proposal?
> thanks,
> Libby
> _______________________________________________
> foaf-dev mailing list
> foaf-dev at lists.foaf-project.org
> http://lists.foaf-project.org/mailman/listinfo/foaf-dev

More information about the foaf-dev mailing list