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 79e4d38..9e02ae1 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,199 +1,228 @@ #+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 Descriptive Metadata Schemes +#+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} +* 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 Software Ontology /Touchstone/ -*** Software citation principles \tiny ( FORCE11's 2015 conference and WG) +*** Software Citation Principles \tiny ( FORCE11's 2015 conference and WG) :PROPERTIES: :BEAMER_act: +- :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 - +* The CodeMeta Initiative ** The CodeMeta Initiative -** Where are the gaps +*** Description :B_block: + :PROPERTIES: + :BEAMER_env: block + :BEAMER_opt: + :END: +an initiative to create a concept vocabulary that can be used to standarize the exchange of + software metadata across repositories and organizations + +*** Advantages :B_block: + :PROPERTIES: + :BEAMER_env: block + :BEAMER_opt: + :END: + - its metadata crosswalk table + - built on schema.org \textit{SoftwareSourceCode} + - an active community + +** The CodeMeta Initiative +*** Where are the gaps ? :B_block: + :PROPERTIES: + :BEAMER_env: block + :BEAMER_opt: + :END: + - missing properties + - missing ontologies + - semantic misconceptions * 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.pdf b/talks-public/2017-09-19-RDA-IG/activities/questionnaire.pdf new file mode 100644 index 0000000..446f1eb Binary files /dev/null and b/talks-public/2017-09-19-RDA-IG/activities/questionnaire.pdf differ diff --git a/talks-public/2017-09-19-RDA-IG/activities/questionnaire.tex b/talks-public/2017-09-19-RDA-IG/activities/questionnaire.tex index 66fd8cb..17c7bff 100644 --- a/talks-public/2017-09-19-RDA-IG/activities/questionnaire.tex +++ b/talks-public/2017-09-19-RDA-IG/activities/questionnaire.tex @@ -1,58 +1,58 @@ %This is a LaTeX template for homework assignments \documentclass{article} \usepackage[utf8]{inputenc} \usepackage{amsmath} \begin{document} \section*{Software Ontologies and Metadata Schemes} Name: \line(1,0){120} %you can change the length of the lines by changing the number in the curly brackets \\Organization: \line(1,0){90} \subsection*{Introduction} %Enter instruction text here A questionnaire to capture the \textbf{Software Source Code IG} participants uses for discovering, describing, managing and archiving \textit{Software Source Code}. \subsection*{Questions} \begin{enumerate} \item Present yourself and/or your organization. -\\\line(1,0){300} -\\\line(1,0){300} -\\\line(1,0){300} +\\\line(1,0){350} +\\\line(1,0){350} +\\\line(1,0){350} \item What is your interest in the \textbf{Software Source Code IG} ? -\\\line(1,0){300} -\\\line(1,0){300} -\\\line(1,0){300} - - -\item Do you or your organization use software metadata ? \\capturing /producing metadata (or other use case)? -\\\line(1,0){300} -\\\line(1,0){300} -\\\line(1,0){300} - -\item Are you using an existing ontology for software? \\if so why did you choose it? -\\\line(1,0){300} -\\\line(1,0){300} -\\\line(1,0){300} - - -\item Are you using Linked data? If yes, in what way? -\\\line(1,0){300} -\\\line(1,0){300} -\\\line(1,0){300} - - - -\item What are the most needed software properties in your workflow? -\\\line(1,0){300} -\\\line(1,0){300} -\\\line(1,0){300} - - - +\\\line(1,0){350} +\\\line(1,0){350} +\\\line(1,0){350} +\\\line(1,0){350} + +\item Describe use cases concerning software metadata. Which do you use in your work and research. +\\\line(1,0){350} +\\\line(1,0){350} +\\\line(1,0){350} +\\\line(1,0){350} + +\item When describing software artifacts, which ontology do you prefer using and for what reasons? +\\\line(1,0){350} +\\\line(1,0){350} +\\\line(1,0){350} +\\\line(1,0){350} + + + +\item Name the most needed software properties in your workflow? +\\\line(1,0){350} +\\\line(1,0){350} +\\\line(1,0){350} +\\\line(1,0){350} + +\item In what way do you find linking software through structured data useful? +\\\line(1,0){350} +\\\line(1,0){350} +\\\line(1,0){350} +\\\line(1,0){350} \end{enumerate} -\end{document} \ No newline at end of file +\end{document}