diff --git a/talks-public/2017-09-19-RDA-IG/2017-09-19-RDA-IG.org b/talks-public/2017-09-19-RDA-IG/2017-09-19-RDA-IG.org index d6c142e..a20426e 100644 --- a/talks-public/2017-09-19-RDA-IG/2017-09-19-RDA-IG.org +++ b/talks-public/2017-09-19-RDA-IG/2017-09-19-RDA-IG.org @@ -1,231 +1,240 @@ #+COLUMNS: %40ITEM %10BEAMER_env(Env) %9BEAMER_envargs(Env Args) %10BEAMER_act(Act) %4BEAMER_col(Col) %10BEAMER_extra(Extra) %8BEAMER_opt(Opt) #+TITLE: Software Ontologies and Metadata Schemes #+SUBTITLE: Introduction # does not allow short title, so we override it for beamer as follows : # +BEAMER_HEADER: \title[Software Ontologies]{Preserving Software with descriptive metadata} #+BEAMER_HEADER: \author[Morane Gruenpeter(Inria)]{{ Morane Gruenpeter (Inria)}} #+AUTHOR: Morane Gruenpeter #+DATE: September 19, 2017 #+EMAIL: morane.gg@gmail.com #+DESCRIPTION: Preserving the technological knowledge with descriptive metadata #+KEYWORDS: software ontologies preservation knowledge metadata # # # Prelude contains all the information needed to export the main beamer latex source # #+INCLUDE: "../../common/modules/prelude.org" :minlevel 1 # #+INCLUDE: "../../common/modules/169.org" #+BEAMER_HEADER: \institute{Inria, Software Heritage} * Preliminary questions ** Preliminary questions :PROPERTIES: :CUSTOM_ID: thesourcecode :END: #+BEGIN_QUOTE “Ontologies are agreements, made in a social context, to accomplish some objectives. It's important to understand those objectives, and be guided by them."\\ \hfill T. Gruber, The Pragmatics of Ontology, 2003 #+END_QUOTE #+Beamer: \pause *** /Software Ontology/ :PROPERTIES: :BEAMER_env: block :BEAMER_act: +- :END: + What is software ? + With what terms should we describe a /software artifact/? + What about /software source code/ ? * Metadata about Software Source Code ** Metadata about Software Source Code :PROPERTIES: :CUSTOM_ID: softwareisdifferent :END: *** Software metadata objectives manage, share, discover, archive /software source code/ *** Use cases :B_block:BMCOL: :PROPERTIES: :BEAMER_col: :BEAMER_env: block :END: - *semantic search*: find software by author, version, keywords - browse /source code/ with context information - cite and be cited *** :B_ignoreheading: :PROPERTIES: :BEAMER_env: ignoreheading :END: *** LOV- Linked open vocabularies \hfill /“Vocabularies provide the *semantic glue* enabling data to become *meaningful data*. ”/ * Where is the metadata available ? ** Where is the metadata available ? *** catalogs and registries :B_block: :PROPERTIES: :BEAMER_COL: .4 :BEAMER_env: block :END: #+ATTR_LATEX: :width \extblockscale{\linewidth} - libraries.io - OpenHub - OntoSoft *** Publisher's repositories :B_block: :PROPERTIES: :BEAMER_COL: .4 :BEAMER_env: block :END: #+ATTR_LATEX: :width \extblockscale{\linewidth} - GitHub - Bitbucket - SourceForge #+BEAMER: \pause *** advantages and drawbacks :B_block: :PROPERTIES: :BEAMER_env: block :BEAMER_opt: :END: | | registries | repositories | |--------------+-------------------------+--------------------------------| | accuracy | - not created by author | + added by authors/maintainers | | completeness | + very detailed | - not a priority | | longevity | - depends on registry | - depends on publisher | ** Where is the metadata available ? *** in the /software source code/ itself :B_block: :PROPERTIES: :BEAMER_env: block :BEAMER_opt: :END: - package management file - CITATION file - .About file - codemeta.json file #+BEAMER: \pause *** advantages and drawbacks :B_block: :PROPERTIES: :BEAMER_env: block :BEAMER_opt: :END: | | metadata file | |--------------+-------------------------------------------------------| | accuracy | + created by author and evolves with code | | completeness | + freedom of vocabulary and terms used | | longevity | + not dependent on platform (repository or registry ) | #+BEAMER: \pause *** \hfill *Bottomline:* to insure the archival of metadata, keep it *in* the data ** This is not /software source code/ #+latex: \begin{center} #+ATTR_LATEX: :width .38\linewidth file:this-is-not-a-pipe.png #+latex: \end{center} ** The Software Ontology /Touchstone/ *** Software Citation Principles \tiny ( FORCE11's 2015 conference and WG) :B_block: :PROPERTIES: :BEAMER_env: block :BEAMER_opt: :END: - *Importance* : first class citizen in the scholarly ecosystem - *Credit and attribution* : authors, maintainer - *Unique identification*: points to a unique, specific software version (DOI, Git SHA1 hash, etc..) - *Persistence* : identification beyond the lifespan of the software (swh-id) - *Accessibility*: url, publisher - *Specificity* : version, environment * Landscape of Software Ontologies ** Landscape of Software Ontologies #+latex: \begin{center} #+ATTR_LATEX: :width \linewidth file:metadata_landscape1.png #+latex: \end{center} ** Landscape of Software Ontologies #+latex: \begin{center} #+ATTR_LATEX: :width \linewidth file:metadata_landscape2.png #+latex: \end{center} ** Landscape of Software Ontologies #+latex: \begin{center} #+ATTR_LATEX: :width \linewidth file:metadata_landscape3.png #+latex: \end{center} ** Landscape of Software Ontologies #+latex: \begin{center} #+ATTR_LATEX: :width \linewidth file:metadata_landscape4.png #+latex: \end{center} ** Landscape of Software Ontologies #+latex: \begin{center} #+ATTR_LATEX: :width \linewidth file:metadata_landscape5.png #+latex: \end{center} ** Landscape of Software Ontologies #+latex: \begin{center} #+ATTR_LATEX: :width \linewidth file:metadata_landscape6.png #+latex: \end{center} * The CodeMeta Initiative ** The CodeMeta Initiative *** A Rosetta Stone for Metadata in Scientific Software :B_block: :PROPERTIES: :BEAMER_env: block :BEAMER_opt: :END: CodeMeta aims to create a framework {*schema*, *crosswalk*, *guidlines*} \\ that can be used to *standarize the exchange* of software metadata *** Advantages :B_block: :PROPERTIES: :BEAMER_env: block :BEAMER_opt: :END: - the crosswalk table - built on schema.org \textit{SoftwareSourceCode} - an active community -** The CodeMeta Initiative -*** Where are the gaps ? :B_block: +** Discussion +*** CodeMeta -where are the gaps ? :B_block: :PROPERTIES: :BEAMER_env: block :BEAMER_opt: :END: - missing properties - missing ontologies - semantic misconceptions +*** /Software Source Code/ metadata recommendations :B_block: + :PROPERTIES: + :BEAMER_env: block + :BEAMER_opt: + :END: + - use cases + - best practices / guidlines + + * References ** Reminder *** RDA page https://www.rd-alliance.org/ig-software-source-code-rda-10th-plenary-meeting *** Working document used during the session http://bit.ly/2wggInQ diff --git a/talks-public/2017-09-19-RDA-IG/activities/questionnaire-insights.md b/talks-public/2017-09-19-RDA-IG/activities/questionnaire-insights.md new file mode 100644 index 0000000..d25991e --- /dev/null +++ b/talks-public/2017-09-19-RDA-IG/activities/questionnaire-insights.md @@ -0,0 +1,77 @@ +Participants are interested in this subject for various reasons: +- cite software +- recover software +- data needs software (without software, data is basically useless) +- discover software +- provide framework for better software discovery and research +- reuse software (with environment) +- manage software +- preserve software +- software as a first class research product +- describe properly software +- PID for software +- identify and incorporate better practices for software +- software provenance + +Use cases: +- discover software by searching for specific interest + - domain/area + - algorithm/ functionality + - data provided (software producing a certain result + with a particular data set) + - environment (software used in particular environment-distro, + compiler, etc) + - conditions for use, reuse and modification +- publish/ deposit/ archive software with associated metadata +- link software artifact to its context: + - data + - people/ authorship + - funding + - dependencies + - built form +- cite software and give due credit +- integrate software to other workflow + - reproduce software + - discover dependencies and environment needed + + +Ontologies used: +- most don't or use data ontologies +- Datacite +- CodeMeta +- DublinCore +- package management (NPM, gemspec, PYPI) + + +Properties needed: +- PID +- maintainer email +- link to compiled version +- repository retrieval link +- data input/output expected +- authorship & affiliation +- version +- description +- references +- origin source (for provenance) +- type +- description / algorithms / problem solved +- language +- revisions+ dates +- funders +- is documented & documentation link +- terms of use / license +- dependencies +- compiler +- environment (compiles / run on) +- status +- examples +- related_to (relations to other software) +- publisher +- tests link & test data + +Advantages for structured and linked data: +- help scientists discover software - better research +- better connection with data +- better credit (by linking to authors) +- backward and forward linking- better ecosystem diff --git a/talks-public/2017-09-19-RDA-IG/activities/questionnaire-summary.ods b/talks-public/2017-09-19-RDA-IG/activities/questionnaire-summary.ods new file mode 100644 index 0000000..d19c581 Binary files /dev/null and b/talks-public/2017-09-19-RDA-IG/activities/questionnaire-summary.ods differ diff --git a/talks-public/2017-09-19-RDA-IG/notes.md b/talks-public/2017-09-19-RDA-IG/notes.md new file mode 100644 index 0000000..561080e --- /dev/null +++ b/talks-public/2017-09-19-RDA-IG/notes.md @@ -0,0 +1,34 @@ +Weekly report- week 38 + +Hi everyone, + +Before taking the plane back and forgetting some of the +During the RDA conference I have discovered many subject and + +Shared challenges: +- PID +- versioning +- metadata + + +There are many metadata challenge is an + +PID IG +- an id without the metadata associated with the object it points to, +is a key component with assigning a pid + + + +WG Research Data Repository Interoperability +- @d_wilcox +- BagIT with DataCite file +- Jeffries: SWORD v.3 + +IG Preservation Tools, Techniques, and Policies +- OSF/FEDORA: @d_wilcox, @nkmeyers +- Rewriting how research is written and shared, authorea, Josh Nicholson +- Mike Kearny- CCSDS- (OAIS) Data Archive Interoperability + +WG Data versioning +- W3C - DCAT +definnig application profiles