Skip to content

Commit 189a1d0

Browse files
alimanfooalimanfoo
committed
initial slides setup
1 parent e168c24 commit 189a1d0

File tree

4 files changed

+220
-0
lines changed

4 files changed

+220
-0
lines changed

‎images/logo1.png‎

9.9 KB
Loading

‎slides.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
layout: page
3+
title: Slides
4+
permalink: /slides/
5+
---
6+
7+
* [v3 design update 20190619](v3-update-20190619.html)

‎slides/v3-update-20190619.html‎

Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
1+
<!doctype html>
2+
<html lang="en">
3+
4+
<head>
5+
<meta charset="utf-8">
6+
7+
<title>v3 design update 19 June 2019</title>
8+
9+
<meta name="description" content="an update on spec design work">
10+
<meta name="author" content="Alistair Miles">
11+
12+
<meta name="apple-mobile-web-app-capable" content="yes">
13+
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">
14+
15+
<meta name="viewport" content="width=device-width, initial-scale=1.0">
16+
17+
<link rel="stylesheet" href="css/reset.css">
18+
<link rel="stylesheet" href="css/reveal.css">
19+
<link rel="stylesheet" href="css/theme/black.css" id="theme">
20+
21+
<!-- Theme used for syntax highlighting of code -->
22+
<link rel="stylesheet" href="lib/css/monokai.css">
23+
24+
<!-- Printing and PDF exports -->
25+
<script>
26+
var link = document.createElement( 'link' );
27+
link.rel = 'stylesheet';
28+
link.type = 'text/css';
29+
link.href = window.location.search.match( /print-pdf/gi ) ? 'css/print/pdf.css' : 'css/print/paper.css';
30+
document.getElementsByTagName( 'head' )[0].appendChild( link );
31+
</script>
32+
33+
<!--[if lt IE 9]>
34+
<script src="lib/js/html5shiv.js"></script>
35+
<![endif]-->
36+
37+
<style type="text/css">
38+
/* turn off all caps in titles */
39+
.reveal h1, .reveal h2, .reveal h3, .reveal h4, .reveal h5 {
40+
text-transform: none;
41+
}
42+
</style>
43+
44+
</head>
45+
46+
<body>
47+
48+
<div class="reveal">
49+
50+
<!-- Any section element inside of this container is displayed as a slide -->
51+
<div class="slides">
52+
53+
<section data-markdown="v3-update-20190619.md"
54+
data-separator="^\n====\n$"
55+
data-separator-vertical="^\n===\n$"></section>
56+
57+
58+
</div>
59+
60+
</div>
61+
62+
<script src="js/reveal.js"></script>
63+
64+
<script>
65+
66+
// More info https://github.com/hakimel/reveal.js#configuration
67+
Reveal.initialize({
68+
controls: true,
69+
progress: true,
70+
center: true,
71+
hash: true,
72+
73+
transition: 'slide', // none/fade/slide/convex/concave/zoom
74+
75+
// More info https://github.com/hakimel/reveal.js#dependencies
76+
dependencies: [
77+
{ src: 'plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
78+
{ src: 'plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
79+
{ src: 'plugin/highlight/highlight.js', async: true },
80+
{ src: 'plugin/search/search.js', async: true },
81+
{ src: 'plugin/zoom-js/zoom.js', async: true },
82+
{ src: 'plugin/notes/notes.js', async: true }
83+
]
84+
});
85+
86+
</script>
87+
88+
</body>
89+
</html>

‎slides/v3-update-20190619.md‎

Lines changed: 124 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,124 @@
1+
Zarr v3 design update
2+
---------------------
3+
4+
Alistair Miles ([@alimanfoo](https://github.com/alimanfoo))
5+
6+
19 June 2019
7+
8+
====
9+
10+
### Current status
11+
12+
* Development is ongoing via the core-protocol-v3.0-dev branch in the
13+
[zarr-specs repo](https://github.com/zarr-developers/zarr-specs),
14+
follow
15+
[PR#16](https://github.com/zarr-developers/zarr-specs/pull/16) for
16+
current status.
17+
18+
* Rendered docs from this branch can be [viewed on
19+
RTFD](https://zarr-specs.readthedocs.io/en/core-protocol-v3.0-dev/).
20+
21+
* This is still a straw man, everything is up for discussion.
22+
23+
====
24+
25+
### Modular spec architecture
26+
27+
* [Core protocol spec](https://zarr-specs.readthedocs.io/en/core-protocol-v3.0-dev/protocol/core/v3.0.html)
28+
* [Protocol extension specs](https://zarr-specs.readthedocs.io/en/core-protocol-v3.0-dev/protocol/extensions.html)
29+
* Codec specs
30+
* Storage specs
31+
32+
===
33+
34+
### [Core protocol spec](https://zarr-specs.readthedocs.io/en/core-protocol-v3.0-dev/protocol/core/v3.0.html)
35+
36+
* Minimal, easy as possible to do full implementation in any language.
37+
38+
* Aiming for intersection of N5 and Zarr v2 features.
39+
40+
* Defines a variety of **extension points** so can also serve as a
41+
foundation for growth and experimentation.
42+
43+
===
44+
45+
### Protocol extension specs
46+
47+
* Each protocol extension gets its own spec.
48+
49+
* Currently the core-protocol-v3.0-dev branch also includes some
50+
protocol extension specs, to illustrate the concept.
51+
52+
* E.g., [Datetime data types
53+
spec](https://zarr-specs.readthedocs.io/en/core-protocol-v3.0-dev/protocol/extensions/datetime-dtypes/v1.0.html)
54+
55+
* Ultimately these extension specs should get split out each into a
56+
separate development branch, so we decouple them from the core
57+
protocol spec.
58+
59+
===
60+
61+
### Codec specs
62+
63+
* Each codec intended for use as a compressor or filter gets it's own
64+
spec.
65+
66+
* @@TODO create an example to illustrate the concept.
67+
68+
===
69+
70+
### Storage specs
71+
72+
* Each concrete storage system (e.g., file system, cloud object
73+
storage, Zip file, LMDB, ...) gets it's own spec.
74+
75+
* @@TODO create an example to illustrate the concept.
76+
77+
====
78+
79+
### Spec development process (1)
80+
81+
* Currently @alimanfoo is acting as editor for the v3.0 core protocol
82+
spec.
83+
84+
* Feedback/comments/ideas welcome from anyone at any time
85+
([PR#16](https://github.com/zarr-developers/zarr-specs/pull/16) is
86+
probably the best place for comments).
87+
88+
* Still in a conceptualisation phase, no need for formal decision
89+
process as yet.
90+
91+
===
92+
93+
### Spec development process (2)
94+
95+
* Ultimately I think we'll need to define a community process for spec
96+
development, so that:
97+
98+
* It's clear how others can contribute.
99+
100+
* It's clear how decisions get made.
101+
102+
* It's clear what stage of maturity each spec is at.
103+
104+
* Postpone that for now, may need external advice/help on best
105+
approach.
106+
107+
===
108+
109+
### Spec development process (3)
110+
111+
* Hopefully the [zarr-specs
112+
repo](https://github.com/zarr-developers/zarr-specs) can serve as a
113+
focus for community spec development.
114+
115+
* However, don't want to force all spec development down the same
116+
route.
117+
118+
* This is one reason why currently the core spec makes use of
119+
**URIs** in metadata to refer to protocol extensions and codecs -
120+
allow for anyone to publish their own spec.
121+
122+
====
123+
124+
###

0 commit comments

Comments
 (0)