際際滷shows by User: adamshepherd7186 / http://www.slideshare.net/images/logo.gif 際際滷shows by User: adamshepherd7186 / Mon, 21 Dec 2015 21:46:17 GMT 際際滷Share feed for 際際滷shows by User: adamshepherd7186 Linked Data: Forming Partnerships at the Data Layer #AGU15 (IN12A-03) /adamshepherd7186/linked-data-forming-partnerships-at-the-data-layer-agu15-in12a03 in12a-03-151221214617
Data are often contextualized, and therefore trapped, by software created for particular context. For data to become reusable outside its intended context, it must be self-describing elevating the data schema to the data layer. Furthermore, some cases require software processes be described as data using techniques such as the PROV data model.]]>
Data are often contextualized, and therefore trapped, by software created for particular context. For data to become reusable outside its intended context, it must be self-describing elevating the data schema to the data layer. Furthermore, some cases require software processes be described as data using techniques such as the PROV data model.]]> Mon, 21 Dec 2015 21:46:17 GMT /adamshepherd7186/linked-data-forming-partnerships-at-the-data-layer-agu15-in12a03 adamshepherd7186@slideshare.net(adamshepherd7186) Linked Data: Forming Partnerships at the Data Layer #AGU15 (IN12A-03) adamshepherd7186 Data are often contextualized, and therefore trapped, by software created for particular context. For data to become reusable outside its intended context, it must be self-describing elevating the data schema to the data layer. Furthermore, some cases require software processes be described as data using techniques such as the PROV data model. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/in12a-03-151221214617-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Data are often contextualized, and therefore trapped, by software created for particular context. For data to become reusable outside its intended context, it must be self-describing elevating the data schema to the data layer. Furthermore, some cases require software processes be described as data using techniques such as the PROV data model.
Linked Data: Forming Partnerships at the Data Layer #AGU15 (IN12A-03) from Biological and Chemical Oceanography Data Management Office
]]> 314 6 https://cdn.slidesharecdn.com/ss_thumbnails/in12a-03-151221214617-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Linked Data + Drupal for Oceanographic data management /slideshow/linked-data-drupal-for-oceanographic-data-management/35544502 linkeddatadrupalslides-140605173029-phpapp01
For ocean science researchers, the success of data discovery revolves around the capability to ask complex questions of data centers like BCO-DMO. Our ability to accurately respond depends on our system's capability to understand the question, interpret its relevancy to what we know, and return those results in a way a human can digest. As the needs for responding to the grand challenges of science become more interdisciplinary, data discovery will become more dependent on information from a variety of sources to enable researchers to reliably access the data they need. To do this effectively, all data and their metadata require context, cooperation and semantic interoperability. This talk explores the current landscape of data discovery, the questions researchers ask of our software, how bad our software is at responding, and how Linked Data is a viable solution for improving those responses. Watch this presentation at: https://www.youtube.com/watch?v=wEllMpcNQFg https://austin2014.drupal.org/session/linked-data-drupal-oceanographic-data-management http://www.bco-dmo.org http://lod.bco-dmo.org/sparql]]>
For ocean science researchers, the success of data discovery revolves around the capability to ask complex questions of data centers like BCO-DMO. Our ability to accurately respond depends on our system's capability to understand the question, interpret its relevancy to what we know, and return those results in a way a human can digest. As the needs for responding to the grand challenges of science become more interdisciplinary, data discovery will become more dependent on information from a variety of sources to enable researchers to reliably access the data they need. To do this effectively, all data and their metadata require context, cooperation and semantic interoperability. This talk explores the current landscape of data discovery, the questions researchers ask of our software, how bad our software is at responding, and how Linked Data is a viable solution for improving those responses. Watch this presentation at: https://www.youtube.com/watch?v=wEllMpcNQFg https://austin2014.drupal.org/session/linked-data-drupal-oceanographic-data-management http://www.bco-dmo.org http://lod.bco-dmo.org/sparql]]> Thu, 05 Jun 2014 17:30:29 GMT /slideshow/linked-data-drupal-for-oceanographic-data-management/35544502 adamshepherd7186@slideshare.net(adamshepherd7186) Linked Data + Drupal for Oceanographic data management adamshepherd7186 For ocean science researchers, the success of data discovery revolves around the capability to ask complex questions of data centers like BCO-DMO. Our ability to accurately respond depends on our system's capability to understand the question, interpret its relevancy to what we know, and return those results in a way a human can digest. As the needs for responding to the grand challenges of science become more interdisciplinary, data discovery will become more dependent on information from a variety of sources to enable researchers to reliably access the data they need. To do this effectively, all data and their metadata require context, cooperation and semantic interoperability. This talk explores the current landscape of data discovery, the questions researchers ask of our software, how bad our software is at responding, and how Linked Data is a viable solution for improving those responses. Watch this presentation at: https://www.youtube.com/watch?v=wEllMpcNQFg https://austin2014.drupal.org/session/linked-data-drupal-oceanographic-data-management http://www.bco-dmo.org http://lod.bco-dmo.org/sparql <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/linkeddatadrupalslides-140605173029-phpapp01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> For ocean science researchers, the success of data discovery revolves around the capability to ask complex questions of data centers like BCO-DMO. Our ability to accurately respond depends on our system&#39;s capability to understand the question, interpret its relevancy to what we know, and return those results in a way a human can digest. As the needs for responding to the grand challenges of science become more interdisciplinary, data discovery will become more dependent on information from a variety of sources to enable researchers to reliably access the data they need. To do this effectively, all data and their metadata require context, cooperation and semantic interoperability. This talk explores the current landscape of data discovery, the questions researchers ask of our software, how bad our software is at responding, and how Linked Data is a viable solution for improving those responses. Watch this presentation at: https://www.youtube.com/watch?v=wEllMpcNQFg https://austin2014.drupal.org/session/linked-data-drupal-oceanographic-data-management http://www.bco-dmo.org http://lod.bco-dmo.org/sparql
Linked Data + Drupal for Oceanographic data management from Biological and Chemical Oceanography Data Management Office
]]> 1179 5 https://cdn.slidesharecdn.com/ss_thumbnails/linkeddatadrupalslides-140605173029-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Sustainable Software Decisions for Long-term Projects, AGU Fall Meeting 2013 /slideshow/sustainable-software-decisions-for-longterm-projects/30865654 ind31-03-presentation-140205141756-phpapp02
How do we develop long-term systems that keep maintenance costs low and reward us with time to innovate with limited development resources? For researchers developing software expected to exist for long-term science projects, there is one software development practice coding practice, that if employed and mastered, can lead to sustainable, flexible, software that can organically grow as your research needs evolve over time. This practice is called loose coupling. ------------------------------------- Imagine yourself a farm boy... By farm boy, I mean, systems engineer... Your systems are old, outdated... They require more and more maintenance... When what you really need to be doing is innovating. Making you less a systems engineer and more a systems caretaker. How do reclaim our role of systems engineer? Loose coupling. ------------------------------------- How do we decide what to loosely couple? 1. Volatile code - code with a likelihood to change over its lifespan 2. Code splatter - similar business logic that exists in more than one place How do we sustainably innovate with web technologies? Pick technologies that leverage what *works* about the web architecture ------------------------------------- Invited Oral Presentation at the AGU Fall Meeting 2013.]]>
How do we develop long-term systems that keep maintenance costs low and reward us with time to innovate with limited development resources? For researchers developing software expected to exist for long-term science projects, there is one software development practice coding practice, that if employed and mastered, can lead to sustainable, flexible, software that can organically grow as your research needs evolve over time. This practice is called loose coupling. ------------------------------------- Imagine yourself a farm boy... By farm boy, I mean, systems engineer... Your systems are old, outdated... They require more and more maintenance... When what you really need to be doing is innovating. Making you less a systems engineer and more a systems caretaker. How do reclaim our role of systems engineer? Loose coupling. ------------------------------------- How do we decide what to loosely couple? 1. Volatile code - code with a likelihood to change over its lifespan 2. Code splatter - similar business logic that exists in more than one place How do we sustainably innovate with web technologies? Pick technologies that leverage what *works* about the web architecture ------------------------------------- Invited Oral Presentation at the AGU Fall Meeting 2013.]]> Wed, 05 Feb 2014 14:17:56 GMT /slideshow/sustainable-software-decisions-for-longterm-projects/30865654 adamshepherd7186@slideshare.net(adamshepherd7186) Sustainable Software Decisions for Long-term Projects, AGU Fall Meeting 2013 adamshepherd7186 How do we develop long-term systems that keep maintenance costs low and reward us with time to innovate with limited development resources? For researchers developing software expected to exist for long-term science projects, there is one software development practice coding practice, that if employed and mastered, can lead to sustainable, flexible, software that can organically grow as your research needs evolve over time. This practice is called loose coupling. ------------------------------------- Imagine yourself a farm boy... By farm boy, I mean, systems engineer... Your systems are old, outdated... They require more and more maintenance... When what you really need to be doing is innovating. Making you less a systems engineer and more a systems caretaker. How do reclaim our role of systems engineer? Loose coupling. ------------------------------------- How do we decide what to loosely couple? 1. Volatile code - code with a likelihood to change over its lifespan 2. Code splatter - similar business logic that exists in more than one place How do we sustainably innovate with web technologies? Pick technologies that leverage what *works* about the web architecture ------------------------------------- Invited Oral Presentation at the AGU Fall Meeting 2013. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/ind31-03-presentation-140205141756-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> How do we develop long-term systems that keep maintenance costs low and reward us with time to innovate with limited development resources? For researchers developing software expected to exist for long-term science projects, there is one software development practice coding practice, that if employed and mastered, can lead to sustainable, flexible, software that can organically grow as your research needs evolve over time. This practice is called loose coupling. ------------------------------------- Imagine yourself a farm boy... By farm boy, I mean, systems engineer... Your systems are old, outdated... They require more and more maintenance... When what you really need to be doing is innovating. Making you less a systems engineer and more a systems caretaker. How do reclaim our role of systems engineer? Loose coupling. ------------------------------------- How do we decide what to loosely couple? 1. Volatile code - code with a likelihood to change over its lifespan 2. Code splatter - similar business logic that exists in more than one place How do we sustainably innovate with web technologies? Pick technologies that leverage what *works* about the web architecture ------------------------------------- Invited Oral Presentation at the AGU Fall Meeting 2013.
Sustainable Software Decisions for Long-term Projects, AGU Fall Meeting 2013 from Biological and Chemical Oceanography Data Management Office
]]> 997 4 https://cdn.slidesharecdn.com/ss_thumbnails/ind31-03-presentation-140205141756-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 https://cdn.slidesharecdn.com/profile-photo-adamshepherd7186-48x48.jpg?cb=1523372041 Currently, I'm interested in how semantic web technologies can help address science-driven use cases for next-generation research. I want to empower researchers who are asking complex, interdisciplinary questions by providing tools for improved data discovery leading to data reuse and new knowledge. I enjoy learning new technologies, applying the right technology to the appropriate use case, and teaching what I've learned. Toolbox: Drupal, PHP, Java, RDF, Schema.org, JSON-LD, SPARQL, OWL, jQuery, HTML5, OpenLink Virtuoso, Hydra, Golang, Python, R http://www.whoi.edu/profile/ashepherd https://cdn.slidesharecdn.com/ss_thumbnails/in12a-03-151221214617-thumbnail.jpg?width=320&height=320&fit=bounds adamshepherd7186/linked-data-forming-partnerships-at-the-data-layer-agu15-in12a03 Linked Data: Forming P... https://cdn.slidesharecdn.com/ss_thumbnails/linkeddatadrupalslides-140605173029-phpapp01-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/linked-data-drupal-for-oceanographic-data-management/35544502 Linked Data + Drupal f... https://cdn.slidesharecdn.com/ss_thumbnails/ind31-03-presentation-140205141756-phpapp02-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/sustainable-software-decisions-for-longterm-projects/30865654 Sustainable Software D...