New issue 408 by Stev...@gmail.com: Document and minimise minimum RDF
requirements
http://code.google.com/p/simal/issues/detail?id=408
I've been having a few issues with submitting RDF descriptions of projects
which later cause exceptions because fields are missing or blank. It would
be good to work out what the minimum required fields are, and document that.
In addition, it would be good that the minimum be as bare-bones as
possible. Although it might not make sense for JISC to want to publish
information about a project that has no description, it might make sense
for some other user.
Comment #1 on issue 408 by sander.v...@oucs.ox.ac.uk: Document and minimise
minimum RDF requirements
http://code.google.com/p/simal/issues/detail?id=408
There's a test project file in the core project [1] containing only
- shortdesc
- name
- homepage
The tests in the core project pass, but that's no guarantee it works well
in the web interface. We could work with that example project though.
Note that in a few of the XML files you've attached in issues, I noticed
that you've stripped the rdf:about, leading to all projects submitting
containing:
<Project rdf:about="http://registry.oss-watch.ac.uk/">
In the doapcreator javascript the rdf:about is generated (line 349) as:
http://registry.oss-watch.ac.uk/projects/shortname
where shortname is the 'Unique project tag' in the UI.
The rdf:about is the unique identification of the project. If you keep this
the same across all project you will get strange side-effects, as these
will all be linked to the same project in some form.
Comment #2 on issue 408 by ross.gardler: Document and minimise minimum RDF
requirements
http://code.google.com/p/simal/issues/detail?id=408
It would be great to wrtite a unit test for the webapp that imports a
minimal project, like this one then retrieves all the main pages to see if
there are any major problems rendering.
We can then, as Sander suggests, use that as an example of the minimal
project data that is accepted.