Hi Markus,<br><br>The LSID spec suggests that RDF is the default return type but you can request different formats. We would just need to agree on names for the formats.<br><br>Thinking from a clients point of view consistency is the most important thing I guess especially if the data is going to be mixed with data from other sources. It would be far easier to write a client to handle just RDF than to handle RDF plus arbitrary other formats - perhaps with a plug in infrastructure etc etc.
<br><br>All the best,<br><br>Roger<br><br><br><br><div><span class="gmail_quote">On 9/28/06, <b class="gmail_sendername">"Döring, Markus"</b> <<a href="mailto:m.doering@bgbm.org">m.doering@bgbm.org</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>I was wondering if the LSID specs require you to return RDF/XML. Could a service also return (or even request?) Turtle, N-Triple, RDFa or whatever comes next year?
<br><br>It would be costly to switch formats using a templating system, so I am just curious.<br><br>Markus<br><br><br>-----Original Message-----<br>From: <a href="mailto:tdwg-guid-bounces@mailman.nhm.ku.edu">tdwg-guid-bounces@mailman.nhm.ku.edu
</a> [mailto:<a href="mailto:tdwg-guid-bounces@mailman.nhm.ku.edu">tdwg-guid-bounces@mailman.nhm.ku.edu</a>] On Behalf Of Steve Perry<br>Sent: Dienstag, 26. September 2006 18:12<br>To: <a href="mailto:peter.hollas@thomson.com">
peter.hollas@thomson.com</a><br>Cc: <a href="mailto:tdwg-guid@mailman.nhm.ku.edu">tdwg-guid@mailman.nhm.ku.edu</a><br>Subject: Re: [Tdwg-guid] Which TCS/RDF?<br><br><br>Hi Peter,<br><br>I was just writing a response to your question about Jena, but I'll
<br>scrap it now. Unfortunately there's no standard representation for TCS<br>in RDF at this time. Hopefully there will be one in the near future.<br><br>Jena is well suited to consuming RDF metadata, but I agree with you that
<br>it's a bit heavyweight if all you want to do is produce many instances<br>of a single class.<br><br>Visualizing the problem as one of templating and using Spring MVC is a<br>neat approach. I use Spring mostly for dependency injection and hadn't
<br>considered that it might be used to isolate this kind of software from<br>changes in the schema.<br><br>-Steve<br><br><br><br><a href="mailto:peter.hollas@thomson.com">peter.hollas@thomson.com</a> wrote:<br>> Hi,<br>
><br>> Could someone advise on which TCS/RDF ontology would be the best to<br>> implement for metadata coming from nomenclatural sources such as<br>> ZooBank? I've yet to come across anything other than a TCS XML Schema
<br>> in public circulation.<br>><br>> I've decided to do away with using the Jena API altogether for<br>> returning metadata responses from ZooBank; it seems to be rather heavy<br>> handed approach to returning what is basically a simple structured
<br>> text document. A much more flexible way to go is with a page<br>> templating system, especially when the schemata are in constant flux.<br>> A Spring Framework MVC/JSTL endpoint will allow for schemata changes
<br>> to be implemented without recompilation. The LSID metadata class will<br>> just act as a façade/decorator to the templating system.<br>><br>> Many thanks, Peter.<br>><br>> _______________________________________________
<br>> TDWG-GUID mailing list<br>> <a href="mailto:TDWG-GUID@mailman.nhm.ku.edu">TDWG-GUID@mailman.nhm.ku.edu</a><br>> <a href="http://mailman.nhm.ku.edu/mailman/listinfo/tdwg-guid">http://mailman.nhm.ku.edu/mailman/listinfo/tdwg-guid
</a><br>><br><br><br>_______________________________________________<br>TDWG-GUID mailing list<br><a href="mailto:TDWG-GUID@mailman.nhm.ku.edu">TDWG-GUID@mailman.nhm.ku.edu</a> <a href="http://mailman.nhm.ku.edu/mailman/listinfo/tdwg-guid">
http://mailman.nhm.ku.edu/mailman/listinfo/tdwg-guid</a><br><br>_______________________________________________<br>TDWG-GUID mailing list<br><a href="mailto:TDWG-GUID@mailman.nhm.ku.edu">TDWG-GUID@mailman.nhm.ku.edu</a><br>
<a href="http://mailman.nhm.ku.edu/mailman/listinfo/tdwg-guid">http://mailman.nhm.ku.edu/mailman/listinfo/tdwg-guid</a><br></blockquote></div><br><br clear="all"><br>-- <br>-------------------------------------<br> Roger Hyam
<br> Technical Architect<br> Taxonomic Databases Working Group<br>-------------------------------------<br> <a href="http://www.tdwg.org">http://www.tdwg.org</a><br> <a href="mailto:roger@tdwg.org">roger@tdwg.org</a><br> +44 1578 722782
<br>-------------------------------------<br><br>