The Future of the Journal

4,318 views

Published on

Updated version of slides ESWC 2010 AI Mashup session

Published in: Technology, Education
1 Comment
9 Likes
Statistics
Notes
No Downloads
Views
Total views
4,318
On SlideShare
0
From Embeds
0
Number of Embeds
1,318
Actions
Shares
0
Downloads
86
Comments
1
Likes
9
Embeds 0
No embeds

No notes for slide

The Future of the Journal

  1. 1. The Future of the Journal Anita de Waard , a.dewaard@elsevier.com Disruptive Technologies Director, Elsevier Labs June 3, 2010
  2. 2. Science is made of information... 2
  3. 3. Science is made of information... ...that gets created... 2
  4. 4. Science is made of information... ...that gets created... ... and destroyed. 2
  5. 5. What is the problem? 3
  6. 6. What is the problem? 1. Researchers can’t keep track of their data. 3
  7. 7. What is the problem? 1. Researchers can’t keep track of their data. 2. Data is not stored in a way that is easy for authors. 3
  8. 8. What is the problem? 1. Researchers can’t keep track of their data. 2. Data is not stored in a way that is easy for authors. 3. For readers, article text is not linked to the underlying data. 3
  9. 9. The Vision Work done with Ed Hovy, Phil Bourne, Gully Burns and Cartic Ramakrishnan 4
  10. 10. The Vision Work done with Ed Hovy, Phil Bourne, Gully Burns and Cartic Ramakrishnan 1. Research: Each item in the system has metadata metadata (including provenance) and relations to other data items metadata added to it. metadata metadata metadata 4
  11. 11. The Vision Work done with Ed Hovy, Phil Bourne, Gully Burns and Cartic Ramakrishnan 1. Research: Each item in the system has metadata metadata (including provenance) and relations to other data items metadata added to it. 2. Workflow: All data items created in the lab are added metadata to a (lab-owned) workflow system. metadata metadata 4
  12. 12. The Vision Work done with Ed Hovy, Phil Bourne, Gully Burns and Cartic Ramakrishnan 1. Research: Each item in the system has metadata metadata (including provenance) and relations to other data items metadata added to it. 2. Workflow: All data items created in the lab are added metadata to a (lab-owned) workflow system. 3. Authoring: A paper is written in an authoring tool which can pull data with provenance from the workflow tool in the appropriate representation into the document. metadata metadata Rats were subjected to two grueling tests (click on fig 2 to see underlying data). These results suggest that the neurological pain pro- 4
  13. 13. The Vision Work done with Ed Hovy, Phil Bourne, Gully Burns and Cartic Ramakrishnan 1. Research: Each item in the system has metadata metadata (including provenance) and relations to other data items metadata added to it. 2. Workflow: All data items created in the lab are added metadata to a (lab-owned) workflow system. 3. Authoring: A paper is written in an authoring tool which can pull data with provenance from the workflow tool in the appropriate representation into the document. metadata 4. Editing and review: Once the co-authors agree, the paper is ‘exposed’ to the editors, who in turn expose it to metadata reviewers. Reports are stored in the authoring/editing system, the paper gets updated, until it is validated. Rats were subjected to two grueling tests (click on fig 2 to see underlying data). These results suggest that the neurological pain pro- Review Revise Edit 4
  14. 14. The Vision Work done with Ed Hovy, Phil Bourne, Gully Burns and Cartic Ramakrishnan 1. Research: Each item in the system has metadata metadata (including provenance) and relations to other data items metadata added to it. 2. Workflow: All data items created in the lab are added metadata to a (lab-owned) workflow system. 3. Authoring: A paper is written in an authoring tool which can pull data with provenance from the workflow tool in the appropriate representation into the document. metadata 4. Editing and review: Once the co-authors agree, the paper is ‘exposed’ to the editors, who in turn expose it to metadata reviewers. Reports are stored in the authoring/editing system, the paper gets updated, until it is validated. 5. Publishing and distribution: When a paper is published, a collection of validated information is exposed to the world. It remains connected to its related Rats were subjected to two data item, and its heritage can be traced. grueling tests (click on fig 2 to see underlying data). These results suggest that the neurological pain pro- Review Revise Edit 4
  15. 15. The Vision Work done with Ed Hovy, Phil Bourne, Gully Burns and Cartic Ramakrishnan 1. Research: Each item in the system has metadata metadata (including provenance) and relations to other data items metadata added to it. 2. Workflow: All data items created in the lab are added metadata to a (lab-owned) workflow system. 3. Authoring: A paper is written in an authoring tool which can pull data with provenance from the workflow tool in the appropriate representation into the document. metadata 4. Editing and review: Once the co-authors agree, the paper is ‘exposed’ to the editors, who in turn expose it to metadata reviewers. Reports are stored in the authoring/editing system, the paper gets updated, until it is validated. 5. Publishing and distribution: When a paper is published, a collection of validated information is exposed to the world. It remains connected to its related Rats were subjected to two data item, and its heritage can be traced. grueling tests (click on fig 2 to see underlying 6. User applications: distributed applications run on this data). These results suggest that ‘exposed data’ universe. the neurological pain pro- Some other publisher Review Revise Edit 4
  16. 16. What is needed to get there? tool builders standards bodies institutes, funding bodies, individuals 5
  17. 17. What is needed to get there? A. Workflow tools: Linked-data-based workflow tools for all science, are scalable, safe, and user-friendly tool builders standards bodies institutes, funding bodies, individuals 5
  18. 18. What is needed to get there? A. Workflow tools: Linked-data-based workflow tools for all science, are scalable, safe, and user-friendly tool builders B. Authoring and reviewing tools: which enable use of rich and provenance-tracked elements standards bodies institutes, funding bodies, individuals 5
  19. 19. What is needed to get there? A. Workflow tools: Linked-data-based workflow tools for all science, are scalable, safe, and user-friendly tool builders B. Authoring and reviewing tools: which enable use of rich and provenance-tracked elements standards bodies C. Metadata standards: Standards that allow interoperable exchange of information on any knowledge item created in a lab, including provenance and privacy/IPR rights institutes, funding bodies, individuals 5
  20. 20. What is needed to get there? A. Workflow tools: Linked-data-based workflow tools for all science, are scalable, safe, and user-friendly tool builders B. Authoring and reviewing tools: which enable use of rich and provenance-tracked elements standards bodies C. Metadata standards: Standards that allow interoperable exchange of information on any knowledge item created in a lab, including provenance and privacy/IPR rights D. Social change: Scientists need to realize they should annotate their work institutes, funding bodies, individuals 5
  21. 21. What is needed to get there? A. Workflow tools: Linked-data-based workflow tools for all science, are scalable, safe, and user-friendly tool builders B. Authoring and reviewing tools: which enable use of rich and provenance-tracked elements standards bodies C. Metadata standards: Standards that allow interoperable exchange of information on any knowledge item created in a lab, including provenance and privacy/IPR rights D. Social change: Scientists need to realize they should annotate their work institutes, funding bodies, individuals E. Semantic/Linked Data XML repositories. 5
  22. 22. What is needed to get there? A. Workflow tools: Linked-data-based workflow tools for all science, are scalable, safe, and user-friendly tool builders B. Authoring and reviewing tools: which enable use of rich and provenance-tracked elements standards bodies C. Metadata standards: Standards that allow interoperable exchange of information on any knowledge item created in a lab, including provenance and privacy/IPR rights D. Social change: Scientists need to realize they should annotate their work institutes, funding bodies, individuals E. Semantic/Linked Data XML repositories. F. Publishing systems that run application servers. 5
  23. 23. What is needed to get there? A. Workflow tools: Linked-data-based workflow tools for all science, are scalable, safe, and user-friendly tool builders B. Authoring and reviewing tools: which enable use of rich and provenance-tracked elements standards bodies C. Metadata standards: Standards that allow interoperable exchange of information on any knowledge item created in a lab, including provenance and privacy/IPR rights D. Social change: Scientists need to realize they should annotate their work institutes, funding bodies, individuals E. Semantic/Linked Data XML repositories. publishers F. Publishing systems that run application servers. 5
  24. 24. What is needed to get there? A. Workflow tools: Linked-data-based workflow tools for all science, are scalable, safe, and user-friendly tool builders B. Authoring and reviewing tools: which enable use of rich and provenance-tracked elements standards bodies C. Metadata standards: Standards that allow interoperable exchange of information on any knowledge item created in a lab, including provenance and privacy/IPR rights D. Social change: Scientists need to realize they should annotate their work institutes, funding bodies, individuals E. Semantic/Linked Data XML repositories. publishers F. Publishing systems that run application servers. publishers 5
  25. 25. Workflow tools are scaling up! 6
  26. 26. Workflow tools are scaling up! http://MyExperiment.org 6
  27. 27. Workflow tools are scaling up! http://VisTrails.org http://MyExperiment.org 6
  28. 28. Workflow tools are scaling up! http://VisTrails.org http://MyExperiment.org http://wings.isi.edu/ 6
  29. 29. Linked Data for Elsevier 10 7
  30. 30. Linked Data for Elsevier <ce:section id=#123> 10 7
  31. 31. Linked Data for Elsevier this says <ce:section id=#123> mice like cheese 10 7
  32. 32. Linked Data for Elsevier said @anita on May 31 2010 this says <ce:section id=#123> mice like cheese 10 7
  33. 33. Linked Data for Elsevier but we all know she was jetlagged then said @anita on May 31 2010 this says <ce:section id=#123> mice like cheese 10 7
  34. 34. Linked Data for Elsevier immutable, $$, proprietary but we all know she was jetlagged then said @anita on May 31 2010 this says <ce:section id=#123> mice like cheese 10 7
  35. 35. Linked Data for Elsevier immutable, $$, proprietary dynamic, personal, task-driven, - open? but we all know she was jetlagged then said @anita on May 31 2010 this says <ce:section id=#123> mice like cheese 10 7
  36. 36. Semantic annotation grid 11 8
  37. 37. Semantic annotation grid 11 8
  38. 38. Granularity Semantic annotation grid collection document claim triple entity 11 8
  39. 39. Granularity Semantic annotation grid collection document claim triple entity Moment measure author/editor typesetter/production reader/data minin 11 8
  40. 40. Granularity Semantic annotation grid collection document claim triple entity Moment measure author/editor typesetter/production reader/data minin Meansmanual semi-automated automated11 8
  41. 41. Granularity Semantic annotation grid collection document claim triple Automated Copy Editing entity Moment measure author/editor typesetter/production reader/data minin Meansmanual semi-automated automated11 8
  42. 42. Granularity Semantic annotation grid collection document claim triple Automated Copy Editing entity Moment measure author/editor typesetter/production reader/data minin Reflect Meansmanual semi-automated automated11 8
  43. 43. .XMP RDF in all our PDFs: DC + PRISM 12 9
  44. 44. Application server: an ecosystem open to accelerate science
  45. 45. Application server: an app-driven ecosystem
  46. 46. Application server: an example

×