Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Data Salon 3 - Ghent

736 views

Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Data Salon 3 - Ghent

  1. 1.
  2. 2.
  3. 3. COMPLEXITY<br />
  4. 4. NOT<br />
  5. 5. COMPUTATIONAL<br />
  6. 6. OR<br />
  7. 7. MATHEMATICAL<br />
  8. 8. P<br />NTIME<br />NP<br />EXPTIME<br />NC<br />DTIME<br />NEXPTIME<br />
  9. 9.
  10. 10. NO<br />
  11. 11. SIMPLER PROBLEMS<br />
  12. 12. WHERE THE BRAIN SAYS<br />
  13. 13. F<br />W<br />T<br />
  14. 14.
  15. 15.
  16. 16. A1,A2,A3,A4<br />
  17. 17. A1<br />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).<br />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.<br />
  18. 18. ONLY 6 CLICKS TO FULL TEXT<br />
  19. 19.
  20. 20. F<br />W<br />T<br />
  21. 21. STANDARDS<br />TOOLBOX<br />
  22. 22. OWL<br />SPARQL<br />EAD<br />XML<br />MARC21<br />FRBR<br />CSS<br />XML-SCHEMA<br />Unicode<br />Z39.50<br />ISAAD<br />DTD<br />Z39.88<br />METS<br />XSLT<br />SSSOAP<br />RDF/XML<br />Handle<br />UTF-8<br />CQL<br />GRRRRRDL<br />
  23. 23. LOVE FOR BOOLEANS<br />
  24. 24. WARNING: REAL CODE<br />if (!$loginAccount or (($userRoleeq &apos;reviewer&apos;) and !$loginAccount-&gt;{departmentRights}) or<br /> ($userRoleeq &apos;localAdmin&apos; and !$loginAccount-&gt;{isLocalAdmin}) or<br /> (($userRoleeq &apos;superAdmin&apos;) and !$loginAccount-&gt;{isSuperAdminAccount})) {<br />…<br />}<br />
  25. 25. LICENCED /PUBLIC DOMAIN<br />
  26. 26. DIGITAL PRESERVATION<br />
  27. 27. F<br />W<br />T<br />
  28. 28. Law of conservation of trouble?<br />
  29. 29. Origin in Trade-Off’s?<br />Interpretable (conceptual distance): humans -&gt; machines<br />Processing (time, production): slow -&gt; fast<br />Extensible: namespaces -&gt; bigger model<br />Community: my group -&gt; your group<br />Cost of production: $$ -&gt; $$$$<br />Security<br />Application Domain: generic (e.g. HTML) -&gt; data models<br />Tradition: If it ain’t broke..<br />Law<br />Future promises: If I do this then I will …<br />Compatibility: forwards -&gt; backwards <br />
  30. 30. OR<br />
  31. 31. INCOMPLETE INFORMATION?<br />
  32. 32. TIME/CONTEXT?<br />At this moment in time we had only access to (…)<br />
  33. 33. Actors aren’t RATIONAL?<br />
  34. 34. Feature Creep<br />Fallacies of Argumentation<br />Community Pressure?<br />Wrong Business Model<br />Not Invented here<br />Bricolage<br />Funding<br />
  35. 35. LESS = MORE<br />
  36. 36. WORSE = BETTER<br />
  37. 37. Richard Gabriel - 1989<br />On Simplicity<br />The design must be simple, both in implementation and interface.<br />Better: simpler implementation <br /> than:<br /> simpler interface<br />
  38. 38. Richard Gabriel - 1989<br />On Correctness<br />The design must be correct in all observable aspects. It is slightly better to be simple than correct.<br />Better:simpler design<br />than:<br />correct design<br />
  39. 39. Richard Gabriel - 1989<br />On Consistency<br />Consistency can be sacrificed for simplicity<br />Better: consistency sacrificed in some cases for simplicity<br /> than:<br /> design must be consistent in all aspects<br />
  40. 40. Richard Gabriel - 1989<br />On Completeness<br />Completeness can be sacrificed in favor of any other quality<br />Better: simplicity may overrule completeness<br />than:<br /> simplicity is not allowed to reduce completeness<br />
  41. 41. SIMPLICITY produces successful software<br />SIMPLICITY takes much less time and effort to produce and adapt<br />SIMPLICITY spreads much rapidly, long before any complete, correct, constitent programs sees the market<br />
  42. 42. THANKS :-)<br />PATRICK HOCHSTENBACH – GHENT UNIVERSITY LIBRARY<br />http://lib.ugent.beDATASALON-3 OCT 2009GENT<br />

×