[doap-interest] ScutterSnacks, ProjectProfileDocument?

[Edd Dumbill]

(Comments below.  DOAP implementors + deployers: PLEASE READ)

On Mon, 2004-10-18 at 12:19 +0200, Danny Ayers wrote:
> I bet it's already occurred to one or two folks around here, it might
> be useful to add a class to the DOAP schema called something like
> ProjectProfileDocument (possibly a subclass of foaf:Document)
> following the same design as FOAF's PersonalProfileDocument. (Is there
> a name which prevents the acronym clash?) In particular: "there is
> just one doap:Project described in the document, which will be its
> foaf:primaryTopic".
> 
> This would allow the tastier:
> 
> <rdf:Description rdf:about="http://doap.net">
>    <rdfs:seeAlso>
>       <doap:ProjectProfileDocument
> rdf:resource="http://doap.net/projectAName" />
>    </rdfs:seeAlso>
>    <rdfs:seeAlso>
>       <doap:ProjectProfileDocument
> rdf:resource="http://doap.net/projectBName" />
>    </rdfs:seeAlso>
> ...
> </rdf:Description>
> 
> (Entries could be decorated further with things like foaf:primaryTopic
> -> doap:Project -> doap:name)

I am starting to think about it.  It may allow the RDF you cite above to
be tastier, but it's going to be a real killer for the XML/RDF
serialisation of the DOAP file itself, ie.

<Project>
...
</Project>

will go to

<ProjectProfile>
 <primaryTopic>
   <Project>
   </Project>
 </primaryTopic>
</ProjectProfile>

at best.

This situation sucks a bit.

I don't know if there's any possible alternatives.  One way is to
specify the extra-RDF semantic that if there's only one Project per file
then it implies the existence of a ProjectProfile.  This is about as
undesirable as the extra markup, however.

I've got a clear requirement from a few users now for a meaningful way
to use a URI to point to a document describing exactly one project, so I
need to find a solution.

Input is required from those who've deployed DOAP here.  How much do you
care about the simplicity of the XML serialization?  Can you see other
ways forward?

-- Edd