Use of org:Organization cf. foaf:Organization

The inital draft of the profile currently suggests that the publisher of a data set will always be foaf:Organization since PSI data portals are not going to carry data created by individuals. If that decision is upheld then I suggest that rather than state foaf:Organization, org:Organization is used instead.

The two are equivalent (ORG's schema makes this explicit with owl:equivalentClass) so we're safe on the semantics - it just makes the link with ORG more explicit.

Incdidentally, I'm querying the underlying decision to restrict the profile to organisations. Might an EU funded project be a foaf:Group or a foaf:Project? Both are sub classes of foaf:Agent It's probably OK since org:Organization is quite general and does not imply legal entity status (that's org:FormalOrganization which is a sub class of org:Organization)

Component

Documentation

Category

feature

Comments

Tue, 09/04/2013 - 11:26

I would say it is a mistake to be too restricting. There will always be an edge case where a dataset needs to be included even though it was published by an individual.

I would vote for foaf:Agent as it includes individuals, groups & organizations. Maybe with a note that it is only to deviate from Organisations in very rare cases.

Mon, 15/04/2013 - 18:03

 

Whereas the current version of DCAT (http://www.w3.org/TR/2013/WD-vocab-dcat-20130312/) only defines classes foaf:Person and foaf:Organization, the range of dct:publisher used for Catalog and Dataset is given as foaf:Agent.

Therefore, the proposed resolution is

  • to replace foaf:Organization by foaf:Agent in section 6.1, 7.1.1, 7.1.2 and 7.4
  • to delete foaf:Person from the excluded classes in section 6.3
  • to add a note in section 6.1 to indicate that the use of an organisation is preferred and that in that case the class should be org:Organization.

 

 

Mon, 22/04/2013 - 19:12

Proposal to widen scope to foaf:Agent was agreed in meeting 2013-04-17 and included in Draft 2.

Mon, 22/04/2013 - 19:25

Login or create an account to comment.