4. Why provide a public SPARQL endpoint
• A 10 man wet laboratory can not afford:
5. Why provide a public SPARQL endpoint
• A 10 man wet laboratory can not afford:
– to host their own database in house holding
all or even a bit of all life science data.
6. Why provide a public SPARQL endpoint
• A 10 man wet laboratory can not afford:
– to host their own database in house holding
all or even a bit of all life science data.
– not to have access, and use, existing life
science information.
7. ← Not CPU Time...
But Brain Time
↓
The right kind of optimisation
8. Why provide a public SPARQL endpoint
• Classical SQL can be provided on the web
–Is not practical
–No federation
–Poor standards conformance
• Local SQL is expensive
• Local JSON is no better
• Nor is local XML
11. Why not some other graph database?
Ecosystem
RDF enables sharing and reuse of data at low cost
Identity Precision Standards
12. Why provide a public SPARQL endpoint
• Document centric REST is not enough
–Swiss-Prot available as REST
–(over e-mail !!) since 1986
–expasy.ch since 1993
–www.uniprot.org since 2002
• Most user use a GUI not a CLI
• developers build GUI on a CLI
16. Real users
Mix between hard analytics and super specific
Estimate somewhere between:
400 - 1200 real humans per month
We know they are real because they take
holidays ;)