https://wiki.softwareheritage.org/api.php?action=feedcontributions&user=Morane&feedformat=atomSoftware Heritage Wiki - User contributions [en]2024-03-28T20:06:39ZUser contributionsMediaWiki 1.31.16https://wiki.softwareheritage.org/index.php?title=Mailing_lists&diff=1745Mailing lists2023-07-19T13:07:08Z<p>Morane: fix swh-stories</p>
<hr />
<div>== Internal lists ==<br />
* [http://sympa.inria.fr/sympa/info/swh-team swh-team] — staff, private coordination list<br />
** post address: [mailto:swh-team@inria.fr swh-team@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-sysadm swh-sysadm] — system administration, private coordination list<br />
** post address: [mailto:swh-sysadm@inria.fr swh-sysadm@inria.fr]<br />
<br />
<br />
=== Partnerships (private lists) ===<br />
* [http://sympa.inria.fr/sympa/info/swh-mirrors swh-mirrors] — SWH Mirrors: the mirror network channel<br />
** post address:[mailto:swh-mirrors@inria.fr swh-mirrors@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-stories swh-stories] — SWH stories partnership to work and improve SWHAP and Stories features and guide<br />
** post address:[mailto:swh-stories@inria.fr swh-stories@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-ambassadors swh-ambassadors] — Ambassadors mailing list<br />
** post address:[mailto:swh-ambassadors@inria.fr swh-ambassadors@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/gt-logiciel-ies-swh gt-logiciel-ies-swh] — Working group with IES INRIA<br />
** post address: [mailto:gt-logiciel-ies-swh@inria.fr gt-logiciel-ies-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-sed swh-sed] — Software Heritage / SED communication channel<br />
** post address:[mailto:swh-sed@inria.fr swh-sed@inria.fr]<br />
<br />
<br />
== Public lists ==<br />
* [http://sympa.inria.fr/sympa/info/swh-devel swh-devel] — software development, public list<br />
** post address: [mailto:swh-devel@inria.fr swh-devel@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-users swh-users] — Software Heritage - user support list<br />
** post address: [mailto:swh-users@inria.fr swh-users@inria.fr]<br />
<br />
=== Working groups and Interest groups mailing lists ===<br />
* [http://sympa.inria.fr/sympa/info/swh-science swh-science] — Scientific discussion on SWH<br />
** post address: [mailto:swh-science@inria.fr swh-science@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swhap swhap] — Software Heritage Acquisition Process interest group<br />
** post address: [mailto:swhap@inria.fr swhap@inria.fr]<br />
<br />
<br />
==== Dormant groups (under 10 participants) ====<br />
* [http://sympa.inria.fr/sympa/info/elie-wg-swh elie-wg-swh] — Ethical and Legal Issues and Environment<br />
** post address: [mailto:elie-wg-swh@inria.fr elie-wg-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/sapi-wg-swh sapi-wg-swh] — Scientific Access API<br />
** post address: [mailto:sapi-wg-swh@inria.fr sapi-wg-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/miv-wg-swh miv-wg-swh] — Modeling and Ingesting Version control systems<br />
** post address: [mailto:miv-wg-swh@inria.fr miv-wg-swh@inria.fr ]<br />
* [http://sympa.inria.fr/sympa/info/direq-wg-swh direq-wg-swh] — Distribution, Replication and Query<br />
** post address: [mailto:direq-wg-swh@inria.fr direq-wg-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/opad-wg-swh opad-wg-swh] — Open Access and Open Data Working Group<br />
** post address: [mailto:opad-wg-swh@inria.fr opad-wg-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/reos-wg-swh reos-wg-swh] — Reproducibility/Replicability of Software<br />
** post address: [mailto:reos-wg-swh@inria.fr reos-wg-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/sodi-wg-swh sodi-wg-swh] — Source Discovery and Ingestion working group<br />
** post address: [mailto:sodi-wg-swh@inria.fr sodi-wg-swh@inria.fr]<br />
<br />
<br />
<br />
[[Category:Communication]]<br />
[[Category:Infrastructure]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Mailing_lists&diff=1744Mailing lists2023-07-19T13:05:40Z<p>Morane: Delete lists</p>
<hr />
<div>== Internal lists ==<br />
* [http://sympa.inria.fr/sympa/info/swh-team swh-team] — staff, private coordination list<br />
** post address: [mailto:swh-team@inria.fr swh-team@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-sysadm swh-sysadm] — system administration, private coordination list<br />
** post address: [mailto:swh-sysadm@inria.fr swh-sysadm@inria.fr]<br />
<br />
<br />
=== Partnerships (private lists) ===<br />
* [http://sympa.inria.fr/sympa/info/swh-mirrors swh-mirrors] — SWH Mirrors: the mirror network channel<br />
** post address:[mailto:swh-mirrors@inria.fr swh-mirrors@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-mirrors swh-mirrors] — SWH stories partnership to work and improve SWHAP and Stories features and guide<br />
** post address:[mailto:swh-stories@inria.fr swh-stories@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-ambassadors swh-ambassadors] — Ambassadors mailing list<br />
** post address:[mailto:swh-ambassadors@inria.fr swh-ambassadors@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/gt-logiciel-ies-swh gt-logiciel-ies-swh] — Working group with IES INRIA<br />
** post address: [mailto:gt-logiciel-ies-swh@inria.fr gt-logiciel-ies-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-sed swh-sed] — Software Heritage / SED communication channel<br />
** post address:[mailto:swh-sed@inria.fr swh-sed@inria.fr]<br />
<br />
<br />
== Public lists ==<br />
* [http://sympa.inria.fr/sympa/info/swh-devel swh-devel] — software development, public list<br />
** post address: [mailto:swh-devel@inria.fr swh-devel@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-users swh-users] — Software Heritage - user support list<br />
** post address: [mailto:swh-users@inria.fr swh-users@inria.fr]<br />
<br />
=== Working groups and Interest groups mailing lists ===<br />
* [http://sympa.inria.fr/sympa/info/swh-science swh-science] — Scientific discussion on SWH<br />
** post address: [mailto:swh-science@inria.fr swh-science@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swhap swhap] — Software Heritage Acquisition Process interest group<br />
** post address: [mailto:swhap@inria.fr swhap@inria.fr]<br />
<br />
<br />
==== Dormant groups (under 10 participants) ====<br />
* [http://sympa.inria.fr/sympa/info/elie-wg-swh elie-wg-swh] — Ethical and Legal Issues and Environment<br />
** post address: [mailto:elie-wg-swh@inria.fr elie-wg-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/sapi-wg-swh sapi-wg-swh] — Scientific Access API<br />
** post address: [mailto:sapi-wg-swh@inria.fr sapi-wg-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/miv-wg-swh miv-wg-swh] — Modeling and Ingesting Version control systems<br />
** post address: [mailto:miv-wg-swh@inria.fr miv-wg-swh@inria.fr ]<br />
* [http://sympa.inria.fr/sympa/info/direq-wg-swh direq-wg-swh] — Distribution, Replication and Query<br />
** post address: [mailto:direq-wg-swh@inria.fr direq-wg-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/opad-wg-swh opad-wg-swh] — Open Access and Open Data Working Group<br />
** post address: [mailto:opad-wg-swh@inria.fr opad-wg-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/reos-wg-swh reos-wg-swh] — Reproducibility/Replicability of Software<br />
** post address: [mailto:reos-wg-swh@inria.fr reos-wg-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/sodi-wg-swh sodi-wg-swh] — Source Discovery and Ingestion working group<br />
** post address: [mailto:sodi-wg-swh@inria.fr sodi-wg-swh@inria.fr]<br />
<br />
<br />
<br />
[[Category:Communication]]<br />
[[Category:Infrastructure]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Mailing_lists&diff=1743Mailing lists2023-07-19T13:01:34Z<p>Morane: Added all working groups and classification</p>
<hr />
<div>== Internal lists ==<br />
* [http://sympa.inria.fr/sympa/info/swh-team swh-team] — staff, private coordination list<br />
** post address: [mailto:swh-team@inria.fr swh-team@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-sysadm swh-sysadm] — system administration, private coordination list<br />
** post address: [mailto:swh-sysadm@inria.fr swh-sysadm@inria.fr]<br />
* swh-copil: Coordination comite de pilotage Software Heritage<br />
<br />
=== Partnerships (private lists) ===<br />
* swh-sponsors: Sponsors mailing list<br />
* [http://sympa.inria.fr/sympa/info/swh-mirrors swh-mirrors] — SWH Mirrors: the mirror network channel<br />
** post address:[mailto:swh-mirrors@inria.fr swh-mirrors@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-mirrors swh-mirrors] — SWH stories partnership to work and improve SWHAP and Stories features and guide<br />
** post address:[mailto:swh-stories@inria.fr swh-stories@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-ambassadors swh-ambassadors] — Ambassadors mailing list<br />
** post address:[mailto:swh-ambassadors@inria.fr swh-ambassadors@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/gt-logiciel-ies-swh gt-logiciel-ies-swh] — Working group with IES INRIA<br />
** post address: [mailto:gt-logiciel-ies-swh@inria.fr gt-logiciel-ies-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-sed swh-sed] — Software Heritage / SED communication channel<br />
** post address:[mailto:swh-sed@inria.fr swh-sed@inria.fr]<br />
<br />
<br />
== Public lists ==<br />
* [http://sympa.inria.fr/sympa/info/swh-devel swh-devel] — software development, public list<br />
** post address: [mailto:swh-devel@inria.fr swh-devel@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-users swh-users] — Software Heritage - user support list<br />
** post address: [mailto:swh-users@inria.fr swh-users@inria.fr]<br />
<br />
=== Working groups and Interest groups mailing lists ===<br />
* [http://sympa.inria.fr/sympa/info/swh-science swh-science] — Scientific discussion on SWH<br />
** post address: [mailto:swh-science@inria.fr swh-science@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swhap swhap] — Software Heritage Acquisition Process interest group<br />
** post address: [mailto:swhap@inria.fr swhap@inria.fr]<br />
<br />
<br />
==== Dormant groups (under 10 participants) ====<br />
* [http://sympa.inria.fr/sympa/info/elie-wg-swh elie-wg-swh] — Ethical and Legal Issues and Environment<br />
** post address: [mailto:elie-wg-swh@inria.fr elie-wg-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/sapi-wg-swh sapi-wg-swh] — Scientific Access API<br />
** post address: [mailto:sapi-wg-swh@inria.fr sapi-wg-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/miv-wg-swh miv-wg-swh] — Modeling and Ingesting Version control systems<br />
** post address: [mailto:miv-wg-swh@inria.fr miv-wg-swh@inria.fr ]<br />
* [http://sympa.inria.fr/sympa/info/direq-wg-swh direq-wg-swh] — Distribution, Replication and Query<br />
** post address: [mailto:direq-wg-swh@inria.fr direq-wg-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/opad-wg-swh opad-wg-swh] — Open Access and Open Data Working Group<br />
** post address: [mailto:opad-wg-swh@inria.fr opad-wg-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/reos-wg-swh reos-wg-swh] — Reproducibility/Replicability of Software<br />
** post address: [mailto:reos-wg-swh@inria.fr reos-wg-swh@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/sodi-wg-swh sodi-wg-swh] — Source Discovery and Ingestion working group<br />
** post address: [mailto:sodi-wg-swh@inria.fr sodi-wg-swh@inria.fr]<br />
<br />
<br />
<br />
[[Category:Communication]]<br />
[[Category:Infrastructure]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Mailing_lists&diff=1742Mailing lists2023-07-19T12:24:45Z<p>Morane: Divide into private and public lists</p>
<hr />
<div>== Private lists ==<br />
* [http://sympa.inria.fr/sympa/info/swh-team swh-team] — staff, private coordination list<br />
** post address: [mailto:swh-team@inria.fr swh-team@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-sysadm swh-sysadm] — system administration, private coordination list<br />
** post address: [mailto:swh-sysadm@inria.fr swh-sysadm@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-ambassadors swh-ambassadors] — Ambassadors mailing list<br />
** post address:[mailto:swh-ambassadors@inria.fr swh-ambassadors@inria.fr]<br />
<br />
== Public lists ==<br />
* [http://sympa.inria.fr/sympa/info/swh-devel swh-devel] — software development, public list<br />
** post address: [mailto:swh-devel@inria.fr swh-devel@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-science swh-science] — Scientific discussion on SWH<br />
** post address: [mailto:swh-science@inria.fr swh-science@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-users swh-users] — Software Heritage - user support list<br />
** post address: [mailto:swh-users@inria.fr swh-users@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swhap swhap] — Software Heritage Acquisition Process interest group<br />
** post address: [mailto:swhap@inria.fr swhap@inria.fr]<br />
<br />
[[Category:Communication]]<br />
[[Category:Infrastructure]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Mailing_lists&diff=1741Mailing lists2023-07-19T12:19:08Z<p>Morane: Added swh-users, swh-ambassadors, swh-science and swhap mailing lists</p>
<hr />
<div>* [http://sympa.inria.fr/sympa/info/swh-devel swh-devel] — software development, public list<br />
** post address: [mailto:swh-devel@inria.fr swh-devel@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-team swh-team] — staff, private coordination list<br />
** post address: [mailto:swh-team@inria.fr swh-team@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-sysadm swh-sysadm] — system administration, private coordination list<br />
** post address: [mailto:swh-sysadm@inria.fr swh-sysadm@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-ambassadors swh-ambassadors] — Ambassadors mailing list<br />
** post address:[mailto:swh-ambassadors@inria.fr swh-ambassadors@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-science swh-science] — Scientific discussion on SWH<br />
** post address: [mailto:swh-science@inria.fr swh-science@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swh-users swh-users] — Software Heritage - user support list<br />
** post address: [mailto:swh-users@inria.fr swh-users@inria.fr]<br />
* [http://sympa.inria.fr/sympa/info/swhap swhap] — Software Heritage Acquisition Process interest group<br />
** post address: [mailto:swhap@inria.fr swhap@inria.fr]<br />
<br />
[[Category:Communication]]<br />
[[Category:Infrastructure]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Ambassadors_onboarding&diff=1732Ambassadors onboarding2023-01-20T12:51:42Z<p>Morane: </p>
<hr />
<div>This page describe the onboarding process for [https://www.softwareheritage.org/ambassadors/ Software Heritage ambassadors].<br />
This page has moved to a closed repository on Gitlab<br />
https://gitlab.softwareheritage.org/outreach/ambassadors/onboarding</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Ambassadors_onboarding&diff=1584Ambassadors onboarding2021-06-25T09:34:09Z<p>Morane: </p>
<hr />
<div>This page describe the onboarding process for [https://www.softwareheritage.org/ambassadors/ Software Heritage ambassadors].<br />
<br />
= Checklist =<br />
<br />
== Welcome kit ==<br />
<br />
* Retrieve ambassadors physical address to send goodies:<br />
** stickers<br />
** documentation to give out (including postcards, flyers, short guides)<br />
** SWH poster (not created yet)<br />
<br />
== Administrative ==<br />
<br />
* add picture and bio to [https://www.softwareheritage.org/people/ambassadors/ ambassadors page] (not created yet)<br />
** 150x150 pixel squared picture, short bio<br />
* prepare blog post and tweet to announce (see [https://www.softwareheritage.org/2021/04/29/first-ambassador/ first announcement])<br />
<br />
== Technical setup ==<br />
<br />
* create account on the Wordpress website to get access to the [https://www.softwareheritage.org/ambassador-material/ materials page]<br />
* create account on the [https://archive.softwareheritage.org/ archive]<br />
<br />
<br />
== Communication ==<br />
<br />
* subscribe to [https://sympa.inria.fr/sympa/info/swh-ambassadors swh-ambassadors] mailing list<br />
* invite to [[IRC channels]]<br />
<br />
== Training ==<br />
<br />
* See all the information on the [https://www.softwareheritage.org/ambassador-material/ materials page]<br />
* See [https://hedgedoc.softwareheritage.org/lw-XTHaYQv2fDPJ9bIpU1Q?view FAQ page] (this page is WIP and will be moved to the website when a first complete draft is ready)<br />
<br />
= See also =<br />
A selection of presentations about '''reproducibility''':<br />
<br />
* https://annex.softwareheritage.org/public/talks/2016/2016-09-16-irif-science-crisis-software-preservation.pdf<br />
* https://annex.softwareheritage.org/public/talks/2016/2016-11-08-grenoble-rdicosmo-reproductibility-preserving-software.pdf<br />
* https://annex.softwareheritage.org/public/talks/2016/2016-11-08-grenoble-rdicosmo-reproductibility-preserving-software.mp4<br />
* https://annex.softwareheritage.org/public/talks/2017/2017-12-07-acmrepro.pdf<br />
<br />
A selection of presentations about '''archive/reference/citation''':<br />
<br />
* https://annex.softwareheritage.org/public/talks/2020/2020-07-15-ICMS.pdf<br />
* https://annex.softwareheritage.org/public/talks/2020/2020-07-15-ICMS.mp4<br />
* https://annex.softwareheritage.org/public/talks/2020/2020-05-05-biblatex-software.pdf<br />
* https://annex.softwareheritage.org/public/talks/2021/2021-01-11-RRPR.pdf<br />
* https://doi.org/10.5281/zenodo.3667713<br />
<br />
<br />
[[Category:Ambassadors]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Ambassadors_onboarding&diff=1583Ambassadors onboarding2021-06-25T09:33:56Z<p>Morane: </p>
<hr />
<div>This page describe the onboarding process for [https://www.softwareheritage.org/ambassadors/ Software Heritage ambassadors].<br />
<br />
= Checklist =<br />
<br />
== Welcome kit ==<br />
<br />
* Retrieve ambassadors physical address to send goodies:<br />
** stickers<br />
** documentation to give out (including postcards, flyers, short guides)<br />
** SWH poster (not created yet)<br />
<br />
== Administrative ==<br />
<br />
* add picture and bio to [https://www.softwareheritage.org/people/ambassadors/ ambassadors page] (not created yet)<br />
** 150x150 pixel squared picture, short bio<br />
* prepare blog post and tweet to announce (see [https://www.softwareheritage.org/2021/04/29/first-ambassador/ first announcement])<br />
<br />
== Technical setup ==<br />
<br />
* create account on the Wordpress website to get access to the [https://www.softwareheritage.org/ambassador-material/ materials page]<br />
* create account on the [[https://archive.softwareheritage.org/ archive]]<br />
<br />
<br />
== Communication ==<br />
<br />
* subscribe to [https://sympa.inria.fr/sympa/info/swh-ambassadors swh-ambassadors] mailing list<br />
* invite to [[IRC channels]]<br />
<br />
== Training ==<br />
<br />
* See all the information on the [https://www.softwareheritage.org/ambassador-material/ materials page]<br />
* See [https://hedgedoc.softwareheritage.org/lw-XTHaYQv2fDPJ9bIpU1Q?view FAQ page] (this page is WIP and will be moved to the website when a first complete draft is ready)<br />
<br />
= See also =<br />
A selection of presentations about '''reproducibility''':<br />
<br />
* https://annex.softwareheritage.org/public/talks/2016/2016-09-16-irif-science-crisis-software-preservation.pdf<br />
* https://annex.softwareheritage.org/public/talks/2016/2016-11-08-grenoble-rdicosmo-reproductibility-preserving-software.pdf<br />
* https://annex.softwareheritage.org/public/talks/2016/2016-11-08-grenoble-rdicosmo-reproductibility-preserving-software.mp4<br />
* https://annex.softwareheritage.org/public/talks/2017/2017-12-07-acmrepro.pdf<br />
<br />
A selection of presentations about '''archive/reference/citation''':<br />
<br />
* https://annex.softwareheritage.org/public/talks/2020/2020-07-15-ICMS.pdf<br />
* https://annex.softwareheritage.org/public/talks/2020/2020-07-15-ICMS.mp4<br />
* https://annex.softwareheritage.org/public/talks/2020/2020-05-05-biblatex-software.pdf<br />
* https://annex.softwareheritage.org/public/talks/2021/2021-01-11-RRPR.pdf<br />
* https://doi.org/10.5281/zenodo.3667713<br />
<br />
<br />
[[Category:Ambassadors]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Ambassadors_onboarding&diff=1580Ambassadors onboarding2021-06-19T14:12:13Z<p>Morane: /* Communication */</p>
<hr />
<div>This page describe the onboarding process for [https://www.softwareheritage.org/ambassadors/ Software Heritage ambassadors].<br />
<br />
= Checklist =<br />
<br />
== Welcome kit ==<br />
<br />
* Retrieve ambassadors physical address to send goodies:<br />
** stickers<br />
** documentation to give out (including postcards, flyers, short guides)<br />
** SWH poster (not created yet)<br />
<br />
== Administrative ==<br />
<br />
* add picture and bio to [https://www.softwareheritage.org/people/ambassadors/ ambassadors page] (not created yet)<br />
** 150x150 pixel squared picture, short bio<br />
* prepare blog post and tweet to announce (see [https://www.softwareheritage.org/2021/04/29/first-ambassador/ first announcement])<br />
<br />
== Technical setup ==<br />
<br />
* create account on the Wordpress website to get access to the [https://www.softwareheritage.org/ambassador-material/ materials page]<br />
* create account on the public wiki: [[swhwiki:Main_Page]]<br />
<br />
== Communication ==<br />
<br />
* subscribe to [https://sympa.inria.fr/sympa/info/swh-ambassadors swh-ambassadors] mailing list<br />
* invite to [[IRC channels]]<br />
<br />
== Training ==<br />
<br />
* See all the information on the [https://www.softwareheritage.org/ambassador-material/ materials page]<br />
* See [https://hedgedoc.softwareheritage.org/lw-XTHaYQv2fDPJ9bIpU1Q?view FAQ page] (this page is WIP and will be moved to the website when a first complete draft is ready)<br />
<br />
= See also =<br />
A selection of presentations about '''reproducibility''':<br />
<br />
* https://annex.softwareheritage.org/public/talks/2016/2016-09-16-irif-science-crisis-software-preservation.pdf<br />
* https://annex.softwareheritage.org/public/talks/2016/2016-11-08-grenoble-rdicosmo-reproductibility-preserving-software.pdf<br />
* https://annex.softwareheritage.org/public/talks/2016/2016-11-08-grenoble-rdicosmo-reproductibility-preserving-software.mp4<br />
* https://annex.softwareheritage.org/public/talks/2017/2017-12-07-acmrepro.pdf<br />
<br />
A selection of presentations about '''archive/reference/citation''':<br />
<br />
* https://annex.softwareheritage.org/public/talks/2020/2020-07-15-ICMS.pdf<br />
* https://annex.softwareheritage.org/public/talks/2020/2020-07-15-ICMS.mp4<br />
* https://annex.softwareheritage.org/public/talks/2020/2020-05-05-biblatex-software.pdf<br />
* https://annex.softwareheritage.org/public/talks/2021/2021-01-11-RRPR.pdf<br />
* https://doi.org/10.5281/zenodo.3667713<br />
<br />
<br />
[[Category:Ambassadors]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Ambassadors_onboarding&diff=1579Ambassadors onboarding2021-06-19T14:11:58Z<p>Morane: /* Goodies */</p>
<hr />
<div>This page describe the onboarding process for [https://www.softwareheritage.org/ambassadors/ Software Heritage ambassadors].<br />
<br />
= Checklist =<br />
<br />
== Welcome kit ==<br />
<br />
* Retrieve ambassadors physical address to send goodies:<br />
** stickers<br />
** documentation to give out (including postcards, flyers, short guides)<br />
** SWH poster (not created yet)<br />
<br />
== Administrative ==<br />
<br />
* add picture and bio to [https://www.softwareheritage.org/people/ambassadors/ ambassadors page] (not created yet)<br />
** 150x150 pixel squared picture, short bio<br />
* prepare blog post and tweet to announce (see [https://www.softwareheritage.org/2021/04/29/first-ambassador/ first announcement])<br />
<br />
== Technical setup ==<br />
<br />
* create account on the Wordpress website to get access to the [https://www.softwareheritage.org/ambassador-material/ materials page]<br />
* create account on the public wiki: [[swhwiki:Main_Page]]<br />
<br />
== Communication ==<br />
<br />
* subscribe to [https://sympa.inria.fr/sympa/info/swh-ambassadors swh-ambassadors]] mailing list<br />
* invite to [[IRC channels]]<br />
<br />
== Training ==<br />
<br />
* See all the information on the [https://www.softwareheritage.org/ambassador-material/ materials page]<br />
* See [https://hedgedoc.softwareheritage.org/lw-XTHaYQv2fDPJ9bIpU1Q?view FAQ page] (this page is WIP and will be moved to the website when a first complete draft is ready)<br />
<br />
= See also =<br />
A selection of presentations about '''reproducibility''':<br />
<br />
* https://annex.softwareheritage.org/public/talks/2016/2016-09-16-irif-science-crisis-software-preservation.pdf<br />
* https://annex.softwareheritage.org/public/talks/2016/2016-11-08-grenoble-rdicosmo-reproductibility-preserving-software.pdf<br />
* https://annex.softwareheritage.org/public/talks/2016/2016-11-08-grenoble-rdicosmo-reproductibility-preserving-software.mp4<br />
* https://annex.softwareheritage.org/public/talks/2017/2017-12-07-acmrepro.pdf<br />
<br />
A selection of presentations about '''archive/reference/citation''':<br />
<br />
* https://annex.softwareheritage.org/public/talks/2020/2020-07-15-ICMS.pdf<br />
* https://annex.softwareheritage.org/public/talks/2020/2020-07-15-ICMS.mp4<br />
* https://annex.softwareheritage.org/public/talks/2020/2020-05-05-biblatex-software.pdf<br />
* https://annex.softwareheritage.org/public/talks/2021/2021-01-11-RRPR.pdf<br />
* https://doi.org/10.5281/zenodo.3667713<br />
<br />
<br />
[[Category:Ambassadors]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Ambassadors_onboarding&diff=1562Ambassadors onboarding2021-05-04T08:31:37Z<p>Morane: Create ambassadors onboarding</p>
<hr />
<div>This page describe the onboarding process for [https://www.softwareheritage.org/ambassadors/ Software Heritage ambassadors].<br />
<br />
= Checklist =<br />
<br />
== Goodies ==<br />
<br />
* Retrieve ambassadors physical address to send goodies:<br />
** stickers<br />
** documentation to give out (including postcards, flyers, short guides)<br />
** SWH poster (not created yet)<br />
<br />
== Administrative ==<br />
<br />
* add picture and bio to [https://www.softwareheritage.org/people/ambassadors/ ambassadors page] (not created yet)<br />
** 150x150 pixel squared picture, short bio<br />
* prepare blog post and tweet to announce (see [https://www.softwareheritage.org/2021/04/29/first-ambassador/ first announcement])<br />
<br />
== Technical setup ==<br />
<br />
* create account on the Wordpress website to get access to the [https://www.softwareheritage.org/ambassador-material/ materials page]<br />
* create account on the public wiki: [[swhwiki:Main_Page]]<br />
<br />
== Communication ==<br />
<br />
* subscribe to [https://sympa.inria.fr/sympa/info/swh-ambassadors swh-ambassadors]] mailing list<br />
* invite to [[IRC channels]]<br />
<br />
== Training ==<br />
<br />
* See all the information on the [https://www.softwareheritage.org/ambassador-material/ materials page]<br />
* See [https://hedgedoc.softwareheritage.org/lw-XTHaYQv2fDPJ9bIpU1Q?view FAQ page] (this page is WIP and will be moved to the website when a first complete draft is ready)<br />
<br />
= See also =<br />
A selection of presentations about '''reproducibility''':<br />
<br />
* https://annex.softwareheritage.org/public/talks/2016/2016-09-16-irif-science-crisis-software-preservation.pdf<br />
* https://annex.softwareheritage.org/public/talks/2016/2016-11-08-grenoble-rdicosmo-reproductibility-preserving-software.pdf<br />
* https://annex.softwareheritage.org/public/talks/2016/2016-11-08-grenoble-rdicosmo-reproductibility-preserving-software.mp4<br />
* https://annex.softwareheritage.org/public/talks/2017/2017-12-07-acmrepro.pdf<br />
<br />
A selection of presentations about '''archive/reference/citation''':<br />
<br />
* https://annex.softwareheritage.org/public/talks/2020/2020-07-15-ICMS.pdf<br />
* https://annex.softwareheritage.org/public/talks/2020/2020-07-15-ICMS.mp4<br />
* https://annex.softwareheritage.org/public/talks/2020/2020-05-05-biblatex-software.pdf<br />
* https://annex.softwareheritage.org/public/talks/2021/2021-01-11-RRPR.pdf<br />
* https://doi.org/10.5281/zenodo.3667713<br />
<br />
<br />
[[Category:Ambassadors]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Main_Page&diff=1561Main Page2021-05-04T08:29:46Z<p>Morane: Add ambassadors page to main page</p>
<hr />
<div>Welcome to the wiki of [[Software Heritage]].<br />
<br />
We are just getting started, so please bear with us while we organize the content of the wiki.<br ><br />
In the meantime you can find below entry points for various communities we're collaborating with.<br />
<br />
== General ==<br />
<br />
* [[Suggestion box]] for software we should add to the [[Archive]] ← add your entry here!<br />
* [[Talks]] about Software Heritage<br />
<br />
== Developers ==<br />
<br />
* Read the [https://docs.softwareheritage.org/devel/ docs]<br />
* Dive into the [https://forge.softwareheritage.org/ code]<br />
* Subscribe to the [[Mailing lists]]<br />
* Chat with us on [[IRC]]<br />
<br />
== Scientists ==<br />
<br />
* [[:Category:Related work|Related work]]<br />
* [[Working groups]]<br />
<br />
== Students ==<br />
<br />
* [[Internships|Internship opportunities]]<br />
* [[Google Summer of Code 2021]]<br />
<br />
== Ambassadors ==<br />
* [[Ambassadors onboarding]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Main_Page&diff=1538Main Page2021-03-18T11:43:01Z<p>Morane: </p>
<hr />
<div>Welcome to the wiki of [[Software Heritage]].<br />
<br />
We are just getting started, so please bear with us while we organize the content of the wiki.<br ><br />
In the meantime you can find below entry points for various communities we're collaborating with.<br />
<br />
== General ==<br />
<br />
* [[Suggestion box]] for software we should add to the [[Archive]] ← add your entry here!<br />
* [[Talks]] about Software Heritage<br />
<br />
== Developers ==<br />
<br />
* Read the [https://docs.softwareheritage.org/devel/| docs]<br />
* Dive into the [https://forge.softwareheritage.org/| code]<br />
* Subscribe to the [https://sympa.inria.fr/sympa/info/swh-devel| mailing list]<br />
* Chat with us on [https://riot.im/app/#/room/#freenode_#swh-devel:matrix.org| IRC]<br />
<br />
== Scientists ==<br />
<br />
* [[:Category:Related work|Related work]]<br />
* [[Working groups]]<br />
<br />
== Students ==<br />
<br />
* [[Internships|Internship opportunities]]<br />
* [[Google Summer of Code 2021]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Google_Season_of_Docs_2021&diff=1531Google Season of Docs 20212021-03-15T14:34:39Z<p>Morane: Create 2021 GSoD page</p>
<hr />
<div>[[File:GSoDLogo.png|800px]]<br />
<br />
== General information ==<br />
<br />
This page is the central point of information for [[Software Heritage]] participation into the [https://developers.google.com/season-of-docs/ Google Season of Docs] program.<br />
<br />
Google Season of Docs is a program where Google pays technical writers stipends to work on free software projects such as Software Heritage. Each writer works with mentors from the community to complete a documentation project.<br />
<br />
== I want to participate as a technical writer ==<br />
<br />
Great!, we are very glad for your interest in contributing to Software Heritage and we are looking forward to work together.<br />
<br />
=== Prerequisites ===<br />
<br />
The following prerequisites apply to Software Heritage GSoD projects:<br />
<br />
* [http://www.sphinx-doc.org/ Sphinx] is our documentation system of choice, you should be familiar with it to apply. In particular, we generally use reStructuredText markup and (for API references) Python docstrings with the [https://www.sphinx-doc.org/en/master/usage/extensions/napoleon.html Napoleon style]<br />
* [https://git-scm.com Git] is our version control system of choice, you should be familiar with it to apply<br />
* additional prerequisites depend on the project you will work on; check project descriptions for details<br />
<br />
=== Before you apply ===<br />
<br />
Here are the steps you should follow before applying, to make sure you have a general idea of the current state of Software Heritage technical documentation:<br />
<br />
* Learn about our project via our [https://www.softwareheritage.org/ main website] and the actual [https://archive.softwareheritage.org/ source code archive]<br />
* Check out the index of our [https://www.softwareheritage.org/community/developers/ resources for developers]<br />
* In particular make sure to have a look at:<br />
** our [https://wiki.softwareheritage.org/ public wiki]<br />
** our [https://docs.softwareheritage.org/devel/ documentation index]<br />
* Technical setup:<br />
** Create an account on our [https://forge.softwareheritage.org development forge]<br />
** Familiarize yourself with our [[Code review in Phabricator|code review workflow]]<br />
** Make a simple change to the documentation of any one of our [https://docs.softwareheritage.org/devel/ software components] and submit it as a [https://forge.softwareheritage.org/differential/ diff] for code review, following the above workflow. Feel free to submit any patch you think it might be useful.<br />
<br />
=== What to include in your application ===<br />
<br />
Make sure that your application includes the following information:<br />
<br />
* Describe the '''specific project''' you want to work on. What do you want to achieve? Why is it important? Why is it useful for Software Heritage? The project might be one of the project ideas that we have prepared below, or something else entirely that you want to contribute to Software Heritage. Your pet peeve, surprise us!<br />
* Detail your '''work plan''': a brief description of how you plan to go about your project, including a list of ''deliverables'' and a ''timeline'' of when do you expect them to be available.<br />
* Include a reference to '''the diff''' you submitted before applying (see the "Before you apply" section above).<br />
<br />
== Ideas list ==<br />
<br />
Below you can find a list of project ideas that are good options for a<br />
reasonably sized GSoD project. They are just suggestion though, don't feel<br />
obliged to pick one of them if there is nothing that fits your taste and<br />
abilities. Feel free to propose something else that you are excited about and<br />
that contributes to improve the Software Heritage documentation: we will be<br />
happy to consider it!<br />
<br />
TBD<br />
<br />
== Contact ==<br />
<br />
GSoD applicants are encouraged to get in touch with the Software Heritage community using the standard development communication channels, i.e.:<br />
<br />
* the #swh-devel IRC channel on [https://freenode.net Freenode]<br />
* the [https://sympa.inria.fr/sympa/info/swh-devel swh-devel mailing list]<br />
<br />
See our [https://www.softwareheritage.org/community/developers/ development information page] for more details.<br />
<br />
== Timeline ==<br />
<br />
See the official [https://developers.google.com/season-of-docs/docs/timeline Google Season of Docs timeline].<br />
<br />
[[Category:Google Season of Docs]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Category:Google_Season_of_Docs&diff=1530Category:Google Season of Docs2021-03-15T14:16:12Z<p>Morane: Add 2021 WIP page</p>
<hr />
<div>Pages related to the [https://developers.google.com/season-of-docs Google Season of Docs program].<br />
<br />
WIP: create page for [[Google Season of Docs 2021]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Category:Google_Season_of_Docs&diff=1529Category:Google Season of Docs2021-03-15T14:14:03Z<p>Morane: Created page with "Pages related to the [https://developers.google.com/season-of-docs Google Season of Docs program]."</p>
<hr />
<div>Pages related to the [https://developers.google.com/season-of-docs Google Season of Docs program].</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Google_Season_of_Docs_2019&diff=1528Google Season of Docs 20192021-03-15T14:12:00Z<p>Morane: Add category</p>
<hr />
<div>[[File:GSoDLogo.png|800px]]<br />
<br />
== General information ==<br />
<br />
This page is the central point of information for [[Software Heritage]] participation into the [https://developers.google.com/season-of-docs/ Google Season of Docs] program.<br />
<br />
Google Season of Docs is a program where Google pays technical writers stipends to work on free software projects such as Software Heritage. Each writer works with mentors from the community to complete a documentation project.<br />
<br />
== I want to participate as a technical writer ==<br />
<br />
Great!, we are very glad for your interest in contributing to Software Heritage and we are looking forward to work together.<br />
<br />
=== Prerequisites ===<br />
<br />
The following prerequisites apply to Software Heritage GSoD projects:<br />
<br />
* [http://www.sphinx-doc.org/ Sphinx] is our documentation system of choice, you should be familiar with it to apply. In particular, we generally use reStructuredText markup and (for API references) Python docstrings with the [https://www.sphinx-doc.org/en/master/usage/extensions/napoleon.html Napoleon style]<br />
* [https://git-scm.com Git] is our version control system of choice, you should be familiar with it to apply<br />
* additional prerequisites depend on the project you will work on; check project descriptions for details<br />
<br />
=== Before you apply ===<br />
<br />
Here are the steps you should follow before applying, to make sure you have a general idea of the current state of Software Heritage technical documentation:<br />
<br />
* Learn about our project via our [https://www.softwareheritage.org/ main website] and the actual [https://archive.softwareheritage.org/ source code archive]<br />
* Check out the index of our [https://www.softwareheritage.org/community/developers/ resources for developers]<br />
* In particular make sure to have a look at:<br />
** our [https://wiki.softwareheritage.org/ public wiki]<br />
** our [https://docs.softwareheritage.org/devel/ documentation index]<br />
* Technical setup:<br />
** Create an account on our [https://forge.softwareheritage.org development forge]<br />
** Familiarize yourself with our [[Code review in Phabricator|code review workflow]]<br />
** Make a simple change to the documentation of any one of our [https://docs.softwareheritage.org/devel/ software components] and submit it as a [https://forge.softwareheritage.org/differential/ diff] for code review, following the above workflow. Feel free to submit any patch you think it might be useful.<br />
<br />
=== What to include in your application ===<br />
<br />
Make sure that your application includes the following information:<br />
<br />
* Describe the '''specific project''' you want to work on. What do you want to achieve? Why is it important? Why is it useful for Software Heritage? The project might be one of the project ideas that we have prepared below, or something else entirely that you want to contribute to Software Heritage. Your pet peeve, surprise us!<br />
* Detail your '''work plan''': a brief description of how you plan to go about your project, including a list of ''deliverables'' and a ''timeline'' of when do you expect them to be available.<br />
* Include a reference to '''the diff''' you submitted before applying (see the "Before you apply" section above).<br />
<br />
== Ideas list ==<br />
<br />
Below you can find a list of project ideas that are good options for a<br />
reasonably sized GSoD project. They are just suggestion though, don't feel<br />
obliged to pick one of them if there is nothing that fits your taste and<br />
abilities. Feel free to propose something else that you are excited about and<br />
that contributes to improve the Software Heritage documentation: we will be<br />
happy to consider it!<br />
<br />
=== Reorganize developer documentation as tutorials/how-to/discussions/references ===<br />
<br />
Our [https://docs.softwareheritage.org/devel/ developer documentation] is not particularly structured, making it hard to use it properly.<br />
We would like to reorganize it following the [https://www.youtube.com/watch?v=t4vKPhjcMZg tutorials/how-to/discussions/references taxonomy], or something equally sensible.<br />
<br />
This project will require discussing the intended use cases of this page, conceptually structure the future version of it, implement it, and (re)write suitable language to introduce the various parts.<br />
<br />
=== Write a high-level technical overview of the project, data model, and data flow ===<br />
<br />
We have described the data model and archival data flow of Software Heritage in [https://upsilon.cc/~zack/research/publications/ipres-2018-doi.pdf various] [https://upsilon.cc/~zack/research/publications/cacm-2018-software-heritage.pdf scientific] [https://upsilon.cc/~zack/research/publications/msr-2019-swh.pdf papers], but haven't really worked on a general, high-level, technical presentation of it that targets developers.<br />
The current [https://docs.softwareheritage.org/devel/swh-model/data-model.html#data-model data model documentation] has been copy-pasted from scientific papers.<br />
We want to revisit it, to make sure the language description is suitable for a more general technical public, possibly complementing it with more abstract data-structure descriptions and cross-references to the code implementing the model and the workflow in the actual implementation.<br />
<br />
=== Design and document consistent writing conventions for Python docstrings ===<br />
<br />
The docstrings of the [https://docs.softwareheritage.org/devel/#components various software components] in the Software Heritage stack are not very consistent.<br />
They have been written by a number of different developers, with varying degrees of English proficiency.<br />
<br />
We would like to document, as a set of writing guidelines, how to write them to the benefits of current and future developers.<br />
The guidelines should include what to write in docstrings and whatnot, writing styles and guidance, examples of good and bad content for them, etc.<br />
<br />
To the extent it is possible, this project will also explore automating checks for guidelines conformance, in the form of basic structural (e.g., are all function parameters documented? is the function name correct? etc.) and writing checks (e.g., spellchecking, grammar checking, etc.).<br />
<br />
=== Revamp new (code) contributor tutorial ===<br />
<br />
The current [https://docs.softwareheritage.org/devel/#getting-started getting started documentation] include two overlapping documents: one about how to ''run'' a local instance of the full Software Heritage stack, another about how to create a local setup for current and future project ''developers''.<br />
We would like to review those documents for consistency and, more generally, revamp documentation that will help wannabe code contributors to quickly get started and submit patches.<br />
<br />
As part of this project we might also want to revamp glossary, data model and other cross-cutting documents that help newcomers understand where-is-what in the code base and how to practically prepare and send us patches.<br />
<br />
=== Restructure wiki landing page as main community entry point ===<br />
<br />
Our [[Main_Page|public wiki landing page]] is, well, a mess.<br />
It has grown inorganically by accumulating links to pages used more as working drafts than reasonably structured documents.<br />
We would like to restructure it to cater for various use cases (users, developers, students, curators, scientists, etc.) in the attempt of making it the primary entry point into Software Heritage for all community members.<br />
<br />
This project will require discussing the various uses cases, design a suitable page layout, implement it in the wiki, write the introductory parts for each path into the wiki.<br />
A related task, if time permits, will be to reorganize the wiki [[Special:Categories|category taxonomy]] and document when/how to use the available categories in the future.<br />
<br />
Working on this project will require familiarity with [https://www.mediawiki.org/wiki/MediaWiki Mediawiki] and its markup language.<br />
<br />
== Contact ==<br />
<br />
GSoD applicants are encouraged to get in touch with the Software Heritage community using the standard development communication channels, i.e.:<br />
<br />
* the #swh-devel IRC channel on [https://freenode.net Freenode]<br />
* the [https://sympa.inria.fr/sympa/info/swh-devel swh-devel mailing list]<br />
<br />
See our [https://www.softwareheritage.org/community/developers/ development information page] for more details.<br />
<br />
== Timeline ==<br />
<br />
See the official [https://developers.google.com/season-of-docs/docs/timeline Google Season of Docs timeline].<br />
<br />
[[Category:Google Season of Docs]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=User:Morane&diff=1526User:Morane2021-03-15T14:06:48Z<p>Morane: Edit email</p>
<hr />
<div>* Nickname: moranegg<br />
* Full name: Morane Ottilia Gruenpeter<br />
* Homepage: http://moranegg.github.io/<br />
* Email: [mailto:morane@softwareheritage.org morane@softwareheritage.org]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Software_Heritage_identifiers&diff=1437Software Heritage identifiers2021-02-01T16:01:33Z<p>Morane: Added Wikidata to adoption</p>
<hr />
<div>Software Heritage Identifiers, or SWHIDs for short, are persistent intrinsic identifiers used to reference objects stored in the Software Heritage Archive.<br />
<br />
The syntax and semantics of SWHIDs can be found in [https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html SWHID specification].<br />
<br />
== Adoption ==<br />
<br />
SWHIDs are used in a number of different technologies and standards, such as:<br />
<br />
* the Software Heritage archive, via its [https://archive.softwareheritage.org/ Web user interface and API]<br />
* [https://docs.softwareheritage.org/devel/swh-model/cli.html <kbd>swh identify</kbd>] command line tool (by Software Heritage), available from PyPI package [https://pypi.org/project/swh.model/ swh.model]<br />
* [https://identifiers.org/ identifiers.org] resolved ([https://registry.identifiers.org/registry/swh prefix "swh"]<br />
* [https://n2t.net/ Name-to-Things] (N2T) resolver<br />
* [https://spdx.org/ Software Package Data Exchange (SPDX)] standard, starting from [https://www.linuxfoundation.org/en/blog/spdx-2-2-specification-released/ version 2.2]<br />
* [https://github.com/jupyterhub/binderhub Jupyter binderhub] will soon allow to (re)create a Jupyter notebook computing environment from a SWHID via [https://github.com/jupyterhub/repo2docker/pull/988] and [https://github.com/jupyterhub/binderhub/pull/1256]<br />
* Wikidata property [https://www.wikidata.org/wiki/Property:P6138 P6138]<br />
<br />
== References ==<br />
<br />
* [https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html SWHID specification]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Expand_package_metadata_coverage_(internship)&diff=1194Expand package metadata coverage (internship)2020-01-30T11:00:56Z<p>Morane: Added links to blog post and tutorial</p>
<hr />
<div>{{Internship<br />
|description=[https://archive.softwareheritage.org/browse/search/ searching] projects in the Software Heritage archive is currently possible by either (parts of) URL or by [https://www.softwareheritage.org/2019/05/28/mining-software-metadata-for-80-m-projects-and-even-more/ package metadata].<br />
Currently, only a limited number of package metadata are [https://docs.softwareheritage.org/devel/swh-indexer/metadata-workflow.html#supported-intrinsic-metadata supported], including Maven, NPM, PyPI, and Gems.<br />
The goal of this internship is to extend the coverage of supported metadata to additional package managers, the long-term goal being supporting all [https://libraries.io/ Libraries.io]-indexed package managers.<br />
<br />
For more information of the existing tools, you can read our [https://www.softwareheritage.org/2019/05/28/mining-software-metadata-for-80-m-projects-and-even-more/ metadata blog post] or dive into the [https://docs.softwareheritage.org/devel/swh-indexer/metadata-workflow.html#adding-support-for-additional-ecosystem-specific-metadata technical tutorial]<br />
<br />
|skills=<br />
* Python development<br />
<br />
Will be considered a plus:<br />
* knowledge of linked data technologies and ontologies (e.g., RDFa, JSON-LD, OWL, etc.)<br />
<br />
|mentors=<br />
* Morane Gruenpeter<br />
* Valentin Lorentz<br />
* Stefano Zacchiroli <zack@irif.fr><br />
}}<br />
<br />
[[Category:Available internship]]<br />
[[Category:Internship]]<br />
[[Category:Lang:English]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=External_contribution_integration&diff=843External contribution integration2018-06-14T11:53:50Z<p>Morane: </p>
<hr />
<div>= How to integrate external contribution =<br />
New [https://forge.softwareheritage.org/D301 external contributions are starting]. Here is the current team<br />
workflow defined on how to integrate them:<br />
<br />
* Review the diff and explain what's need adapting<br />
<br />
* Accept the diff if ready. We should only be able to accept it if the contributor has already signed the [https://wiki.softwareheritage.org/index.php?title=Contributor_License_Agreement CLA]<br />
<br />
* Integrate the patch using [https://wiki.softwareheritage.org/index.php?title=Arcanist arcanist]:<br />
<br />
cd /path/to/<repository-concerned-by-diff><br />
PATCH_NAME=<patch-name> # use the right patch name D301 for example<br />
CONTRIBUTOR_NAME="<contributor-name>" # use the right contributor's full name<br />
arc patch $PATCH_NAME<br />
# this will create a local commit amend the commit message if<br />
# necessary (added a `Close <concerned-task> for example)<br />
echo $CONTRIBUTOR_NAME >> CONTRIBUTORS<br />
git add CONTRIBUTORS<br />
git commit -m 'Update contributors file'<br />
git checkout master<br />
BRANCH_TO_MERGE="arcpatch-$PATCH_NAME"<br />
git merge $BRANCH_TO_MERGE<br />
git branch -d $BRANCH_TO_MERGE<br />
git push</div>Moranehttps://wiki.softwareheritage.org/index.php?title=External_contribution_integration&diff=842External contribution integration2018-06-14T11:53:20Z<p>Morane: </p>
<hr />
<div>= How to integrate external contribution =<br />
New [https://forge.softwareheritage.org/D301 external contributions are starting]. Here is the current team<br />
workflow defined on how to integrate them:<br />
<br />
* Review the diff and explain what's need adapting<br />
<br />
* Accept the diff if ready. We should only be able to accept it if the contributor has already<br />
signed the [https://wiki.softwareheritage.org/index.php?title=Contributor_License_Agreement CLA]<br />
<br />
* Integrate the patch using [https://wiki.softwareheritage.org/index.php?title=Arcanist arcanist]:<br />
<br />
cd /path/to/<repository-concerned-by-diff><br />
PATCH_NAME=<patch-name> # use the right patch name D301 for example<br />
CONTRIBUTOR_NAME="<contributor-name>" # use the right contributor's full name<br />
arc patch $PATCH_NAME<br />
# this will create a local commit amend the commit message if<br />
# necessary (added a `Close <concerned-task> for example)<br />
echo $CONTRIBUTOR_NAME >> CONTRIBUTORS<br />
git add CONTRIBUTORS<br />
git commit -m 'Update contributors file'<br />
git checkout master<br />
BRANCH_TO_MERGE="arcpatch-$PATCH_NAME"<br />
git merge $BRANCH_TO_MERGE<br />
git branch -d $BRANCH_TO_MERGE<br />
git push</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Glossary&diff=816Glossary2018-04-05T09:52:44Z<p>Morane: </p>
<hr />
<div>This glossary contains the definition of common terms used in the Software Heritage project.<br />
<br />
== C ==<br />
; Content<br />
: a (specific version of a) file stored in the archive, identified by its cryptographic hashes (SHA1, [https://git-scm.com/book/en/v2/Git-Internals-Git-Objects "git-like" SHA1], SHA256) and its size<br />
: Also known as: Blob<br />
: Note: it is incorrect to refer to Contents as "files", because files are usually considered to be named, whereas Contents are nameless. It is only in the context of specific Directories that Contents acquire (local) names<br />
<br />
; Cryptographic hash<br />
: a fixed-size "summary" of a stream of bytes that is easy to compute, and hard to reverse. ([https://en.wikipedia.org/wiki/Cryptographic_hash_function Cryptographic hash function Wikipedia article])<br />
: also known as: Checksum, Digest<br />
<br />
== D ==<br />
<br />
; Directory<br />
: a set of named pointers to contents (file entries), directories (directory entries) and revisions (revision entries)<br />
<br />
== H ==<br />
<br />
; Hash<br />
: see Cryptographic hash<br />
<br />
== O ==<br />
<br />
; Origin<br />
: a location from which a coherent set of sources has been obtained.<br />
: Also known as: Data source<br />
: Examples:<br />
:<br />
:* a [https://github.com/torvalds/linux/ Git repository]<br />
:* a [https://www.kernel.org/pub/linux/kernel/v4.x/ directory containing tarballs]<br />
:* the history of a Debian package on [http://snapshot.debian.org/package/linux/ snapshot.debian.org].<br />
<br />
== P ==<br />
<br />
; Project<br />
: an organized effort to develop a software product. Projects might be nested following organizational structures (sub-project, sub-sub-project), are associated to a number of human-meaningful metadata, and release software products via Origins.<br />
<br />
== R ==<br />
<br />
; Release<br />
: a revision that has been marked by a project as noteworthy with a specific, usually mnemonic, name (for instance, a version number).<br />
: Also known as: Tag (Git-specific terminology)<br />
: Examples:<br />
:<br />
:* a Git tag with its name<br />
:* a tarball with its name<br />
:* a Debian source package with its version number.<br />
<br />
; Revision<br />
: a "point in time" snapshot in the development history of a project.<br />
: Also known as: Commit (VCS terminology)<br />
: Examples:<br />
:<br />
:* a Git commit<br />
<br />
== S ==<br />
<br />
; SHA<br />
: (Secure Hash Algorithm) a family of Cryptographic hashes published by the NIST ([https://en.wikipedia.org/wiki/Secure_Hash_Algorithm SHA Wikipedia article])<br />
<br />
; Snapshot<br />
: the state of all visible branches during a specific visit of an origin<br />
<br />
== V ==<br />
<br />
; VCS<br />
: acronym for Version Control System<br />
: Examples: Git, Subversion, Mercurial</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Metadata_initiatives&diff=813Metadata initiatives2018-03-15T14:04:50Z<p>Morane: </p>
<hr />
<div>Collaborations intended to harmonize the chaos regarding metadata and linked data about Software.<br />
<br />
== List of initiatives and contacts ==<br />
* FORCE11- <br />
** [https://www.force11.org/group/software-citation-working-group Software Citation working group]<br />
** [https://www.force11.org/group/software-citation-implementation-working-group Software Citation Implementation working group] <br />
* Software Preservation Network (SPN) - [http://www.softwarepreservationnetwork.org/working-groups/metadatastandards/ Metadata Standards and Policies working group]- Katherine Thornton and Elizabeth Roke<br />
* [[CodeMeta]]<br />
* [https://github.com/nexB/aboutcode AboutCode]- discover and uncover data about software code. A nexB project. - Philippe Ombredanne<br />
* Wikidata for digital preservation<br />
<br />
== Issues for discussion ==<br />
* In the effort of harmonizing metadata : <br />
** should we strive to contain all domains, every use case and every exception?<br />
** should we keep only the vital minimum for citation and search?<br />
* Terminology : What is Software ?<br />
*** distinguishing between a software artifact, a software project and a software entity<br />
*** distinguishing between software "object"(executable) and software source code<br />
*** different versions form one software entity?<br />
<br />
<br />
<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=CodeMeta&diff=735CodeMeta2017-10-24T13:55:55Z<p>Morane: </p>
<hr />
<div>[https://codemeta.github.io/ '''CodeMeta'''] is a joint project by several science <br />
and industry actors to create minimal metadata schemas for science software and code.<br />
<br />
The CodeMeta initiative created a concept vocabulary based on [[Schema.org]] <br />
SoftwareSourceCode class to standardize the exchange of software metadata across <br />
repositories and organizations. <br />
<br />
The [https://github.com/codemeta/codemeta/blob/master/crosswalk.csv '''crosswalk table'''] <br />
is its most valuable component which can facilitate translation between <br />
ontologies and metadata standards.<br />
<br />
<br />
<br />
== Choosing a metadata strategy by choosing a vocabulary ==<br />
<br />
In the effort of harmonizing metadata : <br />
<br />
1. should we strive to contain all domains, every use case and every exception? <br />
<br />
2. should we keep only the vital minimum for discovery and citation? <br />
<br />
We started by choosing a vocabulary we could translate the metadata we discovered.<br />
<br />
=== CodeMeta advantages ===<br />
CodeMeta showed very important advantages, especially when trying<br />
to harmonize the diversity of metadata:<br />
* most of the terms used are directly taken from schema.org which is practical for producing linked data.<br />
* the crosswalk table is very useful for translating<br />
* from one ontology to another the CodeMeta community is active and the ontology is maintained<br />
<br />
<br />
For these advantages and in the hope that tools using CodeMeta will be available<br />
in the future it seems that the CodeMeta vocabulary is most appropriate for<br />
keeping metadata in the SWH archive.<br />
<br />
=== CodeMeta tools===<br />
We developed the swh-metadata-translator to provide a translation of the discovered metadata into <br />
CodeMeta.<br />
<br />
View which package management files can be translated on [[Best practices using metadata]]<br />
<br />
Other tools compatible with CodeMeta vocabulary are available on the [https://codemeta.github.io/tools/ tools page]<br />
== References ==<br />
<br />
* [https://codemeta.github.io/ CodeMeta homepage]<br />
* [https://github.com/codemeta/codemeta CodeMeta GitHub repository]<br />
<br />
[[Category:Software ontology]]<br />
[[Category:Related work]]<br />
[[Category:Related initiatives]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Best_practices_using_metadata&diff=734Best practices using metadata2017-10-24T13:33:55Z<p>Morane: </p>
<hr />
<div><br />
<br />
1. Use a detailed metadata file with name appropriate to context as listed bellow :<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
!context<br />
!filename<br />
!in CodeMeta crosswalk table<br />
!implemented for swh translation<br />
|-<br />
|java- Maven<br />
|pom.xml<br />
|yes<br />
|no<br />
|-<br />
|Octave<br />
|DESCRIPTION<br />
|yes<br />
|no<br />
|-<br />
|R package <br />
|DESCRIPTION<br />
|yes<br />
|no<br />
|-<br />
|ruby gems <br />
|.gemspec or Rakefile <br />
|yes<br />
|no<br />
|-<br />
|Javascript npm <br />
|package.json, [ AUTHORS, README, CHANGES, LICENSE & NOTICE] files<br />
|yes<br />
|yes<br />
|-<br />
|Perl CPAN::META <br />
|META.json, META.yml, .sDpec<br />
|yes<br />
|no<br />
|-<br />
|Dart <br />
|pubspec.yaml<br />
|no<br />
|no<br />
|-<br />
|Debian package <br />
|debian/upstream/metadata<br />
|yes<br />
|no<br />
|-<br />
|puppet <br />
|metadata.json<br />
|no<br />
|no<br />
|-<br />
|PyPI <br />
|setup.py<br />
|yes<br />
|no<br />
|-<br />
|Scientific software <br />
|CITATION<br />
|no<br />
|no<br />
|-<br />
|CodeMeta <br />
|CODE, code.json, codemeta.json<br />
|yes<br />
|yes<br />
|-<br />
|Java gradle <br />
|gradle.properties<br />
|no<br />
|no<br />
|-<br />
|Jekyll <br />
|_config.yml<br />
|no<br />
|no<br />
|-<br />
|clojure <br />
|project.clj or build.boot<br />
|no<br />
|no<br />
|-<br />
|haskell <br />
|<project name>.cabal <br />
|no<br />
|no<br />
|-<br />
|scala<br />
|build.sbt<br />
|no<br />
|no<br />
|-<br />
|Ocaml<br />
|opam<br />
|no<br />
|no<br />
|}<br />
<br />
2. Use Semantic Versioning [http://semver.org/] for reproducibility purposes.<br />
<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Talks&diff=733Talks2017-10-24T12:46:03Z<p>Morane: </p>
<hr />
<div>In this page we keep track of the past and upcoming talks about [[Software Heritage]], in various venues.<br />
<br />
Please keep the table ''sorted by reverse date'' (most recent talk first).<br />
<br />
== 2017 ==<br />
<br />
{| class="wikitable"<br />
!Date<br />
!Venue<br />
!Title<br />
!Speaker<br />
!Slides<br />
!Video<br />
|-<br />
|27 September 2017<br />
|[https://kernel-recipes.org/en/2017/ Kernel Recipes 2017]<br />
|Software Heritage: Our software commons, forever - Challenges in storing the biggest VCS DAG in history<br />
|[[User:NicolasDandrimont|Nicolas Dandrimont]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-09-27-kernel-recipes.pdf PDF]<br />
|<br />
|-<br />
|19 September 2017<br />
|[https://www.rd-alliance.org/ig-software-source-code-rda-10th-plenary-meeting RDA 10th plenary]<br />
|IG Software Source Code discussion- Software Ontologies and Metadata Schemes<br />
|[[User:Morane|Morane Gruenpeter]]<br />
|[https://www.rd-alliance.org/sites/default/files/attachment/2017-09-19-RDA-IG.pdf PDF]<br />
|<br />
|-<br />
|10 August 2017<br />
|[https://debconf17.debconf.org/ DebConf 2017]<br />
|Software Heritage: Our software commons, forever.<br />
|[[User:NicolasDandrimont|Nicolas Dandrimont]], [[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-08-10-debconf.pdf PDF]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-08-10-debconf.vp9.webm VP9]<br />
|-<br />
|5 July 2017<br />
|[http://iticse.acm.org/ ITiCSE 2017]<br />
|Software Heritage: scholarly and educational synergies with preserving our software commons (keynote)<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|<br />
|<br />
|-<br />
|6 Jun 2017<br />
|[https://reseau-loops.github.io/ Café LoOPS]<br />
|[https://reseau-loops.github.io/2017/06/01/cafe-loops Software Heritage: Construire la bibliothèque d'Alexandrie du logiciel]<br />
|[[User:NicolasDandrimont|Nicolas Dandrimont]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-06-06-loops.pdf PDF]<br />
|<br />
|-<br />
|25 May 2017<br />
|[http://www.dauin.polito.it/ DAUIN, Politecnico di Torino]<br />
|Preserving Source Code: Challenges and Opportunities for the Reproductibility of Science<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-05-25-torino-polito.pdf PDF]<br />
|<br />
|-<br />
|24 May 2017<br />
|[https://nexa.polito.it/lunch-seminars Nexa Lunch Seminar]<br />
|[https://nexa.polito.it/lunch-51 Software Heritage: Archiving the Software Commons for Fun and Social Benefit]<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-05-24-torino-nexa.pdf PDF]<br />
|<br />
|-<br />
|10 Mar 2017<br />
|[http://www.incontrodevops.it/events/idi2017/ Incontro DevOps 2017]<br />
|[http://www.incontrodevops.it/sessions/keynote-idi2017/ Software Heritage: DevOps Challenges to Preserve our Software Commons] (keynote)<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-03-10-devops-italia.pdf PDF]<br />
|<br />
|-<br />
|08 Feb 2017<br />
|[https://project.inria.fr/epfl-Inria/workshops/workshop-2017/ INRIA-EPFL workshop]<br />
|[https://project.inria.fr/epfl-Inria/files/2017/01/RobertoDiCosmo-abstract-workshop2017.pdf What would you do with billions of source code files? Challenges and opportunities in software archival]<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-02-07-epfl-billion-files.pdf PDF]<br />
|<br />
|-<br />
|04 Feb 2017<br />
|[https://fosdem.org/2017/ FOSDEM'17]<br />
|[https://fosdem.org/2017/schedule/event/software_heritage/ Software Heritage: Preserving the Free Software Commons] (keynote)<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]], [[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-02-04-fosdem-software-heritage-foss-commons.pdf PDF]<br />
|[https://video.fosdem.org/2017/Janson/software_heritage.vp8.webm VP8]<br />
|-<br />
|10 Jan 2017<br />
|[http://www.congresodelfuturo.cl/ Congreso del Futuro]<br />
|Software [is our] Heritage: Collecting, preserving and sharing the software source code of Mankind<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-01-10-congresofuturo.pdf PDF]<br />
|<br />
|}<br />
<br />
== 2016 ==<br />
<br />
{| class="wikitable"<br />
!Date<br />
!Venue<br />
!Title<br />
!Speaker<br />
!Slides<br />
!Video<br />
|-<br />
|26 Nov 2016<br />
|[http://milan2016.codemotionworld.com/ Codemotion Milan 2016]<br />
|[http://milan2016.codemotionworld.com/talk-detail/?detail=4654 Software Heritage: let's build together the universal archive of our software commons]<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-11-26-codemotion-milan-zack-software-commons-archive.pdf PDF]<br />
|[https://www.youtube.com/watch?v=gi_HydCumRE YouTube]<br />
|-<br />
|9 Nov 2016<br />
|[http://www.dpconline.org/ Digital Preservation Coalition]<br />
|Building the Universal Software Archive<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-11-09-webex-rdicosmo-digital-preservation-coalition.pdf PDF]<br />
|<br />
|-<br />
|8 Nov 2016<br />
|[https://github.com/alegrand/RR_webinars Series of Webinars on Reproducible Research]<br />
|[https://github.com/alegrand/RR_webinars/blob/master/5_archiving_software_and_data/index.org Preserving Software and Data: Ensuring Availability and Traceability]<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-11-08-grenoble-rdicosmo-reproductibility-preserving-software.pdf PDF]<br />
|[https://mi2s.imag.fr/preserving-software-ensuring-availability-and-traceability-0 Flowplayer]<br />
|-<br />
|18 Oct 2016<br />
|[http://conferences.oreilly.com/oscon/open-source-eu OSCON Europe 2016]<br />
|[http://conferences.oreilly.com/oscon/open-source-eu/public/schedule/detail/55989 Why and how Software Heritage is building the universal software archive] (keynote)<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-10-18-oscon-london-rdicosmo-keynote-software-heritage-building-the-universal-software-archive.pdf PDF]<br />
|[https://www.oreilly.com/ideas/why-and-how-software-heritage-is-building-the-universal-software-archive Excerpt]<br />
|-<br />
|14 Oct 2016<br />
|[http://www.upmc.fr/fr/formations/diplomes/sciences_et_technologies2/masters2/master_informatique_m1/master_science_et_technologie_du_logiciel_m2.html UPMC Master 2 STL]<br />
|[https://www-apr.lip6.fr/~chaillou/Public/enseignement/2016-2017/conf-STL/ Software Heritage: Preserving the Free Software Commons]<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-10-14-upmc-software-heritage-preserving-the-free-software-commons.pdf PDF]<br />
|<br />
|-<br />
|21 Sep 2016<br />
|[https://www.ow2con.org/bin/view/2016/ OW2con'16]<br />
|[https://ow2con16.sched.org/event/80KP Beyond OW2: Software Heritage, Building the Universal Software Archive]<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-09-21-ow2con-zack-software-heritage-building-the-universal-software-archive.pdf PDF]<br />
|<br />
|-<br />
|16 Sep 2016<br />
|[https://www.irif.univ-paris-diderot.fr/ IRIF] [https://www.irif.univ-paris-diderot.fr/seminaires/irif/index seminar series]<br />
|[https://www.irif.univ-paris-diderot.fr/seminaires/irif/index Preserving Software: challenges and opportunities for the reproductibility of Science ]<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-09-16-irif-science-crisis-software-preservation.pdf PDF]<br />
|<br />
|-<br />
|07 Sep 2016<br />
|[https://www.meetup.com/git-Paris/events/233368705/?eventId=233368705 Meetup git Paris #3]<br />
|Software Heritage: une archive mondiale du logiciel libre, inspirée de Git<br />
|[[User:NicolasDandrimont|Nicolas Dandrimont]],<br>[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-09-07-paris-olasd+zack-git-meetup.pdf PDF]<br />
|<br />
|-<br />
|04 Sep 2016<br />
|[https://fsfe.org/community/events/2016/summit/frontpage.en.html FSFE Summit 2016]<br />
|[https://conf.qtcon.org/en/qtcon/public/events/466 Software Heritage - the Universal Archive of Free Software]<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-09-04-qtcon-fsfe-rdicosmo-software-heritage-building-the-universal-software-archive.pdf PDF]<br />
|<br />
|-<br />
|05 Aug 2016<br />
|[https://www.emfcamp.org Electromagnetic Field 2016]<br />
|Software Heritage (lightning talk)<br />
|[[User:NicolasDandrimont|Nicolas Dandrimont]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-08-07-emfcamp-olasd-lightning-talk/2016-08-05_emf.html HTML]<br />
|<br />
|-<br />
|04 Jul 2016<br />
|[https://portail.umons.ac.be/FR/universite/admin/aff_etudiant/CultureEtSport/UMONS-culture/Documents_agendas_culture/2015/Research%20Seminar%20on%20Open%20Source%20Software_4-07-2016.pdf Open Source Seminar at UMONS]<br />
|Software Heritage: Building the Universal Software Archive<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-07-04-umons-rdicosmo-software-heritage-building-the-universal-software-archive.pdf PDF]<br />
|<br />
|-<br />
|04 Jul 2016<br />
|[https://debconf16.debconf.org DebConf16]<br />
|[https://debconf16.debconf.org/talks/42/ Software Heritage: Building the Universal Software Archive]<br />
|[[User:NicolasDandrimont|Nicolas Dandrimont]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-07-04-debconf16-olasd-software-heritage-building-the-universal-software-archive.pdf PDF]<br />
|[http://gensho.acc.umu.se/pub/debian-meetings/2016/debconf16/Software_Heritage_Building_the_Universal_Software_Archive.webm WebM]<br />
|-<br />
|21 Jun 2016<br />
|[http://journees-scientifiques2016.inria.fr/francais-programme/ Journées Scientifiques Inria, Rennes]<br />
|What would you do with ''billions'' of source code files? Challenges and opportunities in software archival<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-06-21-inriarennes-rdicosmo-what-would-you-do-with-billions-of-source-code-files.pdf PDF]<br />
|<br />
|}<br />
<br />
== 2015 ==<br />
<br />
{| class="wikitable"<br />
!Date<br />
!Venue<br />
!Title<br />
!Speaker<br />
!Slides<br />
!Video<br />
|-<br />
|16 Dec 2015<br />
|[http://codesource.hypotheses.org/ Seminar "Codes Sources", UPMC]<br />
|Large-scale source code archival, publishing, and indexing with Debsources [and Software Heritage]<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2015/2015-12-16-semcodesources-zack-debsources-and-software-heritage.pdf PDF]<br />
|<br />
|-<br />
|04 Dec 2015<br />
|[http://cristal.univ-lille.fr/evolille2015/ EvoLille 2015]<br />
|Ten years analysing large code bases: a perspective<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2015/2015-12-04-evolille2015-rdicosmo-ten-years-analysing-large-code-bases-a-perspective.pdf PDF]<br />
|<br />
|-<br />
|21 May 2015<br />
|[http://www.scilabtec.com/ International Scilab Users Conference]<br />
|[https://www.scilab.org/fr/community/scilabtec/2015/Keynote-Preserving-Software-challenges-and-opportunities-for-reproducibility-of-Science-and-Technology Preserving Software: Challenges and Opportunities for Reproducibility of Science and Technology]<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2015/2015-05-21-scilabtec-rdicosmo-preserving-software-challenges-and-opportunities-for-reproducibility-of-science-and-technology.pdf PDF]<br />
|[https://vimeo.com/132074333 Vimeo]<br />
|}<br />
<br />
== 2014 ==<br />
<br />
{| class="wikitable"<br />
!Date<br />
!Venue<br />
!Title<br />
!Speaker<br />
!Slides<br />
!Video<br />
|-<br />
|09 Dec 2014<br />
|Reproductibility Working Group, Inria<br />
|Preserving Software: Challenges and opportunities for reproductibility<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2014/2014-12-04-inriareprowg-rdicosmo-preserving-software-challenges-and-opportunities-for-reproducibility.pdf PDF]<br />
|<br />
|-<br />
|}<br />
<br />
<br />
[[Category:Communication]]<br />
[[Category:Talks]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Talks&diff=732Talks2017-10-24T12:45:27Z<p>Morane: </p>
<hr />
<div>In this page we keep track of the past and upcoming talks about [[Software Heritage]], in various venues.<br />
<br />
Please keep the table ''sorted by reverse date'' (most recent talk first).<br />
<br />
== 2017 ==<br />
<br />
{| class="wikitable"<br />
!Date<br />
!Venue<br />
!Title<br />
!Speaker<br />
!Slides<br />
!Video<br />
|-<br />
|27 September 2017<br />
|[https://kernel-recipes.org/en/2017/ Kernel Recipes 2017]<br />
|Software Heritage: Our software commons, forever - Challenges in storing the biggest VCS DAG in history<br />
|[[User:NicolasDandrimont|Nicolas Dandrimont]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-09-27-kernel-recipes.pdf PDF]<br />
|<br />
|-<br />
|19 September 2017<br />
|[https://www.rd-alliance.org/ig-software-source-code-rda-10th-plenary-meeting RDA 10th plenary- IG Software Source Code]<br />
|Software Ontologies and Metadata Schemes<br />
|[[User:Morane|Morane Gruenpeter]]<br />
|[https://www.rd-alliance.org/sites/default/files/attachment/2017-09-19-RDA-IG.pdf PDF]<br />
|<br />
|-<br />
|10 August 2017<br />
|[https://debconf17.debconf.org/ DebConf 2017]<br />
|Software Heritage: Our software commons, forever.<br />
|[[User:NicolasDandrimont|Nicolas Dandrimont]], [[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-08-10-debconf.pdf PDF]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-08-10-debconf.vp9.webm VP9]<br />
|-<br />
|5 July 2017<br />
|[http://iticse.acm.org/ ITiCSE 2017]<br />
|Software Heritage: scholarly and educational synergies with preserving our software commons (keynote)<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|<br />
|<br />
|-<br />
|6 Jun 2017<br />
|[https://reseau-loops.github.io/ Café LoOPS]<br />
|[https://reseau-loops.github.io/2017/06/01/cafe-loops Software Heritage: Construire la bibliothèque d'Alexandrie du logiciel]<br />
|[[User:NicolasDandrimont|Nicolas Dandrimont]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-06-06-loops.pdf PDF]<br />
|<br />
|-<br />
|25 May 2017<br />
|[http://www.dauin.polito.it/ DAUIN, Politecnico di Torino]<br />
|Preserving Source Code: Challenges and Opportunities for the Reproductibility of Science<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-05-25-torino-polito.pdf PDF]<br />
|<br />
|-<br />
|24 May 2017<br />
|[https://nexa.polito.it/lunch-seminars Nexa Lunch Seminar]<br />
|[https://nexa.polito.it/lunch-51 Software Heritage: Archiving the Software Commons for Fun and Social Benefit]<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-05-24-torino-nexa.pdf PDF]<br />
|<br />
|-<br />
|10 Mar 2017<br />
|[http://www.incontrodevops.it/events/idi2017/ Incontro DevOps 2017]<br />
|[http://www.incontrodevops.it/sessions/keynote-idi2017/ Software Heritage: DevOps Challenges to Preserve our Software Commons] (keynote)<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-03-10-devops-italia.pdf PDF]<br />
|<br />
|-<br />
|08 Feb 2017<br />
|[https://project.inria.fr/epfl-Inria/workshops/workshop-2017/ INRIA-EPFL workshop]<br />
|[https://project.inria.fr/epfl-Inria/files/2017/01/RobertoDiCosmo-abstract-workshop2017.pdf What would you do with billions of source code files? Challenges and opportunities in software archival]<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-02-07-epfl-billion-files.pdf PDF]<br />
|<br />
|-<br />
|04 Feb 2017<br />
|[https://fosdem.org/2017/ FOSDEM'17]<br />
|[https://fosdem.org/2017/schedule/event/software_heritage/ Software Heritage: Preserving the Free Software Commons] (keynote)<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]], [[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-02-04-fosdem-software-heritage-foss-commons.pdf PDF]<br />
|[https://video.fosdem.org/2017/Janson/software_heritage.vp8.webm VP8]<br />
|-<br />
|10 Jan 2017<br />
|[http://www.congresodelfuturo.cl/ Congreso del Futuro]<br />
|Software [is our] Heritage: Collecting, preserving and sharing the software source code of Mankind<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2017/2017-01-10-congresofuturo.pdf PDF]<br />
|<br />
|}<br />
<br />
== 2016 ==<br />
<br />
{| class="wikitable"<br />
!Date<br />
!Venue<br />
!Title<br />
!Speaker<br />
!Slides<br />
!Video<br />
|-<br />
|26 Nov 2016<br />
|[http://milan2016.codemotionworld.com/ Codemotion Milan 2016]<br />
|[http://milan2016.codemotionworld.com/talk-detail/?detail=4654 Software Heritage: let's build together the universal archive of our software commons]<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-11-26-codemotion-milan-zack-software-commons-archive.pdf PDF]<br />
|[https://www.youtube.com/watch?v=gi_HydCumRE YouTube]<br />
|-<br />
|9 Nov 2016<br />
|[http://www.dpconline.org/ Digital Preservation Coalition]<br />
|Building the Universal Software Archive<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-11-09-webex-rdicosmo-digital-preservation-coalition.pdf PDF]<br />
|<br />
|-<br />
|8 Nov 2016<br />
|[https://github.com/alegrand/RR_webinars Series of Webinars on Reproducible Research]<br />
|[https://github.com/alegrand/RR_webinars/blob/master/5_archiving_software_and_data/index.org Preserving Software and Data: Ensuring Availability and Traceability]<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-11-08-grenoble-rdicosmo-reproductibility-preserving-software.pdf PDF]<br />
|[https://mi2s.imag.fr/preserving-software-ensuring-availability-and-traceability-0 Flowplayer]<br />
|-<br />
|18 Oct 2016<br />
|[http://conferences.oreilly.com/oscon/open-source-eu OSCON Europe 2016]<br />
|[http://conferences.oreilly.com/oscon/open-source-eu/public/schedule/detail/55989 Why and how Software Heritage is building the universal software archive] (keynote)<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-10-18-oscon-london-rdicosmo-keynote-software-heritage-building-the-universal-software-archive.pdf PDF]<br />
|[https://www.oreilly.com/ideas/why-and-how-software-heritage-is-building-the-universal-software-archive Excerpt]<br />
|-<br />
|14 Oct 2016<br />
|[http://www.upmc.fr/fr/formations/diplomes/sciences_et_technologies2/masters2/master_informatique_m1/master_science_et_technologie_du_logiciel_m2.html UPMC Master 2 STL]<br />
|[https://www-apr.lip6.fr/~chaillou/Public/enseignement/2016-2017/conf-STL/ Software Heritage: Preserving the Free Software Commons]<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-10-14-upmc-software-heritage-preserving-the-free-software-commons.pdf PDF]<br />
|<br />
|-<br />
|21 Sep 2016<br />
|[https://www.ow2con.org/bin/view/2016/ OW2con'16]<br />
|[https://ow2con16.sched.org/event/80KP Beyond OW2: Software Heritage, Building the Universal Software Archive]<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-09-21-ow2con-zack-software-heritage-building-the-universal-software-archive.pdf PDF]<br />
|<br />
|-<br />
|16 Sep 2016<br />
|[https://www.irif.univ-paris-diderot.fr/ IRIF] [https://www.irif.univ-paris-diderot.fr/seminaires/irif/index seminar series]<br />
|[https://www.irif.univ-paris-diderot.fr/seminaires/irif/index Preserving Software: challenges and opportunities for the reproductibility of Science ]<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-09-16-irif-science-crisis-software-preservation.pdf PDF]<br />
|<br />
|-<br />
|07 Sep 2016<br />
|[https://www.meetup.com/git-Paris/events/233368705/?eventId=233368705 Meetup git Paris #3]<br />
|Software Heritage: une archive mondiale du logiciel libre, inspirée de Git<br />
|[[User:NicolasDandrimont|Nicolas Dandrimont]],<br>[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-09-07-paris-olasd+zack-git-meetup.pdf PDF]<br />
|<br />
|-<br />
|04 Sep 2016<br />
|[https://fsfe.org/community/events/2016/summit/frontpage.en.html FSFE Summit 2016]<br />
|[https://conf.qtcon.org/en/qtcon/public/events/466 Software Heritage - the Universal Archive of Free Software]<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-09-04-qtcon-fsfe-rdicosmo-software-heritage-building-the-universal-software-archive.pdf PDF]<br />
|<br />
|-<br />
|05 Aug 2016<br />
|[https://www.emfcamp.org Electromagnetic Field 2016]<br />
|Software Heritage (lightning talk)<br />
|[[User:NicolasDandrimont|Nicolas Dandrimont]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-08-07-emfcamp-olasd-lightning-talk/2016-08-05_emf.html HTML]<br />
|<br />
|-<br />
|04 Jul 2016<br />
|[https://portail.umons.ac.be/FR/universite/admin/aff_etudiant/CultureEtSport/UMONS-culture/Documents_agendas_culture/2015/Research%20Seminar%20on%20Open%20Source%20Software_4-07-2016.pdf Open Source Seminar at UMONS]<br />
|Software Heritage: Building the Universal Software Archive<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-07-04-umons-rdicosmo-software-heritage-building-the-universal-software-archive.pdf PDF]<br />
|<br />
|-<br />
|04 Jul 2016<br />
|[https://debconf16.debconf.org DebConf16]<br />
|[https://debconf16.debconf.org/talks/42/ Software Heritage: Building the Universal Software Archive]<br />
|[[User:NicolasDandrimont|Nicolas Dandrimont]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-07-04-debconf16-olasd-software-heritage-building-the-universal-software-archive.pdf PDF]<br />
|[http://gensho.acc.umu.se/pub/debian-meetings/2016/debconf16/Software_Heritage_Building_the_Universal_Software_Archive.webm WebM]<br />
|-<br />
|21 Jun 2016<br />
|[http://journees-scientifiques2016.inria.fr/francais-programme/ Journées Scientifiques Inria, Rennes]<br />
|What would you do with ''billions'' of source code files? Challenges and opportunities in software archival<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2016/2016-06-21-inriarennes-rdicosmo-what-would-you-do-with-billions-of-source-code-files.pdf PDF]<br />
|<br />
|}<br />
<br />
== 2015 ==<br />
<br />
{| class="wikitable"<br />
!Date<br />
!Venue<br />
!Title<br />
!Speaker<br />
!Slides<br />
!Video<br />
|-<br />
|16 Dec 2015<br />
|[http://codesource.hypotheses.org/ Seminar "Codes Sources", UPMC]<br />
|Large-scale source code archival, publishing, and indexing with Debsources [and Software Heritage]<br />
|[[User:StefanoZacchiroli|Stefano Zacchiroli]]<br />
|[https://annex.softwareheritage.org/public/talks/2015/2015-12-16-semcodesources-zack-debsources-and-software-heritage.pdf PDF]<br />
|<br />
|-<br />
|04 Dec 2015<br />
|[http://cristal.univ-lille.fr/evolille2015/ EvoLille 2015]<br />
|Ten years analysing large code bases: a perspective<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2015/2015-12-04-evolille2015-rdicosmo-ten-years-analysing-large-code-bases-a-perspective.pdf PDF]<br />
|<br />
|-<br />
|21 May 2015<br />
|[http://www.scilabtec.com/ International Scilab Users Conference]<br />
|[https://www.scilab.org/fr/community/scilabtec/2015/Keynote-Preserving-Software-challenges-and-opportunities-for-reproducibility-of-Science-and-Technology Preserving Software: Challenges and Opportunities for Reproducibility of Science and Technology]<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2015/2015-05-21-scilabtec-rdicosmo-preserving-software-challenges-and-opportunities-for-reproducibility-of-science-and-technology.pdf PDF]<br />
|[https://vimeo.com/132074333 Vimeo]<br />
|}<br />
<br />
== 2014 ==<br />
<br />
{| class="wikitable"<br />
!Date<br />
!Venue<br />
!Title<br />
!Speaker<br />
!Slides<br />
!Video<br />
|-<br />
|09 Dec 2014<br />
|Reproductibility Working Group, Inria<br />
|Preserving Software: Challenges and opportunities for reproductibility<br />
|[[User:RobertoDiCosmo|Roberto Di Cosmo]]<br />
|[https://annex.softwareheritage.org/public/talks/2014/2014-12-04-inriareprowg-rdicosmo-preserving-software-challenges-and-opportunities-for-reproducibility.pdf PDF]<br />
|<br />
|-<br />
|}<br />
<br />
<br />
[[Category:Communication]]<br />
[[Category:Talks]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=User:Morane&diff=730User:Morane2017-10-23T10:47:11Z<p>Morane: </p>
<hr />
<div>* Nickname: moranegg<br />
* Full name: Morane Ottilia Gruenpeter<br />
* Homepage: http://moranegg.github.io/<br />
* Email: [mailto:morane.gg@gmail.com morane.gg@gmail.com]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Software_ontologies&diff=669Software ontologies2017-06-23T15:49:57Z<p>Morane: </p>
<hr />
<div>== Definition of Software Ontology ==<br />
In computer science, the term ontology refers to a structure of concepts or entities within a domain, organized by relationships [https://en.wikipedia.org/wiki/Ontology_%28information_science%29]<br />
<br />
The specification takes the form of a representational vocabulary (classes, relations, and so forth), which provide meanings for the vocabulary and formal constraints on its coherent use.<br />
[http://tomgruber.org/writing/ontology-definition-2007.htm]<br />
<br />
A software ontology is a classification of categories describing software with explicit specifications of its entities and relationships. <br />
<br />
== Ontologies, vocabularies and metadata terms == <br />
Pointers to relevant software ontologies and software metadata, that might be used as inspiration for the upper-level/metadata part of the [[Software Heritage]] data model.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| ADMS.SW<br />
| Asset Description Metadata Schema for Software, and specifically FOSS<br />
| software ontology, research<br />
| 2012<br />
| 2015<br />
| 1.00<br />
| [https://joinup.ec.europa.eu/asset/adms_foss/asset_release/admssw-05 global description] ,<br />
[http://dropbox.ashlock.us/private/ADMS.SW_Specification_1.00.pdf specification],<br />
[https://joinup.ec.europa.eu/svn/adms_foss/adms_sw_v1.00/rdf2html.xsl rdf2html]<br />
| no<br />
| -<br />
|-<br />
| DOAP<br />
| Description of a project<br />
| software ontology<br />
| 2010<br />
| 2017<br />
| no version<br />
| [https://github.com/ewilderj/doap on github],<br />
[https://en.wikipedia.org/wiki/DOAP on wikipedia],<br />
[https://github.com/ewilderj/doap rdf]<br />
| yes<br />
|doap.xml, doap.json<br />
|-<br />
| SEON<br />
| A family of Software Evolution ONtologies<br />
| software ontology<br />
| 2012<br />
| unknown<br />
| no version<br />
| [http://www.se-on.org/ homepage][http://se-on.org/ontologies/index.html documentation][]<br />
| no<br />
| -<br />
<!--<br />
|-<br />
| name<br />
| description<br />
| category<br />
| created<br />
| last update<br />
| version<br />
| links<br />
| in crosswalk table<br />
--><br />
|}<br />
<br />
=== Linked data schemas === <br />
The schemes bellow are mostly used by search engines.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| [[Schema.org]]<br />
| Vocabularies for structured data use on the internet and beyond. Code, SoftwareSourceCode and SoftwareApplication are the main classes describing software.<br />
| linked data<br />
| 2011<br />
| 2017<br />
| 3.2<br />
| [https://schema.org/ homepage]<br />
[https://en.wikipedia.org/wiki/Schema.org wikipedia]<br />
[https://github.com/schemaorg/schemaorg github]<br />
| yes<br />
| -<br />
<br />
|-<br />
| Wikidata<br />
| provides data about software with Q7397<br />
| linked data, catalog<br />
| 2012<br />
| 2017<br />
| no version<br />
| [https://www.wikidata.org/wiki/Wikidata:WikiProject_Informatics/Software#Properties generic software propreties],<br />
[https://www.wikidata.org/wiki/Wikidata:WikiProject_Informatics/FLOSS#Properties FOSS-specific properties][https://github.com/Wikidata github]<br />
[https://www.wikidata.org/wiki/Q128751 Source code page]<br />
| yes<br />
| -<br />
|-<br />
| Dbpedia<br />
| Multi-domain ontology<br />
mappings:<br />
* between dbpedia and schema.org without Software entities<br />
* between dbpedia and wikidata and a wikiparser<br />
| linked data<br />
| 2007<br />
| 2015<br />
| 3.11<br />
| [http://dbpedia.org/page/Software software page]<br />
[http://dbpedia.org/page/Source_code software_code page]<br />
| no<br />
| -<br />
|}<br />
<br />
=== Scholarly ecosystem ===<br />
Software ontologies in research and academia.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| SWOP<br />
| The Software Ontology Project- "is a resource for describing software tools, their types, tasks, versions, provenance and data associated." funded by the [https://www.jisc.ac.uk/ JISC]<br />
| software ontology<br />
| 2011<br />
| 2016<br />
| -<br />
| [https://softwareontology.wordpress.com/ SWOP],<br />
[http://theswo.sourceforge.net/ sourceforge project],<br />
[https://softwareontology.wordpress.com/2011/02/23/an-overview-of-sword/ overview blog post]<br />
| no<br />
| -<br />
|-<br />
| [[TOTEM]]<br />
| Trustworthy Online Technical Environment Metadata Database for digital objects in general<br />
| generic, catalog<br />
| 2008<br />
| unknown<br />
| unknown<br />
| [http://www.keep-totem.co.uk/ homepage]<br />
| no<br />
| -<br />
|-<br />
| DataCite<br />
| the schema is not software specific<br />
| generic, research<br />
| 2009<br />
| 2016<br />
| 4.0<br />
| [https://schema.datacite.org/meta/kernel-4.0/metadata.xsd schema][http://rrr.cs.st-andrews.ac.uk/wp-content/uploads/2015/10/guidelines-software-identification.pdf guidlines]<br />
| yes<br />
|-<br />
|-<br />
| Zenodo<br />
| exported possibilities : MARCXML, Dublin Core, and DataCite Metadata Schema <br />
| generic, research<br />
| -<br />
| -<br />
| -<br />
| [https://guides.github.com/activities/citable-code/ github citable-code]<br />
| yes<br />
| no file in source code<br />
|-<br />
| Figshare<br />
| Making research outputs available online<br />
| generic<br />
| 2011<br />
| -<br />
| -<br />
| -<br />
| yes<br />
| no file in source code<br />
|-<br />
|}<br />
<br />
=== Digital preservation schemas ===<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| Dublin Core<br />
| -<br />
| generic<br />
| -<br />
| -<br />
| -<br />
| [http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=terms#dcmitype-Software dcmitype-Software]<br />
| yes<br />
| -<br />
|-<br />
| Marc<br />
| MAchine-Readable Cataloging <br />
* MIT is using MARC records<br />
| generic<br />
| 1960s<br />
| -<br />
| -<br />
| [http://www.loc.gov/marc/ homepage]<br />
| no<br />
| -<br />
|-<br />
|PRONOM<br />
|-<br />
|PREMIS<br />
|-<br />
|}<br />
<br />
<br />
=== Package management vocabularies ===<br />
Found mostly in the source code itself.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
|-<br />
| R Package Description <br />
| DESCRIPTION file stored in an R package, containing important metadata <br />
| dev <br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
|TBD<br />
|-<br />
| Debian Package<br />
| An effort to collect meta-information about projects. Trying to use DOAP vocabulary. Captured in a file called debian/upstream/metadata in YAML format. another file with EDAM ontology can be provided at: debian/upstream/edam<br />
| dev <br />
| -<br />
| 2017<br />
| -<br />
| [https://wiki.debian.org/UpstreamMetadata wiki]<br />
| yes<br />
| debian/upstream/metadata<br />
|-<br />
| debtags <br />
| debtags are terms used to describe package content in a non-formal way.<br />
| dev<br />
| 2005<br />
| 2017<br />
| no version<br />
| [https://anonscm.debian.org/cgit/debtags/vocabulary.git/tree/debian-packages vocabulary]<br />
[https://wiki.debian.org/Debtags/FAQ wiki]<br />
| no<br />
| not in source code<br />
|-<br />
| Python Distutils (PyPI)<br />
| The Python Package Index (PyPI) stores metadata that describes package. setup;py file is used when package was packaged and distributed by Distutils (the standard for distributing Python Modules)<br />
| dev <br />
| 1999<br />
| 2017<br />
| 35.0.1 Setuptools<br />
|[https://setuptools.readthedocs.io/en/latest/setuptools.html setuptools doc]<br />
[https://en.wikipedia.org/wiki/Python_Package_Index wikipedia]<br />
[https://martin-thoma.com/analyzing-pypi-metadata/ analyzing pypi metadata 2015]<br />
| yes<br />
| setup.py<br />
|-<br />
| Trove Software Map <br />
| Distutils Trove Classification <br />
| dev <br />
| 1998<br />
| 2002<br />
| -<br />
| [http://www.catb.org/~esr/trove/ Trove project]<br />
[https://www.python.org/dev/peps/pep-0301/ usage with Python]<br />
| yes<br />
| -<br />
|-<br />
| CPAN::Meta<br />
| Comprehensive Perl Archive Network (CPAN) used somewhat like a package manager. The CPAN::META known as META.yml or META.json file is typically created by other tools, Module::Build and ExtUtils::MakeMaker. The raw form of the metadata doesn't exists in the source code.<br />
| dev<br />
| 2003<br />
| -<br />
| 2.150010<br />
| [https://en.wikipedia.org/wiki/CPAN wikipedia]<br />
[http://www.cpan.org/ homepage]<br />
[https://github.com/Perl-Toolchain-Gang/CPAN-Meta on github]<br />
| yes<br />
| META.json, META.yml, .spec<br />
|-<br />
| Ruby Gem<br />
| Specifications in Ruby called gemspec that can hold arbitrary metadata in a .gemspec file or a Rakefile<br />
| dev <br />
| 2006<br />
| 2015<br />
| 0.3.1<br />
| [http://guides.rubygems.org/specification-reference/ guide]<br />
[https://github.com/pjump/gemspec on github]<br />
| yes<br />
| .gemspec, Rakefile<br />
|-<br />
| JavaScript -npm<br />
| A package.json file containing specifications about npm package. The name and version of the package are a unique identifier, changes to the package should come with changes to the version <br />
| dev <br />
| 2010<br />
| 2017<br />
| -<br />
| [https://docs.npmjs.com/files/package.json documentation]<br />
[https://nodesource.com/blog/the-basics-of-package-json-in-node-js-and-npm/ guide]<br />
| yes<br />
| package.json<br />
|-<br />
| Maven<br />
| pom.xml file in the project root. POM stands for "Project Object Model", an XML representation of a Maven project.<br />
| dev <br />
| -<br />
| 2017<br />
| 3.5.0<br />
| [https://maven.apache.org/pom.html POM reference]<br />
[http://maven.apache.org/ref/3.5.0/maven-model/maven.html maven model]<br />
| yes<br />
| pom.xml<br />
|-<br />
| Octave<br />
| DESCRIPTION file in package which contains various information about package<br />
| dev <br />
| -<br />
| -<br />
| -<br />
| [https://www.gnu.org/software/octave/doc/interpreter/The-DESCRIPTION-File.html howto]<br />
| yes<br />
| DESCRIPTION<br />
|-<br />
| CodeMeta<br />
| a minimal metadata schema for science software and code, in JSON and XML<br />
| software ontology, research, linked data<br />
| 2014<br />
| 2017<br />
| no version<br />
| [http://codemeta.github.io/ homepage]<br />
[https://github.com/codemeta/codemeta on github]<br />
[https://raw.githubusercontent.com/codemeta/codemeta/master/data/codemeta-json-schema.json schema]<br />
| yes<br />
|code.json<br />
|-<br />
| Marc<br />
| MAchine-Readable Cataloging <br />
* MIT is using MARC records<br />
| generic<br />
| 1960s<br />
| -<br />
| -<br />
| [http://www.loc.gov/marc/ homepage]<br />
| no<br />
| -<br />
|-<br />
<!--<br />
|-<br />
| name<br />
| description<br />
| category<br />
| created<br />
| last update<br />
| version<br />
| links<br />
| in crosswalk table<br />
--><br />
|}<br />
<br />
<br />
PRONOM - [https://www.wikidata.org/wiki/User:YULdigitalpreservation/Software] include in Digital preservation schemas<br />
<br />
PREMIS - include in Digital preservation schemas<br />
<br />
DOLCE -Outdated ?<br />
<br />
CSO - Outdated ?<br />
<br />
[[Category:Related work]]<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Best_practices_using_metadata&diff=666Best practices using metadata2017-06-18T23:41:55Z<p>Morane: </p>
<hr />
<div><br />
<br />
1. Use a detailed metadata file with name appropriate to context as listed bellow :<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
!context<br />
!filename<br />
!in CodeMeta crosswalk table<br />
!implemented for swh translation<br />
|-<br />
|java- Maven<br />
|pom.xml<br />
|yes<br />
|no<br />
|-<br />
|Octave<br />
|DESCRIPTION<br />
|yes<br />
|no<br />
|-<br />
|R package <br />
|DESCRIPTION<br />
|yes<br />
|no<br />
|-<br />
|ruby gems <br />
|.gemspec or Rakefile <br />
|yes<br />
|no<br />
|-<br />
|Javascript npm <br />
|package.json, [ AUTHORS, README, CHANGES, LICENSE & NOTICE] files<br />
|yes<br />
|no<br />
|-<br />
|Perl CPAN::META <br />
|META.json, META.yml, .sDpec<br />
|yes<br />
|no<br />
|-<br />
|Dart <br />
|pubspec.yaml<br />
|no<br />
|no<br />
|-<br />
|Debian package <br />
|debian/upstream/metadata<br />
|yes<br />
|no<br />
|-<br />
|puppet <br />
|metadata.json<br />
|no<br />
|no<br />
|-<br />
|PyPI <br />
|setup.py<br />
|yes<br />
|no<br />
|-<br />
|Scientific software <br />
|CITATION<br />
|no<br />
|no<br />
|-<br />
|CodeMeta <br />
|CODE, code.json, codemeta.json<br />
|yes<br />
|no<br />
|-<br />
|Java gradle <br />
|gradle.properties<br />
|no<br />
|no<br />
|-<br />
|Jekyll <br />
|_config.yml<br />
|no<br />
|no<br />
|-<br />
|clojure <br />
|project.clj or build.boot<br />
|no<br />
|no<br />
|-<br />
|haskell <br />
|<project name>.cabal <br />
|no<br />
|no<br />
|-<br />
|scala<br />
|build.sbt<br />
|no<br />
|no<br />
|-<br />
|Ocaml<br />
|opam<br />
|no<br />
|no<br />
|}<br />
<br />
2. Use Semantic Versioning [http://semver.org/] for reproducibility purposes.<br />
<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Software_ontologies&diff=665Software ontologies2017-06-18T23:30:38Z<p>Morane: </p>
<hr />
<div>== Definition of Software Ontology ==<br />
In computer science, the term ontology refers to a structure of concepts or entities within a domain, organized by relationships [https://en.wikipedia.org/wiki/Ontology_%28information_science%29]<br />
<br />
The specification takes the form of a representational vocabulary (classes, relations, and so forth), which provide meanings for the vocabulary and formal constraints on its coherent use.<br />
[http://tomgruber.org/writing/ontology-definition-2007.htm]<br />
<br />
A software ontology is a classification of categories describing software with explicit specifications of its entities and relationships. <br />
<br />
== Ontologies, vocabularies and metadata terms == <br />
Pointers to relevant software ontologies and software metadata, that might be used as inspiration for the upper-level/metadata part of the [[Software Heritage]] data model.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| ADMS.SW<br />
| Asset Description Metadata Schema for Software, and specifically FOSS<br />
| software ontology, research<br />
| 2012<br />
| 2015<br />
| 1.00<br />
| [https://joinup.ec.europa.eu/asset/adms_foss/asset_release/admssw-05 global description] ,<br />
[http://dropbox.ashlock.us/private/ADMS.SW_Specification_1.00.pdf specification],<br />
[https://joinup.ec.europa.eu/svn/adms_foss/adms_sw_v1.00/rdf2html.xsl rdf2html]<br />
| no<br />
| -<br />
|-<br />
| DOAP<br />
| Description of a project<br />
| software ontology<br />
| 2010<br />
| 2017<br />
| no version<br />
| [https://github.com/ewilderj/doap on github],<br />
[https://en.wikipedia.org/wiki/DOAP on wikipedia],<br />
[https://github.com/ewilderj/doap rdf]<br />
| yes<br />
|doap.xml, doap.json<br />
|-<br />
| SEON<br />
| A family of Software Evolution ONtologies<br />
| software ontology<br />
| 2012<br />
| unknown<br />
| no version<br />
| [http://www.se-on.org/ homepage][http://se-on.org/ontologies/index.html documentation][]<br />
| no<br />
| -<br />
<!--<br />
|-<br />
| name<br />
| description<br />
| category<br />
| created<br />
| last update<br />
| version<br />
| links<br />
| in crosswalk table<br />
--><br />
|}<br />
<br />
=== Linked data schemas === <br />
The schemes bellow are mostly used by search engines.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| [[Schema.org]]<br />
| Vocabularies for structured data use on the internet and beyond. Code, SoftwareSourceCode and SoftwareApplication are the main classes describing software.<br />
| linked data<br />
| 2011<br />
| 2017<br />
| 3.2<br />
| [https://schema.org/ homepage]<br />
[https://en.wikipedia.org/wiki/Schema.org wikipedia]<br />
[https://github.com/schemaorg/schemaorg github]<br />
| yes<br />
| -<br />
<br />
|-<br />
| Wikidata<br />
| provides data about software with Q7397<br />
| linked data, catalog<br />
| 2012<br />
| 2017<br />
| no version<br />
| [https://www.wikidata.org/wiki/Wikidata:WikiProject_Informatics/Software#Properties generic software propreties],<br />
[https://www.wikidata.org/wiki/Wikidata:WikiProject_Informatics/FLOSS#Properties FOSS-specific properties][https://github.com/Wikidata github]<br />
[https://www.wikidata.org/wiki/Q128751 Source code page]<br />
| yes<br />
| -<br />
|-<br />
| Dbpedia<br />
| Multi-domain ontology<br />
mappings:<br />
* between dbpedia and schema.org without Software entities<br />
* between dbpedia and wikidata and a wikiparser<br />
| linked data<br />
| 2007<br />
| 2015<br />
| 3.11<br />
| [http://dbpedia.org/page/Software software page]<br />
[http://dbpedia.org/page/Source_code software_code page]<br />
| no<br />
| -<br />
|}<br />
<br />
=== Scholarly ecosystem ===<br />
Software ontologies in research and academia.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| SWOP<br />
| The Software Ontology Project- "is a resource for describing software tools, their types, tasks, versions, provenance and data associated." funded by the [https://www.jisc.ac.uk/ JISC]<br />
| software ontology<br />
| 2011<br />
| 2016<br />
| -<br />
| [https://softwareontology.wordpress.com/ SWOP],<br />
[http://theswo.sourceforge.net/ sourceforge project],<br />
[https://softwareontology.wordpress.com/2011/02/23/an-overview-of-sword/ overview blog post]<br />
| no<br />
| -<br />
|-<br />
| [[TOTEM]]<br />
| Trustworthy Online Technical Environment Metadata Database for digital objects in general<br />
| generic, catalog<br />
| 2008<br />
| unknown<br />
| unknown<br />
| [http://www.keep-totem.co.uk/ homepage]<br />
| no<br />
| -<br />
|-<br />
| DataCite<br />
| the schema is not software specific<br />
| generic, research<br />
| 2009<br />
| 2016<br />
| 4.0<br />
| [https://schema.datacite.org/meta/kernel-4.0/metadata.xsd schema][http://rrr.cs.st-andrews.ac.uk/wp-content/uploads/2015/10/guidelines-software-identification.pdf guidlines]<br />
| yes<br />
|-<br />
|-<br />
| Zenodo<br />
| exported possibilities : MARCXML, Dublin Core, and DataCite Metadata Schema <br />
| generic, research<br />
| -<br />
| -<br />
| -<br />
| [https://guides.github.com/activities/citable-code/ github citable-code]<br />
| yes<br />
| no file in source code<br />
|-<br />
| Figshare<br />
| Making research outputs available online<br />
| generic<br />
| 2011<br />
| -<br />
| -<br />
| -<br />
| yes<br />
| no file in source code<br />
|-<br />
|}<br />
<br />
=== Digital preservation schemas ===<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| Dublin Core<br />
| -<br />
| generic<br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
| -<br />
|-<br />
| Marc<br />
| MAchine-Readable Cataloging <br />
* MIT is using MARC records<br />
| generic<br />
| 1960s<br />
| -<br />
| -<br />
| [http://www.loc.gov/marc/ homepage]<br />
| no<br />
| -<br />
|-<br />
|PRONOM<br />
|-<br />
|PREMIS<br />
|-<br />
|}<br />
<br />
<br />
=== Package management vocabularies ===<br />
Found mostly in the source code itself.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
|-<br />
| R Package Description <br />
| DESCRIPTION file stored in an R package, containing important metadata <br />
| dev <br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
|TBD<br />
|-<br />
| Debian Package<br />
| An effort to collect meta-information about projects. Trying to use DOAP vocabulary. Captured in a file called debian/upstream/metadata in YAML format. another file with EDAM ontology can be provided at: debian/upstream/edam<br />
| dev <br />
| -<br />
| 2017<br />
| -<br />
| [https://wiki.debian.org/UpstreamMetadata wiki]<br />
| yes<br />
| debian/upstream/metadata<br />
|-<br />
| debtags <br />
| debtags are terms used to describe package content in a non-formal way.<br />
| dev<br />
| 2005<br />
| 2017<br />
| no version<br />
| [https://anonscm.debian.org/cgit/debtags/vocabulary.git/tree/debian-packages vocabulary]<br />
[https://wiki.debian.org/Debtags/FAQ wiki]<br />
| no<br />
| not in source code<br />
|-<br />
| Python Distutils (PyPI)<br />
| The Python Package Index (PyPI) stores metadata that describes package. setup;py file is used when package was packaged and distributed by Distutils (the standard for distributing Python Modules)<br />
| dev <br />
| 1999<br />
| 2017<br />
| 35.0.1 Setuptools<br />
|[https://setuptools.readthedocs.io/en/latest/setuptools.html setuptools doc]<br />
[https://en.wikipedia.org/wiki/Python_Package_Index wikipedia]<br />
[https://martin-thoma.com/analyzing-pypi-metadata/ analyzing pypi metadata 2015]<br />
| yes<br />
| setup.py<br />
|-<br />
| Trove Software Map <br />
| Distutils Trove Classification <br />
| dev <br />
| 1998<br />
| 2002<br />
| -<br />
| [http://www.catb.org/~esr/trove/ Trove project]<br />
[https://www.python.org/dev/peps/pep-0301/ usage with Python]<br />
| yes<br />
| -<br />
|-<br />
| CPAN::Meta<br />
| Comprehensive Perl Archive Network (CPAN) used somewhat like a package manager. The CPAN::META known as META.yml or META.json file is typically created by other tools, Module::Build and ExtUtils::MakeMaker. The raw form of the metadata doesn't exists in the source code.<br />
| dev<br />
| 2003<br />
| -<br />
| 2.150010<br />
| [https://en.wikipedia.org/wiki/CPAN wikipedia]<br />
[http://www.cpan.org/ homepage]<br />
[https://github.com/Perl-Toolchain-Gang/CPAN-Meta on github]<br />
| yes<br />
| META.json, META.yml, .spec<br />
|-<br />
| Ruby Gem<br />
| Specifications in Ruby called gemspec that can hold arbitrary metadata in a .gemspec file or a Rakefile<br />
| dev <br />
| 2006<br />
| 2015<br />
| 0.3.1<br />
| [http://guides.rubygems.org/specification-reference/ guide]<br />
[https://github.com/pjump/gemspec on github]<br />
| yes<br />
| .gemspec, Rakefile<br />
|-<br />
| JavaScript -npm<br />
| A package.json file containing specifications about npm package. The name and version of the package are a unique identifier, changes to the package should come with changes to the version <br />
| dev <br />
| 2010<br />
| 2017<br />
| -<br />
| [https://docs.npmjs.com/files/package.json documentation]<br />
[https://nodesource.com/blog/the-basics-of-package-json-in-node-js-and-npm/ guide]<br />
| yes<br />
| package.json<br />
|-<br />
| Maven<br />
| pom.xml file in the project root. POM stands for "Project Object Model", an XML representation of a Maven project.<br />
| dev <br />
| -<br />
| 2017<br />
| 3.5.0<br />
| [https://maven.apache.org/pom.html POM reference]<br />
[http://maven.apache.org/ref/3.5.0/maven-model/maven.html maven model]<br />
| yes<br />
| pom.xml<br />
|-<br />
| Octave<br />
| DESCRIPTION file in package which contains various information about package<br />
| dev <br />
| -<br />
| -<br />
| -<br />
| [https://www.gnu.org/software/octave/doc/interpreter/The-DESCRIPTION-File.html howto]<br />
| yes<br />
| DESCRIPTION<br />
|-<br />
| CodeMeta<br />
| a minimal metadata schema for science software and code, in JSON and XML<br />
| software ontology, research, linked data<br />
| 2014<br />
| 2017<br />
| no version<br />
| [http://codemeta.github.io/ homepage]<br />
[https://github.com/codemeta/codemeta on github]<br />
[https://raw.githubusercontent.com/codemeta/codemeta/master/data/codemeta-json-schema.json schema]<br />
| yes<br />
|code.json<br />
|-<br />
| Marc<br />
| MAchine-Readable Cataloging <br />
* MIT is using MARC records<br />
| generic<br />
| 1960s<br />
| -<br />
| -<br />
| [http://www.loc.gov/marc/ homepage]<br />
| no<br />
| -<br />
|-<br />
<!--<br />
|-<br />
| name<br />
| description<br />
| category<br />
| created<br />
| last update<br />
| version<br />
| links<br />
| in crosswalk table<br />
--><br />
|}<br />
<br />
<br />
PRONOM - [https://www.wikidata.org/wiki/User:YULdigitalpreservation/Software] include in Digital preservation schemas<br />
<br />
PREMIS - include in Digital preservation schemas<br />
<br />
DOLCE -Outdated ?<br />
<br />
CSO - Outdated ?<br />
<br />
[[Category:Related work]]<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Software_ontologies&diff=664Software ontologies2017-06-18T17:17:31Z<p>Morane: editing categorization into separated tables</p>
<hr />
<div>== Definition of Software Ontology ==<br />
In computer science, the term ontology refers to a structure of concepts or entities within a domain, organized by relationships [https://en.wikipedia.org/wiki/Ontology_%28information_science%29]<br />
<br />
The specification takes the form of a representational vocabulary (classes, relations, and so forth), which provide meanings for the vocabulary and formal constraints on its coherent use.<br />
[http://tomgruber.org/writing/ontology-definition-2007.htm]<br />
<br />
A software ontology is a classification of categories describing software with explicit specifications of its entities and relationships. <br />
<br />
== Ontologies, vocabularies and metadata terms == <br />
Pointers to relevant software ontologies and software metadata, that might be used as inspiration for the upper-level/metadata part of the [[Software Heritage]] data model.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| ADMS.SW<br />
| Asset Description Metadata Schema for Software, and specifically FOSS<br />
| software ontology, research<br />
| 2012<br />
| 2015<br />
| 1.00<br />
| [https://joinup.ec.europa.eu/asset/adms_foss/asset_release/admssw-05 global description] ,<br />
[http://dropbox.ashlock.us/private/ADMS.SW_Specification_1.00.pdf specification],<br />
[https://joinup.ec.europa.eu/svn/adms_foss/adms_sw_v1.00/rdf2html.xsl rdf2html]<br />
| no<br />
| -<br />
|-<br />
| DOAP<br />
| Description of a project<br />
| software ontology<br />
| 2010<br />
| 2017<br />
| no version<br />
| [https://github.com/ewilderj/doap on github],<br />
[https://en.wikipedia.org/wiki/DOAP on wikipedia],<br />
[https://github.com/ewilderj/doap rdf]<br />
| yes<br />
|doap.xml, doap.json<br />
|-<br />
| SEON<br />
| A family of Software Evolution ONtologies<br />
| software ontology<br />
| 2012<br />
| unknown<br />
| no version<br />
| [http://www.se-on.org/ homepage][http://se-on.org/ontologies/index.html documentation][]<br />
| no<br />
| -<br />
<!--<br />
|-<br />
| name<br />
| description<br />
| category<br />
| created<br />
| last update<br />
| version<br />
| links<br />
| in crosswalk table<br />
--><br />
|}<br />
<br />
=== Linked data schemas === <br />
The schemes bellow are mostly used by search engines.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| [[Schema.org]]<br />
| Vocabularies for structured data use on the internet and beyond. Code, SoftwareSourceCode and SoftwareApplication are the main classes describing software.<br />
| linked data<br />
| 2011<br />
| 2017<br />
| 3.2<br />
| [https://schema.org/ homepage]<br />
[https://en.wikipedia.org/wiki/Schema.org wikipedia]<br />
[https://github.com/schemaorg/schemaorg github]<br />
| yes<br />
| -<br />
<br />
|-<br />
| Wikidata<br />
| provides data about software with Q7397<br />
| linked data, catalog<br />
| 2012<br />
| 2017<br />
| no version<br />
| [https://www.wikidata.org/wiki/Wikidata:WikiProject_Informatics/Software#Properties generic software propreties],<br />
[https://www.wikidata.org/wiki/Wikidata:WikiProject_Informatics/FLOSS#Properties FOSS-specific properties][https://github.com/Wikidata github]<br />
[https://www.wikidata.org/wiki/Q128751 Source code page]<br />
| yes<br />
| -<br />
|-<br />
| Dbpedia<br />
| Multi-domain ontology<br />
mappings:<br />
* between dbpedia and schema.org without Software entities<br />
* between dbpedia and wikidata and a wikiparser<br />
| linked data<br />
| 2007<br />
| 2015<br />
| 3.11<br />
| [http://dbpedia.org/page/Software software page]<br />
[http://dbpedia.org/page/Source_code software_code page]<br />
| no<br />
| -<br />
|}<br />
<br />
=== Scholarly ecosystem ===<br />
Software ontologies in research and academia.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| SWOP<br />
| The Software Ontology Project- "is a resource for describing software tools, their types, tasks, versions, provenance and data associated." funded by the [https://www.jisc.ac.uk/ JISC]<br />
| software ontology<br />
| 2011<br />
| 2016<br />
| -<br />
| [https://softwareontology.wordpress.com/ SWOP],<br />
[http://theswo.sourceforge.net/ sourceforge project],<br />
[https://softwareontology.wordpress.com/2011/02/23/an-overview-of-sword/ overview blog post]<br />
| no<br />
| -<br />
|-<br />
| [[TOTEM]]<br />
| Trustworthy Online Technical Environment Metadata Database for digital objects in general<br />
| generic, catalog<br />
| 2008<br />
| unknown<br />
| unknown<br />
| [http://www.keep-totem.co.uk/ homepage]<br />
| no<br />
| -<br />
|}<br />
<br />
=== Digital preservation schemas ===<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| DataCite<br />
| the schema is not software specific<br />
| generic, research<br />
| 2009<br />
| 2016<br />
| 4.0<br />
| [https://schema.datacite.org/meta/kernel-4.0/metadata.xsd schema][http://rrr.cs.st-andrews.ac.uk/wp-content/uploads/2015/10/guidelines-software-identification.pdf guidlines]<br />
| yes<br />
|-<br />
|-<br />
| Dublin Core<br />
| -<br />
| generic<br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
| -<br />
|-<br />
| Zenodo<br />
| exported possibilities : MARCXML, Dublin Core, and DataCite Metadata Schema <br />
| generic, research<br />
| -<br />
| -<br />
| -<br />
| [https://guides.github.com/activities/citable-code/ github citable-code]<br />
| yes<br />
| no file in source code<br />
|-<br />
| Figshare<br />
| Making research outputs available online<br />
| generic<br />
| 2011<br />
| -<br />
| -<br />
| -<br />
| yes<br />
| no file in source code<br />
|-<br />
| Marc<br />
| MAchine-Readable Cataloging <br />
* MIT is using MARC records<br />
| generic<br />
| 1960s<br />
| -<br />
| -<br />
| [http://www.loc.gov/marc/ homepage]<br />
| no<br />
| -<br />
|-<br />
|}<br />
<br />
<br />
=== Package management vocabularies ===<br />
Found mostly in the source code itself.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
|-<br />
| R Package Description <br />
| DESCRIPTION file stored in an R package, containing important metadata <br />
| dev <br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
|TBD<br />
|-<br />
| Debian Package<br />
| An effort to collect meta-information about projects. Trying to use DOAP vocabulary. Captured in a file called debian/upstream/metadata in YAML format. another file with EDAM ontology can be provided at: debian/upstream/edam<br />
| dev <br />
| -<br />
| 2017<br />
| -<br />
| [https://wiki.debian.org/UpstreamMetadata wiki]<br />
| yes<br />
| debian/upstream/metadata<br />
|-<br />
| debtags <br />
| debtags are terms used to describe package content in a non-formal way.<br />
| dev<br />
| 2005<br />
| 2017<br />
| no version<br />
| [https://anonscm.debian.org/cgit/debtags/vocabulary.git/tree/debian-packages vocabulary]<br />
[https://wiki.debian.org/Debtags/FAQ wiki]<br />
| no<br />
| not in source code<br />
|-<br />
| Python Distutils (PyPI)<br />
| The Python Package Index (PyPI) stores metadata that describes package. setup;py file is used when package was packaged and distributed by Distutils (the standard for distributing Python Modules)<br />
| dev <br />
| 1999<br />
| 2017<br />
| 35.0.1 Setuptools<br />
|[https://setuptools.readthedocs.io/en/latest/setuptools.html setuptools doc]<br />
[https://en.wikipedia.org/wiki/Python_Package_Index wikipedia]<br />
[https://martin-thoma.com/analyzing-pypi-metadata/ analyzing pypi metadata 2015]<br />
| yes<br />
| setup.py<br />
|-<br />
| Trove Software Map <br />
| Distutils Trove Classification <br />
| dev <br />
| 1998<br />
| 2002<br />
| -<br />
| [http://www.catb.org/~esr/trove/ Trove project]<br />
[https://www.python.org/dev/peps/pep-0301/ usage with Python]<br />
| yes<br />
| -<br />
|-<br />
| CPAN::Meta<br />
| Comprehensive Perl Archive Network (CPAN) used somewhat like a package manager. The CPAN::META known as META.yml or META.json file is typically created by other tools, Module::Build and ExtUtils::MakeMaker. The raw form of the metadata doesn't exists in the source code.<br />
| dev<br />
| 2003<br />
| -<br />
| 2.150010<br />
| [https://en.wikipedia.org/wiki/CPAN wikipedia]<br />
[http://www.cpan.org/ homepage]<br />
[https://github.com/Perl-Toolchain-Gang/CPAN-Meta on github]<br />
| yes<br />
| META.json, META.yml, .spec<br />
|-<br />
| Ruby Gem<br />
| Specifications in Ruby called gemspec that can hold arbitrary metadata in a .gemspec file or a Rakefile<br />
| dev <br />
| 2006<br />
| 2015<br />
| 0.3.1<br />
| [http://guides.rubygems.org/specification-reference/ guide]<br />
[https://github.com/pjump/gemspec on github]<br />
| yes<br />
| .gemspec, Rakefile<br />
|-<br />
| JavaScript -npm<br />
| A package.json file containing specifications about npm package. The name and version of the package are a unique identifier, changes to the package should come with changes to the version <br />
| dev <br />
| 2010<br />
| 2017<br />
| -<br />
| [https://docs.npmjs.com/files/package.json documentation]<br />
[https://nodesource.com/blog/the-basics-of-package-json-in-node-js-and-npm/ guide]<br />
| yes<br />
| package.json<br />
|-<br />
| Maven<br />
| pom.xml file in the project root. POM stands for "Project Object Model", an XML representation of a Maven project.<br />
| dev <br />
| -<br />
| 2017<br />
| 3.5.0<br />
| [https://maven.apache.org/pom.html POM reference]<br />
[http://maven.apache.org/ref/3.5.0/maven-model/maven.html maven model]<br />
| yes<br />
| pom.xml<br />
|-<br />
| Octave<br />
| DESCRIPTION file in package which contains various information about package<br />
| dev <br />
| -<br />
| -<br />
| -<br />
| [https://www.gnu.org/software/octave/doc/interpreter/The-DESCRIPTION-File.html howto]<br />
| yes<br />
| DESCRIPTION<br />
|-<br />
| CodeMeta<br />
| a minimal metadata schema for science software and code, in JSON and XML<br />
| software ontology, research, linked data<br />
| 2014<br />
| 2017<br />
| no version<br />
| [http://codemeta.github.io/ homepage]<br />
[https://github.com/codemeta/codemeta on github]<br />
[https://raw.githubusercontent.com/codemeta/codemeta/master/data/codemeta-json-schema.json schema]<br />
| yes<br />
|code.json<br />
|-<br />
| Marc<br />
| MAchine-Readable Cataloging <br />
* MIT is using MARC records<br />
| generic<br />
| 1960s<br />
| -<br />
| -<br />
| [http://www.loc.gov/marc/ homepage]<br />
| no<br />
| -<br />
|-<br />
<!--<br />
|-<br />
| name<br />
| description<br />
| category<br />
| created<br />
| last update<br />
| version<br />
| links<br />
| in crosswalk table<br />
--><br />
|}<br />
<br />
<br />
PRONOM - [https://www.wikidata.org/wiki/User:YULdigitalpreservation/Software] include in Digital preservation schemas<br />
<br />
PREMIS - include in Digital preservation schemas<br />
<br />
DOLCE -Outdated ?<br />
<br />
CSO - Outdated ?<br />
<br />
[[Category:Related work]]<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Software_ontologies&diff=663Software ontologies2017-06-18T17:14:28Z<p>Morane: /* Ontologies, vocabularies and metadata terms */ in separated tables</p>
<hr />
<div>== Definition of Software Ontology ==<br />
In computer science, the term ontology refers to a structure of concepts or entities within a domain, organized by relationships [https://en.wikipedia.org/wiki/Ontology_%28information_science%29]<br />
<br />
The specification takes the form of a representational vocabulary (classes, relations, and so forth), which provide meanings for the vocabulary and formal constraints on its coherent use.<br />
[http://tomgruber.org/writing/ontology-definition-2007.htm]<br />
<br />
A software ontology is a classification of categories describing software with explicit specifications of its entities and relationships. <br />
<br />
We are working on a list of all ontologies, vocabularies and metadata formats describing software. The categorization of contexts is defined as follows:<br />
* software ontology: for a well defined ontology using xml/rdf with a direct link to the ontology itself<br />
* linked data: vocabularies used by search engines<br />
* generic: metadata terms used in other contexts as well as software domain<br />
* research: metadata terms used in research context, in particular software citation<br />
* catalog: metadata terms in a specific catalog<br />
* dev: metadata terms used in the development process. Can be contained in the software source code package, depending usually on code language<br />
<br />
== Ontologies, vocabularies and metadata terms == <br />
Pointers to relevant software ontologies and software metadata, that might be used as inspiration for the upper-level/metadata part of the [[Software Heritage]] data model.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| ADMS.SW<br />
| Asset Description Metadata Schema for Software, and specifically FOSS<br />
| software ontology, research<br />
| 2012<br />
| 2015<br />
| 1.00<br />
| [https://joinup.ec.europa.eu/asset/adms_foss/asset_release/admssw-05 global description] ,<br />
[http://dropbox.ashlock.us/private/ADMS.SW_Specification_1.00.pdf specification],<br />
[https://joinup.ec.europa.eu/svn/adms_foss/adms_sw_v1.00/rdf2html.xsl rdf2html]<br />
| no<br />
| -<br />
|-<br />
| DOAP<br />
| Description of a project<br />
| software ontology<br />
| 2010<br />
| 2017<br />
| no version<br />
| [https://github.com/ewilderj/doap on github],<br />
[https://en.wikipedia.org/wiki/DOAP on wikipedia],<br />
[https://github.com/ewilderj/doap rdf]<br />
| yes<br />
|doap.xml, doap.json<br />
|-<br />
| SEON<br />
| A family of Software Evolution ONtologies<br />
| software ontology<br />
| 2012<br />
| unknown<br />
| no version<br />
| [http://www.se-on.org/ homepage][http://se-on.org/ontologies/index.html documentation][]<br />
| no<br />
| -<br />
<!--<br />
|-<br />
| name<br />
| description<br />
| category<br />
| created<br />
| last update<br />
| version<br />
| links<br />
| in crosswalk table<br />
--><br />
|}<br />
<br />
=== Linked data schemas === <br />
<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| [[Schema.org]]<br />
| Vocabularies for structured data use on the internet and beyond. Code, SoftwareSourceCode and SoftwareApplication are the main classes describing software.<br />
| linked data<br />
| 2011<br />
| 2017<br />
| 3.2<br />
| [https://schema.org/ homepage]<br />
[https://en.wikipedia.org/wiki/Schema.org wikipedia]<br />
[https://github.com/schemaorg/schemaorg github]<br />
| yes<br />
| -<br />
<br />
|-<br />
| Wikidata<br />
| provides data about software with Q7397<br />
| linked data, catalog<br />
| 2012<br />
| 2017<br />
| no version<br />
| [https://www.wikidata.org/wiki/Wikidata:WikiProject_Informatics/Software#Properties generic software propreties],<br />
[https://www.wikidata.org/wiki/Wikidata:WikiProject_Informatics/FLOSS#Properties FOSS-specific properties][https://github.com/Wikidata github]<br />
[https://www.wikidata.org/wiki/Q128751 Source code page]<br />
| yes<br />
| -<br />
|-<br />
| Dbpedia<br />
| Multi-domain ontology<br />
mappings:<br />
* between dbpedia and schema.org without Software entities<br />
* between dbpedia and wikidata and a wikiparser<br />
| linked data<br />
| 2007<br />
| 2015<br />
| 3.11<br />
| [http://dbpedia.org/page/Software software page]<br />
[http://dbpedia.org/page/Source_code software_code page]<br />
| no<br />
| -<br />
|}<br />
<br />
=== Scholarly ecosystem ===<br />
Software ontologies in research and academia.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| SWOP<br />
| The Software Ontology Project- "is a resource for describing software tools, their types, tasks, versions, provenance and data associated." funded by the [https://www.jisc.ac.uk/ JISC]<br />
| software ontology<br />
| 2011<br />
| 2016<br />
| -<br />
| [https://softwareontology.wordpress.com/ SWOP],<br />
[http://theswo.sourceforge.net/ sourceforge project],<br />
[https://softwareontology.wordpress.com/2011/02/23/an-overview-of-sword/ overview blog post]<br />
| no<br />
| -<br />
|-<br />
| [[TOTEM]]<br />
| Trustworthy Online Technical Environment Metadata Database for digital objects in general<br />
| generic, catalog<br />
| 2008<br />
| unknown<br />
| unknown<br />
| [http://www.keep-totem.co.uk/ homepage]<br />
| no<br />
| -<br />
|}<br />
<br />
=== Digital preservation schemas ===<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| DataCite<br />
| the schema is not software specific<br />
| generic, research<br />
| 2009<br />
| 2016<br />
| 4.0<br />
| [https://schema.datacite.org/meta/kernel-4.0/metadata.xsd schema][http://rrr.cs.st-andrews.ac.uk/wp-content/uploads/2015/10/guidelines-software-identification.pdf guidlines]<br />
| yes<br />
|-<br />
|-<br />
| Dublin Core<br />
| -<br />
| generic<br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
| -<br />
|-<br />
| Zenodo<br />
| exported possibilities : MARCXML, Dublin Core, and DataCite Metadata Schema <br />
| generic, research<br />
| -<br />
| -<br />
| -<br />
| [https://guides.github.com/activities/citable-code/ github citable-code]<br />
| yes<br />
| no file in source code<br />
|-<br />
| Figshare<br />
| Making research outputs available online<br />
| generic<br />
| 2011<br />
| -<br />
| -<br />
| -<br />
| yes<br />
| no file in source code<br />
|-<br />
| Marc<br />
| MAchine-Readable Cataloging <br />
* MIT is using MARC records<br />
| generic<br />
| 1960s<br />
| -<br />
| -<br />
| [http://www.loc.gov/marc/ homepage]<br />
| no<br />
| -<br />
|-<br />
|}<br />
<br />
<br />
=== Package management vocabularies ===<br />
Found mostly in the source code itself.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
|-<br />
| R Package Description <br />
| DESCRIPTION file stored in an R package, containing important metadata <br />
| dev <br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
|TBD<br />
|-<br />
| Debian Package<br />
| An effort to collect meta-information about projects. Trying to use DOAP vocabulary. Captured in a file called debian/upstream/metadata in YAML format. another file with EDAM ontology can be provided at: debian/upstream/edam<br />
| dev <br />
| -<br />
| 2017<br />
| -<br />
| [https://wiki.debian.org/UpstreamMetadata wiki]<br />
| yes<br />
| debian/upstream/metadata<br />
|-<br />
| debtags <br />
| debtags are terms used to describe package content in a non-formal way.<br />
| dev<br />
| 2005<br />
| 2017<br />
| no version<br />
| [https://anonscm.debian.org/cgit/debtags/vocabulary.git/tree/debian-packages vocabulary]<br />
[https://wiki.debian.org/Debtags/FAQ wiki]<br />
| no<br />
| not in source code<br />
|-<br />
| Python Distutils (PyPI)<br />
| The Python Package Index (PyPI) stores metadata that describes package. setup;py file is used when package was packaged and distributed by Distutils (the standard for distributing Python Modules)<br />
| dev <br />
| 1999<br />
| 2017<br />
| 35.0.1 Setuptools<br />
|[https://setuptools.readthedocs.io/en/latest/setuptools.html setuptools doc]<br />
[https://en.wikipedia.org/wiki/Python_Package_Index wikipedia]<br />
[https://martin-thoma.com/analyzing-pypi-metadata/ analyzing pypi metadata 2015]<br />
| yes<br />
| setup.py<br />
|-<br />
| Trove Software Map <br />
| Distutils Trove Classification <br />
| dev <br />
| 1998<br />
| 2002<br />
| -<br />
| [http://www.catb.org/~esr/trove/ Trove project]<br />
[https://www.python.org/dev/peps/pep-0301/ usage with Python]<br />
| yes<br />
| -<br />
|-<br />
| CPAN::Meta<br />
| Comprehensive Perl Archive Network (CPAN) used somewhat like a package manager. The CPAN::META known as META.yml or META.json file is typically created by other tools, Module::Build and ExtUtils::MakeMaker. The raw form of the metadata doesn't exists in the source code.<br />
| dev<br />
| 2003<br />
| -<br />
| 2.150010<br />
| [https://en.wikipedia.org/wiki/CPAN wikipedia]<br />
[http://www.cpan.org/ homepage]<br />
[https://github.com/Perl-Toolchain-Gang/CPAN-Meta on github]<br />
| yes<br />
| META.json, META.yml, .spec<br />
|-<br />
| Ruby Gem<br />
| Specifications in Ruby called gemspec that can hold arbitrary metadata in a .gemspec file or a Rakefile<br />
| dev <br />
| 2006<br />
| 2015<br />
| 0.3.1<br />
| [http://guides.rubygems.org/specification-reference/ guide]<br />
[https://github.com/pjump/gemspec on github]<br />
| yes<br />
| .gemspec, Rakefile<br />
|-<br />
| JavaScript -npm<br />
| A package.json file containing specifications about npm package. The name and version of the package are a unique identifier, changes to the package should come with changes to the version <br />
| dev <br />
| 2010<br />
| 2017<br />
| -<br />
| [https://docs.npmjs.com/files/package.json documentation]<br />
[https://nodesource.com/blog/the-basics-of-package-json-in-node-js-and-npm/ guide]<br />
| yes<br />
| package.json<br />
|-<br />
| Maven<br />
| pom.xml file in the project root. POM stands for "Project Object Model", an XML representation of a Maven project.<br />
| dev <br />
| -<br />
| 2017<br />
| 3.5.0<br />
| [https://maven.apache.org/pom.html POM reference]<br />
[http://maven.apache.org/ref/3.5.0/maven-model/maven.html maven model]<br />
| yes<br />
| pom.xml<br />
|-<br />
| Octave<br />
| DESCRIPTION file in package which contains various information about package<br />
| dev <br />
| -<br />
| -<br />
| -<br />
| [https://www.gnu.org/software/octave/doc/interpreter/The-DESCRIPTION-File.html howto]<br />
| yes<br />
| DESCRIPTION<br />
|-<br />
| CodeMeta<br />
| a minimal metadata schema for science software and code, in JSON and XML<br />
| software ontology, research, linked data<br />
| 2014<br />
| 2017<br />
| no version<br />
| [http://codemeta.github.io/ homepage]<br />
[https://github.com/codemeta/codemeta on github]<br />
[https://raw.githubusercontent.com/codemeta/codemeta/master/data/codemeta-json-schema.json schema]<br />
| yes<br />
|code.json<br />
|-<br />
| Marc<br />
| MAchine-Readable Cataloging <br />
* MIT is using MARC records<br />
| generic<br />
| 1960s<br />
| -<br />
| -<br />
| [http://www.loc.gov/marc/ homepage]<br />
| no<br />
| -<br />
|-<br />
<!--<br />
|-<br />
| name<br />
| description<br />
| category<br />
| created<br />
| last update<br />
| version<br />
| links<br />
| in crosswalk table<br />
--><br />
|}<br />
<br />
<br />
PRONOM - [https://www.wikidata.org/wiki/User:YULdigitalpreservation/Software] include in Digital preservation schemas<br />
<br />
PREMIS - include in Digital preservation schemas<br />
<br />
DOLCE -Outdated ?<br />
<br />
CSO - Outdated ?<br />
<br />
[[Category:Related work]]<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Software_ontologies&diff=661Software ontologies2017-05-24T10:27:42Z<p>Morane: </p>
<hr />
<div>== Definition of Software Ontology ==<br />
In computer science, the term ontology refers to a structure of concepts or entities within a domain, organized by relationships [https://en.wikipedia.org/wiki/Ontology_%28information_science%29]<br />
<br />
The specification takes the form of a representational vocabulary (classes, relations, and so forth), which provide meanings for the vocabulary and formal constraints on its coherent use.<br />
[http://tomgruber.org/writing/ontology-definition-2007.htm]<br />
<br />
A software ontology is a classification of categories describing software with explicit specifications of its entities and relationships. <br />
<br />
We are working on a list of all ontologies, vocabularies and metadata formats describing software. The categorization of contexts is defined as follows:<br />
* software ontology: for a well defined ontology using xml/rdf with a direct link to the ontology itself<br />
* linked data: vocabularies used by search engines<br />
* generic: metadata terms used in other contexts as well as software domain<br />
* research: metadata terms used in research context, in particular software citation<br />
* catalog: metadata terms in a specific catalog<br />
* dev: metadata terms used in the development process. Can be contained in the software source code package, depending usually on code language<br />
<br />
== Ontologies, vocabularies and metadata terms == <br />
Pointers to relevant software ontologies and software metadata, that might be used as inspiration for the upper-level/metadata part of the [[Software Heritage]] data model.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| ADMS.SW<br />
| Asset Description Metadata Schema for Software, and specifically FOSS<br />
| software ontology, research<br />
| 2012<br />
| 2015<br />
| 1.00<br />
| [https://joinup.ec.europa.eu/asset/adms_foss/asset_release/admssw-05 global description] ,<br />
[http://dropbox.ashlock.us/private/ADMS.SW_Specification_1.00.pdf specification],<br />
[https://joinup.ec.europa.eu/svn/adms_foss/adms_sw_v1.00/rdf2html.xsl rdf2html]<br />
| no<br />
| -<br />
|-<br />
| DOAP<br />
| Description of a project<br />
| software ontology<br />
| 2010<br />
| 2017<br />
| no version<br />
| [https://github.com/ewilderj/doap on github],<br />
[https://en.wikipedia.org/wiki/DOAP on wikipedia],<br />
[https://github.com/ewilderj/doap rdf]<br />
| yes<br />
|doap.xml, doap.json<br />
|-<br />
| [[Schema.org]]<br />
| Vocabularies for structured data use on the internet and beyond. Code, SoftwareSourceCode and SoftwareApplication are the main classes describing software.<br />
| linked data<br />
| 2011<br />
| 2017<br />
| 3.2<br />
| [https://schema.org/ homepage]<br />
[https://en.wikipedia.org/wiki/Schema.org wikipedia]<br />
[https://github.com/schemaorg/schemaorg github]<br />
| yes<br />
| -<br />
|-<br />
| SEON<br />
| A family of Software Evolution ONtologies<br />
| software ontology<br />
| 2012<br />
| unknown<br />
| no version<br />
| [http://www.se-on.org/ homepage][http://se-on.org/ontologies/index.html documentation][]<br />
| no<br />
| -<br />
|-<br />
| SWOP<br />
| The Software Ontology Project- "is a resource for describing software tools, their types, tasks, versions, provenance and data associated." funded by the [https://www.jisc.ac.uk/ JISC]<br />
| software ontology<br />
| 2011<br />
| 2016<br />
| -<br />
| [https://softwareontology.wordpress.com/ SWOP],<br />
[http://theswo.sourceforge.net/ sourceforge project],<br />
[https://softwareontology.wordpress.com/2011/02/23/an-overview-of-sword/ overview blog post]<br />
| no<br />
| -<br />
|-<br />
| [[TOTEM]]<br />
| Trustworthy Online Technical Environment Metadata Database for digital objects in general<br />
| generic, catalog<br />
| 2008<br />
| unknown<br />
| unknown<br />
| [http://www.keep-totem.co.uk/ homepage]<br />
| no<br />
| -<br />
|-<br />
| Wikidata<br />
| provides data about software with Q7397<br />
| linked data, catalog<br />
| 2012<br />
| 2017<br />
| no version<br />
| [https://www.wikidata.org/wiki/Wikidata:WikiProject_Informatics/Software#Properties generic software propreties],<br />
[https://www.wikidata.org/wiki/Wikidata:WikiProject_Informatics/FLOSS#Properties FOSS-specific properties][https://github.com/Wikidata github]<br />
[https://www.wikidata.org/wiki/Q128751 Source code page]<br />
| yes<br />
| -<br />
|-<br />
| Dbpedia<br />
| Multi-domain ontology<br />
mappings:<br />
* between dbpedia and schema.org without Software entities<br />
* between dbpedia and wikidata and a wikiparser<br />
| linked data<br />
| 2007<br />
| 2015<br />
| 3.11<br />
| [http://dbpedia.org/page/Software software page]<br />
[http://dbpedia.org/page/Source_code software_code page]<br />
| no<br />
| -<br />
|-<br />
| DataCite<br />
| the schema is not software specific<br />
| generic, research<br />
| 2009<br />
| 2016<br />
| 4.0<br />
| [https://schema.datacite.org/meta/kernel-4.0/metadata.xsd schema][http://rrr.cs.st-andrews.ac.uk/wp-content/uploads/2015/10/guidelines-software-identification.pdf guidlines]<br />
| yes<br />
|-<br />
|-<br />
| Dublin Core<br />
| -<br />
| generic<br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
| -<br />
|-<br />
| Zenodo<br />
| exported possibilities : MARCXML, Dublin Core, and DataCite Metadata Schema <br />
| generic, research<br />
| -<br />
| -<br />
| -<br />
| [https://guides.github.com/activities/citable-code/ github citable-code]<br />
| yes<br />
| no file in source code<br />
|-<br />
| Figshare<br />
| Making research outputs available online<br />
| generic<br />
| 2011<br />
| -<br />
| -<br />
| -<br />
| yes<br />
| no file in source code<br />
|-<br />
| code.jsonld <br />
| in CodeMeta crosswalk table but can't find source<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
| -<br />
|-<br />
| R Package Description <br />
| DESCRIPTION file stored in an R package, containing important metadata <br />
| dev <br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
|TBD<br />
|-<br />
| Debian Package<br />
| An effort to collect meta-information about projects. Trying to use DOAP vocabulary. Captured in a file called debian/upstream/metadata in YAML format. another file with EDAM ontology can be provided at: debian/upstream/edam<br />
| dev <br />
| -<br />
| 2017<br />
| -<br />
| [https://wiki.debian.org/UpstreamMetadata wiki]<br />
| yes<br />
| debian/upstream/metadata<br />
|-<br />
| debtags <br />
| debtags are terms used to describe package content in a non-formal way.<br />
| dev<br />
| 2005<br />
| 2017<br />
| no version<br />
| [https://anonscm.debian.org/cgit/debtags/vocabulary.git/tree/debian-packages vocabulary]<br />
[https://wiki.debian.org/Debtags/FAQ wiki]<br />
| no<br />
| not in source code<br />
|-<br />
| Python Distutils (PyPI)<br />
| The Python Package Index (PyPI) stores metadata that describes package. setup;py file is used when package was packaged and distributed by Distutils (the standard for distributing Python Modules)<br />
| dev <br />
| 1999<br />
| 2017<br />
| 35.0.1 Setuptools<br />
|[https://setuptools.readthedocs.io/en/latest/setuptools.html setuptools doc]<br />
[https://en.wikipedia.org/wiki/Python_Package_Index wikipedia]<br />
[https://martin-thoma.com/analyzing-pypi-metadata/ analyzing pypi metadata 2015]<br />
| yes<br />
| setup.py<br />
|-<br />
| Trove Software Map <br />
| Distutils Trove Classification <br />
| dev <br />
| 1998<br />
| 2002<br />
| -<br />
| [http://www.catb.org/~esr/trove/ Trove project]<br />
[https://www.python.org/dev/peps/pep-0301/ usage with Python]<br />
| yes<br />
| -<br />
|-<br />
| CPAN::Meta<br />
| Comprehensive Perl Archive Network (CPAN) used somewhat like a package manager. The CPAN::META known as META.yml or META.json file is typically created by other tools, Module::Build and ExtUtils::MakeMaker. The raw form of the metadata doesn't exists in the source code.<br />
| dev<br />
| 2003<br />
| -<br />
| 2.150010<br />
| [https://en.wikipedia.org/wiki/CPAN wikipedia]<br />
[http://www.cpan.org/ homepage]<br />
[https://github.com/Perl-Toolchain-Gang/CPAN-Meta on github]<br />
| yes<br />
| META.json, META.yml, .spec<br />
|-<br />
| Ruby Gem<br />
| Specifications in Ruby called gemspec that can hold arbitrary metadata in a .gemspec file or a Rakefile<br />
| dev <br />
| 2006<br />
| 2015<br />
| 0.3.1<br />
| [http://guides.rubygems.org/specification-reference/ guide]<br />
[https://github.com/pjump/gemspec on github]<br />
| yes<br />
| .gemspec, Rakefile<br />
|-<br />
| JavaScript -npm<br />
| A package.json file containing specifications about npm package. The name and version of the package are a unique identifier, changes to the package should come with changes to the version <br />
| dev <br />
| 2010<br />
| 2017<br />
| -<br />
| [https://docs.npmjs.com/files/package.json documentation]<br />
[https://nodesource.com/blog/the-basics-of-package-json-in-node-js-and-npm/ guide]<br />
| yes<br />
| package.json<br />
|-<br />
| Maven<br />
| pom.xml file in the project root. POM stands for "Project Object Model", an XML representation of a Maven project.<br />
| dev <br />
| -<br />
| 2017<br />
| 3.5.0<br />
| [https://maven.apache.org/pom.html POM reference]<br />
[http://maven.apache.org/ref/3.5.0/maven-model/maven.html maven model]<br />
| yes<br />
| pom.xml<br />
|-<br />
| Octave<br />
| DESCRIPTION file in package which contains various information about package<br />
| dev <br />
| -<br />
| -<br />
| -<br />
| [https://www.gnu.org/software/octave/doc/interpreter/The-DESCRIPTION-File.html howto]<br />
| yes<br />
| DESCRIPTION<br />
|-<br />
| CodeMeta<br />
| a minimal metadata schema for science software and code, in JSON and XML<br />
| software ontology, research, linked data<br />
| 2014<br />
| 2017<br />
| no version<br />
| [http://codemeta.github.io/ homepage]<br />
[https://github.com/codemeta/codemeta on github]<br />
[https://raw.githubusercontent.com/codemeta/codemeta/master/data/codemeta-json-schema.json schema]<br />
| yes<br />
|code.json<br />
|-<br />
| Marc<br />
| MAchine-Readable Cataloging <br />
* MIT is using MARC records<br />
| generic<br />
| 1960s<br />
| -<br />
| -<br />
| [http://www.loc.gov/marc/ homepage]<br />
| no<br />
| -<br />
|-<br />
<!--<br />
|-<br />
| name<br />
| description<br />
| category<br />
| created<br />
| last update<br />
| version<br />
| links<br />
| in crosswalk table<br />
--><br />
|}<br />
<br />
<br />
PRONOM - [https://www.wikidata.org/wiki/User:YULdigitalpreservation/Software]<br />
<br />
DOLCE -Outdated ?<br />
<br />
CSO - Outdated ?<br />
<br />
[[Category:Related work]]<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Software_catalogs&diff=660Software catalogs2017-05-23T14:28:13Z<p>Morane: </p>
<hr />
<div>Software catalogs are used to capture data about software. Most use a metadata schema or a software ontology to do so. <br />
<br />
== List of Software catalogs ==<br />
* [https://directory.fsf.org/wiki/Main_Page The Free Software Directory] FSF's (Free Software Foundation) catalog of free software.<br />
* [http://www.ontosoft.org/portal/ Ontosoft] - geosciences software.<br />
* [http://swmath.org/ SwMATH]- math software, [http://swmath.org/media/documents/swMATH.pdf swMath article]<br />
* [http://libraries.io/ libraries.io]- keeps track of open source libraries, modules and frameworks.<br />
* [http://orms.mfo.de/ orms]<br />
* [http://www.openhub.net/ OpenHub]<br />
* [http://freecode.com/ FreeCode] read only copy of the old Freshmeat project, [http://fgiasson.com/blog/index.php/2007/08/04/freshmeatnet-now-available-in-doap-43-000-new-doap-projects/ apparently converted in DOAP sometimes in 2007]<br />
* [https://www.projet-plume.org/breve/le-projet-plume-devient-le-service-fenix-fiches-devaluation-normalisees-issues-de-lexperience Plume/Fenix] hundreds of descriptions of software used in research in France<br />
* [http://distrowatch.com/ distrowatch] first published in 2001, keeps track of linux distributions and open source packages.<br />
* [https://freshfoss.com/ freshfoss] providing updates on free and open source software.<br />
<br />
<br />
<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Best_practices_using_metadata&diff=658Best practices using metadata2017-05-15T14:24:14Z<p>Morane: </p>
<hr />
<div><br />
<br />
1. Use a detailed metadata file with name appropriate to context as listed bellow :<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
!context<br />
!filename<br />
!in CodeMeta crosswalk table<br />
!implemented for swh translation<br />
|-<br />
|java- Maven<br />
|pom.xml<br />
|yes<br />
|no<br />
|-<br />
|Octave<br />
|DESCRIPTION<br />
|yes<br />
|no<br />
|-<br />
|R package <br />
|DESCRIPTION<br />
|yes<br />
|no<br />
|-<br />
|ruby gems <br />
|.gemspec or Rakefile <br />
|yes<br />
|no<br />
|-<br />
|Javascript npm <br />
|package.json, [ AUTHORS, README, CHANGES, LICENSE & NOTICE] files<br />
|yes<br />
|no<br />
|-<br />
|Perl CPAN::META <br />
|META.json, META.yml, .sDpec<br />
|yes<br />
|no<br />
|-<br />
|Dart <br />
|pubspec.yaml<br />
|no<br />
|no<br />
|-<br />
|Debian package <br />
|debian/upstream/metadata<br />
|yes<br />
|no<br />
|-<br />
|puppet <br />
|metadata.json<br />
|no<br />
|no<br />
|-<br />
|PyPI <br />
|setup.py<br />
|yes<br />
|no<br />
|-<br />
|Scientific software <br />
|CITATION<br />
|no<br />
|no<br />
|-<br />
|CodeMeta <br />
|CODE, code.json, codemeta.json<br />
|yes<br />
|no<br />
|-<br />
|Java gradle <br />
|gradle.properties<br />
|no<br />
|no<br />
|-<br />
|Jekyll <br />
|_config.yml<br />
-no<br />
|no<br />
|-<br />
|clojure <br />
|project.clj or build.boot<br />
|no<br />
|no<br />
|-<br />
|haskell <br />
|<project name>.cabal <br />
|no<br />
|no<br />
|-<br />
|scala<br />
|build.sbt<br />
|no<br />
|no<br />
|-<br />
|Ocaml<br />
|opam<br />
|no<br />
|no<br />
|}<br />
<br />
2. Use Semantic Versioning [http://semver.org/] for reproducibility purposes.<br />
<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Best_practices_using_metadata&diff=657Best practices using metadata2017-05-15T14:19:32Z<p>Morane: </p>
<hr />
<div><br />
<br />
1. Use a detailed metadata file with name appropriate to context as listed bellow :<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
!context<br />
!filename<br />
!implemented for swh translation<br />
|-<br />
|java- Maven<br />
|pom.xml<br />
|no<br />
|-<br />
|Octave<br />
|DESCRIPTION<br />
|no<br />
|-<br />
|R package <br />
|DESCRIPTION<br />
|no<br />
|-<br />
|ruby gems <br />
|.gemspec or Rakefile <br />
|no<br />
|-<br />
|Javascript npm <br />
|package.json, [ AUTHORS, README, CHANGES, LICENSE & NOTICE] files<br />
|no<br />
|-<br />
|Perl CPAN::META <br />
|META.json, META.yml, .sDpec<br />
|no<br />
|-<br />
|Dart <br />
|pubspec.yaml<br />
|no<br />
|-<br />
|Debian package <br />
|debian/upstream/metadata<br />
|no<br />
|-<br />
|puppet <br />
|metadata.json<br />
|no<br />
|-<br />
|PyPI <br />
|setup.py<br />
|no<br />
|-<br />
|Scientific software <br />
|CITATION<br />
|no<br />
|-<br />
|CodeMeta <br />
|CODE, code.json<br />
|no<br />
|-<br />
|Java gradle <br />
|gradle.properties<br />
|no<br />
|-<br />
|Jekyll <br />
|_config.yml<br />
|no<br />
|-<br />
|clojure <br />
|project.clj or build.boot<br />
|no<br />
|-<br />
|haskell <br />
|<project name>.cabal <br />
|no<br />
|-<br />
|scala<br />
|build.sbt<br />
|no<br />
|-<br />
|Ocaml<br />
|opam<br />
|no<br />
|}<br />
<br />
2. Use Semantic Versioning [http://semver.org/] for reproducibility purposes.<br />
<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Best_practices_using_metadata&diff=655Best practices using metadata2017-05-05T14:36:01Z<p>Morane: Created page with " 1. Use a detailed metadata file with name appropriate to context as listed bellow : {| class="wikitable sortable" |- !context !filename !implemented for swh translation |-..."</p>
<hr />
<div><br />
<br />
1. Use a detailed metadata file with name appropriate to context as listed bellow :<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
!context<br />
!filename<br />
!implemented for swh translation<br />
|-<br />
|java- Maven<br />
|pom.xml<br />
|no<br />
|-<br />
|Octave <br />
|DESCRIPTION<br />
|no<br />
|-<br />
|ruby gems <br />
|.gemspec or Rakefile <br />
|no<br />
|-<br />
|Javascript npm <br />
|package.json, [ AUTHORS, README, CHANGES, LICENSE & NOTICE] files<br />
|no<br />
|-<br />
|Perl CPAN::META <br />
|META.json, META.yml, .sDpec<br />
|no<br />
|-<br />
|Dart <br />
|pubspec.yaml<br />
|no<br />
|-<br />
|Debian package <br />
|debian/upstream/metadata<br />
|no<br />
|-<br />
|puppet <br />
|metadata.json<br />
|no<br />
|-<br />
|PyPI <br />
|setup.py<br />
|no<br />
|-<br />
|Scientific software <br />
|CITATION<br />
|no<br />
|-<br />
|CodeMeta <br />
|CODE, code.json<br />
|no<br />
|-<br />
|Java gradle <br />
|gradle.properties<br />
|no<br />
|-<br />
|Jekyll <br />
|_config.yml<br />
|no<br />
|-<br />
|clojure <br />
|project.clj or build.boot<br />
|no<br />
|-<br />
|haskell <br />
|<project name>.cabal <br />
|no<br />
|-<br />
|scala<br />
|build.sbt<br />
|no<br />
|-<br />
|Ocaml<br />
|opam<br />
|no<br />
|}<br />
<br />
2. Use Semantic Versioning [http://semver.org/] for reproducibility purposes.<br />
<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Software_ontologies&diff=654Software ontologies2017-04-27T08:35:23Z<p>Morane: /* Ontologies, vocabularies and metadata terms */</p>
<hr />
<div>== Definition of Software Ontology ==<br />
In computer science, the term ontology refers to a structure of concepts or entities within a domain, organized by relationships [https://en.wikipedia.org/wiki/Ontology_%28information_science%29]<br />
<br />
The specification takes the form of a representational vocabulary (classes, relations, and so forth), which provide meanings for the vocabulary and formal constraints on its coherent use.<br />
[http://tomgruber.org/writing/ontology-definition-2007.htm]<br />
<br />
A software ontology is a classification of categories describing software with explicit specifications of its entities and relationships. <br />
<br />
We are working on a list of all ontologies, vocabularies and metadata formats describing software. The categorization of contexts is defined as follows:<br />
* software ontology: for a well defined ontology using xml/rdf with a direct link to the ontology itself<br />
* linked data: vocabularies used by search engines<br />
* generic: metadata terms used in other contexts as well as software domain<br />
* research: metadata terms used in research context, in particular software citation<br />
* catalog: metadata terms in a specific catalog<br />
* dev: metadata terms used in the development process. Can be contained in the software source code package, depending usually on code language<br />
<br />
== Ontologies, vocabularies and metadata terms == <br />
Pointers to relevant software ontologies and software metadata, that might be used as inspiration for the upper-level/metadata part of the [[Software Heritage]] data model.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| ADMS.SW<br />
| Asset Description Metadata Schema for Software, and specifically FOSS<br />
| software ontology, research<br />
| 2012<br />
| 2015<br />
| 1.00<br />
| [https://joinup.ec.europa.eu/asset/adms_foss/asset_release/admssw-05 global description] ,<br />
[http://dropbox.ashlock.us/private/ADMS.SW_Specification_1.00.pdf specification],<br />
[https://joinup.ec.europa.eu/svn/adms_foss/adms_sw_v1.00/rdf2html.xsl rdf2html]<br />
| no<br />
| -<br />
|-<br />
| DOAP<br />
| Description of a project<br />
| software ontology<br />
| 2010<br />
| 2017<br />
| no version<br />
| [https://github.com/ewilderj/doap on github],<br />
[https://en.wikipedia.org/wiki/DOAP on wikipedia],<br />
[https://github.com/ewilderj/doap rdf]<br />
| waiting pull request<br />
|doap.xml, doap.json<br />
|-<br />
| [[Schema.org]]<br />
| Vocabularies for structured data use on the internet and beyond. Code, SoftwareSourceCode and SoftwareApplication are the main classes describing software.<br />
| linked data<br />
| 2011<br />
| 2017<br />
| 3.2<br />
| [https://schema.org/ homepage]<br />
[https://en.wikipedia.org/wiki/Schema.org wikipedia]<br />
[https://github.com/schemaorg/schemaorg github]<br />
| no but used by CodeMeta<br />
| -<br />
|-<br />
| SEON<br />
| A family of Software Evolution ONtologies<br />
| software ontology<br />
| 2012<br />
| unknown<br />
| no version<br />
| [http://www.se-on.org/ homepage][http://se-on.org/ontologies/index.html documentation][]<br />
| no<br />
| -<br />
|-<br />
| SWOP<br />
| The Software Ontology Project- "is a resource for describing software tools, their types, tasks, versions, provenance and data associated." funded by the [https://www.jisc.ac.uk/ JISC]<br />
| software ontology<br />
| 2011<br />
| 2016<br />
| -<br />
| [https://softwareontology.wordpress.com/ SWOP],<br />
[http://theswo.sourceforge.net/ sourceforge project],<br />
[https://softwareontology.wordpress.com/2011/02/23/an-overview-of-sword/ overview blog post]<br />
| no<br />
| -<br />
|-<br />
| [[TOTEM]]<br />
| Trustworthy Online Technical Environment Metadata Database for digital objects in general<br />
| generic, catalog<br />
| 2008<br />
| unknown<br />
| unknown<br />
| [http://www.keep-totem.co.uk/ homepage]<br />
| no<br />
| -<br />
|-<br />
| Wikidata<br />
| provides data about software with Q7397<br />
| linked data, catalog<br />
| 2012<br />
| 2017<br />
| no version<br />
| [https://www.wikidata.org/wiki/Wikidata:WikiProject_Informatics/Software#Properties generic software propreties],<br />
[https://www.wikidata.org/wiki/Wikidata:WikiProject_Informatics/FLOSS#Properties FOSS-specific properties][https://github.com/Wikidata github]<br />
[https://www.wikidata.org/wiki/Q128751 Source code page]<br />
| no<br />
| -<br />
|-<br />
| Dbpedia<br />
| Multi-domain ontology<br />
mappings:<br />
* between dbpedia and schema.org without Software entities<br />
* between dbpedia and wikidata and a wikiparser<br />
| linked data<br />
| 2007<br />
| 2015<br />
| 3.11<br />
| [http://dbpedia.org/page/Software software page]<br />
[http://dbpedia.org/page/Source_code software_code page]<br />
| no<br />
| -<br />
|-<br />
| DataCite<br />
| the schema is not software specific<br />
| generic, research<br />
| 2009<br />
| 2016<br />
| 4.0<br />
| [https://schema.datacite.org/meta/kernel-4.0/metadata.xsd schema][http://rrr.cs.st-andrews.ac.uk/wp-content/uploads/2015/10/guidelines-software-identification.pdf guidlines]<br />
| yes<br />
|-<br />
|-<br />
| Dublin Core<br />
| -<br />
| generic<br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
| -<br />
|-<br />
| Zenodo<br />
| exported possibilities : MARCXML, Dublin Core, and DataCite Metadata Schema <br />
| generic, research<br />
| -<br />
| -<br />
| -<br />
| [https://guides.github.com/activities/citable-code/ github citable-code]<br />
| yes<br />
| no file in source code<br />
|-<br />
| Figshare<br />
| Making research outputs available online<br />
| generic<br />
| 2011<br />
| -<br />
| -<br />
| -<br />
| yes<br />
| no file in source code<br />
|-<br />
| code.jsonld <br />
| in CodeMeta crosswalk table but can't find source<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
| -<br />
|-<br />
| R Package Description <br />
| DESCRIPTION file stored in an R package, containing important metadata <br />
| dev <br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
|TBD<br />
|-<br />
| Debian Package<br />
| An effort to collect meta-information about projects. Trying to use DOAP vocabulary. Captured in a file called debian/upstream/metadata in YAML format. another file with EDAM ontology can be provided at: debian/upstream/edam<br />
| dev <br />
| -<br />
| 2017<br />
| -<br />
| [https://wiki.debian.org/UpstreamMetadata wiki]<br />
| yes<br />
| debian/upstream/metadata<br />
|-<br />
| debtags <br />
| debtags are terms used to describe package content in a non-formal way.<br />
| dev<br />
| 2005<br />
| 2017<br />
| no version<br />
| [https://anonscm.debian.org/cgit/debtags/vocabulary.git/tree/debian-packages vocabulary]<br />
[https://wiki.debian.org/Debtags/FAQ wiki]<br />
| no<br />
| not in source code<br />
|-<br />
| Python Distutils (PyPI)<br />
| The Python Package Index (PyPI) stores metadata that describes package. setup;py file is used when package was packaged and distributed by Distutils (the standard for distributing Python Modules)<br />
| dev <br />
| 1999<br />
| 2017<br />
| 35.0.1 Setuptools<br />
|[https://setuptools.readthedocs.io/en/latest/setuptools.html setuptools doc]<br />
[https://en.wikipedia.org/wiki/Python_Package_Index wikipedia]<br />
[https://martin-thoma.com/analyzing-pypi-metadata/ analyzing pypi metadata 2015]<br />
| yes<br />
| setup.py<br />
|-<br />
| Trove Software Map <br />
| Distutils Trove Classification <br />
| dev <br />
| 1998<br />
| 2002<br />
| -<br />
| [http://www.catb.org/~esr/trove/ Trove project]<br />
[https://www.python.org/dev/peps/pep-0301/ usage with Python]<br />
| yes<br />
| -<br />
|-<br />
| CPAN::Meta<br />
| Comprehensive Perl Archive Network (CPAN) used somewhat like a package manager. The CPAN::META known as META.yml or META.json file is typically created by other tools, Module::Build and ExtUtils::MakeMaker. The raw form of the metadata doesn't exists in the source code.<br />
| dev<br />
| 2003<br />
| -<br />
| 2.150010<br />
| [https://en.wikipedia.org/wiki/CPAN wikipedia]<br />
[http://www.cpan.org/ homepage]<br />
[https://github.com/Perl-Toolchain-Gang/CPAN-Meta on github]<br />
| yes<br />
| META.json, META.yml, .spec<br />
|-<br />
| Ruby Gem<br />
| Specifications in Ruby called gemspec that can hold arbitrary metadata in a .gemspec file or a Rakefile<br />
| dev <br />
| 2006<br />
| 2015<br />
| 0.3.1<br />
| [http://guides.rubygems.org/specification-reference/ guide]<br />
[https://github.com/pjump/gemspec on github]<br />
| yes<br />
| .gemspec, Rakefile<br />
|-<br />
| JavaScript -npm<br />
| A package.json file containing specifications about npm package. The name and version of the package are a unique identifier, changes to the package should come with changes to the version <br />
| dev <br />
| 2010<br />
| 2017<br />
| -<br />
| [https://docs.npmjs.com/files/package.json documentation]<br />
[https://nodesource.com/blog/the-basics-of-package-json-in-node-js-and-npm/ guide]<br />
| yes<br />
| package.json<br />
|-<br />
| Maven<br />
| pom.xml file in the project root. POM stands for "Project Object Model", an XML representation of a Maven project.<br />
| dev <br />
| -<br />
| 2017<br />
| 3.5.0<br />
| [https://maven.apache.org/pom.html POM reference]<br />
[http://maven.apache.org/ref/3.5.0/maven-model/maven.html maven model]<br />
| yes<br />
| pom.xml<br />
|-<br />
| Octave<br />
| DESCRIPTION file in package which contains various information about package<br />
| dev <br />
| -<br />
| -<br />
| -<br />
| [https://www.gnu.org/software/octave/doc/interpreter/The-DESCRIPTION-File.html howto]<br />
| yes<br />
| DESCRIPTION<br />
|-<br />
| CodeMeta<br />
| a minimal metadata schema for science software and code, in JSON and XML<br />
| software ontology, research, linked data<br />
| 2014<br />
| 2017<br />
| no version<br />
| [http://codemeta.github.io/ homepage]<br />
[https://github.com/codemeta/codemeta on github]<br />
[https://raw.githubusercontent.com/codemeta/codemeta/master/data/codemeta-json-schema.json schema]<br />
| yes<br />
|code.json<br />
|-<br />
| Marc<br />
| MAchine-Readable Cataloging <br />
* MIT is using MARC records<br />
| generic<br />
| 1960s<br />
| -<br />
| -<br />
| [http://www.loc.gov/marc/ homepage]<br />
| no<br />
| -<br />
|-<br />
<!--<br />
|-<br />
| name<br />
| description<br />
| category<br />
| created<br />
| last update<br />
| version<br />
| links<br />
| in crosswalk table<br />
--><br />
|}<br />
<br />
<br />
PRONOM - [https://www.wikidata.org/wiki/User:YULdigitalpreservation/Software]<br />
<br />
DOLCE -Outdated ?<br />
<br />
CSO - Outdated ?<br />
<br />
[[Category:Related work]]<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Software_ontologies&diff=653Software ontologies2017-04-27T08:33:30Z<p>Morane: </p>
<hr />
<div>== Definition of Software Ontology ==<br />
In computer science, the term ontology refers to a structure of concepts or entities within a domain, organized by relationships [https://en.wikipedia.org/wiki/Ontology_%28information_science%29]<br />
<br />
The specification takes the form of a representational vocabulary (classes, relations, and so forth), which provide meanings for the vocabulary and formal constraints on its coherent use.<br />
[http://tomgruber.org/writing/ontology-definition-2007.htm]<br />
<br />
A software ontology is a classification of categories describing software with explicit specifications of its entities and relationships. <br />
<br />
We are working on a list of all ontologies, vocabularies and metadata formats describing software. The categorization of contexts is defined as follows:<br />
* software ontology: for a well defined ontology using xml/rdf with a direct link to the ontology itself<br />
* linked data: vocabularies used by search engines<br />
* generic: metadata terms used in other contexts as well as software domain<br />
* research: metadata terms used in research context, in particular software citation<br />
* catalog: metadata terms in a specific catalog<br />
* dev: metadata terms used in the development process. Can be contained in the software source code package, depending usually on code language<br />
<br />
== Ontologies, vocabularies and metadata terms == <br />
Pointers to relevant software ontologies and software metadata, that might be used as inspiration for the upper-level/metadata part of the [[Software Heritage]] data model.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! name<br />
! description<br />
! context<br />
! created<br />
! last update<br />
! version<br />
! links<br />
! in CodeMeta crosswalk table<br />
! file name<br />
|-<br />
| ADMS.SW<br />
| Asset Description Metadata Schema for Software, and specifically FOSS<br />
| software ontology, research<br />
| 2012<br />
| 2015<br />
| 1.00<br />
| [https://joinup.ec.europa.eu/asset/adms_foss/asset_release/admssw-05 global description] ,<br />
[http://dropbox.ashlock.us/private/ADMS.SW_Specification_1.00.pdf specification],<br />
[https://joinup.ec.europa.eu/svn/adms_foss/adms_sw_v1.00/rdf2html.xsl rdf2html]<br />
| no<br />
| -<br />
|-<br />
| DOAP<br />
| Description of a project<br />
| software ontology<br />
| 2010<br />
| 2017<br />
| no version<br />
| [https://github.com/ewilderj/doap on github],<br />
[https://en.wikipedia.org/wiki/DOAP on wikipedia],<br />
[https://github.com/ewilderj/doap rdf]<br />
| waiting pull request<br />
|doap.xml, doap.json<br />
|-<br />
| [[Schema.org]]<br />
| Vocabularies for structured data use on the internet and beyond. Code, SoftwareSourceCode and SoftwareApplication are the main classes describing software.<br />
| linked data<br />
| 2011<br />
| 2017<br />
| 3.2<br />
| [https://schema.org/ homepage]<br />
[https://en.wikipedia.org/wiki/Schema.org wikipedia]<br />
[https://github.com/schemaorg/schemaorg github]<br />
| no but used by CodeMeta<br />
|-<br />
|-<br />
| SEON<br />
| A family of Software Evolution ONtologies<br />
| software ontology<br />
| 2012<br />
| unknown<br />
| no version<br />
| [http://www.se-on.org/ homepage][http://se-on.org/ontologies/index.html documentation][]<br />
| no<br />
|-<br />
|-<br />
| SWOP<br />
| The Software Ontology Project- "is a resource for describing software tools, their types, tasks, versions, provenance and data associated." funded by the [https://www.jisc.ac.uk/ JISC]<br />
| software ontology<br />
| 2011<br />
| 2016<br />
| -<br />
| [https://softwareontology.wordpress.com/ SWOP],<br />
[http://theswo.sourceforge.net/ sourceforge project],<br />
[https://softwareontology.wordpress.com/2011/02/23/an-overview-of-sword/ overview blog post]<br />
| no<br />
|-<br />
| [[TOTEM]]<br />
| Trustworthy Online Technical Environment Metadata Database for digital objects in general<br />
| generic, catalog<br />
| 2008<br />
| unknown<br />
| unknown<br />
| [http://www.keep-totem.co.uk/ homepage]<br />
| no<br />
|-<br />
| Wikidata<br />
| provides data about software with Q7397<br />
| linked data, catalog<br />
| 2012<br />
| 2017<br />
| no version<br />
| [https://www.wikidata.org/wiki/Wikidata:WikiProject_Informatics/Software#Properties generic software propreties],<br />
[https://www.wikidata.org/wiki/Wikidata:WikiProject_Informatics/FLOSS#Properties FOSS-specific properties][https://github.com/Wikidata github]<br />
[https://www.wikidata.org/wiki/Q128751 Source code page]<br />
| no<br />
|-<br />
|-<br />
| Dbpedia<br />
| Multi-domain ontology<br />
mappings:<br />
* between dbpedia and schema.org without Software entities<br />
* between dbpedia and wikidata and a wikiparser<br />
| linked data<br />
| 2007<br />
| 2015<br />
| 3.11<br />
| [http://dbpedia.org/page/Software software page]<br />
[http://dbpedia.org/page/Source_code software_code page]<br />
| no<br />
|-<br />
|-<br />
| DataCite<br />
| the schema is not software specific<br />
| generic, research<br />
| 2009<br />
| 2016<br />
| 4.0<br />
| [https://schema.datacite.org/meta/kernel-4.0/metadata.xsd schema][http://rrr.cs.st-andrews.ac.uk/wp-content/uploads/2015/10/guidelines-software-identification.pdf guidlines]<br />
| yes<br />
|-<br />
|-<br />
| Dublin Core<br />
| -<br />
| generic<br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
|-<br />
|-<br />
| Zenodo<br />
| exported possibilities : MARCXML, Dublin Core, and DataCite Metadata Schema <br />
| generic, research<br />
| -<br />
| -<br />
| -<br />
| [https://guides.github.com/activities/citable-code/ github citable-code]<br />
| yes<br />
| no file in source code<br />
|-<br />
| Figshare<br />
| Making research outputs available online<br />
| generic<br />
| 2011<br />
| -<br />
| -<br />
| -<br />
| yes<br />
| no file in source code<br />
|-<br />
| code.jsonld <br />
| in CodeMeta crosswalk table but can't find source<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
|-<br />
|-<br />
| R Package Description <br />
| DESCRIPTION file stored in an R package, containing important metadata <br />
| dev <br />
| -<br />
| -<br />
| -<br />
| -<br />
| yes<br />
|TBD<br />
|-<br />
| Debian Package<br />
| An effort to collect meta-information about projects. Trying to use DOAP vocabulary. Captured in a file called debian/upstream/metadata in YAML format. another file with EDAM ontology can be provided at: debian/upstream/edam<br />
| dev <br />
| -<br />
| 2017<br />
| -<br />
| [https://wiki.debian.org/UpstreamMetadata wiki]<br />
| yes<br />
| debian/upstream/metadata<br />
|-<br />
| debtags <br />
| debtags are terms used to describe package content in a non-formal way.<br />
| dev<br />
| 2005<br />
| 2017<br />
| no version<br />
| [https://anonscm.debian.org/cgit/debtags/vocabulary.git/tree/debian-packages vocabulary]<br />
[https://wiki.debian.org/Debtags/FAQ wiki]<br />
| no<br />
| not in source code<br />
|-<br />
| Python Distutils (PyPI)<br />
| The Python Package Index (PyPI) stores metadata that describes package. setup;py file is used when package was packaged and distributed by Distutils (the standard for distributing Python Modules)<br />
| dev <br />
| 1999<br />
| 2017<br />
| 35.0.1 Setuptools<br />
|[https://setuptools.readthedocs.io/en/latest/setuptools.html setuptools doc]<br />
[https://en.wikipedia.org/wiki/Python_Package_Index wikipedia]<br />
[https://martin-thoma.com/analyzing-pypi-metadata/ analyzing pypi metadata 2015]<br />
| yes<br />
| setup.py<br />
|-<br />
| Trove Software Map <br />
| Distutils Trove Classification <br />
| dev <br />
| 1998<br />
| 2002<br />
| -<br />
| [http://www.catb.org/~esr/trove/ Trove project]<br />
[https://www.python.org/dev/peps/pep-0301/ usage with Python]<br />
| yes<br />
|-<br />
|-<br />
| CPAN::Meta<br />
| Comprehensive Perl Archive Network (CPAN) used somewhat like a package manager. The CPAN::META known as META.yml or META.json file is typically created by other tools, Module::Build and ExtUtils::MakeMaker. The raw form of the metadata doesn't exists in the source code.<br />
| dev<br />
| 2003<br />
| -<br />
| 2.150010<br />
| [https://en.wikipedia.org/wiki/CPAN wikipedia]<br />
[http://www.cpan.org/ homepage]<br />
[https://github.com/Perl-Toolchain-Gang/CPAN-Meta on github]<br />
| yes<br />
| META.json, META.yml, .spec<br />
|-<br />
| Ruby Gem<br />
| Specifications in Ruby called gemspec that can hold arbitrary metadata in a .gemspec file or a Rakefile<br />
| dev <br />
| 2006<br />
| 2015<br />
| 0.3.1<br />
| [http://guides.rubygems.org/specification-reference/ guide]<br />
[https://github.com/pjump/gemspec on github]<br />
| yes<br />
| .gemspec, Rakefile<br />
|-<br />
| JavaScript -npm<br />
| A package.json file containing specifications about npm package. The name and version of the package are a unique identifier, changes to the package should come with changes to the version <br />
| dev <br />
| 2010<br />
| 2017<br />
| -<br />
| [https://docs.npmjs.com/files/package.json documentation]<br />
[https://nodesource.com/blog/the-basics-of-package-json-in-node-js-and-npm/ guide]<br />
| yes<br />
| package.json<br />
|-<br />
| Maven<br />
| pom.xml file in the project root. POM stands for "Project Object Model", an XML representation of a Maven project.<br />
| dev <br />
| -<br />
| 2017<br />
| 3.5.0<br />
| [https://maven.apache.org/pom.html POM reference]<br />
[http://maven.apache.org/ref/3.5.0/maven-model/maven.html maven model]<br />
| yes<br />
| pom.xml<br />
|-<br />
| Octave<br />
| DESCRIPTION file in package which contains various information about package<br />
| dev <br />
| -<br />
| -<br />
| -<br />
| [https://www.gnu.org/software/octave/doc/interpreter/The-DESCRIPTION-File.html howto]<br />
| yes<br />
| DESCRIPTION<br />
|-<br />
| CodeMeta<br />
| a minimal metadata schema for science software and code, in JSON and XML<br />
| software ontology, research, linked data<br />
| 2014<br />
| 2017<br />
| no version<br />
| [http://codemeta.github.io/ homepage]<br />
[https://github.com/codemeta/codemeta on github]<br />
[https://raw.githubusercontent.com/codemeta/codemeta/master/data/codemeta-json-schema.json schema]<br />
| yes<br />
|code.json<br />
|-<br />
| Marc<br />
| MAchine-Readable Cataloging <br />
* MIT is using MARC records<br />
| generic<br />
| 1960s<br />
| -<br />
| -<br />
| [http://www.loc.gov/marc/ homepage]<br />
| no<br />
|-<br />
<!--<br />
|-<br />
| name<br />
| description<br />
| category<br />
| created<br />
| last update<br />
| version<br />
| links<br />
| in crosswalk table<br />
--><br />
|}<br />
<br />
<br />
PRONOM - [https://www.wikidata.org/wiki/User:YULdigitalpreservation/Software]<br />
<br />
DOLCE -Outdated ?<br />
<br />
CSO - Outdated ?<br />
<br />
[[Category:Related work]]<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Metadata_initiatives&diff=652Metadata initiatives2017-04-27T08:32:26Z<p>Morane: </p>
<hr />
<div>Collaborations intended to harmonize the chaos regarding metadata and linked data about Software.<br />
<br />
== List of initiatives and contacts ==<br />
* FORCE11- <br />
** [https://www.force11.org/group/software-citation-working-group Software Citation working group]<br />
** [https://www.force11.org/group/software-citation-implementation-working-group Software Citation Implementation working group] <br />
* Software Preservation Network (SPN) - [http://www.softwarepreservationnetwork.org/working-groups/metadatastandards/ Metadata Standards and Policies working group]- Katherine Thornton and Elizabeth Roke<br />
* [[CodeMeta]]<br />
* [https://github.com/nexB/aboutcode AboutCode]- discover and uncover data about software code. A nexB project. - Philippe Ombredanne<br />
* BNF : metadata group<br />
<br />
== Issues for discussion ==<br />
* In the effort of harmonizing metadata : <br />
** should we strive to contain all domains, every use case and every exception?<br />
** should we keep only the vital minimum for citation and search?<br />
* Terminology : What is Software ?<br />
*** distinguishing between a software entity and a software project <br />
*** distinguishing between software "object"(executable) and software source code<br />
*** different versions form one software entity?<br />
<br />
<br />
<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Metadata_initiatives&diff=651Metadata initiatives2017-04-27T08:32:14Z<p>Morane: /* List of initiatives and contacts */</p>
<hr />
<div>Collaborations intended to harmonize the chaos regarding metadata and linked data about Software.<br />
<br />
<br />
== List of initiatives and contacts ==<br />
* FORCE11- <br />
** [https://www.force11.org/group/software-citation-working-group Software Citation working group]<br />
** [https://www.force11.org/group/software-citation-implementation-working-group Software Citation Implementation working group] <br />
* Software Preservation Network (SPN) - [http://www.softwarepreservationnetwork.org/working-groups/metadatastandards/ Metadata Standards and Policies working group]- Katherine Thornton and Elizabeth Roke<br />
* [[CodeMeta]]<br />
* [https://github.com/nexB/aboutcode AboutCode]- discover and uncover data about software code. A nexB project. - Philippe Ombredanne<br />
* BNF : metadata group<br />
<br />
== Issues for discussion ==<br />
* In the effort of harmonizing metadata : <br />
** should we strive to contain all domains, every use case and every exception?<br />
** should we keep only the vital minimum for citation and search?<br />
* Terminology : What is Software ?<br />
*** distinguishing between a software entity and a software project <br />
*** distinguishing between software "object"(executable) and software source code<br />
*** different versions form one software entity?<br />
<br />
<br />
<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Metadata_initiatives&diff=650Metadata initiatives2017-04-27T08:28:08Z<p>Morane: /* Issues for discussion */</p>
<hr />
<div>Collaborations intended to harmonize the chaos regarding metadata and linked data about Software.<br />
<br />
<br />
== List of initiatives and contacts ==<br />
* FORCE11- <br />
** [https://www.force11.org/group/software-citation-working-group Software Citation working group]<br />
** [https://www.force11.org/group/software-citation-implementation-working-group Software Citation Implementation working group] <br />
* Software Preservation Network (SPN) - [http://www.softwarepreservationnetwork.org/working-groups/metadatastandards/ Metadata Standards and Policies working group]- Katherine Thornton and Elizabeth Roke<br />
* [[CodeMeta]]<br />
* [https://github.com/nexB/aboutcode AboutCode]- discover and uncover data about software code. A nexB project. - Philippe Ombredanne<br />
* BNF<br />
<br />
== Issues for discussion ==<br />
* In the effort of harmonizing metadata : <br />
** should we strive to contain all domains, every use case and every exception?<br />
** should we keep only the vital minimum for citation and search?<br />
* Terminology : What is Software ?<br />
*** distinguishing between a software entity and a software project <br />
*** distinguishing between software "object"(executable) and software source code<br />
*** different versions form one software entity?<br />
<br />
<br />
<br />
[[Category:Software ontology]]<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=WG/Metadata_and_Linked_Data&diff=649WG/Metadata and Linked Data2017-04-25T15:12:46Z<p>Morane: /* Documents */</p>
<hr />
<div>= Charter =<br />
<br />
== Mission ==<br />
The Software Heritage archive collects the source code of software projects from a variety of origins.<br />
The same source code can be collected from different origins, each providing ''potentially complementary or conflicting''<br />
metadata describing ''the project'' of which this source code is part, and ''the people'' that take part in it.<br />
<br />
The goal of the MELD working group is to propose ''metadata schemas'' for appropriately describing <br />
the ''projects'', and ''the people'' involved with source code stored in Software Heritage's software archive.<br />
<br />
== Duration ==<br />
This working group has an initial duration of two years.<br />
<br />
== Expected outcomes ==<br />
The main expected outcomes are listed below.<br />
<br />
''Metadata schemas'' for ''software projects'' and ''people'' contributing to them will be<br />
proposed for extending the data model used in the Software Heritage archive.<br />
<br />
''Methods and algorithms'' for ''reconciliating'' complementary of conflicting<br />
metadata collected from different origins, and for ''synthesising'' missing<br />
parts of the metadata from the available context information.<br />
<br />
''Coordination with existing initiatives'' The MELD working group will monitor<br />
all related emerging initiatives or standards and will take into account<br />
existing schemas like [https://en.wikipedia.org/wiki/DOAP DOAP], [http://www.foaf-project.org/ FOAF], [http://schema.org schema.org], [https://www.w3.org/TR/vocab-dcat/ DCAT], [[CodeMeta]] or [https://joinup.ec.europa.eu/asset/adms_foss/asset_release/admssw-05 ADMS.SW], reusing and sharing efforts<br />
where possible (see also our list of [[Software ontologies]]).<br />
It will also develop a list of pointers to existing efforts to build<br />
databases of metadata for software projects and their contributors.<br />
<br />
''Awareness''<br />
The MELD working group will establish the relevant connections in order to <br />
raise awareness among all the interested parties.<br />
<br />
== Milestones ==<br />
A first version of the metadata proposal is expected to arise from experiments conducted on existing collections of project metadata, like the ones originally present in [http://freecode.com/about Freecode].<br />
<br />
== Related working groups ==<br />
The MELD working group shares concerns with the [[Ethical_and_Legal_Issues_and_Environment | ELIE]] and [[Open_Access_and_Data | OPAD]] working groups.<br />
<br />
= Team contact(s) =<br />
* [http://www.dicosmo.org Roberto Di Cosmo]<br />
<br />
= Documents =<br />
[[Metadata initiatives]]<br />
<br />
[[Software catalogs]]<br />
<br />
= Connections =<br />
Active or planned connections to other initiatives, and activities will be listed in this section.<br />
<br />
= Infrastructure =<br />
<br />
== Mailing list ==<br />
* https://sympa.inria.fr/sympa/info/meld-wg-swh<br />
<br />
[[Category:Working group]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Software_catalogs&diff=647Software catalogs2017-04-25T15:11:12Z<p>Morane: Morane moved page Software Catalogs to Software catalogs</p>
<hr />
<div>Software catalogs are used to capture data about software. Most use a metadata schema or a software ontology to do so. <br />
<br />
== List of Software catalogs ==<br />
* [http://www.ontosoft.org/portal/ Ontosoft] - geosciences software.<br />
* [http://swmath.org/ SwMATH]- math software, [http://swmath.org/media/documents/swMATH.pdf swMath article]<br />
* [http://libraries.io/ libraries.io]- keeps track of open source libraries, modules and frameworks.<br />
* [http://orms.mfo.de/ orms]<br />
* [http://www.openhub.net/ OpenHub]<br />
* [http://freecode.com/ FreeCode] read only copy of the old Freshmeat project, [http://fgiasson.com/blog/index.php/2007/08/04/freshmeatnet-now-available-in-doap-43-000-new-doap-projects/ apparently converted in DOAP sometimes in 2007]<br />
* [https://www.projet-plume.org/breve/le-projet-plume-devient-le-service-fenix-fiches-devaluation-normalisees-issues-de-lexperience Plume/Fenix] hundreds of descriptions of software used in research in France<br />
<br />
<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Software_Catalogs&diff=648Software Catalogs2017-04-25T15:11:12Z<p>Morane: Morane moved page Software Catalogs to Software catalogs</p>
<hr />
<div>#REDIRECT [[Software catalogs]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=Software_catalogs&diff=646Software catalogs2017-04-25T15:10:49Z<p>Morane: Created page with "Software catalogs are used to capture data about software. Most use a metadata schema or a software ontology to do so. == List of Software catalogs == * [http://www.ontosoft..."</p>
<hr />
<div>Software catalogs are used to capture data about software. Most use a metadata schema or a software ontology to do so. <br />
<br />
== List of Software catalogs ==<br />
* [http://www.ontosoft.org/portal/ Ontosoft] - geosciences software.<br />
* [http://swmath.org/ SwMATH]- math software, [http://swmath.org/media/documents/swMATH.pdf swMath article]<br />
* [http://libraries.io/ libraries.io]- keeps track of open source libraries, modules and frameworks.<br />
* [http://orms.mfo.de/ orms]<br />
* [http://www.openhub.net/ OpenHub]<br />
* [http://freecode.com/ FreeCode] read only copy of the old Freshmeat project, [http://fgiasson.com/blog/index.php/2007/08/04/freshmeatnet-now-available-in-doap-43-000-new-doap-projects/ apparently converted in DOAP sometimes in 2007]<br />
* [https://www.projet-plume.org/breve/le-projet-plume-devient-le-service-fenix-fiches-devaluation-normalisees-issues-de-lexperience Plume/Fenix] hundreds of descriptions of software used in research in France<br />
<br />
<br />
[[Category:Software metadata]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=WG/Metadata_and_Linked_Data&diff=645WG/Metadata and Linked Data2017-04-25T15:09:53Z<p>Morane: /* Documents */</p>
<hr />
<div>= Charter =<br />
<br />
== Mission ==<br />
The Software Heritage archive collects the source code of software projects from a variety of origins.<br />
The same source code can be collected from different origins, each providing ''potentially complementary or conflicting''<br />
metadata describing ''the project'' of which this source code is part, and ''the people'' that take part in it.<br />
<br />
The goal of the MELD working group is to propose ''metadata schemas'' for appropriately describing <br />
the ''projects'', and ''the people'' involved with source code stored in Software Heritage's software archive.<br />
<br />
== Duration ==<br />
This working group has an initial duration of two years.<br />
<br />
== Expected outcomes ==<br />
The main expected outcomes are listed below.<br />
<br />
''Metadata schemas'' for ''software projects'' and ''people'' contributing to them will be<br />
proposed for extending the data model used in the Software Heritage archive.<br />
<br />
''Methods and algorithms'' for ''reconciliating'' complementary of conflicting<br />
metadata collected from different origins, and for ''synthesising'' missing<br />
parts of the metadata from the available context information.<br />
<br />
''Coordination with existing initiatives'' The MELD working group will monitor<br />
all related emerging initiatives or standards and will take into account<br />
existing schemas like [https://en.wikipedia.org/wiki/DOAP DOAP], [http://www.foaf-project.org/ FOAF], [http://schema.org schema.org], [https://www.w3.org/TR/vocab-dcat/ DCAT], [[CodeMeta]] or [https://joinup.ec.europa.eu/asset/adms_foss/asset_release/admssw-05 ADMS.SW], reusing and sharing efforts<br />
where possible (see also our list of [[Software ontologies]]).<br />
It will also develop a list of pointers to existing efforts to build<br />
databases of metadata for software projects and their contributors.<br />
<br />
''Awareness''<br />
The MELD working group will establish the relevant connections in order to <br />
raise awareness among all the interested parties.<br />
<br />
== Milestones ==<br />
A first version of the metadata proposal is expected to arise from experiments conducted on existing collections of project metadata, like the ones originally present in [http://freecode.com/about Freecode].<br />
<br />
== Related working groups ==<br />
The MELD working group shares concerns with the [[Ethical_and_Legal_Issues_and_Environment | ELIE]] and [[Open_Access_and_Data | OPAD]] working groups.<br />
<br />
= Team contact(s) =<br />
* [http://www.dicosmo.org Roberto Di Cosmo]<br />
<br />
= Documents =<br />
[[Metadata initiatives]]<br />
<br />
[[Software Catalogs]]<br />
<br />
= Connections =<br />
Active or planned connections to other initiatives, and activities will be listed in this section.<br />
<br />
= Infrastructure =<br />
<br />
== Mailing list ==<br />
* https://sympa.inria.fr/sympa/info/meld-wg-swh<br />
<br />
[[Category:Working group]]</div>Moranehttps://wiki.softwareheritage.org/index.php?title=WG/Metadata_and_Linked_Data&diff=644WG/Metadata and Linked Data2017-04-25T15:09:37Z<p>Morane: /* Documents */</p>
<hr />
<div>= Charter =<br />
<br />
== Mission ==<br />
The Software Heritage archive collects the source code of software projects from a variety of origins.<br />
The same source code can be collected from different origins, each providing ''potentially complementary or conflicting''<br />
metadata describing ''the project'' of which this source code is part, and ''the people'' that take part in it.<br />
<br />
The goal of the MELD working group is to propose ''metadata schemas'' for appropriately describing <br />
the ''projects'', and ''the people'' involved with source code stored in Software Heritage's software archive.<br />
<br />
== Duration ==<br />
This working group has an initial duration of two years.<br />
<br />
== Expected outcomes ==<br />
The main expected outcomes are listed below.<br />
<br />
''Metadata schemas'' for ''software projects'' and ''people'' contributing to them will be<br />
proposed for extending the data model used in the Software Heritage archive.<br />
<br />
''Methods and algorithms'' for ''reconciliating'' complementary of conflicting<br />
metadata collected from different origins, and for ''synthesising'' missing<br />
parts of the metadata from the available context information.<br />
<br />
''Coordination with existing initiatives'' The MELD working group will monitor<br />
all related emerging initiatives or standards and will take into account<br />
existing schemas like [https://en.wikipedia.org/wiki/DOAP DOAP], [http://www.foaf-project.org/ FOAF], [http://schema.org schema.org], [https://www.w3.org/TR/vocab-dcat/ DCAT], [[CodeMeta]] or [https://joinup.ec.europa.eu/asset/adms_foss/asset_release/admssw-05 ADMS.SW], reusing and sharing efforts<br />
where possible (see also our list of [[Software ontologies]]).<br />
It will also develop a list of pointers to existing efforts to build<br />
databases of metadata for software projects and their contributors.<br />
<br />
''Awareness''<br />
The MELD working group will establish the relevant connections in order to <br />
raise awareness among all the interested parties.<br />
<br />
== Milestones ==<br />
A first version of the metadata proposal is expected to arise from experiments conducted on existing collections of project metadata, like the ones originally present in [http://freecode.com/about Freecode].<br />
<br />
== Related working groups ==<br />
The MELD working group shares concerns with the [[Ethical_and_Legal_Issues_and_Environment | ELIE]] and [[Open_Access_and_Data | OPAD]] working groups.<br />
<br />
= Team contact(s) =<br />
* [http://www.dicosmo.org Roberto Di Cosmo]<br />
<br />
= Documents =<br />
[[Metadata initiatives]]<br />
[[Software Catalogs]]<br />
<br />
= Connections =<br />
Active or planned connections to other initiatives, and activities will be listed in this section.<br />
<br />
= Infrastructure =<br />
<br />
== Mailing list ==<br />
* https://sympa.inria.fr/sympa/info/meld-wg-swh<br />
<br />
[[Category:Working group]]</div>Morane