3. COMPLEXITY

4. NOT

5. COMPUTATIONAL

6. OR

7. MATHEMATICAL

8. P NTIME NP EXPTIME NC DTIME NEXPTIME

10. NO

11. SIMPLER PROBLEMS

12. WHERE THE BRAIN SAYS

13. F W T

16. A1,A2,A3,A4

17. A1 Enkelpublicaties 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, kunnenerkendwordenals A1 (z.o. definitie van A1 publicatie in vorigevraag). Anderedocumenttypes, zoals book review, biographical item, editorial material, ..., krijgengeen A1 status en wordendaarom door de reviewer geklasseerdals V. Indienuwpublicatietochgelijkstaataaneenvolwaardigartikel (bijv. in velegevallen van editorial material), dankuntu in samenspraak met de uitgever van het tijdschriftwaarinuwbijdrageverscheen, eenvraagindienenbij Thomson Reuter om het documenttypeomtezettennaar article of review.

18. ONLY 6 CLICKS TO FULL TEXT

20. F W T

21. STANDARDS TOOLBOX

22. OWL SPARQL EAD XML MARC21 FRBR CSS XML-SCHEMA Unicode Z39.50 ISAAD DTD Z39.88 METS XSLT SSSOAP RDF/XML Handle UTF-8 CQL GRRRRRDL

23. LOVE FOR BOOLEANS

24. WARNING: REAL CODE if (!$loginAccount or (($userRoleeq 'reviewer') and !$loginAccount->{departmentRights}) or ($userRoleeq 'localAdmin' and !$loginAccount->{isLocalAdmin}) or (($userRoleeq 'superAdmin') and !$loginAccount->{isSuperAdminAccount})) { … }

25. LICENCED /PUBLIC DOMAIN

26. DIGITAL PRESERVATION

27. F W T

28. Law of conservation of trouble?

29. 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

30. OR

31. INCOMPLETE INFORMATION?

32. TIME/CONTEXT? At this moment in time we had only access to (…)

33. Actors aren’t RATIONAL?

34. Feature Creep Fallacies of Argumentation Community Pressure? Wrong Business Model Not Invented here Bricolage Funding

35. LESS = MORE

36. WORSE = BETTER

37. Richard Gabriel - 1989 On Simplicity The design must be simple, both in implementation and interface. Better: simpler implementation than: simpler interface

38. Richard Gabriel - 1989 On Correctness The design must be correct in all observable aspects. It is slightly better to be simple than correct. Better:simpler design than: correct design

39. Richard Gabriel - 1989 On Consistency Consistency can be sacrificed for simplicity Better: consistency sacrificed in some cases for simplicity than: design must be consistent in all aspects

40. Richard Gabriel - 1989 On Completeness Completeness can be sacrificed in favor of any other quality Better: simplicity may overrule completeness than: simplicity is not allowed to reduce completeness

41. SIMPLICITY produces successful software SIMPLICITY takes much less time and effort to produce and adapt SIMPLICITY spreads much rapidly, long before any complete, correct, constitent programs sees the market

42. THANKS :-) PATRICK HOCHSTENBACH – GHENT UNIVERSITY LIBRARY http://lib.ugent.beDATASALON-3 OCT 2009GENT