Top Banner
Conclusions
141
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Conclusions

Page 2: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

LSIDs suck (sadly)

Page 3: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

“suck”is a technical term

Page 4: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

DOIs suck ($ € £ )

Page 5: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Handles suck less

Page 6: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Metadata matters

Page 7: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

RDF rocks

Page 8: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

XML schema suck

Page 9: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

What we need:

Page 10: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Unique identifiers

Page 11: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Resolvable

Page 12: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Have metadata

Page 13: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Taxonomic names aren’t enough

Page 14: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Names have too much information

Cherie Booth

Page 15: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Cherie Booth Cherie Blair

Names can change when circumstances change

Page 16: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Jonathon Roughgarden = Joan Roughgarden

Names carry meaning

QuickTime™ and aTIFF (Uncompressed) decompressor

are needed to see this picture.

QuickTime™ and aTIFF (Uncompressed) decompressor

are needed to see this picture.

Page 17: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Semantically opaque

Page 18: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

identifier has no meaning

Page 19: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

trouble with meaning

Page 20: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Zbtb7

Page 21: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

POK erythroid myeloid ontogenic factor

Page 22: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

POK erythroid myeloid ontogenic factor

Page 23: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Pokemon gene

Page 24: Conclusions. LSIDs suck (sadly) “suck”is a technical term.
Page 25: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Pokemon causes cancer

Page 26: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Funny!

Page 27: Conclusions. LSIDs suck (sadly) “suck”is a technical term.
Page 28: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Not funny

Page 29: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Zbtb7

Page 30: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Zbtb7

Page 31: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

LSID parts

Page 32: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Opaque is a myth

Page 33: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Credit card

Page 34: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

LSIDs are nice

Page 35: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Explict metadata and data access

Page 36: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

QuickTime™ and aTIFF (LZW) decompressor

are needed to see this picture.

Page 37: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

QuickTime™ and aTIFF (LZW) decompressor

are needed to see this picture.

Page 38: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

LSIDs suck

Page 39: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Have to fuss with DNS

Page 40: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Reliant on Internet address

Page 41: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

What about DOI’s ?

Page 42: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Resolve this:

Page 43: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

doi:10.1080/10635150490264996

Page 44: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

What do you get?

Page 45: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Have subscription?

Page 46: Conclusions. LSIDs suck (sadly) “suck”is a technical term.
Page 47: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

What, no subscription?

Page 48: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Metadata?

Page 49: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Human-readable documents

Page 50: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Can’t predict what you get

Page 51: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Handles might be useful

Page 52: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

hdl:2254/20971

Page 53: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Handle to HTML

Page 54: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

HTML is XML

Page 55: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

GUID resolving to metadata

Page 56: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Metadata matters

Page 57: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

RDF

Page 58: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Resource Description Framework

Page 59: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Simple format (e.g., XML)

Page 60: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Everything is a resource…

Page 61: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

…or a literal

Page 62: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

supports inference

Page 63: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

underpins Semantic Web

Page 64: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

subject object

property

Page 65: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

“triple”

Page 66: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

http://www.w3.orgWorld Wide Web

consortium

dc:publisher

Page 67: Conclusions. LSIDs suck (sadly) “suck”is a technical term.
Page 68: Conclusions. LSIDs suck (sadly) “suck”is a technical term.
Page 69: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

RDF is everywhere

Page 70: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

RDF is everywhere

Page 71: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

RDF is everywhere

Page 72: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Existing vocabularies

Page 73: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Basic metadata (Dublin Core)

Page 74: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Geography (WGS 84)

Page 75: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Publications (PRISM)

Page 76: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

People (FOAF)

Page 77: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Rights (Creative Commons)

Page 78: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Requires you to have URIs for objects

Page 79: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

URIs include:

Page 80: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

URL

Page 81: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

URN

Page 82: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

DOI

Page 83: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

LSID

Page 84: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

RDF documents can be independent

Page 85: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Can be as small as one triple

Page 86: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Aggregate triples from different sources

Page 87: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Store in a triple store

QuickTime™ and aTIFF (LZW) decompressor

are needed to see this picture.

Page 88: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Make new inferences

Page 89: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

There are known knowns, things we know that we

know

Page 90: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

There are known unknowns, things we now

know we don’t know

Page 91: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

But there are also unknown unknowns, things we do not

know we don't know

Page 92: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

unknown knowns

Page 93: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

things we don’t know we know

Page 94: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

latent knowledge

Page 95: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

QuickTime™ and aTIFF (Uncompressed) decompressor

are needed to see this picture.

Poissonia heterantha

Coursetia heterantha

Tephrosia heterantha

QuickTime™ and aTIFF (Uncompressed) decompressor

are needed to see this picture.

Tephrosia heterantha

basionym

basionym

International Plant Names Index (IPNI)

Page 96: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

QuickTime™ and aTIFF (Uncompressed) decompressor

are needed to see this picture.

Poissonia heterantha

Coursetia heterantha

Tephrosia heterantha

QuickTime™ and aTIFF (Uncompressed) decompressor

are needed to see this picture.

basionym

International Plant Names Index (IPNI)

basionym

Poissonia heterantha Coursetia heterantha

Page 97: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

IPNI “knows” these names are synonyms

Page 98: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

But doesn’t know it knows it

Page 99: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Melissotarsus insularis

Page 100: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Melissotarsus insularis no hit

CASENT0107663-D01 DQ176312

Melissotarsus sp. BLF m1DQ176312

CASENT0107663-D01Melissotarsus insularis

1

Melissotarsus insularisMelissotarsus sp. BLF m1 =

Page 101: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

CASENT0107663-D01

DQ176312

Melissotarsus sp. BLF m1

source

subject TaxId:342313

TaxId:342313

HNS30687 Melissotarsus insularislabel

CASENT0107663-D01subject HNS30687

label

Page 102: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

GUIDs are trivial

Page 103: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

It’s about metadata

Page 104: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

It’s about inference

Page 105: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Lessons from DOIs

Page 106: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Crossref

Page 107: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

“reference backbone”

Page 108: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

add value to electronic publications

Page 109: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

$$$$$$

Page 110: Conclusions. LSIDs suck (sadly) “suck”is a technical term.
Page 111: Conclusions. LSIDs suck (sadly) “suck”is a technical term.
Page 112: Conclusions. LSIDs suck (sadly) “suck”is a technical term.
Page 113: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Crossref assigns DOI prefix

Page 114: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Crossref stores metadata

Page 115: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Crossref can be searched

Page 116: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Sound familiar?

Page 117: Conclusions. LSIDs suck (sadly) “suck”is a technical term.
Page 118: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

“Oh, the vision thing” George Bush (Snr), 1987

Page 119: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

GBIF assigns handles

Page 120: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Data sources provide identifiers

Page 121: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Data sources provide metadata and data

Page 122: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

GBIF has metadata standards

Page 123: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Data sources supply metadata to GBIF

Page 124: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Low barrier to entry

Page 125: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Data sources install Java Handle System (or

whatever)

Page 126: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

If use RDF then GBIF can support inference

Page 127: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

We learn something we didn’t know

Page 128: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Are we ready to do this?

Page 129: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Quality of service

Page 130: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

24

Page 131: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

7

Page 132: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

365

Page 133: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

downtime

Page 134: Conclusions. LSIDs suck (sadly) “suck”is a technical term.
Page 135: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Memorandum

Page 136: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

ASMX

Page 137: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

404

Page 138: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

GUIDs are easy

Page 139: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

Metadata is what counts…

Page 140: Conclusions. LSIDs suck (sadly) “suck”is a technical term.

…and persistence

Page 141: Conclusions. LSIDs suck (sadly) “suck”is a technical term.