Maven 2.x DOAP Plugin

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.1
• Fix Version/s: 1.1
• Component/s: None
• Labels:

  None
• Environment:

  Any

Summary
The foaf:Organization node is misplaced inside the foaf:Person node. It is not compliant with the FoaF or Doap specs.

The Problem
This is an instance of the issue described here: http://lists.foaf-project.org/pipermail/foaf-dev/2009-January/009452.html
foaf:Organization like foaf:Group is a foaf:Agent (see http://xmlns.com/foaf/spec/#term_Agent), so the issue is the same.
The recommended syntax from the DoaP project examples is to use the foaf:member property between the foaf:Organization node and the foaf:Person node.
Unfortunately, per the FoaF spec, the relation only goes in that direction (Organization->member->Person) with no convenient inverse property.

The Fix
The best fix I can currently find is to use blank nodes and a separate Organization element that is not nested in the person element. Unfortunately, because the DoaP plugin isn't using native RDF tools internally, this will require a little more bookkeeping.

<rdf:RDF>
<doap:Project>
<maintainer rdf:nodeID="jdoe"/>
<founder rdf:nodeID="jdoe"/>
</doap:Project>

<Person nodeID="jdoe">
<name>John Doe</name>
<mbox rdf:resource="mailto:jdoe@example.org" />
</Person>

<doap:Organization>
<doap:homepage rdf:resource="http://www.example.org" />
<doap:member rdf:nodeID="jdoe" />
</doap:Organization>
</rdf:RDF>

Additional Info
Info about rdf:nodeID is available at: http://www.w3.org/TR/rdf-syntax-grammar/#section-Syntax-blank-nodes

1. 

   doap-organization-bugreport.tgz

   29/Sep/09 4:17 PM

   1 kB

   Tim Fliss

2. 

   MDOAP-25.patch

   30/Sep/09 2:05 PM

   13 kB

   Tim Fliss

• Assignee:

  Vincent Siveton

  Reporter:

  Tim Fliss

• Created:

  29/Sep/09 4:17 PM

  Updated:

  10/Dec/10 6:22 AM

  Resolved:

  10/Dec/10 6:22 AM