HughP / simal

Automatically exported from code.google.com/p/simal
0 stars 0 forks source link

Some invalid DOAP uploads, cause 500s when later attempting to display project information #293

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I uploaded some RDF/XML[0] that was well-formed but which didn't respect the 
DOAP ontology (i.e. resources in place of literals). Simal accepted the upload 
and added it to its triplestore.

When searching for the project I had added, it appeared in the search results, 
but when I attempted to view the project details it 500s and displays 'Internal 
error'.

When I approached Sander about this, the logs showed that I'd included:

  [ doap:anon-root <http://some/resource/> ]

The DOAP ontology states that the range of doap:anon-root is a literal, and 
Simal was casting the object of this statement to a Literal without checking.

[0] http://mollyproject.org/rdf

Original issue reported on code.google.com by asd.ox.a...@googlemail.com on 15 Jun 2010 at 7:50

GoogleCodeExporter commented 9 years ago
Changed issue title since Simal does validate imports, but not as completely as 
it might. 

There are two issues here:

1) validate against th RDF schema
2) degrade gracefully in the case of a 500

these should probably be split into seperate issues. 

Original comment by ross.gardler on 15 Jun 2010 at 8:38

GoogleCodeExporter commented 9 years ago
this seems to relate to issue 165 (add a tool to validate RDF model)

Original comment by john.mor...@yahoo.com on 20 Jun 2010 at 1:23

GoogleCodeExporter commented 9 years ago
Lowering priority. This is a "user error". It's certainly true that Simal 
should address this, but the real problem is to provide a complete validation 
rather than this specific problem exposed by not having one.

See Issue 165 as suggested by John.

Original comment by ross.gardler on 3 Aug 2010 at 10:39