[foaf-dev] Proposal: deprecate pastProject and currentProject

[Josef Petrák]

Deprecating foaf:Project in favour of promoting doap:Project? OK, and all projects are software-related? How about extend the FOAF's project term to be have some common properties to be usable for non-software-related projects?

Josef

On Dec 22, 2009, at 12:53 PM, Sergio Fernandez wrote:

> On Sun, 2009-12-13 at 11:00 +0100, Dan Brickley wrote:
>> I just remembered! Project *is* heavily used. Via subclassing in the
>> DOAP project! :)
> 
> Exactly!
> 
> For my data I used doap:Project with both properties,
> foaf:currentProject and foaf:pastProject.
> 
> Then my two cents would go to deprecate the less used class
> (foaf:Project), recommending the usage of doap:Project for such a kind
> of things.
> 
> Cheers, 
> 
> -- 
> __      ___ _   _           
> \ \    / (_) |_(_)___ _ _   
> \ \/\/ /| | / / / -_) '_|  Sergio Fernández
>  \_/\_/ |_|_\_\_\___|_|    http://www.wikier.org/
> 
> _______________________________________________
> foaf-dev mailing list
> foaf-dev at lists.foaf-project.org
> http://lists.foaf-project.org/mailman/listinfo/foaf-dev