diff --git a/common/images/fossid-press-release.png b/common/images/fossid-press-release.png
new file mode 100644
index 0000000..3dd6988
Binary files /dev/null and b/common/images/fossid-press-release.png differ
diff --git a/talks-public/2018-12-07-yokohama-ocsasia/2018-12-07-yokohama-ocsasia.org b/talks-public/2018-12-07-yokohama-ocsasia/2018-12-07-yokohama-ocsasia.org
new file mode 100644
index 0000000..fdcd9de
--- /dev/null
+++ b/talks-public/2018-12-07-yokohama-ocsasia/2018-12-07-yokohama-ocsasia.org
@@ -0,0 +1,99 @@
+#+COLUMNS: %40ITEM %10BEAMER_env(Env) %9BEAMER_envargs(Env Args) %10BEAMER_act(Act) %4BEAMER_col(Col) %10BEAMER_extra(Extra) %8BEAMER_opt(Opt)
+#+TITLE: Software Heritage
+#+SUBTITLE: Archive All the Source Code for Better Compliance
+#+BEAMER_HEADER: \date[07/12/2018, OCSAsia]{7 December 2018\\Open Compliance Summit\\Yokohama, Japan}
+#+DATE: 7 December 2018
+
+#+INCLUDE: "../../common/modules/prelude.org" :minlevel 1
+#+INCLUDE: "../../common/modules/169.org"
+#+BEAMER_HEADER: \institute[Software Heritage]{\\[-5mm]Software Heritage --- {\tt zack@upsilon.cc, @zacchiro}}
+#+BEAMER_HEADER: \author{Stefano Zacchiroli}
+
+#+LATEX_HEADER_EXTRA: \usepackage{tikz}
+#+LATEX_HEADER_EXTRA: \usetikzlibrary{arrows,shapes}
+#+LATEX_HEADER_EXTRA: \definecolor{swh-orange}{RGB}{254,205,27}
+#+LATEX_HEADER_EXTRA: \definecolor{swh-red}{RGB}{226,0,38}
+#+LATEX_HEADER_EXTRA: \definecolor{swh-green}{RGB}{77,181,174}
+
+* Outline
+** Talk spoilers
+   - Software Heritage: the ultimate source code archive
+   - 3 highlights on how Software Heritage relates to Open Compliance
+     1. complete corresponding source code deposit
+     2. persistent identifiers for source code artifacts
+     3. a mutualized, open data, FOSS provenance database
+* Software Heritage
+  #+INCLUDE: "../../common/modules/swh-overview-sourcecode.org::#mission" :minlevel 2
+  #+INCLUDE: "../../common/modules/principles-short.org::#principles" :minlevel 2
+** Breaking news: the first /independent/ mirror is coming
+   #+BEAMER: \centering \includegraphics[width=0.9\textwidth]{fossid-press-release}
+  #+INCLUDE: "../../common/modules/status-extended.org::#dataflow" :minlevel 2
+  #+INCLUDE: "../../common/modules/status-extended.org::#archive" :minlevel 2
+** Accessing the archive
+  :PROPERTIES:
+  :CUSTOM_ID: accessing-short
+  :END:
+*** Browse                                                    :B_block:BMCOL:
+    :PROPERTIES:
+    :BEAMER_col: 0.4
+    :BEAMER_env: block
+    :END:
+    #+BEAMER: \begin{center}\includegraphics[width=0.5\textwidth]{archive-browse}\end{center}
+    - https://archive.softwareheritage.org/browse
+    - way back machine for software source code
+  #+BEAMER: \pause
+*** Web API                                                   :B_block:BMCOL:
+    :PROPERTIES:
+    :BEAMER_col: 0.4
+    :BEAMER_env: block
+    :END:
+    #+BEAMER: \begin{center}\includegraphics[width=0.5\textwidth]{archive-webapi}\end{center}
+    - https://archive.softwareheritage.org/api
+    - point-wise navigation of the archive as a graph
+* Outsourcing CCS distribution
+** Case study: Complete Corresponding Source code distribution
+   - if you ship copylefted code, you also need to ship Complete Corresponding
+     Source (CCS) code
+   - can you /outsource/ hosting & distribution of CCS archives?
+     #+BEAMER: \pause \\
+     yes (IANAL, etc.), e.g., 
+     #+BEGIN_QUOTE
+     GPL FAQ: Can I put the binaries on my Internet server and put the source on
+     a different Internet site?
+     - [v3] Yes. Section 6(d) allows this. However, you must provide clear
+       instructions people can follow to obtain the source, and you must take
+       care to *make sure that the source remains available* for as long as you
+       distribute the object code.
+     - [v2] The GPL says you must offer access to copy the source code ``from the
+       same place''; that is, next to the binaries.  However, if you *make
+       arrangements with another site* to keep the necessary source code
+       available, and put a link or cross-reference to the source code next to
+       the binaries, we think that qualifies as ``from the same place''.
+   #+END_QUOTE
+   #+BEAMER: \vspace{-2mm} \pause
+*** Open Compliance --- Highlight #1
+    Software Heritage can permanently archive, host, and distribute CCS
+    archives for you
+
+ #+INCLUDE: "../../common/modules/deposit.org::#overview" :minlevel 2
+ #+INCLUDE: "../../common/modules/deposit.org::#prepare" :minlevel 2
+ #+INCLUDE: "../../common/modules/deposit.org::#send" :minlevel 2
+ #+INCLUDE: "../../common/modules/deposit.org::#status" :minlevel 2
+ #+INCLUDE: "../../common/modules/deposit.org::#access" :minlevel 2
+*** Open Compliance --- Highlight #2
+    Software Heritage assigns persistent identifiers to all archived source
+    code artifacts.
+** Towards an open provenance database
+   TODO
+** Wrapping up
+*** Software Heritage…
+    - … collects, preserves, and shares the **entire software commons**
+    - … exhibits many synergies with the vision and goals of **Open Provenance**
+    - … is a non-profit endeavor, creating **mutualized infrastructures and
+      services**
+  #+BEAMER: \pause
+*** Come and join us
+    - https://www.softwareheritage.org
+    - https://archive.softwareheritage.org
+    - https://www.softwareheritage.org/support/sponsors/
+    … or just talk to me! =:-)= Stefano Zacchiroli / zack@upsilon.cc / @zacchiro
diff --git a/talks-public/2018-12-07-yokohama-ocsasia/Makefile b/talks-public/2018-12-07-yokohama-ocsasia/Makefile
new file mode 100644
index 0000000..68fbee7
--- /dev/null
+++ b/talks-public/2018-12-07-yokohama-ocsasia/Makefile
@@ -0,0 +1 @@
+include ../Makefile.slides