Ok, you press copy all, and Export to RDF/XML, and you get some RDF/XML. As you might expect, the terms are given local namespaces. So how can you tell Exhibit that your terms come from vocabularies like FOAF, DC, or whatever? This is maybe especially desirable if your data comes from RDF in the first place, and you want to preserve the semantics.
Here's what I've found so far, hopefully someone can point out solutions to the problems: You can give properties a "uri" property. (The JSON->SPARQL->JSON php script I mentioned before stupidly made use of an "iri" property; I'll change this.) This lets you use proper vocabularies for your properties. You can give each item a "uri" property, but all this does is give you the 'real' uri in the html display (for URI:). You still get the uri-as-fragment-id in the rdf:about. Also, even if this did work (one could presumably modify the exporter script to do this), Exhibit doesn't use the uri as the id (it defaults to the label), so you've got to have a lot of bloat and duplication in your json if you're using the uri as the Exhibit id. Is there a way to tell Exhibit to use another property as id? The "type" property comes out as <rdf:type>[whatever the string key for the 'type' JSON object was]</rdf:type>, even if the "type" object has a uri. You can make the key a uri, but it isn't very human friendly in the display So is there a way of writing JSON that Exhibit can use, and then export to RDF/XML with semantics intact, or would you have to modify the RDF/XML exporter script to do this? Cheers, Keith _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
