On 4/28/13 12:27 PM, Margaret Warren wrote:
Hello All,Metadata Authoring Systems, LLC has released a completely new kind of application for images that uses linked data for metadata creation and saves the data in html+RDFa. ImageSnippets can be used both for digital asset management within the application and/or as an image publishing platform - with images shared/embedded in metadata wrappers. The application has a lot of features for linked data professionals, but it is designed to be very easy to use by people who have little or no understanding of the semantic web. In preliminary testing, most users who had no knowledge of linked data learned how to use the system very rapidly. But the system also has a number of features for advanced users, oranizations or specialized communities. Custom datasets can be built on the fly and by request, custom releases of ImageSnippets can be loaded with specialized vocabularies. The system is in very early beta testing and works best in Chrome so we urge you to test it that way. Firefox has some known bugs and other browsers have not yet been tested at all. Also - at this time, any image you link or upload into the system will be publically searchable. We welcome your feedback! http://www.imagesnippets.com Thank you, Margaret Warren
Very interesting project and certainly a useful contribution to the growing tools collection associated with RDF and RDF based Linked Data.
A few questions (* Not A Criticism *):1. What is the URL of your SPARQL endpoint? -- I ask because the results in your SPARQL query form don't expose the actual SPARQL service endpoint thereby not allowing me to access data using the SPARQL-Protocol URL patterns.
2. Are you exposing 5-star Linked Data URIs via this service? -- I ask because I took a random URI (plus one for an image I annotated) from your sample SPARQL query and passed it through the Vapour Linked Data URI verifier, without successful results [1][2].
I ask the question above because you are minting URIs that denote entities in a domain controlled by your app/service. Thus, you do have the ability to put content negotiation to use by virtue of your URI pattern choices. By that I mean, your content negotiation can be explicit (using HTTP response metadata) or implicit (hash based HTTP URIs give you that).
For instance, I was able to figure out that by substituting ".png" with ".html" in the URIs generated by your service is how I get to an (X)HTML+RDFa document that exposes the RDF metadata for the image I uploaded and annotated [3]. I successfully passed the document through the W3C RDFa distiller to get a Turtle based description document [4].
Links:1. http://uriburner.com:8000/vapour?uri=http%3A%2F%2Fwww.imagesnippets.com%2Fimgtag%2Fimages%2Fmm%40carmapro.com%2FP1010996.JPG&defaultResponse=dontmind&userAgent=vapour.sourceforge.net -- vapour report on a sample URI
2. http://uriburner.com:8000/vapour?uri=http%3A%2F%2Fwww.imagesnippets.com%2Fimgtag%2Fimages%2Fkidehen%40openlinksw.com%2FLinked_Data_Semiotic_Triangle.png&defaultResponse=dontmind&userAgent=vapour.sourceforge.net
3. http://www.imagesnippets.com/imgtag/images/[email protected]/Linked_Data_Semiotic_Triangle.html
4. http://www.w3.org/2007/08/pyRdfa/extract?uri=http%3A%2F%2Fwww.imagesnippets.com%2Fimgtag%2Fimages%2Fkidehen%40openlinksw.com%2FLinked_Data_Semiotic_Triangle.html&format=turtle&warnings=false&parser=lax&space-preserve=true .
Kingsley
-- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
smime.p7s
Description: S/MIME Cryptographic Signature
