Leigh Dodds has drafted a diagram illustrating relationships between resources in an effort to understand and describe Dataset and API discovery in Linked Data. He writes, “While there’s been lots of research done on finding and using (semantic) web services I’m initially interested in supporting the kind of bootstrapping use cases covered by Autodiscovery. We can characterise that use case as helping to answer the following kinds of questions: Given a resource URI, how can I find out which dataset it is from? Given a dataset URI, how can I find out which resources it contains and which APIs might let me interact with it? Given a domain on the web, how can I find out whether it exposes some machine-readable data? Where is the SPARQL endpoint for this dataset?”
He end the list, “More succinctly: can we follow our nose to find all related data and APIs? I decided to try and draw a diagram to illustrate the different resources involved and their connections. I’ve included a small version [above].” Dodds goes on, “Lets run through the links between different types of resources: (1) From Dataset to Sparql Endpoint (and Item Lookup, and Open Search Description): this is covered by VoiD which provides simple predicates for linking a dataset to three types of resources. I’m not aware of other types of linking yet, but it might be nice to support reconciliation APIs. (2) From Well-Known VoiD Description (background) to Dataset. This well known URL allows a client to find the “top-level” VoiD description for a domain. It’s not clear what that entails, but I suspect the default option will be to serve a basic description of a single dataset, with reference to sub-sets (void:subset) where appropriate. There might also just be rdfs:seeAlso links.”
Read more here.
Image: Courtesy Leigh Dodds