Re: [Treebase-devel] [dryad-dev] Re: Dryad API, advice on cyberinfastructure

[Hilmar L. <hl...@ne...>]

On May 12, 2011, at 5:50 PM, Carl Boettiger <cbo...@gm...> wrote:

> Is there anything more clever than a bunch of grep rules for distinguishing between these?  

Well, you can pack the semantics into the property, or into the resources that they connect. Personally, I loath RDF models that have a baroque number of properties because typically you end up having to hardcode these into applications that try to do something meaningful with the RDF. I.e., there is no good way to infer or deduce much about the semantics of properties. Conversely, the Semantic Web and LOD already provide the conventions and standards For resources to describe themselves on the web, so while figuring out what it is that a property connects a subject to requires a HTTP GET on the resource URI, it is the recommended (and I think most extensible) way of doing this. (Though unfortunately in our case this doesn't quite hold - yet; however, Crossref is finally starting to implement LOD-compliant DOI resolution, and the question is when DataCite DOIs will play ball too.)

> Is there a way to get the URL of the actual data file (i.e. some csv file) through the dryad API?  So far I can only return the website that contains the data file.  

Yes, it's documented on the Data Access API page on the Dryad wiki that I referred to earlier.

-hilmar

Sent with a tap.