[foaf-dev] Proposal: deprecate pastProject and currentProject

Danny Ayers danny.ayers at gmail.com
Sun Dec 13 20:51:49 CET 2009

2009/12/13 Dan Brickley <danbri at danbri.org>:
> On Sat, Dec 12, 2009 at 10:04 PM, Libby Miller <libby at nicecupoftea.org> wrote:
>> hi all,
>> I've being reading through the foaf spec and I want to make the
>> following proposal: deprecate pastProject and currentProject.
> You missed a bit of our proposal?

Sorry, I did miss that bit.

> Since FOAF is presented as a "dictionary of terms", and since it
> tracks vocabulary usage in a global Web, the idea of 'deprecate' is a
> bit strong. So we are instead suggesting to use a marker of "archaic"
> in the spec. This is similar to what you'd find in a natural language
> dictionary when some terminology was very old-fashioned and not common
> in contemporary usage. It also leaves the door open for things to come
> back into fashion. In this way the FOAF spec has a somewhat
> anthropological aspect, rather than being purely imperative.

That makes a lot of sense, win-win, though to me 'archaic' sounds more
sweeping than 'deprecated'. Must be another more suitable word...

Whatever, just use it as another potential value for status in -





More information about the foaf-dev mailing list