On Feb 25, 2015, at 3:12 PM, Sarah Weissman <[log in to unmask]> wrote:

> I am kind of new to this linked data thing, but it seems like the real
> power of it is not full-text search, but linking through the use of shared
> vocabularies. So if you have data about Jane Austen in your database and
> you are using the same URI as other databases to represent Jane Austen in
> your data (say http://dbpedia.org/resource/Jane_Austen), then you (or
> rather, your software) can do an exact search on that URI in remote
> resources vs. a fuzzy text search. In other words, linked data is really
                                                    ^^^^^^^^^^^^^^^^^^^^^
> supposed to be linked by machines and discoverable through URIs. If you
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> visit the URL: http://dbpedia.org/page/Jane_Austen you can see a
> human-interpretable representation of the data a SPARQL endpoint would
> return for a query for triples {http://dbpedia.org/page/Jane_Austen ?p ?o}.
> This is essentially asking the database for all subject-predicate-object
> facts it contains where Jane Austen is the subject.


Again, seweissman++  The implementation of linked data is VERY much like the implementation of a relational database over HTTP, and in such a scenario, the URIs are the database keys. —ELM