42

Data Salon 3 - Ghent

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Data Salon 3 - Ghent
Page 2: Data Salon 3 - Ghent
Page 3: Data Salon 3 - Ghent

COMPLEXITY

Page 4: Data Salon 3 - Ghent

NOT

Page 5: Data Salon 3 - Ghent

COMPUTATIONAL

Page 6: Data Salon 3 - Ghent

OR

Page 7: Data Salon 3 - Ghent

MATHEMATICAL

Page 8: Data Salon 3 - Ghent

DTIME

EXPTIME

NTIME

NEXPTIME

NP

NC

P

Page 9: Data Salon 3 - Ghent
Page 10: Data Salon 3 - Ghent

NO

Page 11: Data Salon 3 - Ghent

SIMPLER PROBLEMS

Page 12: Data Salon 3 - Ghent

WHERE THE BRAIN SAYS

Page 13: Data Salon 3 - Ghent

W T F

Page 14: Data Salon 3 - Ghent
Page 15: Data Salon 3 - Ghent
Page 16: Data Salon 3 - Ghent

A1,A2,A3,A4

Page 17: Data Salon 3 - Ghent

A1Enkel publicaties die in de Science Citation Index, de Social Science Citation Index en de Arts & Humanities Citation Index in Web of Science het documenttype article, letter, note, review of proceedings paper krijgen, kunnen erkend worden als A1 (z.o. definitie van A1 publicatie in vorige vraag).

Andere documenttypes, zoals book review, biographical item, editorial material, ..., krijgen geen A1 status en worden daarom door de reviewer geklasseerd als V. Indien uw publicatie toch gelijkstaat aan een volwaardig artikel (bijv. in vele gevallen van editorial material), dan kunt u in samenspraak met de uitgever van het tijdschrift waarin uw bijdrage verscheen, een vraag indienen bij Thomson Reuter om het documenttype om te zetten naar article of review.

Page 18: Data Salon 3 - Ghent

ONLY 6 CLICKS TO FULL TEXT

Page 19: Data Salon 3 - Ghent
Page 20: Data Salon 3 - Ghent

WTF

Page 21: Data Salon 3 - Ghent

STANDARDS

TOOLBOX

Page 22: Data Salon 3 - Ghent

Z39.50

Z39.88

UTF-8

XML-SCHEMA

EAD

XSLT Handl

e

SSSOAPRDF/XML

ISAAD

GRRRRRDLCQL

MARC21

METS

FRBRUnicode

DTD

XML

SPARQLOWL

CSS

Page 23: Data Salon 3 - Ghent

LOVE FOR BOOLEANS

Page 24: Data Salon 3 - Ghent

if (!$loginAccount or (($userRole eq 'reviewer') and !$loginAccount->{departmentRights}) or

($userRole eq 'localAdmin' and !$loginAccount->{isLocalAdmin}) or

(($userRole eq 'superAdmin') and !$loginAccount->{isSuperAdminAccount})) {

}

WARNING: REAL CODE

Page 25: Data Salon 3 - Ghent

LICENCED /PUBLIC DOMAIN

Page 26: Data Salon 3 - Ghent

DIGITAL PRESERVATIO

N

Page 27: Data Salon 3 - Ghent

WTF

Page 28: Data Salon 3 - Ghent

Law of conservation of trouble?

Page 29: Data Salon 3 - Ghent

Origin in Trade-Off’s?• Interpretable (conceptual distance): humans ->

machines• Processing (time, production): slow -> fast• Extensible: namespaces -> bigger model• Community: my group -> your group• Cost of production: $$ -> $$$$• Security• Application Domain: generic (e.g. HTML) -> data

models• Tradition: If it ain’t broke..• Law• Future promises: If I do this then I will …• Compatibility: forwards -> backwards

Page 30: Data Salon 3 - Ghent

OR

Page 31: Data Salon 3 - Ghent

INCOMPLETE INFORMATIO

N?

Page 32: Data Salon 3 - Ghent

TIME/CONTEXT?

At this moment in time we had only access to (…)

Page 33: Data Salon 3 - Ghent

Actors aren’t RATIONAL?

Page 34: Data Salon 3 - Ghent

Feature Creep Fallacies of

Argumentation

Wrong Business Model

Bricolage

Not Invented here

Community Pressure?

Funding

Page 35: Data Salon 3 - Ghent

LESS = MORE

Page 36: Data Salon 3 - Ghent

WORSE = BETTER

Page 37: Data Salon 3 - Ghent

Richard Gabriel - 1989

On SimplicityThe design must be simple, both in implementation and interface.

Better: simpler implementation

than: simpler interface

Page 38: Data Salon 3 - Ghent

Richard Gabriel - 1989

On CorrectnessThe design must be correct in all observable aspects. It is slightly better to be simple than correct.Better: simpler design

than:correct design

Page 39: Data Salon 3 - Ghent

Richard Gabriel - 1989

On ConsistencyConsistency can be sacrificed for simplicity

Better: consistency sacrificed in some cases for simplicity

than: design must be consistent in all aspects

Page 40: Data Salon 3 - Ghent

Richard Gabriel - 1989

On CompletenessCompleteness can be sacrificed in favor of any other quality

Better:simplicity may overrule

completeness

than: simplicity is not allowed to reduce completeness

Page 41: Data Salon 3 - Ghent

SIMPLICITY produces successful softwareSIMPLICITY takes much less time and

effort to produce and adapt

SIMPLICITY spreads much rapidly, long before

any complete, correct, constitent programs sees

the market

Page 42: Data Salon 3 - Ghent

THANKS :-)

PATRICK HOCHSTENBACH – GHENT UNIVERSITY LIBRARYhttp://lib.ugent.be

DATASALON-3 OCT 2009GENT