initialisation
David Valentine

David Valentine commited on 2024-12-06 22:19:45
Showing 24 changed files, with 2142 additions and 0 deletions.

... ...
@@ -0,0 +1,14 @@
1
+# directories
2
+tmp/
3
+
4
+# ignore all files in these directories
5
+archives/*
6
+docs/*
7
+scripts/local/*
8
+src/example/*
9
+# except .gitkeep
10
+!.gitkeep
11
+
12
+# files, anywhere in tree
13
+log.json
14
+config-tidy
... ...
@@ -0,0 +1,437 @@
1
+Attribution-NonCommercial-ShareAlike 4.0 International
2
+
3
+=======================================================================
4
+
5
+Creative Commons Corporation ("Creative Commons") is not a law firm and
6
+does not provide legal services or legal advice. Distribution of
7
+Creative Commons public licenses does not create a lawyer-client or
8
+other relationship. Creative Commons makes its licenses and related
9
+information available on an "as-is" basis. Creative Commons gives no
10
+warranties regarding its licenses, any material licensed under their
11
+terms and conditions, or any related information. Creative Commons
12
+disclaims all liability for damages resulting from their use to the
13
+fullest extent possible.
14
+
15
+Using Creative Commons Public Licenses
16
+
17
+Creative Commons public licenses provide a standard set of terms and
18
+conditions that creators and other rights holders may use to share
19
+original works of authorship and other material subject to copyright
20
+and certain other rights specified in the public license below. The
21
+following considerations are for informational purposes only, are not
22
+exhaustive, and do not form part of our licenses.
23
+
24
+     Considerations for licensors: Our public licenses are
25
+     intended for use by those authorized to give the public
26
+     permission to use material in ways otherwise restricted by
27
+     copyright and certain other rights. Our licenses are
28
+     irrevocable. Licensors should read and understand the terms
29
+     and conditions of the license they choose before applying it.
30
+     Licensors should also secure all rights necessary before
31
+     applying our licenses so that the public can reuse the
32
+     material as expected. Licensors should clearly mark any
33
+     material not subject to the license. This includes other CC-
34
+     licensed material, or material used under an exception or
35
+     limitation to copyright. More considerations for licensors:
36
+    wiki.creativecommons.org/Considerations_for_licensors
37
+
38
+     Considerations for the public: By using one of our public
39
+     licenses, a licensor grants the public permission to use the
40
+     licensed material under specified terms and conditions. If
41
+     the licensor's permission is not necessary for any reason--for
42
+     example, because of any applicable exception or limitation to
43
+     copyright--then that use is not regulated by the license. Our
44
+     licenses grant only permissions under copyright and certain
45
+     other rights that a licensor has authority to grant. Use of
46
+     the licensed material may still be restricted for other
47
+     reasons, including because others have copyright or other
48
+     rights in the material. A licensor may make special requests,
49
+     such as asking that all changes be marked or described.
50
+     Although not required by our licenses, you are encouraged to
51
+     respect those requests where reasonable. More considerations
52
+     for the public:
53
+    wiki.creativecommons.org/Considerations_for_licensees
54
+
55
+=======================================================================
56
+
57
+Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
58
+Public License
59
+
60
+By exercising the Licensed Rights (defined below), You accept and agree
61
+to be bound by the terms and conditions of this Creative Commons
62
+Attribution-NonCommercial-ShareAlike 4.0 International Public License
63
+("Public License"). To the extent this Public License may be
64
+interpreted as a contract, You are granted the Licensed Rights in
65
+consideration of Your acceptance of these terms and conditions, and the
66
+Licensor grants You such rights in consideration of benefits the
67
+Licensor receives from making the Licensed Material available under
68
+these terms and conditions.
69
+
70
+
71
+Section 1 -- Definitions.
72
+
73
+  a. Adapted Material means material subject to Copyright and Similar
74
+     Rights that is derived from or based upon the Licensed Material
75
+     and in which the Licensed Material is translated, altered,
76
+     arranged, transformed, or otherwise modified in a manner requiring
77
+     permission under the Copyright and Similar Rights held by the
78
+     Licensor. For purposes of this Public License, where the Licensed
79
+     Material is a musical work, performance, or sound recording,
80
+     Adapted Material is always produced where the Licensed Material is
81
+     synched in timed relation with a moving image.
82
+
83
+  b. Adapter's License means the license You apply to Your Copyright
84
+     and Similar Rights in Your contributions to Adapted Material in
85
+     accordance with the terms and conditions of this Public License.
86
+
87
+  c. BY-NC-SA Compatible License means a license listed at
88
+     creativecommons.org/compatiblelicenses, approved by Creative
89
+     Commons as essentially the equivalent of this Public License.
90
+
91
+  d. Copyright and Similar Rights means copyright and/or similar rights
92
+     closely related to copyright including, without limitation,
93
+     performance, broadcast, sound recording, and Sui Generis Database
94
+     Rights, without regard to how the rights are labeled or
95
+     categorized. For purposes of this Public License, the rights
96
+     specified in Section 2(b)(1)-(2) are not Copyright and Similar
97
+     Rights.
98
+
99
+  e. Effective Technological Measures means those measures that, in the
100
+     absence of proper authority, may not be circumvented under laws
101
+     fulfilling obligations under Article 11 of the WIPO Copyright
102
+     Treaty adopted on December 20, 1996, and/or similar international
103
+     agreements.
104
+
105
+  f. Exceptions and Limitations means fair use, fair dealing, and/or
106
+     any other exception or limitation to Copyright and Similar Rights
107
+     that applies to Your use of the Licensed Material.
108
+
109
+  g. License Elements means the license attributes listed in the name
110
+     of a Creative Commons Public License. The License Elements of this
111
+     Public License are Attribution, NonCommercial, and ShareAlike.
112
+
113
+  h. Licensed Material means the artistic or literary work, database,
114
+     or other material to which the Licensor applied this Public
115
+     License.
116
+
117
+  i. Licensed Rights means the rights granted to You subject to the
118
+     terms and conditions of this Public License, which are limited to
119
+     all Copyright and Similar Rights that apply to Your use of the
120
+     Licensed Material and that the Licensor has authority to license.
121
+
122
+  j. Licensor means the individual(s) or entity(ies) granting rights
123
+     under this Public License.
124
+
125
+  k. NonCommercial means not primarily intended for or directed towards
126
+     commercial advantage or monetary compensation. For purposes of
127
+     this Public License, the exchange of the Licensed Material for
128
+     other material subject to Copyright and Similar Rights by digital
129
+     file-sharing or similar means is NonCommercial provided there is
130
+     no payment of monetary compensation in connection with the
131
+     exchange.
132
+
133
+  l. Share means to provide material to the public by any means or
134
+     process that requires permission under the Licensed Rights, such
135
+     as reproduction, public display, public performance, distribution,
136
+     dissemination, communication, or importation, and to make material
137
+     available to the public including in ways that members of the
138
+     public may access the material from a place and at a time
139
+     individually chosen by them.
140
+
141
+  m. Sui Generis Database Rights means rights other than copyright
142
+     resulting from Directive 96/9/EC of the European Parliament and of
143
+     the Council of 11 March 1996 on the legal protection of databases,
144
+     as amended and/or succeeded, as well as other essentially
145
+     equivalent rights anywhere in the world.
146
+
147
+  n. You means the individual or entity exercising the Licensed Rights
148
+     under this Public License. Your has a corresponding meaning.
149
+
150
+
151
+Section 2 -- Scope.
152
+
153
+  a. License grant.
154
+
155
+       1. Subject to the terms and conditions of this Public License,
156
+          the Licensor hereby grants You a worldwide, royalty-free,
157
+          non-sublicensable, non-exclusive, irrevocable license to
158
+          exercise the Licensed Rights in the Licensed Material to:
159
+
160
+            a. reproduce and Share the Licensed Material, in whole or
161
+               in part, for NonCommercial purposes only; and
162
+
163
+            b. produce, reproduce, and Share Adapted Material for
164
+               NonCommercial purposes only.
165
+
166
+       2. Exceptions and Limitations. For the avoidance of doubt, where
167
+          Exceptions and Limitations apply to Your use, this Public
168
+          License does not apply, and You do not need to comply with
169
+          its terms and conditions.
170
+
171
+       3. Term. The term of this Public License is specified in Section
172
+          6(a).
173
+
174
+       4. Media and formats; technical modifications allowed. The
175
+          Licensor authorizes You to exercise the Licensed Rights in
176
+          all media and formats whether now known or hereafter created,
177
+          and to make technical modifications necessary to do so. The
178
+          Licensor waives and/or agrees not to assert any right or
179
+          authority to forbid You from making technical modifications
180
+          necessary to exercise the Licensed Rights, including
181
+          technical modifications necessary to circumvent Effective
182
+          Technological Measures. For purposes of this Public License,
183
+          simply making modifications authorized by this Section 2(a)
184
+          (4) never produces Adapted Material.
185
+
186
+       5. Downstream recipients.
187
+
188
+            a. Offer from the Licensor -- Licensed Material. Every
189
+               recipient of the Licensed Material automatically
190
+               receives an offer from the Licensor to exercise the
191
+               Licensed Rights under the terms and conditions of this
192
+               Public License.
193
+
194
+            b. Additional offer from the Licensor -- Adapted Material.
195
+               Every recipient of Adapted Material from You
196
+               automatically receives an offer from the Licensor to
197
+               exercise the Licensed Rights in the Adapted Material
198
+               under the conditions of the Adapter's License You apply.
199
+
200
+            c. No downstream restrictions. You may not offer or impose
201
+               any additional or different terms or conditions on, or
202
+               apply any Effective Technological Measures to, the
203
+               Licensed Material if doing so restricts exercise of the
204
+               Licensed Rights by any recipient of the Licensed
205
+               Material.
206
+
207
+       6. No endorsement. Nothing in this Public License constitutes or
208
+          may be construed as permission to assert or imply that You
209
+          are, or that Your use of the Licensed Material is, connected
210
+          with, or sponsored, endorsed, or granted official status by,
211
+          the Licensor or others designated to receive attribution as
212
+          provided in Section 3(a)(1)(A)(i).
213
+
214
+  b. Other rights.
215
+
216
+       1. Moral rights, such as the right of integrity, are not
217
+          licensed under this Public License, nor are publicity,
218
+          privacy, and/or other similar personality rights; however, to
219
+          the extent possible, the Licensor waives and/or agrees not to
220
+          assert any such rights held by the Licensor to the limited
221
+          extent necessary to allow You to exercise the Licensed
222
+          Rights, but not otherwise.
223
+
224
+       2. Patent and trademark rights are not licensed under this
225
+          Public License.
226
+
227
+       3. To the extent possible, the Licensor waives any right to
228
+          collect royalties from You for the exercise of the Licensed
229
+          Rights, whether directly or through a collecting society
230
+          under any voluntary or waivable statutory or compulsory
231
+          licensing scheme. In all other cases the Licensor expressly
232
+          reserves any right to collect such royalties, including when
233
+          the Licensed Material is used other than for NonCommercial
234
+          purposes.
235
+
236
+
237
+Section 3 -- License Conditions.
238
+
239
+Your exercise of the Licensed Rights is expressly made subject to the
240
+following conditions.
241
+
242
+  a. Attribution.
243
+
244
+       1. If You Share the Licensed Material (including in modified
245
+          form), You must:
246
+
247
+            a. retain the following if it is supplied by the Licensor
248
+               with the Licensed Material:
249
+
250
+                 i. identification of the creator(s) of the Licensed
251
+                    Material and any others designated to receive
252
+                    attribution, in any reasonable manner requested by
253
+                    the Licensor (including by pseudonym if
254
+                    designated);
255
+
256
+                ii. a copyright notice;
257
+
258
+               iii. a notice that refers to this Public License;
259
+
260
+                iv. a notice that refers to the disclaimer of
261
+                    warranties;
262
+
263
+                 v. a URI or hyperlink to the Licensed Material to the
264
+                    extent reasonably practicable;
265
+
266
+            b. indicate if You modified the Licensed Material and
267
+               retain an indication of any previous modifications; and
268
+
269
+            c. indicate the Licensed Material is licensed under this
270
+               Public License, and include the text of, or the URI or
271
+               hyperlink to, this Public License.
272
+
273
+       2. You may satisfy the conditions in Section 3(a)(1) in any
274
+          reasonable manner based on the medium, means, and context in
275
+          which You Share the Licensed Material. For example, it may be
276
+          reasonable to satisfy the conditions by providing a URI or
277
+          hyperlink to a resource that includes the required
278
+          information.
279
+       3. If requested by the Licensor, You must remove any of the
280
+          information required by Section 3(a)(1)(A) to the extent
281
+          reasonably practicable.
282
+
283
+  b. ShareAlike.
284
+
285
+     In addition to the conditions in Section 3(a), if You Share
286
+     Adapted Material You produce, the following conditions also apply.
287
+
288
+       1. The Adapter's License You apply must be a Creative Commons
289
+          license with the same License Elements, this version or
290
+          later, or a BY-NC-SA Compatible License.
291
+
292
+       2. You must include the text of, or the URI or hyperlink to, the
293
+          Adapter's License You apply. You may satisfy this condition
294
+          in any reasonable manner based on the medium, means, and
295
+          context in which You Share Adapted Material.
296
+
297
+       3. You may not offer or impose any additional or different terms
298
+          or conditions on, or apply any Effective Technological
299
+          Measures to, Adapted Material that restrict exercise of the
300
+          rights granted under the Adapter's License You apply.
301
+
302
+
303
+Section 4 -- Sui Generis Database Rights.
304
+
305
+Where the Licensed Rights include Sui Generis Database Rights that
306
+apply to Your use of the Licensed Material:
307
+
308
+  a. for the avoidance of doubt, Section 2(a)(1) grants You the right
309
+     to extract, reuse, reproduce, and Share all or a substantial
310
+     portion of the contents of the database for NonCommercial purposes
311
+     only;
312
+
313
+  b. if You include all or a substantial portion of the database
314
+     contents in a database in which You have Sui Generis Database
315
+     Rights, then the database in which You have Sui Generis Database
316
+     Rights (but not its individual contents) is Adapted Material,
317
+     including for purposes of Section 3(b); and
318
+
319
+  c. You must comply with the conditions in Section 3(a) if You Share
320
+     all or a substantial portion of the contents of the database.
321
+
322
+For the avoidance of doubt, this Section 4 supplements and does not
323
+replace Your obligations under this Public License where the Licensed
324
+Rights include other Copyright and Similar Rights.
325
+
326
+
327
+Section 5 -- Disclaimer of Warranties and Limitation of Liability.
328
+
329
+  a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
330
+     EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
331
+     AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
332
+     ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
333
+     IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
334
+     WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
335
+     PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
336
+     ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
337
+     KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
338
+     ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
339
+
340
+  b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
341
+     TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
342
+     NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
343
+     INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
344
+     COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
345
+     USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
346
+     ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
347
+     DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
348
+     IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
349
+
350
+  c. The disclaimer of warranties and limitation of liability provided
351
+     above shall be interpreted in a manner that, to the extent
352
+     possible, most closely approximates an absolute disclaimer and
353
+     waiver of all liability.
354
+
355
+
356
+Section 6 -- Term and Termination.
357
+
358
+  a. This Public License applies for the term of the Copyright and
359
+     Similar Rights licensed here. However, if You fail to comply with
360
+     this Public License, then Your rights under this Public License
361
+     terminate automatically.
362
+
363
+  b. Where Your right to use the Licensed Material has terminated under
364
+     Section 6(a), it reinstates:
365
+
366
+       1. automatically as of the date the violation is cured, provided
367
+          it is cured within 30 days of Your discovery of the
368
+          violation; or
369
+
370
+       2. upon express reinstatement by the Licensor.
371
+
372
+     For the avoidance of doubt, this Section 6(b) does not affect any
373
+     right the Licensor may have to seek remedies for Your violations
374
+     of this Public License.
375
+
376
+  c. For the avoidance of doubt, the Licensor may also offer the
377
+     Licensed Material under separate terms or conditions or stop
378
+     distributing the Licensed Material at any time; however, doing so
379
+     will not terminate this Public License.
380
+
381
+  d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
382
+     License.
383
+
384
+
385
+Section 7 -- Other Terms and Conditions.
386
+
387
+  a. The Licensor shall not be bound by any additional or different
388
+     terms or conditions communicated by You unless expressly agreed.
389
+
390
+  b. Any arrangements, understandings, or agreements regarding the
391
+     Licensed Material not stated herein are separate from and
392
+     independent of the terms and conditions of this Public License.
393
+
394
+
395
+Section 8 -- Interpretation.
396
+
397
+  a. For the avoidance of doubt, this Public License does not, and
398
+     shall not be interpreted to, reduce, limit, restrict, or impose
399
+     conditions on any use of the Licensed Material that could lawfully
400
+     be made without permission under this Public License.
401
+
402
+  b. To the extent possible, if any provision of this Public License is
403
+     deemed unenforceable, it shall be automatically reformed to the
404
+     minimum extent necessary to make it enforceable. If the provision
405
+     cannot be reformed, it shall be severed from this Public License
406
+     without affecting the enforceability of the remaining terms and
407
+     conditions.
408
+
409
+  c. No term or condition of this Public License will be waived and no
410
+     failure to comply consented to unless expressly agreed to by the
411
+     Licensor.
412
+
413
+  d. Nothing in this Public License constitutes or may be interpreted
414
+     as a limitation upon, or waiver of, any privileges and immunities
415
+     that apply to the Licensor or You, including from the legal
416
+     processes of any jurisdiction or authority.
417
+
418
+=======================================================================
419
+
420
+Creative Commons is not a party to its public
421
+licenses. Notwithstanding, Creative Commons may elect to apply one of
422
+its public licenses to material it publishes and in those instances
423
+will be considered the “Licensor.” The text of the Creative Commons
424
+public licenses is dedicated to the public domain under the CC0 Public
425
+Domain Dedication. Except for the limited purpose of indicating that
426
+material is shared under a Creative Commons public license or as
427
+otherwise permitted by the Creative Commons policies published at
428
+creativecommons.org/policies, Creative Commons does not authorize the
429
+use of the trademark "Creative Commons" or any other trademark or logo
430
+of Creative Commons without its prior written consent including,
431
+without limitation, in connection with any unauthorized modifications
432
+to any of its public licenses or any other arrangements,
433
+understandings, or agreements concerning use of licensed material. For
434
+the avoidance of doubt, this paragraph does not form part of the
435
+public licenses.
436
+
437
+Creative Commons may be contacted at creativecommons.org.
... ...
@@ -0,0 +1,31 @@
1
+# Introduction
2
+
3
+Ce dépôt contient les sources du processeur d'écriture des documents de rédaction scientifique de David Valentine.
4
+L'architecture globale est basée sur celle de [https://git.loupbrun.ca/louis/lobrassard-net/](loupbrun), qui a l'immense gentillesse de partager son installation sous la licence CC-BY.
5
+Plusieurs modifications y sont toutefois appliquées pour répondre à des besoins particuliers.
6
+
7
+# Approche
8
+
9
+Tant les tâches de rédaction que les tâches de développement sont suivies avec Git.
10
+Le dépôt applique un principe de séparation entre la production des contenus textuels et le développement technique du processeur.
11
+Les tâches de développement sont validées (commitées) directement dans ce dépôt, tandis que l'historique de la rédaction évolue dans un système de sous-modules prévu à cet effet. 
12
+ 
13
+Pour mettre à jour un sous-module localement (modifié à distance) :
14
+
15
+- `$ git submodule update --remote <nom-du-dépôt>`
16
+- `$ git add <nom-du-dépôt>`
17
+- `$ git commit -m "update display-ontology submodule"`
18
+
19
+Pour mettre à jour un sous-module à distance (modifié localement) : https://stackoverflow.com/a/5814351/16839131
20
+
21
+```bash
22
+$ cd your_submodule
23
+$ git checkout master
24
+<hack,edit>
25
+$ git commit -a -m "commit in submodule"
26
+$ git push
27
+$ cd ..
28
+$ git add your_submodule
29
+$ git commit -m "Updated submodule"
30
+```
31
+
... ...
@@ -0,0 +1,72 @@
1
+# Makefile
2
+# documents
3
+
4
+#############################################################
5
+# 1. argument obligatoire en ligne de commande
6
+#############################################################
7
+# passer le nom projet du projet à traiter
8
+# avec la variable PROJET
9
+# le projet doit être un dossier de src/
10
+# exemple : $ make PROJET=proposition
11
+
12
+#############################################################
13
+# variables
14
+#############################################################
15
+
16
+SHELL := /bin/bash
17
+
18
+# Timestamp
19
+#timestamp := $(shell date +%Y-%m-%dT%H:%M:%S-05:00)
20
+date      := $(shell date +%Y-%m-%dT%H:%M:%S-05:00)
21
+#hash      := $(shell cat .git/refs/heads/main)
22
+
23
+# Name
24
+name = $(PROJET)
25
+
26
+# Varialbles pour les sources
27
+src_dir = ./src/$(name)
28
+# *.md important, sinon il traite les dossiers et cela génère une erreur
29
+src     = $(src_dir)/*.md
30
+config  = $(src_dir)/config.yml
31
+
32
+# Variables pour les extrants
33
+zip  = ./archives/$(name).zip
34
+docs = ./docs/$(name)
35
+
36
+#############################################################
37
+# receipes
38
+#############################################################
39
+
40
+.PHONY: all
41
+all: projet $(zip)
42
+
43
+.PHONY: projet
44
+projet:
45
+ifndef PROJET
46
+	@echo "Aucun projet sélectionné. Bye."
47
+	@exit 1	
48
+endif
49
+
50
+$(zip): $(config) $(src_dir)/*
51
+	@echo "Projet sélectionné : $(PROJET)"
52
+	@echo "============================================"
53
+	@echo "\n"
54
+	pandoc $(src) \
55
+   --defaults $(config) \
56
+   --metadata-file ./src/global-metadata.yml \
57
+   --metadata-file $(src_dir)/abstract.yml \
58
+   --metadata-file $(src_dir)/metadata.yml \
59
+   --metadata-file $(src_dir)/theme.yml \
60
+   --metadata=date:$(date) \
61
+   --toc \
62
+   --log $(src_dir)/log.json \
63
+   --output $@
64
+	unzip -o -O UTF-8 $@ -d $(docs)
65
+
66
+.PHONY: antidote
67
+antidote:
68
+	/usr/local/bin/Antidote9 $(CORRIGER)
69
+
70
+wordcount:
71
+	pandoc $(SOURCE) \
72
+   --lua-filter ./filters/wordcount.lua
0 73
\ No newline at end of file
... ...
@@ -0,0 +1,242 @@
1
+--- section-bibliographies - chapter-wise reference sections
2
+---
3
+--- Copyright: © 2018 Jesse Rosenthal, 2020–2024 Albert Krewinkel
4
+--- License: MIT – see LICENSE for details
5
+
6
+-- pandoc.utils.citeproc exists since pandoc 2.19.1
7
+PANDOC_VERSION:must_be_at_least {2,19,1}
8
+
9
+local List = require 'pandoc.List'
10
+local utils = require 'pandoc.utils'
11
+local citeproc, sha1, stringify = utils.citeproc, utils.sha1, utils.stringify
12
+local make_sections = function (doc, opts)
13
+  return utils.make_sections(opts.number_sections, nil, doc.blocks)
14
+end
15
+if PANDOC_VERSION >= '3.0' then
16
+  make_sections = (require 'pandoc.structure').make_sections
17
+end
18
+
19
+-- Returns true iff a div is a section div.
20
+local function is_section_div (div)
21
+  return div.t == 'Div'
22
+    and div.classes[1] == 'section'
23
+    and (div.attributes.number or div.classes:includes 'unnumbered')
24
+end
25
+
26
+--- Returns the section heading when given a section div, and nil otherwise.
27
+-- @param div   a pandoc Block element
28
+-- @return heading element or nil
29
+-- @return suffix to be used with identifiers
30
+local function section_header (div)
31
+  local header = div.content and div.content[1]
32
+  local is_header = is_section_div(div)
33
+    and header
34
+    and header.t == 'Header'
35
+
36
+  if not is_header then
37
+    return nil, nil
38
+  end
39
+
40
+  local suffix = header.attributes.number or sha1(stringify(header.content))
41
+  return header, '--' .. suffix
42
+end
43
+
44
+--- Unwrap and remove section divs
45
+local function flatten_sections (div)
46
+  local header = section_header(div)
47
+  if not header then
48
+    return nil
49
+  else
50
+    header.identifier = div.identifier
51
+    header.attributes.number = nil
52
+    div.content[1] = header
53
+    return div.content
54
+  end
55
+end
56
+
57
+local function adjust_refs_components (div)
58
+  local header, suffix = section_header(div)
59
+  if not header then
60
+    return div
61
+  end
62
+
63
+  return div:walk {
64
+    traverse = 'topdown',
65
+    Header = function (h)
66
+      if h.identifier == 'bibliography' then
67
+        h.identifier = 'bibliography' .. suffix
68
+        h.level = header.level + 1
69
+        return h
70
+      end
71
+    end,
72
+    Div = function (d)
73
+      if d.identifier == 'refs' then
74
+        d.identifier = 'refs' .. suffix
75
+        return d
76
+      end
77
+    end
78
+  }
79
+end
80
+
81
+--- Create a deep copy of a table.
82
+-- Values that aren't tables are returned unchanged.
83
+local function deepcopy (tbl)
84
+  if type(tbl) ~= 'table' then
85
+    return tbl
86
+  end
87
+
88
+  local copy = {}
89
+  for k, v in pairs(tbl) do
90
+    copy[k] = deepcopy(v)
91
+  end
92
+  return copy
93
+end
94
+
95
+-- negate a property
96
+local negate = function (property)
97
+  return function (x) return not property(x) end
98
+end
99
+
100
+--- Create a bibliography for a given section. This acts on all
101
+-- section divs at or above `opts.level`
102
+local function create_section_bibliography (meta, opts)
103
+  local newmeta = deepcopy(meta)
104
+
105
+  -- Load bibliography files just once.
106
+  newmeta.bibliography = deepcopy(opts.bibliography)
107
+  newmeta.references = deepcopy(opts.references)
108
+  newmeta.nocite = pandoc.Inlines{
109
+    pandoc.Cite('@*', {pandoc.Citation('*', 'NormalCitation')})
110
+  }
111
+  local references = utils.references(pandoc.Pandoc({}, newmeta))
112
+  newmeta.bibliography = nil
113
+  newmeta.nocite = nil
114
+
115
+  -- Don't do anything if there is no bibliography
116
+  if not next(references) then
117
+    return nil
118
+  end
119
+
120
+  local function section_citeproc(section, suffix)
121
+    section = pandoc.Blocks(section):walk{
122
+      Cite = function (cite)
123
+        cite.citations = cite.citations:map(function(c)
124
+            c.id = c.id .. suffix
125
+            return c
126
+        end)
127
+        return cite
128
+      end,
129
+      Div = function (div)
130
+        if div.classes:includes 'sectionrefs' then
131
+          div.identifier = 'refs'
132
+          return div
133
+        end
134
+      end
135
+    }
136
+    newmeta.references = deepcopy(references)
137
+    for i, ref in ipairs(newmeta.references) do
138
+      newmeta.references[i].id = ref.id .. suffix
139
+    end
140
+    return citeproc(pandoc.Pandoc(section, newmeta)).blocks
141
+  end
142
+
143
+  local process_div
144
+  process_div = function (div)
145
+    local header, suffix = section_header(div)
146
+    if not header or not suffix or opts.level < header.level then
147
+      -- Don't do anything for deeply-nested sections.
148
+      return div, false
149
+    elseif header.level < opts.minlevel then
150
+      -- Don't process sections above minlevel
151
+      div.content = div.content:map(process_div)
152
+      return div, false
153
+    elseif opts.level == header.level then
154
+      div.content = section_citeproc(div.content, suffix)
155
+      return adjust_refs_components(div), false
156
+    else
157
+      -- Replace subsections, which we don't want to process, with
158
+      -- placeholder blocks.
159
+      local subsections = {}
160
+      local subsection_to_placeholder = function (blk, i)
161
+        local subh = section_header(blk)
162
+        if subh and not subh.classes:includes 'sectionbibliography' then
163
+          subsections[i] = blk
164
+          return pandoc.RawBlock('placeholder', tostring(i))
165
+        end
166
+        return blk
167
+      end
168
+      -- replace placeholders with processed subsections
169
+      local restore_from_placeholder = function (blk)
170
+        if blk.t == 'RawBlock' and blk.format == 'placeholder' then
171
+          return process_div(subsections[tonumber(blk.text)])
172
+        end
173
+        return blk
174
+      end
175
+      div.content = div.content:map(subsection_to_placeholder)
176
+      div.content = section_citeproc(div.content, suffix)
177
+      div.content = div.content:map(restore_from_placeholder)
178
+      return adjust_refs_components(div), false
179
+    end
180
+  end
181
+
182
+  return process_div
183
+end
184
+
185
+--- Filter to the references div and bibliography header added by
186
+--- pandoc-citeproc.
187
+local remove_pandoc_citeproc_results = {
188
+  Header = function (header)
189
+    return header.identifier == 'bibliography'
190
+      and {}
191
+      or nil
192
+  end,
193
+  Div = function (div)
194
+    return div.identifier == 'refs'
195
+      and {}
196
+      or nil
197
+  end
198
+}
199
+
200
+--- Create an options table from document metadata.
201
+local function get_options (meta)
202
+  local opts = meta['section-bibliographies'] or {}
203
+  opts.bibliography = opts.bibliography
204
+    or meta['section-bibs-bibliography']
205
+    or meta['bibliography']
206
+  opts.level = tonumber(opts.level)
207
+    or tonumber(meta['section-bibs-level'])
208
+    or 1
209
+  opts.minlevel = tonumber(opts.minlevel)
210
+    or 1
211
+  opts.references = opts.references
212
+    or meta['references']
213
+
214
+  -- sanity check
215
+  if opts.level < opts.minlevel then
216
+    warn('level cannot be smaller than minlevel, setting minlevel = level')
217
+    opts.minlevel = opts.level
218
+  end
219
+
220
+  return opts
221
+end
222
+
223
+return {
224
+  {
225
+    Pandoc = function (doc)
226
+      local opts = get_options(doc.meta)
227
+      if opts['cleanup-first'] then
228
+        -- clear results of a previous citeproc run
229
+        doc = doc:walk(remove_pandoc_citeproc_results)
230
+      end
231
+      -- Setup the document for further processing by wrapping all
232
+      -- sections in Div elements, but undo that after.
233
+      doc.blocks = make_sections(doc, {number_sections=true})
234
+        :walk{
235
+          traverse = 'topdown',
236
+          Div = create_section_bibliography(doc.meta, opts)
237
+        }
238
+        :walk{Div = flatten_sections}
239
+      return doc
240
+    end
241
+  }
242
+}
... ...
@@ -0,0 +1,56 @@
1
+-- counts words in a document
2
+
3
+words = 0
4
+characters = 0
5
+characters_and_spaces = 0
6
+process_anyway = false
7
+
8
+wordcount = {
9
+  Str = function(el)
10
+    -- we don't count a word if it's entirely punctuation:
11
+    if el.text:match("%P") then
12
+        words = words + 1
13
+    end
14
+    characters = characters + utf8.len(el.text)
15
+    characters_and_spaces = characters_and_spaces + utf8.len(el.text)
16
+  end,
17
+
18
+  Space = function(el)
19
+    characters_and_spaces = characters_and_spaces + 1
20
+  end,
21
+
22
+  Code = function(el)
23
+    _,n = el.text:gsub("%S+","")
24
+    words = words + n
25
+    text_nospace = el.text:gsub("%s", "")
26
+    characters = characters + utf8.len(text_nospace)
27
+    characters_and_spaces = characters_and_spaces + utf8.len(el.text)
28
+  end,
29
+
30
+  CodeBlock = function(el)
31
+    _,n = el.text:gsub("%S+","")
32
+    words = words + n
33
+    text_nospace = el.text:gsub("%s", "")
34
+    characters = characters + utf8.len(text_nospace)
35
+    characters_and_spaces = characters_and_spaces + utf8.len(el.text)
36
+  end
37
+}
38
+
39
+-- check if the `wordcount` variable is set to `process-anyway`
40
+function Meta(meta)
41
+  if meta.wordcount and (meta.wordcount=="process-anyway"
42
+    or meta.wordcount=="process" or meta.wordcount=="convert") then
43
+      process_anyway = true
44
+  end
45
+end
46
+
47
+function Pandoc(el)
48
+    -- skip metadata, just count body:
49
+    pandoc.walk_block(pandoc.Div(el.blocks), wordcount)
50
+    print(words .. " words in body")
51
+    print(characters .. " characters in body")
52
+    print(characters_and_spaces .. " characters in body (including spaces)")
53
+    if not process_anyway then
54
+      os.exit(0)
55
+    end
56
+end
0 57
\ No newline at end of file
... ...
@@ -0,0 +1,93 @@
1
+[
2
+  {"id":"abadie_ontologie_2019","abstract":"Ontologie des primitives géométriques représentant la forme et la localisation d'entités topographiques.","accessed":{"date-parts":[["2023",2,17]]},"author":[{"family":"Abadie","given":"Nathalie"},{"family":"Atemezing","given":"Ghislain"}],"citation-key":"abadie_ontologie_2019","container-title":"Institut national de l'information géographique et forestière","issued":{"date-parts":[["2019",2,12]]},"title":"Ontologie des primitives géométriques","type":"webpage","URL":"http://data.ign.fr/def/geometrie/20190212.htm"},
3
+  {"id":"abadie_ontologie_2021","accessed":{"date-parts":[["2023",2,17]]},"author":[{"family":"Abadie","given":"Nathalie"}],"citation-key":"abadie_ontologie_2021","container-title":"Institut national de l'information géographique et forestière","issued":{"date-parts":[["2021",9,28]]},"title":"Ontologie des documents d'archives géographiques","type":"webpage","URL":"http://data.alegoria-project.fr/def/geotheque/index-fr.html"},
4
+  {"id":"abiven_histoire_2018","accessed":{"date-parts":[["2023",8,29]]},"author":[{"family":"Abiven","given":"Marie-Morgane"},{"family":"Laubé","given":"Sylvain"},{"family":"Querrec","given":"Ronan"},{"family":"Garlatti","given":"Serge"},{"family":"Rohou","given":"Bruno"},{"family":"Courgeon","given":"Matthieu"},{"family":"Vourch","given":"Robert"},{"family":"Roué","given":"Jean-Pierre"}],"citation-key":"abiven_histoire_2018","issued":{"date-parts":[["2018",5,22]]},"language":"fr","source":"shs.hal.science","title":"Histoire des paysages portuaires et humanités numériques","type":"document","URL":"https://hal.univ-brest.fr/hal-01797296"},
5
+  {"id":"aussenac-gilles_hierarchical_2023","abstract":"The notion of territory plays a major role in human and social sciences. In an historical context, most approaches are irrelevant as they rely on geometric data, which is not available. In order to represent historical territories,we conceived the HHT ontology (Hierarchical Historical Territory) to represent hierarchical historical territorial divisions, without having to know their geometry. This approach relies on a notion of building blocks to replace polygonal geometry.","accessed":{"date-parts":[["2024",1,12]]},"author":[{"family":"Aussenac-Gilles","given":"Nathalie"},{"family":"Hernandez","given":"Nathalie"},{"family":"Charles","given":"William"}],"citation-key":"aussenac-gilles_hierarchical_2023","genre":"Ontology Specification Draft","issued":{"date-parts":[["2023",12,1]]},"language":"en","note":"sameAs: https://www.irit.fr/recherches/MELODI/ontologies/HHT/index-en.html","title":"Hierarchical Historical Territories","type":"standard","URL":"https://w3id.org/HHT#","version":"1.1"},
6
+  {"id":"battle_geosparql_2012","abstract":"As the amount of Linked Open Data on the web increases, so does the amount of data with an inherent spatial context. Without spatial reasoning, however, the value of this spatial context is limited. Over the past decade there have been several vocabularies and query languages that attempt to exploit this knowledge and enable spatial reasoning. These attempts provide varying levels of support for fundamental geospatial concepts. In this paper we look at the overall state of geospatial data in the Semantic Web, with a focus on the upcoming OGC standard GeoSPARQL. GeoSPARQL attempts to unify data access for the geospatial Semantic Web. We describe the motivation for GeoSPARQL, the current state of the art in industry and research, an example use case, and the implementation of GeoSPARQL in the Parliament triple store.","author":[{"family":"Battle","given":"Robert"},{"family":"Kolas","given":"Dave"}],"citation-key":"battle_geosparql_2012","container-title":"Semantic Web journal","issue":"4","issued":{"date-parts":[["2012"]]},"language":"en","page":"355-370","source":"Zotero","title":"GeoSPARQL: Enabling a Geospatial Semantic Web","type":"article-journal","URL":"https://www.semantic-web-journal.net/content/enabling-geospatial-semantic-web-parliament-and-geosparql","volume":"3"},
7
+  {"id":"bekiari_definition_2021","accessed":{"date-parts":[["2022",5,24]]},"citation-key":"bekiari_definition_2021","editor":[{"family":"Bekiari","given":"Chryssoula"},{"family":"Bruseker","given":"George"},{"family":"Doerr","given":"Martin"},{"family":"Ore","given":"Christian-Emil"},{"family":"Stead","given":"Stephen"},{"family":"Velios","given":"Athanasios"}],"issued":{"date-parts":[["2021",4]]},"language":"en","publisher":"CIDOC CRM Special Interest Group","title":"Definition of the CIDOC Conceptual Reference Model Version 7.1.1","title-short":"Definition of the CIDOC Conceptual Reference Model","type":"document","URL":"https://cidoc-crm.org/sites/default/files/cidoc_crm_v.7.1.1_0.pdf","version":"7.1.1"},
8
+  {"id":"beretta_challenge_2021","abstract":"This paper addresses the issue of interoperability of data generated by historical research and heritage institutions in order to make them re-usable for new research agendas according to the FAIR principles. After introducing the symogih.org project","accessed":{"date-parts":[["2022",2,7]]},"author":[{"family":"Beretta","given":"Francesco"}],"citation-key":"beretta_challenge_2021","container-title":"Semantic Web","DOI":"10.3233/SW-200416","ISSN":"1570-0844","issue":"2","issued":{"date-parts":[["2021",1,1]]},"language":"en","page":"279-294","publisher":"IOS Press","source":"content.iospress.com","title":"A challenge for historical research: Making data FAIR using a collaborative ontology management environment (OntoME)","title-short":"A challenge for historical research","type":"article-journal","URL":"https://content.iospress.com/articles/semantic-web/sw200416","volume":"12"},
9
+  {"id":"beretta_interoperabilite_2017","abstract":"Il s'agira tout d'abord de proposer une réflexion sur la définition de \"donnée historique\" entendue comme expression d'un croisement entre deux perspectives : celle de l'histoire (plus précisément de la réflexion sur la méthode historique) et celle de l'informatique (plus précisément de l’ingénierie des connaissances). Cette définition sera formalisée en adoptant un modèle conceptuel générique issu de l'expérience du projet Système modulaire de gestion de l'information historique (SyMoGIH). Ce modèle a été développé dès 2007 afin de permettre l’interopérabilité entre données produites par différents projets de recherche, dans le but de profiter du caractère cumulatif d'une plate-forme collaborative. Je vais ensuite comparer ce modèle avec d'autres modèles utilisés dans le contexte du web sémantique afin d'en mettre en évidence les spécificités. Enfin, j'aborderai la question de l’interopérabilité des données produites selon différents modèles et des conditions de leur utilisation pour la recherche en histoire.","accessed":{"date-parts":[["2023",3,1]]},"author":[{"family":"Beretta","given":"Francesco"}],"citation-key":"beretta_interoperabilite_2017","container-title":"Enjeux numériques pour les médiations scientifiques et culturelles du passé","editor":[{"family":"Juanals","given":"Brigitte"},{"family":"Minel","given":"Jean-Luc"}],"issued":{"date-parts":[["2017"]]},"language":"fr","page":"87-127","publisher":"Presses universitaires de Paris Nanterre","source":"hal.science","title":"L'interopérabilité des données historiques et la question du modèle : l'ontologie du projet SyMoGIH","title-short":"L'interopérabilité des données historiques et la question du modèle","type":"chapter","URL":"https://shs.hal.science/halshs-01559816"},
10
+  {"id":"beretta_interoperabilite_2022","accessed":{"date-parts":[["2022",8,31]]},"author":[{"family":"Beretta","given":"Francesco"}],"citation-key":"beretta_interoperabilite_2022","container-title":"Actes des journées humanités numériques et Web sémantique","DOI":"10.5281/ZENODO.7014341","editor":[{"family":"Lasolle","given":"Nicolas"},{"family":"Bruneau","given":"Olivier"},{"family":"Lieber","given":"Jean"}],"event-place":"Nancy","event-title":"Journées d’étude - Humanités numériques et Web sémantique","issued":{"date-parts":[["2022",6]]},"language":"fr","license":"Creative Commons Attribution 4.0 International, Open Access","page":"2-22","publisher":"LORIA","publisher-place":"Nancy","source":"DOI.org (Datacite)","title":"Interopérabilité des données de la recherche et ontologies fondationnelles : un écosystème d’extensions du CIDOC CRM pour les sciences humaines et sociales","type":"paper-conference","URL":"https://zenodo.org/record/7014341"},
11
+  {"id":"bernard_immersing_2019","abstract":"Nowadays, the volume of data coming from the public sector is growing rapidly on the Open Data Web. Most of data come from governmental agencies such as Statistical and Mapping Agencies. Together, these public institutions publish geo-coded statistics that are of utmost importance for policy-makers to conduct various analyses upon their jurisdiction, in time and space. However, through times, all over the world, the subdivisions of such ju- risdictions (portions of space on Earth) delimited by or, under the control of human groups (e.g., administrative or electoral areas) are subject to change: their names, belonging or boundaries change for political or administrative reasons. Likewise, the Territorial Statistical Nomenclatures (TSNs) that are sets of artifact areas (although they usually correspond to political or administrative structures) built by Statistical Agencies to observe a territory at several levels (e.g., regions, districts, sub-districts) also change over time. Changes in TSNs are an obstacle to maintain the comparability of socio-economic data over time, unless past data are recalculated according to present geographic areas, a complicated process that, in the end, hide the territorial changes. Then, territorial changes lead to breaks in the statistical series, and are sources of misinterpretations of statistics, or statistical bias when not properly documented. Therefore, solutions for representing different versions of TSNs, and their evolution on the Open Data Web are to be proposed in order to enhance the understanding of territorial dynamics.In this thesis, we present the Theseus Framework with reference to philosophical issue raised by the Ship of Theseus that, according to legend, was rebuilt entirely over the years, every plank of the ship being replaced one by one. This software framework adopts Semantic Web technologies and Linked Open Data (LOD) representation for the description of the TSNs’ areas, and of their changes: this guaranties the syntactic and, moreover, semantic interoperability between systems exchanging TSN information. Theseus is composed of a set of modules to handle the whole TSN data life cycle on the LOD Web: from the modeling of geographic areas and of their changes, to the exploitation of these descriptions on the LOD Web. All the software modules rely on two ontologies, TSN Ontology and TSN-Change Ontology, we have designed for an unambiguous description of the areas in time and space, and for the description of their changes. In order to automate the detection of such changes in TSN geospatial files, Theseus embeds an implementation of the TSN Semantic Matching Algorithm that computes LOD semantic graphs describing all the TSN elements and their evolution, based on the vocabulary of the two ontologies.This framework is intended first for the Statistical Agencies, since it considerably helps in complying with Open Data directives, by automating the publication of Open Data representation of their geographic areas that change over time. Second, the created LOD graphs enhance the understanding of territorial dynamics over time, providing policy-makers, researchers, general public with semantic descriptions of territorial changes to conduct various analyses upon their jurisdiction, in time and space. The applicability and genericity of our approach is illustrated by three tests of Theseus, each of them being led on three official TSNs: The European Nomenclature of Territorial Units for Statistics (NUTS) (versions 1999, 2003, 2006, and 2010) from the European Eurostat Statistical Institute; The Switzerland Administrative Units (SAU), from The Swiss Federal Statistical Office, that describes the cantons, districts and municipalities of Switzerland in 2017 and 2018; The Australian Statistical Geography Standard (ASGS), built by the Australian Bureau of Statistics, composed of seven nested divisions of the Australian territory, in versions 2011 and 2016.","accessed":{"date-parts":[["2023",7,8]]},"author":[{"family":"Bernard","given":"Camille"}],"citation-key":"bernard_immersing_2019","genre":"Thèse de doctorat","issued":{"date-parts":[["2019",11,27]]},"language":"en","publisher":"Université Grenoble Alpes","source":"theses.hal.science","title":"Immersing evolving geographic divisions in the semantic Web","type":"thesis","URL":"https://theses.hal.science/tel-02524361"},
12
+  {"id":"bernard_modeling_2018","accessed":{"date-parts":[["2022",4,6]]},"author":[{"family":"Bernard","given":"Camille"},{"family":"Villanova-Oliver","given":"Marlène"},{"family":"Gensel","given":"Jérôme"},{"family":"Dao","given":"Hy"}],"citation-key":"bernard_modeling_2018","container-title":"SAC '18: Proceedings of the 33rd annual ACM symposium on applied computing","DOI":"10.1145/3167132.3167227","event-place":"Pau","event-title":"SAC 2018: Symposium on Applied Computing","ISBN":"978-1-4503-5191-1","issued":{"date-parts":[["2018",4,9]]},"language":"en","page":"866-875","publisher":"Association for computing machinery","publisher-place":"Pau","source":"DOI.org (Crossref)","title":"Modeling changes in territorial partitions over time: ontologies TSN and TSN-change","title-short":"Modeling changes in territorial partitions over time","type":"paper-conference","URL":"https://dl.acm.org/doi/10.1145/3167132.3167227"},
13
+  {"id":"bernard_ontology-based_2018","abstract":"Through times, regions all over the world are very often subject to change (their names, their belonging, their composition, and their geometries). In this paper, we present a Semantic Matching Algorithm for automatically detecting, describing and publishing in the Linked Open Data Web, rich descriptions of changes occurring in multi-level territorial partitions (e.g., partitions made of major regions, regions and districts levels). We adopt a Linked Data (LD) approach for the semantic descriptions of the changes they undergo, relying on two existing generic ontologies, TSN-Ontology and TSN-Change Ontology. The created RDF graphs draw the lineage of each region over time (horizontal reading of the graphs), as well as the propagation of a change event through the partition levels (vertical reading).","accessed":{"date-parts":[["2022",10,29]]},"author":[{"family":"Bernard","given":"Camille"},{"family":"Plumejeaud-Perreau","given":"Christine"},{"family":"Villanova-Oliver","given":"Marlène"},{"family":"Gensel","given":"Jérôme"},{"family":"Dao","given":"Hy"}],"citation-key":"bernard_ontology-based_2018","collection-title":"SIGSPATIAL '18","container-title":"Proceedings of the 26th ACM SIGSPATIAL International Conference on Advances in Geographic Information Systems","DOI":"10.1145/3274895.3274944","event-place":"New York","ISBN":"978-1-4503-5889-7","issued":{"date-parts":[["2018",11,6]]},"page":"456–459","publisher":"Association for Computing Machinery","publisher-place":"New York","source":"ACM Digital Library","title":"An ontology-based algorithm for managing the evolution of multi-level territorial partitions","type":"paper-conference","URL":"https://doi.org/10.1145/3274895.3274944"},
14
+  {"id":"bernard_territorial_2019","abstract":"This ontology allows describing any Territorial Statistical Nomenclature (TSN) i.e., partition of the territory (electoral, administrative, statistical, etc.) used as a support to the collection and restitution of statistical data (e.g., describing a territory in terms of population, unemployement rate, transport access, etc.).","accessed":{"date-parts":[["2023",12,7]]},"author":[{"family":"Bernard","given":"Camille"},{"family":"Gensel","given":"Jérôme"},{"family":"Dao","given":"Hy"},{"family":"Villanova-Oliver","given":"Marlène"}],"citation-key":"bernard_territorial_2019","genre":"Ontology Specification","issued":{"date-parts":[["2019",5,24]]},"language":"en","publisher":"STeamer group","title":"Territorial Statistical Nomenclature Ontology","type":"standard","URL":"http://lig-tdcge.imag.fr/tsn/index.html","version":"1.1"},
15
+  {"id":"bernard_territorial_2019-1","abstract":"The TSN-Change ontology aims at describing changes that occured from one version of a Territorial Statistical Nomenclature (TSN) (i.e., partition of the territory) and its subsequent (e.g., change in territorial units boundaries to reflect an administrative reorganisation).","accessed":{"date-parts":[["2023",12,7]]},"author":[{"family":"Bernard","given":"Camille"},{"family":"Gensel","given":"Jérôme"},{"family":"Dao","given":"Hy"},{"family":"Villanova-Oliver","given":"Marlène"}],"citation-key":"bernard_territorial_2019-1","genre":"Ontology Specification","issued":{"date-parts":[["2019",5,24]]},"language":"en","publisher":"STeamer group","title":"Territorial Statistical Nomenclature Change Ontology","type":"standard","URL":"http://lig-tdcge.imag.fr/tsnchange/index.html","version":"1.1"},
16
+  {"id":"berube_histoire_2022","abstract":"Depuis le milieu du XIXe siècle, les métropoles nord-américaines s'imposent comme l'incarnation d'une modernité urbaine triomphante. De Montréal à La Nouvelle-Orléans, le développement des transports en commun donne naissance à des quartiers bourgeois prestigieux, mais aussi à des quartiers chauds. De Toronto à New York, experts, architectes et politiciens tentent de faire sens du chaos urbain pour enrichir la ville et la sauver d'elle-même. De Vancouver à Chicago, parcs, boulevards et gratte-ciel sont construits et aménagés pour célébrer la grandeur des cités. Et dans l'ombre de chacune d'entre elles, il y a ceux et celles qui luttent contre les inégalités qui s'y accentuent et y persistent.","author":[{"family":"Bérubé","given":"Harold"}],"call-number":"307.760 97","citation-key":"berube_histoire_2022","collection-title":"Aujourd'hui l'histoire avec...","event-place":"Québec","ISBN":"978-2-89791-338-0","issued":{"date-parts":[["2022"]]},"language":"fr","publisher":"Septentrion","publisher-place":"Québec","source":"BnF ISBN","title":"Histoire des villes nord-américaines","type":"book"},
17
+  {"id":"berube_tramway_2022","author":[{"family":"Bérubé","given":"Harold"}],"call-number":"307.760 97","citation-key":"berube_tramway_2022","collection-title":"Aujourd'hui l'histoire avec...","container-author":[{"family":"Bérubé","given":"Harold"}],"container-title":"Histoire des villes nord-américaines","event-place":"Québec","ISBN":"978-2-89791-338-0","issued":{"date-parts":[["2022"]]},"language":"fr","publisher":"Septentrion","publisher-place":"Québec","source":"BnF ISBN","title":"Le tramway et la fin de la ville piétonne","type":"chapter"},
18
+  {"id":"bourel_graphes_2022","abstract":"The notion of territory amounts for an important part of human and social sciences. As a spatio-temporal object considered from the digital humanities viewpoint, the question of its digital representation brings forward the need to represent its various aspects. Territory is considered here as a geographical area defined by stakeholders exerting a defined kind of power (religious, legal, …) over said area, or at least trying to exert it. Inspired by the territorial ontologies TSN and TSN-Change, we propose the HHT ontology (Hierarchical Historical Territory) which is designed to represent the state of affairs of various hierarchical territorial divisions identified by historians’ research. Such territory representation implies an overcoming of the main difficulty of such work, which is the lack of exhaustive historical sources regarding the whole territory. Additionally, the HHT ontology endeavors to represent the former states of historical knowledge of territories, now considered deprecated. Defined as part of the ANR ObARDI project, which aims to study territories under the historical period known as Ancien Régime (1661-1789), HHT fills the specific need of representing hierarchical historical territorial divisions.","accessed":{"date-parts":[["2022",8,31]]},"author":[{"family":"Bourel","given":"Lucas"},{"family":"Charles","given":"William"},{"family":"Hernandez","given":"Nathalie"},{"family":"Aussenac-Gilles","given":"Nathalie"},{"family":"Gay","given":"Victor"},{"family":"Poublanc","given":"Sébastien"}],"citation-key":"bourel_graphes_2022","container-title":"Actes des journées humanités numériques et Web sémantique","DOI":"10.5281/ZENODO.7014341","editor":[{"family":"Lasolle","given":"Nicolas"},{"family":"Bruneau","given":"Olivier"},{"family":"Lieber","given":"Jean"}],"event-place":"Nancy","event-title":"Journées d’étude - Humanités numériques et Web sémantique","issued":{"date-parts":[["2022",6,21]]},"language":"fr","license":"Creative Commons Attribution 4.0 International, Open Access","page":"23-37","publisher":"LORIA","publisher-place":"Nancy","title":"Graphes de connaissances pour représenter et analyser l’évolution des territoires en Histoire","type":"paper-conference","URL":"https://zenodo.org/record/7014341"},
19
+  {"id":"bourel_hht_2022","abstract":"In digital humanities, modeling the concept of territory requires to take into account its different dimensions. The HHT ontology (Hierarchical Historical Territory) tries to represent the state of several hierarchical territorial divisions identified by historical research. In the ANR ObARDI project which studies the territories under the Ancien Régime, HHT comes in modular form to answer the specific need to represent historical evolutions of territorial divisions as well as claims on these divisions.","accessed":{"date-parts":[["2023",7,13]]},"author":[{"family":"Bourel","given":"Lucas"},{"family":"Hernandez","given":"Nathalie Jane"},{"family":"Aussenac-Gilles","given":"Nathalie"},{"family":"Charles","given":"William"}],"citation-key":"bourel_hht_2022","collection-title":"IC 2022 : Journées Francophones D'Ingénierie des Connaissances","container-title":"33ème Journées Francophones d'Ingénierie des Connaissances (IC 2022)","editor":[{"family":"Saïs","given":"Fatiha"}],"event-place":"Saint-Etienne, France","issued":{"date-parts":[["2022",6]]},"note":"Backup Publisher: Collège SIC (Science de l'Ingénierie des Connaissances) de l'AFIA","page":"131-136","publisher":"AFIA","publisher-place":"Saint-Etienne, France","source":"HAL Archives Ouvertes","title":"HHT : une ontologie modulaire pour représenter l'évolution des territoires en Histoire","title-short":"HHT","type":"paper-conference","URL":"https://hal.science/hal-03760559"},
20
+  {"id":"brando_humanites_2021","abstract":"Cet article propose une introduction aux contributions présentées dans ce numéro thématique dédié aux humanités numériques spatialisées. Trois grands thèmes sont abordés : (1) le traitement de l’information spatiale dans des corpus textuels issus des travaux en sciences humaines et sociales, principalement en études littéraires ; (2) les problématiques d’acquisition, de spatialisation et de diffusion de données géographiques du passé et du patrimoine, donc, ici, davantage en lien avec la recherche en histoire ; (3) l’information spatiale, son traitement et ses usages en archéologie. Pour chacun de ces thèmes, nous présentons les initiatives fondatrices, un bref état de l’art et une synthèse des contributions.","accessed":{"date-parts":[["2022",2,7]]},"author":[{"family":"Brando","given":"Carmen"},{"family":"Frontini","given":"Francesca"},{"family":"Moreau","given":"Dominic"},{"family":"Roche","given":"Mathieu"},{"family":"Masson","given":"Éric"}],"citation-key":"brando_humanites_2021","container-title":"Humanités numériques","DOI":"10.4000/revuehn.2038","ISSN":"2736-2337","issued":{"date-parts":[["2021",5,1]]},"language":"fr","license":"Les contenus de la revue Humanités numériques sont mis à disposition selon les termes de la Licence Creative Commons Attribution 4.0 International.","number":"3","publisher":"Humanistica","source":"journals.openedition.org","title":"Humanités numériques et analyses spatiales : enjeux et perspectives","title-short":"Introduction. Humanités numériques et analyses spatiales","type":"article-journal","URL":"https://journals.openedition.org/revuehn/2038","volume":"3"},
21
+  {"id":"braudel_mediterranee_1977","author":[{"family":"Braudel","given":"Fernand"}],"citation-key":"braudel_mediterranee_1977","event-place":"Paris","ISBN":"978-2-7004-0028-1","issued":{"date-parts":[["1977"]]},"language":"fr","note":"OCLC: 4488059\nnote: Nouvelle édition en 1985 chez Flammarion\nInternetArchive: https://archive.org/details/lamediterraneele0000unse/mode/2up","number-of-pages":"225","publisher":"Arts et métiers graphiques","publisher-place":"Paris","source":"Open WorldCat","title":"La Méditerranée : l’espace et l’histoire","title-short":"La Méditerranée","type":"book"},
22
+  {"id":"brickley_basic_2004","abstract":"This is a basic RDF vocabulary that provides the Semantic Web community with a namespace for representing lat(itude), long(itude) and other information about spatially-located things, using WGS84 as a reference datum.","accessed":{"date-parts":[["2023",8,16]]},"author":[{"family":"Brickley","given":"Dan"}],"citation-key":"brickley_basic_2004","container-title":"W3C Semantic Web Interest Group","issued":{"date-parts":[["2004",2,6]]},"title":"Basic Geo (WGS84 lat/long) Vocabulary","title-short":"Basic Geo Vocabulary","type":"webpage","URL":"https://www.w3.org/2003/01/geo/"},
23
+  {"id":"brickley_geonames_2008","abstract":"Geonames released an ontology of its geospatial information schema in the Web Ontology Language OWL. This ontology directly maps to the DB schema that is used by Geonames data export.\n\nIn the rest of this post, I’ll describe key concepts in the Geonames ontology. It may be of interest to readers who want to learn and play with the Semantic Web Geonames.","accessed":{"date-parts":[["2023",8,16]]},"author":[{"family":"Brickley","given":"Dan"}],"citation-key":"brickley_geonames_2008","container-title":"Geospatial Semantic Web Blog","issued":{"date-parts":[["2008",2,12]]},"language":"en","title":"Geonames ontology in OWL","type":"post-weblog","URL":"https://web.archive.org/web/20080212144050/http://www.geospatialsemanticweb.com/2006/10/14/geonames-ontology-in-owl"},
24
+  {"id":"brickley_wgs84_2009","accessed":{"date-parts":[["2023",7,20]]},"author":[{"family":"Brickley","given":"Dan"},{"family":"Berners-Lee","given":"Tim"}],"citation-key":"brickley_wgs84_2009","issued":{"date-parts":[["2009"]]},"note":"seeAlso: https://www.w3.org/2003/01/geo/","title":"WGS84 Geo Positioning: an RDF vocabulary","type":"software","URL":"https://www.w3.org/2003/01/geo/wgs84_pos","version":"1.22"},
25
+  {"id":"brouillet_apercu_2021","abstract":"All the documentation pertaining to DOPHEDA developed by CHIN. Toute la documentation à propos de DOPHEDA développé par le RCIP.","accessed":{"date-parts":[["2022",9,5]]},"author":[{"family":"Brouillet","given":"Karine Léonard"},{"family":"Blain","given":"Marie-Pier"},{"family":"Michon","given":"Philippe"},{"family":"Hart","given":"Stephen"},{"family":"Dang","given":"Trang"}],"citation-key":"brouillet_apercu_2021","container-title":"DOPHEDA","genre":"documentation","issued":{"date-parts":[["2021",4,29]]},"language":"fr","license":"CC0 Réseau canadien d'information sur le patrimoine 2021","note":"extra-url: https://github.com/chin-rcip/collections-model/","title":"Aperçu de DOPHEDA","type":"webpage","URL":"https://chin-rcip.github.io/collections-model/fr"},
26
+  {"id":"brown_about_2022","abstract":"LINCS is undertaking a ground-breaking, multi-disciplinary research program organized across three themes—Making Connections, Navigating Scale, and Building Knowledge—alongside collaborations with researchers engaging with a variety of domains and areas of inquiry.","accessed":{"date-parts":[["2023",7,18]]},"author":[{"family":"Brown","given":"Susan"},{"family":"Martin","given":"Kim"},{"family":"Stacey","given":"Deb"}],"citation-key":"brown_about_2022","container-title":"LINCS Portal","genre":"documentation","issued":{"date-parts":[["2022"]]},"language":"en","title":"About LINCS: research","type":"webpage","URL":"https://lincsproject.ca/docs/about-lincs/research"},
27
+  {"id":"bruseker_cultural_2017","abstract":"Building models for integrating the diverse data generated in Cultural Heritage disciplines is a long-term challenge both for securing presently generated knowledge and for making it progressively more widely accessible and interoperable into the future. This chapter reviews the multiple approaches undertaken to address this problem, finally proposing CIDOC CRM as the most robust solution for information integration in CH. The chapter begins by outlining the data challenge specific to the field and the main approaches that can be taken in facing it. Within this frame, it distinguishes knowledge engineering and formal ontology from other information modelling techniques as the necessary approach for tackling the broader data integration problem. It then outlines the basic principles of CIDOC CRM, the ISO standard formal ontology for CH. From there, an overview is given of some of the work that has been done both theoretically and in practice over the past five years in developing and implementing CRM as a practical data integration strategy in CH, particularly looking at model extensions to handle knowledge provenance across various disciplines and typical documentation and reasoning activities, as well as at successful implementation projects. Lastly, it summarizes the present potentials and challenges for using CIDOC CRM for solving the CH data management and integration puzzle. The intended audience of this chapter are specialists from all backgrounds within the broader domain of CH with an interest in data integration and CIDOC CRM.","accessed":{"date-parts":[["2021",1,9]]},"author":[{"family":"Bruseker","given":"George"},{"family":"Carboni","given":"Nicola"},{"family":"Guillem","given":"Anaïs"}],"citation-key":"bruseker_cultural_2017","collection-title":"Quantitative Methods in the Humanities and Social Sciences","container-title":"Heritage and Archaeology in the Digital Age: Acquisition, Curation, and Dissemination of Spatial Cultural Heritage Data","DOI":"10.1007/978-3-319-65370-9_6","editor":[{"family":"Vincent","given":"Matthew L."},{"family":"López-Menchero Bendicho","given":"Víctor Manuel"},{"family":"Ioannides","given":"Marinos"},{"family":"Levy","given":"Thomas E."}],"event-place":"Cham","ISBN":"978-3-319-65370-9","issued":{"date-parts":[["2017"]]},"language":"en","page":"93-131","publisher":"Springer International Publishing","publisher-place":"Cham","source":"Springer Link","title":"Cultural heritage data management: the role of formal ontology and CIDOC CRM","title-short":"Cultural heritage data management","type":"chapter","URL":"http://link.springer.com/10.1007/978-3-319-65370-9_6"},
28
+  {"id":"burgess_documentation_2021","accessed":{"date-parts":[["2023",1,9]]},"author":[{"family":"Burgess","given":"Joanne"},{"family":"Robichaud","given":"Léon"},{"family":"Michon","given":"Philippe"}],"citation-key":"burgess_documentation_2021","event-place":"Montréal","issued":{"date-parts":[["2021",3,4]]},"language":"fr","publisher-place":"Montréal","title":"Documentation sémantique de la spatialité urbaine : les données ouvertes et liées, l’histoire et les défis d’une géographie multiple en constante évolution","type":"book","URL":"https://lhpm.uqam.ca/programmation-scientifique/humanites-numeriques/documentation-semantique-de-la-spatialite-urbaine-les-donnees-ouvertes-et-liees-lhistoire-et-les-defis-dune-geographie-multiple-en-constante-evolution/"},
29
+  {"id":"car_geosparql_2022","abstract":"In 2012, the Open Geospatial Consortium published GeoSPARQL defining “an RDF/OWL ontology for [spatial] information”, “SPARQL extension functions” for performing spatial operations on RDF data and “RIF rules” defining entailments to be drawn from graph pattern matching. In the 8+ years since its publication, GeoSPARQL has become the most important spatial Semantic Web standard, as judged by references to it in other Semantic Web standards and its wide use for Semantic Web data. An update to GeoSPARQL was proposed in 2019 to deliver a version 1.1 with a charter to: handle outstanding change requests and source new ones from the user community and to “better present” the standard, that is to better link all the standard’s parts and better document and exemplify elements. Expected updates included new geometry representations, alignments to other ontologies, handling of new spatial referencing systems, and new artifact presentation. This paper describes motivating change requests and actual resultant updates in the candidate version 1.1 of the standard alongside reference implementations and usage examples. We also describe the theory behind particular updates, initial implementations of many parts of the standard, and our expectations for GeoSPARQL 1.1’s use.","accessed":{"date-parts":[["2022",2,13]]},"author":[{"family":"Car","given":"Nicholas J."},{"family":"Homburg","given":"Timo"}],"citation-key":"car_geosparql_2022","container-title":"ISPRS International journal of geo-information","DOI":"10.3390/ijgi11020117","ISSN":"2220-9964","issue":"2","issued":{"date-parts":[["2022",2]]},"language":"en","license":"http://creativecommons.org/licenses/by/3.0/","number":"2","page":"117","publisher":"Multidisciplinary Digital Publishing Institute","source":"www.mdpi.com","title":"GeoSPARQL 1.1: Motivations, details and applications of the decadal update to the most important geospatial LOD standard","title-short":"GeoSPARQL 1.1","type":"article-journal","URL":"https://www.mdpi.com/2220-9964/11/2/117","volume":"11"},
30
+  {"id":"cayless_lawd_2013","accessed":{"date-parts":[["2023",8,29]]},"author":[{"family":"Cayless","given":"Hugh A."}],"citation-key":"cayless_lawd_2013","issued":{"date-parts":[["2013"]]},"language":"en","title":"LAWD: An ontology for Linked Ancient World Data","type":"webpage","URL":"https://github.com/lawdi/LAWD/"},
31
+  {"id":"charles_hht_2023","abstract":"The notion of territory plays a major role in human and social sciences. Representation of this spatio-temporal object and computation of the changes occurring have been tackled in various ways. However, in an historical context, most approaches are irrelevant as they rely on geometric data, which is not available. In order to represent historical territories, we conceived the HHT ontology (Hierarchical Historical Territory) to represent hierarchical historical territorial divisions, without having to know their geometry. This approach relies on a notion of building blocks to replace polygonal geometry. This representation is further used to provide an algorithm to detect and characterize territorial changes in a knowledge graph. Said algorithm creates a knowledge graph of changes at multiple levels encompassing basic changes occurring in a single territory, and composite changes, which are the abstraction of several smaller changes into a large change. The approach was followed to produce 3 knowledge graphs available online. Each of these graphs allowed to set up an analysis of the evolution of the territories during the historical period they cover.","author":[{"family":"Charles","given":"William"},{"family":"Aussenac-Gilles","given":"Nathalie"},{"family":"Hernandez","given":"Nathalie"}],"citation-key":"charles_hht_2023","collection-title":"Lecture Notes in Computer Science","container-title":"The Semantic Web","DOI":"10.1007/978-3-031-33455-9_25","editor":[{"family":"Pesquita","given":"Catia"},{"family":"Jimenez-Ruiz","given":"Ernesto"},{"family":"McCusker","given":"Jamie"},{"family":"Faria","given":"Daniel"},{"family":"Dragoni","given":"Mauro"},{"family":"Dimou","given":"Anastasia"},{"family":"Troncy","given":"Raphael"},{"family":"Hertling","given":"Sven"}],"event-place":"Cham","ISBN":"978-3-031-33455-9","issued":{"date-parts":[["2023"]]},"language":"en","page":"419-435","publisher":"Springer Nature Switzerland","publisher-place":"Cham","source":"Springer Link","title":"HHT: An Approach for Representing Temporally-Evolving Historical Territories","title-short":"HHT","type":"paper-conference"},
32
+  {"id":"chas_e_goad_co_atlas_1912","author":[{"literal":"Chas. E. Goad Co."}],"citation-key":"chas_e_goad_co_atlas_1912","genre":"Atlas","issued":{"date-parts":[["1912"],["1914"]]},"publisher":"Chas. E. Goad, Co., civil engineers","scale":"1:1200","title":"Atlas of the City of Montreal and vicinity : in four volumes, from official plans - special surveys showing cadastral numbers, buildings & lots","type":"map","URL":"https://collections.banq.qc.ca/ark:/52327/2244204"},
33
+  {"id":"chiang_creating_2020","accessed":{"date-parts":[["2022",2,11]]},"author":[{"family":"Chiang","given":"Yao-Yi"},{"family":"Duan","given":"Weiwei"},{"family":"Leyk","given":"Stefan"},{"family":"Uhl","given":"Johannes H."},{"family":"Knoblock","given":"Craig A."}],"citation-key":"chiang_creating_2020","collection-title":"SpringerBriefs in Geography","container-title":"Using Historical Maps in Scientific Studies: Applications, Challenges, and Best Practices","DOI":"10.1007/978-3-319-66908-3_3","event-place":"Cham","ISBN":"978-3-319-66907-6 978-3-319-66908-3","issued":{"date-parts":[["2020"]]},"language":"en","page":"37-63","publisher":"Springer International Publishing","publisher-place":"Cham","source":"DOI.org (Crossref)","title":"Creating structured, linked geographic data from historical maps: challenges and trends","title-short":"Creating structured, linked geographic data from historical maps","type":"chapter","URL":"http://link.springer.com/10.1007/978-3-319-66908-3"},
34
+  {"id":"chiang_querying_2015","abstract":"Historical spatiotemporal datasets are important for a variety of studies such as cancer and environmental epidemiology, urbanization, and landscape ecology. However, existing data sources typically contain only contemporary datasets. Historical maps hold a great deal of detailed geographic information at various times in the past. Yet, finding relevant maps is difficult and the map content are not machine-readable. I envision a map processing, modeling, linking, and publishing framework that allows querying historical map collections as a unified and structured spatiotemporal source in which individual geographic phenomena (extracted from maps) are modeled with semantic descriptions and linked to other data sources (e.g., DBpedia). This framework will make it possible to efficiently study historical spatiotemporal datasets on a large scale. Realizing such a framework poses significant research challenges in multiple fields in computer science including digital map processing, data integration, and the Semantic Web technologies, and other disciplines such as spatial, earth, social, and health sciences. Tackling these challenges will not only advance research in computer science but also present a unique opportunity for interdisciplinary research.","author":[{"family":"Chiang","given":"Yao-Yi"}],"citation-key":"chiang_querying_2015","container-title":"SIGSPATIAL '15: Proceedings of the 23rd SIGSPATIAL international conference on advances in geographic information systems","DOI":"10.1145/2820783.2820887","editor":[{"family":"Ali","given":"Mohamed"},{"family":"Huang","given":"Yan"},{"family":"Gertz","given":"Michael"},{"family":"Renz","given":"Matthias"},{"family":"Sankaranarayanan","given":"Jagan"}],"event-place":"New York","issued":{"date-parts":[["2015",11,3]]},"language":"en","page":"1-4","publisher":"Association for Computing Machinery","publisher-place":"New York","title":"Querying historical maps as a unified, structured, and linked spatiotemporal source: vision paper","type":"paper-conference"},
35
+  {"id":"chiang_survey_2014","abstract":"Maps depict natural and human-induced changes on earth at a fine resolution for large areas and over long periods of time. In addition, maps—especially historical maps—are often the only information source about the earth as surveyed using geodetic techniques. In order to preserve these unique documents, increasing numbers of digital map archives have been established, driven by advances in software and hardware technologies. Since the early 1980s, researchers from a variety of disciplines, including computer science and geography, have been working on computational methods for the extraction and recognition of geographic features from archived images of maps (digital map processing). The typical result from map processing is geographic information that can be used in spatial and spatiotemporal analyses in a Geographic Information System environment, which benefits numerous research fields in the spatial, social, environmental, and health sciences. However, map processing literature is spread across a broad range of disciplines in which maps are included as a special type of image. This article presents an overview of existing map processing techniques, with the goal of bringing together the past and current research efforts in this interdisciplinary field, to characterize the advances that have been made, and to identify future research directions and opportunities.","accessed":{"date-parts":[["2022",12,11]]},"author":[{"family":"Chiang","given":"Yao-Yi"},{"family":"Leyk","given":"Stefan"},{"family":"Knoblock","given":"Craig A."}],"citation-key":"chiang_survey_2014","container-title":"ACM Computing Surveys","container-title-short":"ACM Comput. Surv.","DOI":"10.1145/2557423","ISSN":"0360-0300","issue":"1","issued":{"date-parts":[["2014"]]},"page":"1:1–1:44","source":"July 2014","title":"A survey of digital map processing techniques","type":"article-journal","URL":"https://doi.org/10.1145/2557423","volume":"47"},
36
+  {"id":"chiang_using_2020","accessed":{"date-parts":[["2022",2,11]]},"author":[{"family":"Chiang","given":"Yao-Yi"},{"family":"Duan","given":"Weiwei"},{"family":"Leyk","given":"Stefan"},{"family":"Uhl","given":"Johannes H."},{"family":"Knoblock","given":"Craig A."}],"citation-key":"chiang_using_2020","collection-title":"SpringerBriefs in Geography","DOI":"10.1007/978-3-319-66908-3","event-place":"Cham","ISBN":"978-3-319-66907-6 978-3-319-66908-3","issued":{"date-parts":[["2020"]]},"language":"en","publisher":"Springer International Publishing","publisher-place":"Cham","source":"DOI.org (Crossref)","title":"Using historical maps in scientific studies: applications, challenges, and best practices","title-short":"Using Historical Maps in Scientific Studies","type":"book","URL":"http://link.springer.com/10.1007/978-3-319-66908-3"},
37
+  {"id":"clavaud_international_2021","accessed":{"date-parts":[["2022",5,21]]},"author":[{"family":"Clavaud","given":"Florence"},{"literal":"Expert Group on Archival Description"}],"citation-key":"clavaud_international_2021","container-title":"International Council on Archives","issued":{"date-parts":[["2021",2,12]]},"language":"en","title":"International Council on Archives Records in Contexts Ontology (ICA RiC-O) version 0.2","type":"webpage","URL":"https://www.ica.org/standards/RiC/RiC-O_v0-2.html"},
38
+  {"id":"coret_gouda_2023","abstract":"De Gouda Tijdmachine beschrijft en linkt geo-temporele objecten die betrekking hebben op Gouda.\nDeze ontologie beschrijft met name de klasse GeoTemporeelObject, de properties en subklassen.","accessed":{"date-parts":[["2023",12,9]]},"author":[{"family":"Coret","given":"Bob"}],"citation-key":"coret_gouda_2023","genre":"Ontologie","issued":{"date-parts":[["2023",10,4]]},"language":"nl","title":"Gouda Tijdmachine Ontologie","type":"standard","URL":"https://www.goudatijdmachine.nl/def/","version":"0.8"},
39
+  {"id":"coret_onder_2022","abstract":"De Gouda Tijdmachine gebruikt Omeka S als collectiebeheersysteem. Alhoewel de data er als RDF (in JSON-LD representatie) uit komt en er ook een search API is, kun je standaard geen SPARQL query loslaten op je in Omeka S beheerde semantische data. In dit artikel wordt er gekeken naar een aantal oplossingsrichtingen om linked open data… Lees verder ...","accessed":{"date-parts":[["2023",12,9]]},"author":[{"family":"Coret","given":"Bob"}],"citation-key":"coret_onder_2022","container-title":"Gouda Tijdmachine","issued":{"date-parts":[["2022",12,22]]},"language":"nl","title":"Onder de motorkap: linked open data bieden via SPARQL endpoint","title-short":"Onder de motorkap","type":"post-weblog","URL":"https://www.goudatijdmachine.nl/2022/12/22/onder-de-motorkap-linked-open-data-bieden-via-sparql-endpoint/"},
40
+  {"id":"drouin_demolition_2012","abstract":"En 1954, le dépôt du plan Dozois prévoyait l’élimination d’une zone de taudis en vue de la construction du projet d’habitation sociale connue sous le nom des Habitations Jeanne-Mance. En se lançant dans une telle opération, la Ville de Montréal posait un premier geste concret pour enrayer un mal qui affectait les quartiers centraux : la dépréciation du cadre bâti ancien. Le geste peut également s’inscrire dans la genèse d’un mouvement pour la conservation du patrimoine. En explorant l’histoire de l’aménagement urbain à Montréal jusqu’à la création de l’association Sauvons Montréal en 1973, il est possible d’observer la transformation du regard posé sur l’environnement bâti. La juxtaposition des notions de taudis et de patrimoine permet en effet de se placer au coeur d’une mutation qui transforma radicalement la manière d’aménager la ville.\n          , \n            In 1954, the newly tabled Dozois plan provided for the elimination of a slum area to make way for the building of the Habitations Jeanne-Mance social housing complex. With the launching of such an operation, the City of Montreal took a first concrete step toward curbing an evil that was affecting inner-city neighbourhoods: the depreciation of the old housing stock. This may also be seen as part of an emerging historic preservation movement. By exploring the history of urban planning in Montreal up until the creation of Save Montreal association in 1973, we can observe a transformation in the ways in which the built environment was actually seen. The juxtaposition of notions of slum and heritage places us at the heart of a mutation that radically transformed urban planning once and for all.","accessed":{"date-parts":[["2022",5,23]]},"author":[{"family":"Drouin","given":"Martin"}],"citation-key":"drouin_demolition_2012","container-title":"Urban History Review","container-title-short":"uhr","DOI":"10.7202/1013762ar","ISSN":"1918-5138, 0703-0428","issue":"1","issued":{"date-parts":[["2012"]]},"language":"fr","page":"22-36","source":"DOI.org (Crossref)","title":"De la démolition des taudis à la sauvegarde du patrimoine bâti (Montréal, 1954-1973)","type":"article-journal","URL":"http://id.erudit.org/iderudit/1013762ar","volume":"41"},
41
+  {"id":"gelly_comprendre_2019","abstract":"Le canal de Lachine a fait l’objet de maintes études de la part de la communauté historienne. À juste titre, avec une aussi impressionnante historiographie, une question se pose : y a-t-il encore quelque chose à raconter sur le passé du canal ? À cette interrogation, sans conteste, la réponse est oui. Car, outre la réinterprétation nécessaire de pans entiers de son histoire, au moins un rôle essentiel du canal – soit celui d’être un prolongement du port de Montréal – n’avait jusqu’ici fait l’objet d’aucune étude approfondie.","author":[{"family":"Gelly","given":"Alain"},{"family":"Burgess","given":"Joanne"}],"citation-key":"gelly_comprendre_2019","container-title":"Intersections : au carrefour de l’histoire et des collectivités","issue":"2.3","issued":{"date-parts":[["2019"]]},"language":"fr","page":"20-21","title":"Comprendre et visualiser le passé portuaire du canal de Lachine","type":"article-journal"},
42
+  {"id":"grossner_bringing_2022","accessed":{"date-parts":[["2022",10,18]]},"author":[{"family":"Grossner","given":"Karl"},{"family":"Grunewald","given":"Susan"},{"family":"Mostern","given":"Ruth"}],"citation-key":"grossner_bringing_2022","container-title":"International Journal on Digital Libraries","DOI":"10.1007/s00799-022-00341-2","ISSN":"1432-5012, 1432-1300","issued":{"date-parts":[["2022",10,12]]},"language":"en","source":"DOI.org (Crossref)","title":"Bringing places from the distant past to the present: A report on the World Historical Gazetteer","title-short":"Bringing places from the distant past to the present","type":"article-journal","URL":"https://link.springer.com/epdf/10.1007/s00799-022-00341-2?sharing_token=3YQYgc6nR7o5I9eTk8AWzfe4RwlQNchNByi7wbcMAY5X_VvOaDVusdiWdcF7utm4uzDIVl--8a4PCKDm-1DCdLTimtDavZ2POHK8gSwFdkoKAJvGx7ssi4MJ5wb-FtCqUcCu-ltJAc89K_bOvy2ChXeZ9zszUNiEjdAIKGLE5IE%3D"},
43
+  {"id":"grossner_linked_2023","abstract":"Our goal is not to define The One unified data model for gazetteers. Historical research projects producing gazetteer data have distinctive data models reflecting their source data and project-specific requirements. Linked Places format provides a uniform way to build links between different gazetteers.","author":[{"family":"Grossner","given":"Karl"},{"literal":"Richard Zijdeman"},{"family":"Shaw","given":"Ryan"},{"family":"Elwert","given":"Frederik"}],"citation-key":"grossner_linked_2023","issued":{"date-parts":[["2023"]]},"title":"Linked places format (LPF)","type":"software","URL":"https://github.com/LinkedPasts/linked-places-format","version":"1.2.2"},
44
+  {"id":"grossner_linking_2017","abstract":"This white paper presents results of a 2017 initiative undertaken by the Linked Pasts Working Group (LPWG) of Pelagios Commons. First, a compilation of requirements as expressed by our community of interest for what the Pelagios investigative team has called “a wider ecosystem of projects dedicated to interlinking online resources about the past.” Secondly, a draft road map to aid discussion about steps the Pelagios project and broader community can take towards fulfilling them.","author":[{"family":"Grossner","given":"Karl"},{"family":"Hill","given":"Timothy"}],"citation-key":"grossner_linking_2017","contributor":[{"family":"Simon","given":"Rainer"},{"family":"Light","given":"Richard"},{"family":"Bosse","given":"Arno"},{"family":"Bodard","given":"Gabriel"},{"family":"Ridge","given":"Mia"},{"family":"Schmidle","given":"Wolfgang"}],"issued":{"date-parts":[["2017",12,7]]},"language":"en","publisher":"Linked Pasts Working Group","source":"Zotero","title":"From linking places to a linked pasts network","type":"document","URL":"http://kgeographer.com/pubs/LinkedPastsNetwork_7Dec.pdf"},
45
+  {"id":"guldi_what_2011","abstract":"What is a turn? Humanities scholars speak of a quantitative turn in history in the 1960s, a linguistic and cultural turn of the 1980s in history and literature, and even more recently an animal turn. Beyond the academy, to turn implies retrospection, a process of stopping in the road and glancing backwards at the way by which one has come.","accessed":{"date-parts":[["2023",7,18]]},"author":[{"family":"Guldi","given":"Jo"}],"citation-key":"guldi_what_2011","container-title":"Spatial Humanities. A Project of the Institute for Enabling Geospatial Scholarship","issued":{"date-parts":[["2011"]]},"title":"What is the spatial turn?","type":"webpage","URL":"https://spatial.scholarslab.org/spatial-turn/what-is-the-spatial-turn/"},
46
+  {"id":"harris_geospatial_2010","abstract":"The so-called spatial turn in the humanities represents a complexity of ideas and applications and the term is in dire need of unpacking. At the very base level the spatial turn represents an awareness of the significant role that space plays in human actions and events, and specifically the influence that space plays in humanities disciplines. Without question, the spatial turn has been heavily driven by the growing awareness and availability of Geographic Information Systems (GIS).¹ There have long been exchanges between geography and the humanities that extend as far back as Carl Sauer’s inaugural work in cultural geography and","accessed":{"date-parts":[["2023",7,1]]},"archive":"JSTOR","author":[{"family":"Harris","given":"Trevor M."},{"family":"Rosue","given":"L. Jesse"},{"family":"Bergeron","given":"Susan"}],"citation-key":"harris_geospatial_2010","collection-title":"GIS and the Future of Humanities Scholarship","container-title":"The Spatial Humanities","editor":[{"family":"Bodenhamer","given":"David J."},{"family":"Corrigan","given":"John"},{"family":"Harris","given":"Trevor M."}],"ISBN":"978-0-253-35505-8","issued":{"date-parts":[["2010"]]},"page":"124-142","publisher":"Indiana University Press","title":"The Geospatial Semantic Web, Pareto GIS, and the Humanities","type":"chapter","URL":"http://www.jstor.org/stable/j.ctt16gzj77.11"},
47
+  {"id":"hawkins_archives_2021","abstract":"Mass digitisation and the exponential growth of born-digital archives over the past two decades have resulted in an enormous volume of archives and archival data being available digitally. This has produced a valuable but under-utilised source of large-scale digital data ripe for interrogation by scholars and practitioners in the Digital Humanities. However, current digitisation approaches fall short of the requirements of digital humanists for structured, integrated, interoperable, and interrogable data. Linked Data provides a viable means of producing such data, creating machine-readable archival data suited to analysis using digital humanities research methods. While a growing body of archival scholarship and praxis has explored Linked Data, its potential to open up digitised and born-digital archives to the Digital Humanities is under-examined. This article approaches Archival Linked Data from the perspective of the Digital Humanities, extrapolating from both archival and digital humanities Linked Data scholarship to identify the benefits to digital humanists of the production and provision of access to Archival Linked Data. It will consider some of the current barriers preventing digital humanists from being able to experience the benefits of Archival Linked Data evidenced, and to fully utilise archives which have been made available digitally. The article argues for increased collaboration between the two disciplines, challenges individuals and institutions to engage with Linked Data, and suggests the incorporation of AI and low-barrier tools such as Wikidata into the Linked Data production workflow in order to scale up the production of Archival Linked Data as a means of increasing access to and utilisation of digitised and born-digital archives.","accessed":{"date-parts":[["2022",1,15]]},"author":[{"family":"Hawkins","given":"Ashleigh"}],"citation-key":"hawkins_archives_2021","container-title":"Archival Science","container-title-short":"Arch Sci","DOI":"10.1007/s10502-021-09381-0","ISSN":"1389-0166, 1573-7500","issued":{"date-parts":[["2021",12,27]]},"language":"en","page":"319–344","source":"DOI.org (Crossref)","title":"Archives, linked data and the digital humanities : Increasing access to digitised and born-digital archives via the semantic web","title-short":"Archives, linked data and the digital humanities","type":"article-journal","URL":"https://link.springer.com/10.1007/s10502-021-09381-0","volume":"22"},
48
+  {"id":"hiebel_crmgeo_2017","abstract":"CRMgeo is a formal ontology intended to be used as a global schema for integrating spatiotemporal properties of temporal entities and persistent items. Its primary purpose is to provide a schema consistent with the CIDOC CRM to integrate geoinformation using the conceptualizations, formal definitions, encoding standards and topological relations defined by the Open Geospatial Consortium in GeoSPARQL. To build the ontology, the same ontology engineering methodology was used as in the CIDOC CRM. CRMgeo first introduced the concept of Spacetime volume that was subsequently included in the CIDOC CRM and provides a differentiation between phenomenal and declarative Spacetime volume, Place and Time-Span. Phenomenal classes derive their identity from real world phenomena like events or things and declarative classes derive their identity from human declarations like dates or coordinates. This differentiation is an essential conceptual background to link CIDOC CRM to the classes, topological relations and encodings provided by Geo-SPARQL and thus allowing spatiotemporal analysis offered by geoinformation systems based on the semantic distinctions of the CIDOC CRM. CRMgeo introduces the classes and relations necessary to model the spatiotemporal properties of real world phenomena and their topological and semantic relations to spatiotemporal information about these phenomena that was derived from historic sources, maps, observations or measurements. It is able to model the full chain of approximating and finding again a phenomenal place, like the actual site of a ship wreck, by a declarative place, like a mark on a sea chart.","accessed":{"date-parts":[["2023",7,8]]},"author":[{"family":"Hiebel","given":"Gerald"},{"family":"Doerr","given":"Martin"},{"family":"Eide","given":"Øyvind"}],"citation-key":"hiebel_crmgeo_2017","container-title":"International Journal on Digital Libraries","container-title-short":"Int J Digit Libr","DOI":"10.1007/s00799-016-0192-4","ISSN":"1432-1300","issue":"4","issued":{"date-parts":[["2017",11,1]]},"language":"en","page":"271-279","source":"Springer Link","title":"CRMgeo: A spatiotemporal extension of CIDOC-CRM","title-short":"CRMgeo","type":"article-journal","URL":"https://doi.org/10.1007/s00799-016-0192-4","volume":"18"},
49
+  {"id":"hosseini_mapreader_2022","abstract":"We present MapReader, a free, open-source software library written in Python for analyzing large map collections. MapReader allows users with little computer vision expertise to i) retrieve maps via web-servers; ii) preprocess and divide them into patches; iii) annotate patches; iv) train, fine-tune, and evaluate deep neural network models; and v) create structured data about map content. We demonstrate how MapReader enables historians to interpret a collection of ≈16K nineteenth-century maps of Britain (≈30.5M patches), foregrounding the challenge of translating visual markers into machine-readable data. We present a case study focusing on rail and buildings. We also show how the outputs from the MapReader pipeline can be linked to other, external datasets. We release ≈62K manually annotated patches used here for training and evaluating the models.","accessed":{"date-parts":[["2023",10,5]]},"author":[{"family":"Hosseini","given":"Kasra"},{"family":"Wilson","given":"Daniel C. S."},{"family":"Beelen","given":"Kaspar"},{"family":"McDonough","given":"Katherine"}],"citation-key":"hosseini_mapreader_2022","collection-title":"GeoHumanities '22","container-title":"Proceedings of the 6th ACM SIGSPATIAL International Workshop on Geospatial Humanities","DOI":"10.1145/3557919.3565812","event-place":"New York, NY, USA","ISBN":"978-1-4503-9533-5","issued":{"date-parts":[["2022",11,11]]},"page":"8–19","publisher":"Association for Computing Machinery","publisher-place":"New York, NY, USA","source":"ACM Digital Library","title":"MapReader: a computer vision pipeline for the semantic exploration of maps at scale","title-short":"MapReader","type":"paper-conference","URL":"https://doi.org/10.1145/3557919.3565812"},
50
+  {"id":"hubl_spatial_2021","abstract":"Question answering in Geohumanities within the Semantic Web is a broad research field. This work incorporates the investigation, use and extension of existing patterns and ontologies having a space and time dimension to combine historical Linked Places and Linked Traces data. Linked Traces are way to collect historical events and places in a so-called trace, in order to describe events that consist of several single places/events-e.g., the expeditions of Charles Darwin. The paper deals with the integration of Linked Data repositories like World Historical Gazetteer for trace data. By linking different historical data sources new historical findings can be inferred. That can be managed by creating a Knowledge Graph, a semantically enriched contextual triplestore, which functions as a basis for e.g., Geographic Question Answering. The data-driven method of creating a Knowledge Graph can be realized by combining ontologies and data sources of interest. The resulting spatial Linked Data approach is tested and evaluated with regard to geoseman-tic capabilities in form of a Knowledge Graph investigation. To follow the motivation of \"linking\" a SPARQL Endpoint is used to show a standardized proof-of-concept implementation.","accessed":{"date-parts":[["2023",7,16]]},"author":[{"family":"Hübl","given":"Franziska"},{"family":"Scholz","given":"Johannes"}],"citation-key":"hubl_spatial_2021","container-title":"Spatial Data Science Symposium 2021 Short Paper Proceedings","DOI":"https://doi.org/10.25436/E2T882","event-place":"Santa Barbara","event-title":"Spatial Data Science Symposium 2021","issued":{"date-parts":[["2021",12,1]]},"language":"en","publisher":"eScholarship","publisher-place":"Santa Barbara","source":"escholarship.org","title":"Spatial linked data approach for trace data in digital humanities","type":"paper-conference","URL":"https://escholarship.org/uc/item/57z4w749"},
51
+  {"id":"isaksen_pelagios_2014","abstract":"This paper discusses an emerging cloud of Linked Open Data in the humanities sometimes referred to as the Graph of Ancient World Data (GAWD). It provides historical background to the domain, before gong on to describe the open and decentralised characteristics which have partially characterised its development. This is done principally through the lens of Pelagios, a collaborative initiative led by the authors which connects online historical resources based on common references to places. The benefits and limitations of the approach are evaluated, in particular its low barrier to entry, open architecture and restricted scope. The paper concludes with a number of suggestion for encouraging the adoption of Linked Open Data within other humanities communities and beyond.","accessed":{"date-parts":[["2023",12,10]]},"author":[{"family":"Isaksen","given":"Leif"},{"family":"Simon","given":"Rainer"},{"family":"Barker","given":"Elton T.E."},{"family":"Soto Cañamares","given":"Pau","non-dropping-particle":"de"}],"citation-key":"isaksen_pelagios_2014","collection-title":"WebSci '14","container-title":"Proceedings of the 2014 ACM conference on Web science","DOI":"10.1145/2615569.2615693","event-place":"New York, NY, USA","ISBN":"978-1-4503-2622-3","issued":{"date-parts":[["2014",6,23]]},"page":"197–201","publisher":"Association for Computing Machinery","publisher-place":"New York, NY, USA","source":"ACM Digital Library","title":"Pelagios and the emerging graph of ancient world data","type":"paper-conference","URL":"https://doi.org/10.1145/2615569.2615693"},
52
+  {"id":"jaillant_archives_2022","abstract":"Digital archives are transforming the Humanities and the Sciences. Digitized collections of newspapers and books have pushed scholars to develop new, data-rich methods. Born-digital archives are now better preserved and managed thanks to the development of open-access and commercial software. Digital Humanities have moved from the fringe to the center of academia. Yet, the path from the appraisal of records to their analysis is far from smooth. This book explores crossovers between various disciplines to improve the discoverability, accessibility, and use of born-digital archives and other cultural assets.","citation-key":"jaillant_archives_2022","collection-number":"Volume 2","collection-title":"Digital Humanities Research","DOI":"10.14361/9783839455845","editor":[{"family":"Jaillant","given":"Lise"}],"event-place":"Bielefeld","ISBN":"978-3-8376-5584-1","issued":{"date-parts":[["2022"]]},"language":"eng","number-of-pages":"221","publisher":"Bielefeld University Press","publisher-place":"Bielefeld","source":"K10plus ISBN","title":"Archives, access and artificial intelligence: Working with born-digital and digitised archival collections","title-short":"Archives, access and artificial intelligence","type":"book","URL":"https://www.transcript-publishing.com/978-3-8376-5584-1/archives-access-and-artificial-intelligence/"},
53
+  {"id":"kervegan__2023","abstract":"À partir d'un corpus complexe (iconographique, cartographique, textuel) portant sur un quartier parisien (1750-1950), nous proposons de définir un élément à même de réunir, de modéliser et de représenter nos sources : le lieu. Celui-ci permet de faire converger les composantes spatiales et historiques de notre corpus. Il s'agit alors de montrer la manière dont le lieu est appréhendé d'un point de vue technique : de quelle manière il peut être modélisé, mais aussi comment il peut être représenté dans un modèle 3D historique. Enfin, nous présenterons la manière dont le lieu peut servir de moteur pour l'exploration et l'interaction avec le corpus sur une application Web. En définitive, nous souhaitons interroger la manière dont le lieu vient modifier notre rapport aux sources et à la technique, dans le cadre d'un projet en humanités numériques et en histoire de l'architecture.","accessed":{"date-parts":[["2023",6,30]]},"author":[{"family":"Kervegan","given":"Paul"},{"family":"Duvette","given":"Charlotte"},{"family":"Jeanson","given":"Loïc"},{"family":"Prudhomme","given":"Colin"},{"family":"Gain","given":"Justine"},{"family":"Dasilva","given":"Esther"},{"family":"Baranger","given":"Louise"}],"citation-key":"kervegan__2023","container-title":"Recueil des communications du 4<sup>e</sup> colloque Humanistica","event-place":"Genève","event-title":"Humanistica 2023","issued":{"date-parts":[["2023",6,26]]},"language":"fr","publisher-place":"Genève","source":"hal.science","title":"« La marque du lieu » dans le « quartier Richelieu »","type":"paper-conference","URL":"https://hal.science/hal-04108218"},
54
+  {"id":"kim_mapkurator_2023","abstract":"Scanned historical maps in libraries and archives are valuable repositories of geographic data that often do not exist elsewhere. Despite the potential of machine learning tools like the Google Vision APIs for automatically transcribing text from these maps into machinereadable formats, they do not work well with large-sized images (e.g., high-resolution scanned documents), cannot infer the relation between the recognized text and other datasets, and are challenging to integrate with post-processing tools. This paper introduces the mapKurator system, an end-to-end system integrating machine learning models with a comprehensive data processing pipeline. mapKurator empowers automated extraction, post-processing, and linkage of text labels from large numbers of large-dimension historical map scans. The output data, comprising bounding polygons and recognized text, is in the standard GeoJSON format, making it easily modifiable within Geographic Information Systems (GIS). The proposed system allows users to quickly generate valuable data from large numbers of historical maps for in-depth analysis of the map content and, in turn, encourages map findability, accessibility, interoperability, and reusability (FAIR principles). We deployed the mapKurator system and enabled the processing of over 60,000 maps and over 100 million text/place names in the David Rumsey Historical Map collection. We also demonstrated a seamless integration of mapKurator with a collaborative web platform to enable accessing automated approaches for extracting and linking text labels from historical map scans and collective work to improve the results.","accessed":{"date-parts":[["2023",9,16]]},"author":[{"family":"Kim","given":"Jina"},{"family":"Li","given":"Zekun"},{"family":"Lin","given":"Yijun"},{"family":"Namgung","given":"Min"},{"family":"Jang","given":"Leeje"},{"family":"Chiang","given":"Yao-Yi"}],"citation-key":"kim_mapkurator_2023","issued":{"date-parts":[["2023",7,3]]},"language":"en","number":"arXiv:2306.17059","publisher":"arXiv","source":"arXiv.org","title":"The mapkurator system: a complete pipeline for extracting and linking text from historical maps","title-short":"The mapkurator system","type":"article","URL":"http://arxiv.org/abs/2306.17059"},
55
+  {"id":"knowles_introduction_2000","accessed":{"date-parts":[["2022",2,6]]},"author":[{"family":"Knowles","given":"Anne Kelly"}],"citation-key":"knowles_introduction_2000","container-title":"Social Science History","DOI":"10.1017/S0145553200010269","ISSN":"0145-5532, 1527-8034","issue":"3","issued":{"date-parts":[["2000"]]},"language":"en","page":"451-470","source":"DOI.org (Crossref)","title":"Introduction. Special Issue: Historical GIS: The Spatial Turn in Social Science History","type":"article-journal","URL":"https://www.cambridge.org/core/product/identifier/S0145553200010269/type/journal_article","volume":"24"},
56
+  {"id":"koster_fair_2018","abstract":"Many heritage institutions would like their collections to be open and reusable but fail to achieve that situation because of organizational, legal and technological barriers. A set of guidelines and best practices is proposed to facilitate the process of making heritage collections reusable. These guidelines are based on the FAIR Principles for scholarly output (FAIR data principles [2014]), taking into account a number of other recent initiatives for making data findable, accessible, interoperable and reusable. The resulting FAIR Principles for Heritage Library, Archive and Museum Collections focus on three levels: objects, metadata and metadata records. Clarifications and examples of these proposed principles are presented, as well as recommendations for the assessment of current situations and implementations of the principles.","accessed":{"date-parts":[["2022",1,22]]},"author":[{"family":"Koster","given":"Lukas"},{"family":"Woutersen-Windhouwer","given":"Saskia"}],"citation-key":"koster_fair_2018","container-title":"The Code4Lib Journal","ISSN":"1940-5758","issued":{"date-parts":[["2018",5,4]]},"source":"Code4Lib Journal","title":"FAIR Principles for Library, Archive and Museum Collections: A proposal for standards for reusable collections","title-short":"FAIR Principles for Library, Archive and Museum Collections","type":"article-journal","URL":"https://journal.code4lib.org/articles/13427","volume":"40"},
57
+  {"id":"le_clech_archives_2017","abstract":"Dans cet article, Laetitia Le Clech fait le survol de différents enjeux et particularités qui touchent la conservation des archives géographiques. En plus des cartes, ces dernières comprennent également des photographies et images, ainsi que certaines études de terrain. Elle présente dans un premier temps quelques exemples de traitement de documents cartographiques en différents endroits, en plus de nous exposer les défis particuliers que posent ces documents. Les archives géographiques ont de multiples utilités, que ce soit dans le domaine historique, en géopolitique ou même dans le développement de politiques gouvernementales. L’auteure en fait la recension et illustre chacun de ces usages par des exemples. Elle donne ensuite un aperçu de la conservation des documents cartographiques suite à l’avènement de l’ère du numérique. En effet, tout comme pour d’autres types d’archives, ce contexte amène son lot de questionnements et de nouvelles pratiques, que ce soit par la numérisation dans le but de les conserver et de les diffuser, mais aussi par la nécessité de se préoccuper de l’obsolescence des supports et d’établir de nouvelles normes. L’auteure termine son texte en nous présentant diverses initiatives de diffusion et de création qui sont issues de ces nouvelles possibilités qu’offre le monde numérique. Elle ne manque pas en passant de nous mettre en garde contre certains abus et de plaider pour un encadrement renforcé afin de mieux mettre en valeur ces documents bien particuliers.","accessed":{"date-parts":[["2023",3,1]]},"author":[{"family":"Le Clech","given":"Laetitia"}],"citation-key":"le_clech_archives_2017","container-title":"Archives","container-title-short":"archives","DOI":"10.7202/1041826ar","ISSN":"0044-9423, 2369-9256","issue":"1","issued":{"date-parts":[["2017"]]},"language":"fr","page":"59-83","publisher":"Association des archivistes du Québec (AAQ)","source":"www.erudit.org","title":"Archives et géographie : typologie, caractéristiques et perspectives","title-short":"Archives et géographie","type":"article-journal","URL":"https://www.erudit.org/fr/revues/archives/2017-v47-n1-archives03257/1041826ar/","volume":"47"},
58
+  {"id":"li_automatic_2020","accessed":{"date-parts":[["2022",2,9]]},"author":[{"family":"Li","given":"Zekun"},{"family":"Chiang","given":"Yao-Yi"},{"family":"Tavakkol","given":"Sasan"},{"family":"Shbita","given":"Basel"},{"family":"Uhl","given":"Johannes H."},{"family":"Leyk","given":"Stefan"},{"family":"Knoblock","given":"Craig A."}],"citation-key":"li_automatic_2020","container-title":"Proceedings of the 26th ACM SIGKDD International Conference on Knowledge Discovery & Data Mining","DOI":"10.1145/3394486.3403381","event-place":"Virtual Event CA USA","event-title":"KDD '20: The 26th ACM SIGKDD Conference on Knowledge Discovery and Data Mining","ISBN":"978-1-4503-7998-4","issued":{"date-parts":[["2020",8,23]]},"language":"en","page":"3290-3298","publisher":"ACM","publisher-place":"Virtual Event CA USA","source":"DOI.org (Crossref)","title":"An automatic approach for generating rich, linked geo-metadata from historical map images","type":"paper-conference","URL":"https://dl.acm.org/doi/10.1145/3394486.3403381"},
59
+  {"id":"lieberman_w3c_2007","abstract":"This is a report of the W3C Geospatial Incubator Group (GeoXG) as specified in the Deliverables section of its charter.","accessed":{"date-parts":[["2023",7,20]]},"author":[{"family":"Lieberman","given":"Joshua"},{"family":"Singh","given":"Raj"},{"family":"Goad","given":"Chris"}],"citation-key":"lieberman_w3c_2007","issued":{"date-parts":[["2007"]]},"publisher":"World Wide Web Consortium","title":"W3C Geospatial Ontologies","type":"report","URL":"https://www.w3.org/2005/Incubator/geo/XGR-geo-ont-20071023/"},
60
+  {"id":"light_linked_2020","abstract":"Work-in-progress ontology to support Linked Places and Linked Traces formats","accessed":{"date-parts":[["2023",7,16]]},"author":[{"family":"Light","given":"Richard"},{"family":"Grossner","given":"Karl"}],"citation-key":"light_linked_2020","issued":{"date-parts":[["2021",5,25]]},"publisher":"Linked Pasts","source":"GitHub","title":"Linked Pasts Ontology","type":"software","URL":"https://github.com/LinkedPasts/linked-pasts-ontology","version":"1.1"},
61
+  {"id":"linteau_histoire_2022","abstract":"\"Ville portuaire, centre industriel et métropole de services, Montréal a joué un rôle exceptionnel dans le développement du Québec et du Canada et elle continue à le faire. Montréal est un carrefour où circulent non seulement des personnes et des marchandises mais aussi des idées, des cultures et des influences multiples. Certes, beaucoup d'autres villes ont de telles fonctions, mais celles-ci prennent une coloration spécifique à Montréal. Ce qui la distingue avant tout, c'est sa fibre francophone. Cette ville a été fondée par une poignée de Français dont les descendants ont su négocier avec les autochtones qui occupaient déjà le territoire nord-américain. Ils y ont très tôt forgé une identité spécifique, celle de Montréalistes, qui encore aujourd'hui les distingue de leurs compatriotes du Québec. Montréal a aussi été profondément marquée par l'apport des peuples de souche britannique, les Montrealers, qui sont présents dans la ville depuis deux siècles et demi et qui ont laissé des traces durables dans l'organisation spatiale et économique du territoire, dans les institutions et la sociabilité urbaines ainsi que dans le patrimoine architectural. Depuis un peu plus d'un siècle, la métropole vit au rythme de l'arrivée continuelle de vagues de nouveaux Montréalais. Les Juifs et les Italiens, puis les Grecs et les Haïtiens, les Chinois et les Pakistanais côtoient les Algériens, les Marocains, les Libanais et tant d'autres peuples qui font de Montréal un creuset interculturel et renforcent son rôle de ville d'accueil. Cette synthèse, signée par le plus grand expert de l'histoire de Montréal, tient compte des dimensions démographiques, économiques, spatiales, sociales, culturelles et politiques de l'histoire de Montréal pour en dresser le portrait le plus complet possible. La reprise dans la collection \"Boréal compact\" est l'occasion pour Paul-André Linteau d'effectuer une mise à jour qui tient compte des dernières avancées de la recherche ainsi que des élections de novembre 2021.\"","author":[{"family":"Linteau","given":"Paul-André"}],"call-number":"971.428","citation-key":"linteau_histoire_2022","collection-number":"332","collection-title":"Boréal compact","edition":"Édition revue et augmentée","event-place":"Montréal, Québec","ISBN":"978-2-7646-2703-7","issued":{"date-parts":[["2022"]]},"language":"fre","publisher":"Boréal","publisher-place":"Montréal, Québec","source":"BnF ISBN","title":"Une histoire de Montréal","type":"book"},
62
+  {"id":"mai_deeply_2019","abstract":"The realization that knowledge often forms a densely interconnected graph has fueled the development of graph databases, Web-scale knowledge graphs and query languages for them, novel visualization and query paradigms, as well as new machine learning methods tailored to graphs as data structures. One such example is the densely connected and global Linked Data cloud that contains billions of statements about numerous domains, including life science and geography. While Linked Data has found its way into everyday applications such as search engines and question answering systems, there is a growing disconnect between the classical ways in which Geographic Information Systems (GIS) are still used today and the open-ended, exploratory approaches used to retrieve and consume data from knowledge graphs such as Linked Data. In this work, we conceptualize and prototypically implement a Linked Data connector framework as a set of toolboxes for Esri's ArcGIS to close this gap and enable the retrieval, integration, and analysis of Linked Data from within GIS. We discuss how to connect to Linked Data endpoints, how to use ontologies to probe data and derive appropriate GIS representations on the fly, how to make use of reasoning, how to derive data that are ready for spatial analysis out of RDF triples, and, most importantly, how to utilize the link structure of Linked Data to enable analysis. The proposed Linked Data connector framework can also be regarded as the first step toward a guided geographic question answering system over geographic knowledge graphs.","accessed":{"date-parts":[["2023",2,14]]},"author":[{"family":"Mai","given":"Gengchen"},{"family":"Janowicz","given":"Krzysztof"},{"family":"Yan","given":"Bo"},{"family":"Scheider","given":"Simon"}],"citation-key":"mai_deeply_2019","container-title":"Transactions in GIS","DOI":"10.1111/tgis.12538","ISSN":"1467-9671","issue":"3","issued":{"date-parts":[["2019",6,11]]},"language":"en","page":"579-600","source":"Wiley Online Library","title":"Deeply integrating Linked Data with Geographic Information Systems","type":"article-journal","URL":"https://onlinelibrary.wiley.com/doi/abs/10.1111/tgis.12538","volume":"23"},
63
+  {"id":"mcdonough_machines_2023","accessed":{"date-parts":[["2022",2,9]]},"author":[{"family":"McDonough","given":"Katherine"},{"family":"Rainer","given":"Simon"},{"family":"Vitale","given":"Valeria"},{"family":"Chiang","given":"Yao-Yi"},{"family":"Zekun","given":"Li"},{"family":"Kim","given":"Jina"},{"family":"Holmes-Wong","given":"Deborah"}],"citation-key":"mcdonough_machines_2023","issued":{"date-parts":[["2023"]]},"language":"en-US","title":"Machines Reading Maps. Unlocking unique information from large collections of historical maps using AI","type":"webpage","URL":"https://machines-reading-maps.github.io"},
64
+  {"id":"melvin_modeles_2023","abstract":"L'interopérabilité des données dans un projet pluridisciplinaire est primordiale. Prenant l'exemple d'un projet de recherche en histoire spatiale, nous comparerons dans un premier temps les standards et vocabulaires à notre disposition pour décrire des données géographiques et des documents d'archives. Nous proposons ensuite un alignement entre les standards retenus : l'ISO 19115 et RiC-O. Enfin, nous proposons une architecture de microservices pour la saisie, le stockage, la publication sur le Web et l'interrogation unifiée des métadonnées de nos sources.","accessed":{"date-parts":[["2023",6,29]]},"author":[{"family":"Hersent","given":"Melvin"},{"family":"Abadie","given":"Nathalie"},{"family":"Duménieu","given":"Bertrand"},{"family":"Perret","given":"Julien"}],"citation-key":"melvin_modeles_2023","event-title":"Humanistica 2023","issued":{"date-parts":[["2023",6,26]]},"language":"fr","source":"hal.science","title":"Modèles et outils pour la publication de métadonnées d'archives géographiques et de leurs données dérivées","type":"paper-conference","URL":"https://hal.science/hal-04110787"},
65
+  {"id":"michon_archivistique_2017","abstract":"Le Web sémantique commence à intéresser les chercheurs en sciences historiques au Québec. Son fonctionnement demande par contre une restructuration des méthodologies archivistique et historienne afin d’accroître l’interopérabilité des données produites par chacune de ces disciplines. Les données liées, initiative technique qui sous-tend le Web sémantique, nécessitent l’utilisation de multiples vocabulaires et normes afin de créer des liens entre les contenus dans le but d’inscrire ces derniers dans un nuage de données interrogeable dynamiquement. Ce court article explique succinctement le fonctionnement du Web sémantique dans le but de présenter un modèle ontologique construit autour de la notion d’événement qui s’intitule Conceptual Reference Model élaboré par le Comité international pour la documentation de l’International Council of Museums. Cette introduction à une des ontologies susceptibles d’emmagasiner la complexité d’un fait patrimonial, amènera une réflexion autour des compétences communes et à acquérir pour les professionnels de chacune de ces disciplines. La question de l’interdisciplinarité est au coeur de l’argumentaire afin de démontrer que l’implication d’un grand nombre d’acteurs est primordiale pour assurer le développement d’une plateforme sémantique provinciale sur l’histoire québécoise.","accessed":{"date-parts":[["2022",2,3]]},"author":[{"family":"Michon","given":"Philippe"}],"citation-key":"michon_archivistique_2017","container-title":"Archives","container-title-short":"archives","DOI":"10.7202/1041827ar","ISSN":"0044-9423, 2369-9256","issue":"1","issued":{"date-parts":[["2017"]]},"language":"fr","page":"85-105","source":"www.erudit.org","title":"Archivistique, histoire et Web sémantique : une approche interdisciplinaire basée sur l’événementiel","title-short":"Archivistique, histoire et Web sémantique","type":"article-journal","URL":"https://id.erudit.org/iderudit/1041827ar","volume":"47"},
66
+  {"id":"moss_reconfiguration_2018","abstract":"This article discusses changing practices brought about by the move to online digital records, the impact these are having on the way history is written, and the way in which archivists are responding (and will need to respond in the future). We argue that digital administrative records are surrounded by other sources – online newspapers and social media – and that the huge volume of digital records alters the way historians read material. This will require a shift in approach from archivists, who will need to view archives as collections of data to be mined and not as texts to be read. Approaches to appraisal will need to be modified, and archivists will need to understand the tools and techniques used to make sense of digital records. While grappling with these issues, archivists will also need to recognize that the future record will be as much about sound and vision as about text. RÉSUMÉCet article aborde les pratiques changeantes occasionnées par le passage vers les documents numériques en ligne, l’impact de ces changements sur la façon dont l’histoire est écrite, et les façons dont les archivistes réagissent (et devront réagir à l’avenir). Nous soutenons que les documents administratifs numériques sont entourés d’autres sources – quotidiens en ligne et médias sociaux – et que la quantité énorme de documents numériques modifie la façon dont les historiens lisent le matériel. Ceci nécessitera un changement dans l’approche des archivistes qui devront voir les archives comme collections de données à exploiter et non comme textes à lire. Les approches en évaluation archivistique devront être modifiées et les archivistes devront bien saisir les outils et techniques qui servent à comprendre les documents numériques. Tout en faisant face à ces questions, les archivistes devront aussi reconnaître que le document d’archives de l’avenir sera autant une question de son et d’images que de texte.","accessed":{"date-parts":[["2022",1,31]]},"author":[{"family":"Moss","given":"Michael"},{"family":"Thomas","given":"David"},{"family":"Gollins","given":"Tim"}],"citation-key":"moss_reconfiguration_2018","container-title":"Archivaria","ISSN":"1923-6409","issue":"November","issued":{"date-parts":[["2018",11,26]]},"language":"en","license":"Copyright (c) 2018 Michael Moss, David Thomas, Tim Gollins","page":"118-151","title":"The reconfiguration of the archive as data to be mined","type":"article-journal","URL":"https://archivaria.ca/index.php/archivaria/article/view/13646","volume":"86"},
67
+  {"id":"nishanbaev_survey_2019","abstract":"The amount of digital cultural heritage data produced by cultural heritage institutions is growing rapidly. Digital cultural heritage repositories have therefore become an efficient and effective way to disseminate and exploit digital cultural heritage data. However, many digital cultural heritage repositories worldwide share technical challenges such as data integration and interoperability among national and regional digital cultural heritage repositories. The result is dispersed and poorly-linked cultured heritage data, backed by non-standardized search interfaces, which thwart users&rsquo; attempts to contextualize information from distributed repositories. A recently introduced geospatial semantic web is being adopted by a great many new and existing digital cultural heritage repositories to overcome these challenges. However, no one has yet conducted a conceptual survey of the geospatial semantic web concepts for a cultural heritage audience. A conceptual survey of these concepts pertinent to the cultural heritage field is, therefore, needed. Such a survey equips cultural heritage professionals and practitioners with an overview of all the necessary tools, and free and open source semantic web and geospatial semantic web platforms that can be used to implement geospatial semantic web-based cultural heritage repositories. Hence, this article surveys the state-of-the-art geospatial semantic web concepts, which are pertinent to the cultural heritage field. It then proposes a framework to turn geospatial cultural heritage data into machine-readable and processable resource description framework (RDF) data to use in the geospatial semantic web, with a case study to demonstrate its applicability. Furthermore, it outlines key free and open source semantic web and geospatial semantic platforms for cultural heritage institutions. In addition, it examines leading cultural heritage projects employing the geospatial semantic web. Finally, the article discusses attributes of the geospatial semantic web that require more attention, that can result in generating new ideas and research questions for both the geospatial semantic web and cultural heritage fields.","accessed":{"date-parts":[["2021",2,21]]},"author":[{"family":"Nishanbaev","given":"Ikrom"},{"family":"Champion","given":"Erik"},{"family":"McMeekin","given":"David A."}],"citation-key":"nishanbaev_survey_2019","container-title":"Heritage","DOI":"10.3390/heritage2020093","issue":"2","issued":{"date-parts":[["2019",6]]},"language":"en","license":"http://creativecommons.org/licenses/by/3.0/","number":"2","page":"1471-1498","publisher":"Multidisciplinary Digital Publishing Institute","source":"www.mdpi.com","title":"A Survey of Geospatial Semantic Web for Cultural Heritage","type":"article-journal","URL":"https://www.mdpi.com/2571-9408/2/2/93","volume":"2"},
68
+  {"id":"noauthor_gouda_nodate","accessed":{"date-parts":[["2023",12,9]]},"citation-key":"noauthor_gouda_nodate","container-title":"Gouda Tijdmachine","language":"nl","title":"Gouda Tijdmachine data gebruik","type":"webpage","URL":"https://www.goudatijdmachine.nl/omeka/s/data/page/usageInfo"},
69
+  {"id":"noizet_paris_2013","abstract":"Ce travail collectif regroupant historiens, géographes et informaticiens, témoigne des profonds renouvellements de l'histoire médiévale et moderne de Paris grâce à l'analyse spatiale. Le plus ancien plan parcellaire de Paris (plans Vasserot 1810-1836) a été reconstitué dans un système d'information géographique, permettant d'analyser la morphologie urbaine et de la croiser avec diverses emprises sociales : localisation des enceintes, densités socio-économiques, spatialités du pouvoir seigneurial et royal, présence de la noblesse à Paris sont autant de dimensions de la fabrique urbaine bénéficiant d'un éclairage nouveau.","accessed":{"date-parts":[["2023",9,9]]},"author":[{"family":"Noizet","given":"Hélène"},{"family":"Bove","given":"Boris"},{"family":"Costa","given":"Laurent"}],"citation-key":"noizet_paris_2013","issued":{"date-parts":[["2013"]]},"language":"fr","note":"URL2: https://www.puv-editions.fr/ouvrage/paris-de-parcelles-en-pixels/","number-of-pages":"354","publisher":"Presses universitaires de Vincennes","source":"hal.science","title":"Paris de parcelles en pixels. Analyse géomatique de l’espace parisien médiéval et moderne","type":"book","URL":"https://hal.science/halshs-00857608"},
70
+  {"id":"norton_fighting_2011","author":[{"family":"Norton","given":"Peter D."}],"citation-key":"norton_fighting_2011","collection-title":"Inside technology","event-place":"Cambridge","ISBN":"978-0-262-51612-9","issued":{"date-parts":[["2011"]]},"language":"eng","number-of-pages":"396","publisher":"MIT Press","publisher-place":"Cambridge","source":"K10plus ISBN","title":"Fighting traffic: The dawn of the motor age in the American city","title-short":"Fighting traffic","type":"book"},
71
+  {"id":"norton_neogeo_2012","abstract":"Numerous providers publish geospatial data as Linked Data. However, no consensus had been achieved for developing a shared RDF vocabulary with enough descriptive power for modelling geographic regions. Every publisher (and every dataset) uses its own vocabulary, making integration difficult. The NeoGeo Vocabulary is the result of discussions at numerous VoCamps related to geospatial data.","accessed":{"date-parts":[["2023",8,16]]},"author":[{"family":"Norton","given":"Barry"},{"family":"Vilches","given":"Luis M."},{"family":"León","given":"Alexander De"},{"family":"Goodwin","given":"John"},{"family":"Stadler","given":"Claus"},{"family":"Anand","given":"Suchith"},{"family":"Harries","given":"Dominic"},{"family":"Villazón-Terrazas","given":"Boris"},{"family":"Atemezing","given":"Ghislain A."}],"citation-key":"norton_neogeo_2012","genre":"spécification","issued":{"date-parts":[["2012",2,7]]},"language":"en","title":"NeoGeo Vocabulary Specification - Madrid Edition","title-short":"NeoGeo Vocabulary Specification","type":"webpage","URL":"http://geovocab.org/doc/neogeo/"},
72
+  {"id":"olson_montre_2015","abstract":"Nouveau site web du projet MAP hébergé parle CIEQ.","accessed":{"date-parts":[["2022",5,23]]},"author":[{"family":"Olson","given":"Sherry"},{"family":"Sweeny","given":"Robert C.H."}],"citation-key":"olson_montre_2015","container-title":"Centre interuniversitaire d’études québécoises","issued":{"date-parts":[["2015"]]},"language":"fr","title":"Montréal, l’avenir du passé","type":"webpage","URL":"https://map.cieq.ca"},
73
+  {"id":"palomino_pour_2023","abstract":"Ce projet, mené par le Laboratoire en collaboration avec Bibliothèque et Archives nationales du Québec (BAnQ), vise à faciliter l’accès aux plans d’assurance-incendie de Montréal conservés et diffusés par BAnQ, par le géoréférencement des plans et par la mise en ligne d’une carte-index interactive.","accessed":{"date-parts":[["2021",9,4]]},"author":[{"family":"Palomino","given":"Jean-François"},{"family":"Robichaud","given":"Léon"}],"citation-key":"palomino_pour_2023","container-title":"Laboratoire d'histoire et de patrimoine de Montréal","issued":{"date-parts":[["2023",1,25]]},"language":"fr-CA","title":"Pour un meilleur accès aux cartes anciennes de Montréal","type":"webpage","URL":"https://lhpm.uqam.ca/programmation-scientifique/patrimonialisation-commemoration-et-exposition/pour-un-meilleur-acces-aux-cartes-anciennes-de-montreal/"},
74
+  {"id":"peroni_simplified_2017","accessed":{"date-parts":[["2022",5,25]]},"author":[{"family":"Peroni","given":"Silvio"}],"citation-key":"peroni_simplified_2017","collection-number":"10161","collection-title":"Lecture notes in computer science","container-title":"OWL: Experiences and directions – Reasoner evaluation. 13th international workshop, OWLED 2016, and 5th international workshop, ORE 2016","DOI":"10.1007/978-3-319-54627-8_5","editor":[{"family":"Dragoni","given":"Mauro"},{"family":"Poveda-Villalón","given":"María"},{"family":"Jimenez-Ruiz","given":"Ernesto"}],"event-place":"Cham","ISBN":"978-3-319-54626-1 978-3-319-54627-8","issued":{"date-parts":[["2017"]]},"page":"55-69","publisher":"Springer International Publishing","publisher-place":"Cham","source":"DOI.org (Crossref)","title":"A simplified agile methodology for ontology development","type":"chapter","URL":"http://link.springer.com/10.1007/978-3-319-54627-8_5"},
75
+  {"id":"poublanc_obardi_2022","abstract":"Introduction  ObARDI est un projet interdisciplinaire financé par l’Agence nationale de la recherche pour la période 2021-2025. Il s’inscrit dans l’axe “Révolution numérique : rapports au savoir et à la culture”, axe liant sciences du numérique et SHS, et a pour objet de recherche le développement d’ontologies informatiques pour étudier la construction de l’État moderne dans la France d’Ancien Régime. Les participants sont des chercheurs en économie (Victor Gay, coordinateur), en histoire (Ga...","accessed":{"date-parts":[["2022",12,17]]},"author":[{"family":"Poublanc","given":"Sébastien"},{"family":"Gay","given":"Victor"}],"citation-key":"poublanc_obardi_2022","container-title":"e-Storia. Les Cahiers de Framespa","DOI":"10.4000/framespa.13379","ISSN":"1760-4761","issue":"41","issued":{"date-parts":[["2022",11,15]]},"language":"fr","license":"https://creativecommons.org/licenses/by-nc-nd/4.0/","number":"41","publisher":"UMR 5136 – FRAMESPA","source":"journals.openedition.org","title":"ObARDI : un projet interdisciplinaire pour comprendre la construction de l'État moderne (1661-1789)","title-short":"ObARDI","type":"article-journal","URL":"https://journals.openedition.org/framespa/13379"},
76
+  {"id":"raimond_event_2007","abstract":"This document describes the Event ontology developed in the Centre for Digital Music in Queen Mary, University of London. The first draft of the ontology was written in October, 2004. This ontology is centered around the notion of event, seen here as the way by which cognitive agents classify arbitrary time/space regions.","accessed":{"date-parts":[["2023",8,28]]},"author":[{"family":"Raimond","given":"Yves"},{"family":"Abdallah","given":"Samer"}],"citation-key":"raimond_event_2007","issued":{"date-parts":[["2007"]]},"title":"The Event Ontology","type":"document","URL":"https://motools.sourceforge.net/event/event.html"},
77
+  {"id":"robichaud_comment_2016","accessed":{"date-parts":[["2023",2,28]]},"author":[{"family":"Robichaud","given":"Léon"}],"citation-key":"robichaud_comment_2016","container-title":"Geohistory-Géohistoire Canada","issued":{"date-parts":[["2016",5,30]]},"language":"fr","title":"Comment retrouver et relier toute cette information géohistorique?","title-short":"Comment retrouver et relier toute cette information géohistorique?","type":"post-weblog","URL":"http://geohist.ca/fr/2016/05/comment-retrouver-et-relier-toute-cette-information-geohistorique/"},
78
+  {"id":"robichaud_description_2022","accessed":{"date-parts":[["2022",8,29]]},"author":[{"family":"Robichaud","given":"Léon"},{"family":"Lampron","given":"Catherine"}],"citation-key":"robichaud_description_2022","event":"Journée annuelle du Laboratoire d’histoire et de patrimoine de Montréal","event-place":"Montréal","event-title":"Journée annuelle du Laboratoire d’histoire et de patrimoine de Montréal","genre":"Conférence","issued":{"date-parts":[["2022",6,3]]},"language":"fr-CA","publisher-place":"Montréal","title":"La description sémantique des lieux. Réflexions sur la mise en relation des références spatiales extraites d’un document d’archive","title-short":"La description sémantique des lieux","type":"speech","URL":"https://lhpm.uqam.ca/production-scientifique/communications/"},
79
+  {"id":"robichaud_montreen_nodate","abstract":"Les 4 applications de ce projet offrent un portrait de Montréal en 1881 à partir des sources suivantes :\n\n    l’annuaire Lovell, 1880\n    le rôle d’évaluation de la ville de Montréal, 1880\n    le recensement du Canada pour le territoire de la ville de Montréal, 1881.\n\nLes jeux de données tirées de ces sources ont été compilées dans le cadre du projet MAP « Montréal, l’avenir du passé », dirigé par Sherry Olson et Robert C.H. Sweeny et sont disponibles en ligne","accessed":{"date-parts":[["2021",9,4]]},"author":[{"family":"Robichaud","given":"Léon"},{"family":"Burgess","given":"Joanne"},{"family":"Olson","given":"Sherry"},{"family":"Berreto","given":"Laura"}],"citation-key":"robichaud_montreen_nodate","container-title":"Laboratoire d'histoire et de patrimoine de Montréal","language":"fr","title":"Montréal en 1881","type":"webpage","URL":"https://schemamontreal.uqam.ca/projets/montreal-en-1881/"},
80
+  {"id":"robichaud_prendre_2019","abstract":"Le contenu de cet ouvrage est étroitement lié aux réalisations du Laboratoire d’histoire et de patrimoine de Montréal.\n\nL’histoire et les études patrimoniales ont pendant longtemps évolué en parallèle. Mais, depuis quelques années, les collaborations et les échanges se sont accrus. C’est ce dont témoigne cet ouvrage dans lequel la relation entre histoire et patrimoine est explorée sous divers angles. On y met en lumière les apports originaux de travaux récents et on y esquisse des pistes de recherche. En outre, l’appropriation et la diffusion des résultats et les enjeux de la mise en valeur reçoivent une attention particulière.","author":[{"family":"Robichaud","given":"Léon"}],"citation-key":"robichaud_prendre_2019","container-title":"Histoire et patrimoine. Pistes de recherche et de mise en valeur","editor":[{"family":"Burgess","given":"Joanne"},{"family":"Linteau","given":"Paul-André"}],"event-place":"Québec","ISBN":"978-2-7627-4329-5","issued":{"date-parts":[["2019"]]},"language":"fr","page":"213-236","publisher":"Presses de l’Université Laval","publisher-place":"Québec","title":"Prendre le tournant spatial en histoire : le Laboratoire d’histoire et de patrimoine de Montréal et le Système de cartographie de l’histoire de Montréal (SCHEMA)","type":"chapter","URL":"https://www.pulaval.com/libre-acces/9782763743295/"},
81
+  {"id":"shaw_lode_2020","abstract":"This document describes an ontology for publishing descriptions of historical events as Linked Data, and for mapping between other event-related vocabularies and ontologies.","accessed":{"date-parts":[["2023",8,28]]},"author":[{"family":"Shaw","given":"Ryan"}],"citation-key":"shaw_lode_2020","issued":{"date-parts":[["2020"]]},"title":"LODE: An ontology for Linking Open Descriptions of Events","type":"document","URL":"https://linkedevents.org/ontology/"},
82
+  {"id":"shbita_building_2020","abstract":"Historical maps provide a rich source of information for researchers in the social and natural sciences. These maps contain detailed documentation of a wide variety of natural and human-made features and their changes over time, such as the changes in the transportation networks and the decline of wetlands. It can be labor-intensive for a scientist to analyze changes across space and time in such maps, even after they have been digitized and converted to a vector format. In this paper, we present an unsupervised approach that converts vector data of geographic features extracted from multiple historical maps into linked spatio-temporal data. The resulting graphs can be easily queried and visualized to understand the changes in specific regions over time. We evaluate our technique on railroad network data extracted from USGS historical topographic maps for several regions over multiple map sheets and demonstrate how the automatically constructed linked geospatial data enables effective querying of the changes over different time periods.","author":[{"family":"Shbita","given":"Basel"},{"family":"Knoblock","given":"Craig A."},{"family":"Duan","given":"Weiwei"},{"family":"Chiang","given":"Yao-Yi"},{"family":"Uhl","given":"Johannes H."},{"family":"Leyk","given":"Stefan"}],"citation-key":"shbita_building_2020","collection-title":"Lecture Notes in Computer Science","container-title":"The semantic web. 17th International Conference, ESWC 2020","DOI":"10.1007/978-3-030-49461-2_24","editor":[{"family":"Harth","given":"Andreas"},{"family":"Kirrane","given":"Sabrina"},{"family":"Ngonga Ngomo","given":"Axel-Cyrille"},{"family":"Paulheim","given":"Heiko"},{"family":"Rula","given":"Anisa"},{"family":"Gentile","given":"Anna Lisa"},{"family":"Haase","given":"Peter"},{"family":"Cochez","given":"Michael"}],"event-place":"Cham","ISBN":"978-3-030-49461-2","issued":{"date-parts":[["2020",6,4]]},"language":"en","page":"409-426","publisher":"Springer International Publishing","publisher-place":"Cham","source":"Springer Link","title":"Building linked spatio-temporal data from vectorized historical maps","type":"paper-conference"},
83
+  {"id":"sweeny_map_2003","abstract":"Montréal l'avenir du passé (MAP) was established in 2000 to create an historical GIS research infrastructure for 19th and 20th century Montreal. The authors digitized six highly detailed historical maps representing all buildings in the city for 1825, 1846, 1880, 1912, 1949 and 2000. The first three and last were geo-referenced and successfully \"peopled\" by linking at the street-scape (1846) or lot level (1880 & 2000) census returns, tax records, city directories and a wide variety of non-routinely generated sources. The project is currently focusing on turn of the century Montreal. A CD entitled \"MAP: le 19e siècle/The 19th Century\" was launched in October 2010 and is available from the web site www.mun.ca/mapm.","author":[{"family":"Sweeny","given":"Robert C.H."},{"family":"Olson","given":"Sherry"}],"citation-key":"sweeny_map_2003","container-title":"Geomatica","issue":"2","issued":{"date-parts":[["2003"]]},"page":"145-154","title":"MAP: Montréal l’avenir du passé, sharing geodatabases yesterday, today and tomorrow","type":"article-journal","volume":"57"},
84
+  {"id":"sweeny_new_2017","abstract":"Editor's note: this post first appeared in the historical GIS series as New Ways to Imagine an Old City. It has been translated by members of Géohistorie Canada: Partenariat canadien en systèmes d’information géographiques historiques.\n\nImaginez si vous pouviez examiner l’ensemble du portfolio imm","accessed":{"date-parts":[["2023",2,27]]},"author":[{"family":"Sweeny","given":"Robert C.H."}],"citation-key":"sweeny_new_2017","container-title":"Nouvelle initiative Canadienne en histoire de l'environnement","issued":{"date-parts":[["2017",4,17]]},"language":"fr","note":"Last Modified: 2017-04-17T02:42:23-04:00","title":"New ways to imagine an old city","type":"webpage","URL":"http://niche-canada.org/2017/01/03/new-ways-to-imagine-an-old-city/"},
85
+  {"id":"tambassi_geographical_2017","abstract":"This article intends to provide an overview on the philosophical and geographical background of geo-ontologies and to propose a geographical classification of these ontologies, in response to their increasing diffusion within the contemporary debate. Accordingly, the first two paragraphs are devoted to offer a short introduction to the ontological turn in philosophy and to the development of the ontology of geography, that is that part of the (philosophical) ontology mainly focused on geographic entities and their boundaries, spatial representation, meretopological relations and location. As a second step, this preliminary analysis is taken to be a helpful device in showing some philosophical tools useful for geo-ontologies and in determining whether and what geographical sub-areas can be identified from non-professional geographers. Consequently, paragraphs three and four investigate the emerging of geo-ontologies from the spatial turn and their general aims. Part of this inquiry is dedicated to show some taxonomies derived from the domain of computer and information science and to underline the absence of a classification suitable for spreading geo-ontologies in the geographical debate. As it is, the fifth paragraph is concerned with a taxonomy for geo-ontologies grounded on some fundamental geographical distinctions. The basic idea is that such a taxonomy might best introduce geo-ontologies to the geographical debate that, in turn, might deeply influence the advancement of these ontologies in terms of conceptualizations and trace gradually the guidelines for a classification, in which the development of geo-ontologies would follow all the different sub-disciplines within the same geography.","accessed":{"date-parts":[["2023",7,20]]},"author":[{"family":"Tambassi","given":"Timothy"}],"citation-key":"tambassi_geographical_2017","container-title":"Axiomathes","container-title-short":"Axiomathes","DOI":"10.1007/s10516-016-9309-z","ISSN":"1572-8390","issue":"4","issued":{"date-parts":[["2017",8,1]]},"language":"en","page":"355-374","source":"Springer Link","title":"A geographical taxonomy for geo-ontologies","type":"article-journal","URL":"https://doi.org/10.1007/s10516-016-9309-z","volume":"27"},
86
+  {"id":"tambassi_philosophy_2021","accessed":{"date-parts":[["2023",4,11]]},"author":[{"family":"Tambassi","given":"Timothy"}],"citation-key":"tambassi_philosophy_2021","collection-title":"SpringerBriefs in Geography","DOI":"10.1007/978-3-030-78145-3","event-place":"Cham","ISBN":"978-3-030-78144-6 978-3-030-78145-3","issued":{"date-parts":[["2021"]]},"language":"en","publisher":"Springer International Publishing","publisher-place":"Cham","source":"DOI.org (Crossref)","title":"The Philosophy of Geo-Ontologies: Applied Ontology of Geography","title-short":"The Philosophy of Geo-Ontologies","type":"book","URL":"https://link.springer.com/10.1007/978-3-030-78145-3"},
87
+  {"id":"teaford_rough_1990","author":[{"family":"Teaford","given":"Jon C."}],"call-number":"HT175 .T43 1990","citation-key":"teaford_rough_1990","collection-title":"Creating the North American landscape","event-place":"Baltimore","ISBN":"978-0-8018-3971-9 978-0-8018-4134-7","issued":{"date-parts":[["1990"]]},"number-of-pages":"383","publisher":"Johns Hopkins University Press","publisher-place":"Baltimore","source":"Library of Congress ISBN","title":"The rough road to renaissance: Urban revitalization in America, 1940-1985","title-short":"The rough road to renaissance","type":"book"},
88
+  {"id":"valentine_defragmenter_2023","author":[{"family":"Valentine","given":"David"}],"citation-key":"valentine_defragmenter_2023","event-place":"Montréal","event-title":"Colloque étudiant du Centre de recherche interuniversitaire sur les humanités numériques","genre":"communication orale","issued":{"date-parts":[["2023",4,3]]},"language":"fr","publisher-place":"Montréal","title":"Défragmenter la mémoire montréalaise : la reconstitution sémantique des liaisons documentaires du Faubourg à m’lasse","type":"speech","URL":"http://colloque-crihn.ecrituresnumeriques.ca/about-fr.html#schedule"},
89
+  {"id":"valentine_projet_2023","abstract":"Cet article expose la démarche et les résultats d’un projet d’implémentation d’un réseau de données ouvertes et liées. Ce projet porte sur des quartiers disparus de Montréal dans les décennies 1950-1960. À partir de données principalement extraites de documents d’archives, le projet QDMTL propose la modélisation sémantique de ce fonds numérisé, accompagnée de la description du patrimoine bâti des quartiers disparus. Sous la forme d’un ensemble de triplets, le jeu de données produit dans le cadre de ces travaux est exposé au moyen des technologies du Web sémantique. Le projet cherche à établir la faisabilité et la pertinence d’une telle démarche dans le cadre de l’étude des quartiers disparus de Montréal et plus largement pour l’histoire de la ville.","accessed":{"date-parts":[["2023",7,13]]},"author":[{"family":"Valentine","given":"David"},{"family":"Forest","given":"Dominic"}],"citation-key":"valentine_projet_2023","container-title":"Humanités numériques","ISSN":"2736-2337","issue":"7","issued":{"date-parts":[["2023",7,1]]},"language":"fr","license":"https://creativecommons.org/licenses/by/4.0/","number":"7","publisher":"Humanistica","source":"journals.openedition.org","title":"Le projet QDMTL : modéliser les quartiers disparus de Montréal avec des données ouvertes et liées","title-short":"Le projet QDMTL","type":"article-journal","URL":"https://journals.openedition.org/revuehn/3336"},
90
+  {"id":"vatant_geonames_2022","abstract":"The Geonames ontologies provides elements of description for geographical features, in particular those defined in the geonames.org data base.","accessed":{"date-parts":[["2023",7,20]]},"author":[{"family":"Vatant","given":"Bernard"}],"citation-key":"vatant_geonames_2022","issued":{"date-parts":[["2022",1,30]]},"title":"The Geonames ontology","type":"software","URL":"https://www.geonames.org/ontology/ontology_v3.3.rdf","version":"3.3"},
91
+  {"id":"wick_geonames_2021","abstract":"The GeoNames Ontology makes it possible to add geospatial semantic information to the Word Wide Web. All over 11 million geonames toponyms now have a unique URL with a corresponding RDF web service. Other services describe the relation between toponyms.","accessed":{"date-parts":[["2023",7,20]]},"author":[{"family":"Wick","given":"Marc"}],"citation-key":"wick_geonames_2021","container-title":"GeoNames","issued":{"date-parts":[["2021"]]},"title":"Geonames ontology","type":"webpage","URL":"http://www.geonames.org/ontology/documentation.html"},
92
+  {"id":"wilkinson_fair_2016","abstract":"There is an urgent need to improve the infrastructure supporting the reuse of scholarly data. A diverse set of stakeholders—representing academia, industry, funding agencies, and scholarly publishers—have come together to design and jointly endorse a concise and measureable set of principles that we refer to as the FAIR Data Principles. The intent is that these may act as a guideline for those wishing to enhance the reusability of their data holdings. Distinct from peer initiatives that focus on the human scholar, the FAIR Principles put specific emphasis on enhancing the ability of machines to automatically find and use the data, in addition to supporting its reuse by individuals. This Comment is the first formal publication of the FAIR Principles, and includes the rationale behind them, and some exemplar implementations in the community.","accessed":{"date-parts":[["2022",1,22]]},"author":[{"family":"Wilkinson","given":"Mark D."},{"family":"Dumontier","given":"Michel"},{"family":"Aalbersberg","given":"IJsbrand Jan"},{"family":"Appleton","given":"Gabrielle"},{"family":"Axton","given":"Myles"},{"family":"Baak","given":"Arie"},{"family":"Blomberg","given":"Niklas"},{"family":"Boiten","given":"Jan-Willem"},{"family":"Silva Santos","given":"Luiz Bonino","non-dropping-particle":"da"},{"family":"Bourne","given":"Philip E."},{"family":"Bouwman","given":"Jildau"},{"family":"Brookes","given":"Anthony J."},{"family":"Clark","given":"Tim"},{"family":"Crosas","given":"Mercè"},{"family":"Dillo","given":"Ingrid"},{"family":"Dumon","given":"Olivier"},{"family":"Edmunds","given":"Scott"},{"family":"Evelo","given":"Chris T."},{"family":"Finkers","given":"Richard"},{"family":"Gonzalez-Beltran","given":"Alejandra"},{"family":"Gray","given":"Alasdair J. G."},{"family":"Groth","given":"Paul"},{"family":"Goble","given":"Carole"},{"family":"Grethe","given":"Jeffrey S."},{"family":"Heringa","given":"Jaap"},{"family":"Hoen","given":"Peter A. C.","dropping-particle":"’t"},{"family":"Hooft","given":"Rob"},{"family":"Kuhn","given":"Tobias"},{"family":"Kok","given":"Ruben"},{"family":"Kok","given":"Joost"},{"family":"Lusher","given":"Scott J."},{"family":"Martone","given":"Maryann E."},{"family":"Mons","given":"Albert"},{"family":"Packer","given":"Abel L."},{"family":"Persson","given":"Bengt"},{"family":"Rocca-Serra","given":"Philippe"},{"family":"Roos","given":"Marco"},{"family":"Schaik","given":"Rene","non-dropping-particle":"van"},{"family":"Sansone","given":"Susanna-Assunta"},{"family":"Schultes","given":"Erik"},{"family":"Sengstag","given":"Thierry"},{"family":"Slater","given":"Ted"},{"family":"Strawn","given":"George"},{"family":"Swertz","given":"Morris A."},{"family":"Thompson","given":"Mark"},{"family":"Lei","given":"Johan","non-dropping-particle":"van der"},{"family":"Mulligen","given":"Erik","non-dropping-particle":"van"},{"family":"Velterop","given":"Jan"},{"family":"Waagmeester","given":"Andra"},{"family":"Wittenburg","given":"Peter"},{"family":"Wolstencroft","given":"Katherine"},{"family":"Zhao","given":"Jun"},{"family":"Mons","given":"Barend"}],"citation-key":"wilkinson_fair_2016","container-title":"Scientific Data","container-title-short":"Sci Data","DOI":"10.1038/sdata.2016.18","ISSN":"2052-4463","issue":"1","issued":{"date-parts":[["2016",3,15]]},"language":"en","license":"2016 The Author(s)","note":"Bandiera_abtest: a\nCg_type: Nature Research Journals\nPrimary_atype: Comments & Opinion\nSubject_term: Publication characteristics;Research data\nSubject_term_id: publication-characteristics;research-data","number":"1","publisher":"Nature Publishing Group","source":"www.nature.com","title":"The FAIR guiding principles for scientific data management and stewardship","type":"article-journal","URL":"https://www.nature.com/articles/sdata201618","volume":"3"}
93
+]
... ...
@@ -0,0 +1,11 @@
1
+# Applied to all documents
2
+author:
3
+  first: David
4
+  last: Valentine
5
+  full: David Valentine
6
+  url: "https://ntnlv.ca"
7
+  email: "d@ntnlv.ca"
8
+bibliography: ./src/bibliography.json
9
+csl: ./templates/default.csl
10
+license: CC-BY David Valentine
11
+favicon: ../favicon.ico
0 12
\ No newline at end of file
... ...
@@ -0,0 +1,110 @@
1
+$-- head.html
2
+$-- This file should go directly inside and existing `head` element
3
+$--------------------------------------------------------------------
4
+$-- charset (utf-8 please)
5
+$-- must be defined early in the document (within first 1024 bytes)
6
+$-- https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset
7
+<meta charset="utf-8" />
8
+
9
+$-- generator
10
+$-- credit to John MacFarlane's wonderful software
11
+$-- and of course GNU make
12
+<!--
13
+  This html file is generated using a template adaptation after pandoc-markdown-css-theme
14
+  https://github.com/jez/pandoc-markdown-css-theme
15
+-->
16
+<!-- pandoc - https://pandoc.org -->
17
+<!-- gnu make - https://www.gnu.org/software/make/ -->
18
+<!-- pandoc-markdown-css-theme - https://github.com/jez/pandoc-markdown-css-theme -->
19
+<meta name="generator" content="pandoc, GNU make, pandoc-markdown-css-theme" />
20
+
21
+$-- viewport
22
+$-- https://developer.mozilla.org/fr/docs/Web/HTML/Viewport_meta_tag
23
+<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
24
+
25
+$--------------------------------------------------------------------
26
+$-- Metadata
27
+$-- For `title`, `author` and `description`, pandoc automatically 
28
+$-- sets the matching variables suffixed with `-meta`.
29
+$-- https://pandoc.org/MANUAL.html#metadata-variables
30
+$--------------------------------------------------------------------
31
+$-- page title
32
+$--------------------------------------------------------------------
33
+<title>${if(title-prefix)}${title-prefix} – ${endif}${pagetitle}</title>
34
+
35
+$-- author
36
+$-- this site is designed to accomodate for a *single* author
37
+$-- and expects an object (`author.first`, `author.last`, ...)
38
+$--------------------------------------------------------------------
39
+${if(author)}
40
+<meta name="author" content="${author.full}" />
41
+${endif}
42
+
43
+$-- description
44
+$--------------------------------------------------------------------
45
+${if(description-meta)}
46
+<meta name="description" content="${description-meta}" />
47
+${endif}
48
+
49
+$-- date
50
+$--------------------------------------------------------------------
51
+${if(date-meta)}
52
+<meta name="dcterms.date" content="${date-meta}" />
53
+${elseif(date)}
54
+<meta name="dcterms.date" content="${date}" />
55
+${endif}
56
+
57
+$-- keywords
58
+$-- (note that keywords listed here have little if no impact on SEO)
59
+$--------------------------------------------------------------------
60
+${if(keywords)}
61
+<meta name="keywords" content="${for(keywords)}${keywords}${sep}, ${endfor}" />
62
+${endif}
63
+
64
+<!-- Styles -->
65
+$-- additional stylesheets may be defined through the `css` prop
66
+$-- in theme.yml
67
+$--------------------------------------------------------------------
68
+<style>
69
+  div.sitenav { display: flex; flex-direction: row; flex-wrap: wrap; }
70
+  span.navlink { flex: 1; }
71
+  span.navlink-right { margin-left: auto; }
72
+  span.navlink-label { display: inline-block; min-width: 4em; }
73
+</style>
74
+
75
+${for(css)}
76
+<link rel="stylesheet" href="${css}" />
77
+${endfor}
78
+
79
+$-- scripts
80
+$-- additional scripts may be defined through the `js` prop
81
+$-- in theme.yml
82
+${if(js)}
83
+<!-- Scripts -->
84
+${for(js)}
85
+<script src="${js}"></script>
86
+${endfor}
87
+${else}
88
+<!-- No JavaScripts -->
89
+${endif}
90
+
91
+$-- favicon
92
+$-- If the favicon is set, reference it; otherwise, resort to a small
93
+$-- transparent Gif, which avoids a useless request to the server
94
+$-- (and therefore avoids such error in the console).
95
+$--------------------------------------------------------------------
96
+${if(favicon)}
97
+<link rel="icon" href="${favicon}">
98
+${else}
99
+<link rel="icon" href="data:;base64,iVBORw0KGgo=">
100
+${endif}
101
+
102
+$-- math
103
+$--------------------------------------------------------------------
104
+${if(math)}
105
+${if(mathjax)}
106
+$-- beware, this script is loaded externally (through a CDN)
107
+<script src="https://polyfill.io/v3/polyfill.min.js?features=es6"></script>
108
+${endif}
109
+${math}
110
+${endif}
0 111
\ No newline at end of file
... ...
@@ -0,0 +1,29 @@
1
+<nav id="sitenav">
2
+  <div class="sitenav">
3
+  $--------------------------------------------------------------------
4
+  $-- Travail sur un niveau seulement
5
+  $-- <span class="navlink">
6
+  $-- $if(up.url)$
7
+  $--<span class="navlink-label">Niveau supérieur</span> <a href="$up.url$" accesskey="u" rel="up">$up.title$</a>
8
+  $--$endif$
9
+  $--</span>
10
+  $--------------------------------------------------------------------
11
+  <span class="navlink">
12
+  $if(top)$
13
+  <a href="${top.url}#main-toc" accesskey="t" rel="top">↑ Table des matières</a>
14
+  $endif$
15
+  </span>
16
+  </div>
17
+  <div class="sitenav">
18
+  <span class="navlink">
19
+  $if(previous.url)$
20
+  <a href="$previous.url$" accesskey="p" rel="previous">← $previous.title$</a>
21
+  $endif$
22
+  </span>
23
+  <span class="navlink-right">
24
+  $if(next.url)$
25
+  <a href="$next.url$" accesskey="n" rel="next">$next.title$ →</a>
26
+  $endif$
27
+  </span>
28
+  </div>
29
+  </nav>  
0 30
\ No newline at end of file
... ...
@@ -0,0 +1,4 @@
1
+<!--
2
+  toc-nav component
3
+  Generated by Pandoc and handled by ./scripts/components/nav-toc.js
4
+-->
0 5
\ No newline at end of file
... ...
@@ -0,0 +1,930 @@
1
+<?xml version="1.0" encoding="utf-8"?>
2
+<style xmlns="http://purl.org/net/xbiblio/csl" class="in-text" version="1.0" demote-non-dropping-particle="never" default-locale="fr-CA">
3
+  <info>
4
+    <title>Université du Québec à Montréal - APA (Français - Canada)</title>
5
+    <title-short>UQAM</title-short>
6
+    <id>http://www.zotero.org/styles/universite-du-quebec-a-montreal</id>
7
+    <link href="http://www.zotero.org/styles/universite-du-quebec-a-montreal" rel="self"/>
8
+    <link href="http://www.zotero.org/styles/apa" rel="template"/>
9
+    <link href="http://guides.bibliotheques.uqam.ca/themes/105-Logiciels-de-gestion-bibliographique?tab=563" rel="documentation"/>
10
+    <link href="http://www.guidemt.uqam.ca/citer/style-uqam" rel="documentation"/>
11
+    <author>
12
+      <name>Jean-Jacques Rondeau</name>
13
+      <email>rondeau.jean-jacques@uqam.ca</email>
14
+    </author>
15
+    <category citation-format="author-date"/>
16
+    <category field="psychology"/>
17
+    <category field="generic-base"/>
18
+    <summary>Le style UQAM APA est une adaptation française canadienne de la 7e édition de la norme APA conforme au Guide de présentation des mémoires et des thèses de l'Université du Québec à Montréal. Il remplace l'ancienne version qui portait le nom de style UQAM qui était basée sur la 6e édition du style APA.</summary>
19
+    <updated>2022-06-13T13:01:15+00:00</updated>
20
+    <rights license="http://creativecommons.org/licenses/by-sa/3.0/">This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 License</rights>
21
+  </info>
22
+  <locale xml:lang="fr">
23
+    <terms>
24
+      <term name="editor" form="short">dir.</term>
25
+      <term name="editortranslator" form="short">éd. &amp; trad.</term>
26
+      <term name="translator" form="short">trad.</term>
27
+      <term name="no date" form="short">s. d.</term>
28
+      <term name="in">dans</term>
29
+      <term name="retrieved">récupéré</term>
30
+      <term name="from">de</term>
31
+      <term name="presented at">communication présentée au</term>
32
+      <term name="page" form="short">p.</term>
33
+      <term name="chapter-number" form="short">chap.</term>
34
+      <term name="section">section</term>
35
+      <term name="number-of-volumes" form="short">vol.</term>
36
+      <term name="number">numéro</term>
37
+      <term name="scale">échelle</term>
38
+      <term name="circa" form="short">v. </term>
39
+      <term name="interview" form="verb">interviewé par</term>
40
+      <term name="author" form="verb">enregistré par</term>
41
+      <term name="number" form="short">n&amp;#7506;</term>
42
+    </terms>
43
+  </locale>
44
+  <macro name="container-contributors">
45
+    <choose>
46
+      <if type="chapter paper-conference entry-encyclopedia entry-dictionary map" match="any">
47
+        <names variable="editor container-author" delimiter=", " suffix=", ">
48
+          <name and="text" delimiter-precedes-last="never" initialize-with=". "/>
49
+          <label form="short" prefix=" (" suffix=")"/>
50
+        </names>
51
+      </if>
52
+      <else-if type="interview broadcast" match="any">
53
+        <choose>
54
+          <if match="any" variable="container-title">
55
+            <text variable="publisher" suffix=", "/>
56
+          </if>
57
+        </choose>
58
+      </else-if>
59
+    </choose>
60
+  </macro>
61
+  <macro name="secondary-contributors">
62
+    <choose>
63
+      <if type="article-journal book chapter paper-conference entry-encyclopedia entry-dictionary" match="none">
64
+        <names variable="editor" delimiter=", " prefix=" (" suffix=")">
65
+          <name and="symbol" initialize-with=". " delimiter=", "/>
66
+          <label form="short" prefix=", "/>
67
+        </names>
68
+      </if>
69
+    </choose>
70
+  </macro>
71
+  <macro name="author">
72
+    <choose>
73
+      <if match="any" variable="composer">
74
+        <names variable="composer">
75
+          <name and="text" delimiter-precedes-last="never" et-al-use-last="true" initialize-with=". " name-as-sort-order="all"/>
76
+        </names>
77
+      </if>
78
+      <else>
79
+        <names variable="author">
80
+          <name and="text" delimiter-precedes-last="never" et-al-use-last="true" initialize-with=". " name-as-sort-order="all"/>
81
+          <label form="short" prefix=" (" suffix=")"/>
82
+          <substitute>
83
+            <choose>
84
+              <if type="entry-dictionary entry-encyclopedia webpage manuscript legislation legal_case bill treaty article map article-magazine article-newspaper" match="any">
85
+                <text macro="title"/>
86
+              </if>
87
+              <else-if type="book" match="any">
88
+                <names variable="editor"/>
89
+                <text macro="title" font-style="italic"/>
90
+              </else-if>
91
+              <else>
92
+                <names variable="editor"/>
93
+                <names variable="translator"/>
94
+              </else>
95
+            </choose>
96
+            <choose>
97
+              <if type="report">
98
+                <text variable="publisher"/>
99
+                <text variable="title" font-style="italic" suffix="."/>
100
+              </if>
101
+            </choose>
102
+          </substitute>
103
+        </names>
104
+      </else>
105
+    </choose>
106
+  </macro>
107
+  <macro name="author-short">
108
+    <choose>
109
+      <if match="any" variable="composer">
110
+        <names variable="composer">
111
+          <name form="short" and="text" name-as-sort-order="all"/>
112
+        </names>
113
+      </if>
114
+      <else>
115
+        <names variable="author">
116
+          <name form="short" and="text" name-as-sort-order="all"/>
117
+          <et-al font-style="italic"/>
118
+          <substitute>
119
+            <choose>
120
+              <if variable="container-title">
121
+                <choose>
122
+                  <if type="bill legal_case legislation treaty article-journal" match="none">
123
+                    <text variable="title" quotes="true"/>
124
+                  </if>
125
+                </choose>
126
+              </if>
127
+            </choose>
128
+            <names variable="editor"/>
129
+            <names variable="translator"/>
130
+            <choose>
131
+              <if type="report">
132
+                <text variable="publisher"/>
133
+                <text variable="title" font-style="italic"/>
134
+              </if>
135
+              <else>
136
+                <choose>
137
+                  <if match="any" variable="title-short">
138
+                    <text variable="title-short" quotes="false"/>
139
+                  </if>
140
+                  <else>
141
+                    <text variable="title" font-style="italic"/>
142
+                  </else>
143
+                </choose>
144
+              </else>
145
+            </choose>
146
+          </substitute>
147
+        </names>
148
+      </else>
149
+    </choose>
150
+  </macro>
151
+  <macro name="access">
152
+    <choose>
153
+      <if type="thesis dataset" match="any">
154
+        <choose>
155
+          <if variable="DOI">
156
+            <text variable="DOI" prefix="https://doi.org/"/>
157
+          </if>
158
+          <else-if variable="archive" match="any">
159
+            <group delimiter=". ">
160
+              <text variable="archive" suffix="."/>
161
+              <text variable="URL"/>
162
+            </group>
163
+          </else-if>
164
+          <else>
165
+            <choose>
166
+              <if type="dataset" match="all" variable="accessed">
167
+                <group delimiter=" ">
168
+                  <text term="retrieved" text-case="capitalize-first"/>
169
+                  <date form="text" variable="accessed" prefix="le "/>
170
+                  <text term="from"/>
171
+                  <text variable="URL"/>
172
+                </group>
173
+              </if>
174
+              <else>
175
+                <text variable="URL"/>
176
+              </else>
177
+            </choose>
178
+          </else>
179
+        </choose>
180
+      </if>
181
+      <else>
182
+        <choose>
183
+          <if variable="DOI">
184
+            <text variable="DOI" prefix="https://doi.org/"/>
185
+          </if>
186
+          <else>
187
+            <choose>
188
+              <if type="entry-encyclopedia entry-dictionary map article" match="any">
189
+                <choose>
190
+                  <if match="any" variable="accessed">
191
+                    <group delimiter=" ">
192
+                      <text term="retrieved" text-case="capitalize-first"/>
193
+                      <date form="text" variable="accessed" prefix="le "/>
194
+                      <text term="from"/>
195
+                      <text variable="URL"/>
196
+                    </group>
197
+                  </if>
198
+                  <else>
199
+                    <text variable="URL"/>
200
+                  </else>
201
+                </choose>
202
+              </if>
203
+              <else>
204
+                <text variable="URL"/>
205
+              </else>
206
+            </choose>
207
+          </else>
208
+        </choose>
209
+      </else>
210
+    </choose>
211
+  </macro>
212
+  <macro name="title">
213
+    <choose>
214
+      <if type="legislation bill" match="any">
215
+        <choose>
216
+          <if match="any" variable="issued">
217
+            <group delimiter=". ">
218
+              <text variable="title" font-style="italic"/>
219
+              <text variable="container-title"/>
220
+            </group>
221
+          </if>
222
+          <else-if match="none" variable="number">
223
+            <group delimiter=". ">
224
+              <text variable="title" font-style="italic"/>
225
+              <text variable="container-title"/>
226
+            </group>
227
+          </else-if>
228
+          <else>
229
+            <group delimiter=". " suffix=", ">
230
+              <text variable="title" font-style="italic"/>
231
+              <text variable="container-title"/>
232
+            </group>
233
+          </else>
234
+        </choose>
235
+      </if>
236
+      <else-if type="interview" match="any">
237
+        <group delimiter=" " suffix=". ">
238
+          <text term="interview" form="verb" text-case="capitalize-first"/>
239
+          <names variable="interviewer">
240
+            <name and="text" initialize-with="."/>
241
+          </names>
242
+        </group>
243
+        <text variable="title"/>
244
+      </else-if>
245
+      <else-if type="legal_case" match="all" variable="references">
246
+        <text variable="title" font-style="italic" suffix=","/>
247
+      </else-if>
248
+      <else-if type="thesis report book graphic manuscript speech dataset legal_case treaty article webpage" match="any">
249
+        <text variable="title" font-style="italic"/>
250
+      </else-if>
251
+      <else-if type="motion_picture broadcast figure map article-journal entry-encyclopedia song musical_score" match="any">
252
+        <choose>
253
+          <if match="any" variable="container-title">
254
+            <text variable="title"/>
255
+          </if>
256
+          <else>
257
+            <text variable="title" font-style="italic"/>
258
+          </else>
259
+        </choose>
260
+      </else-if>
261
+      <else-if type="patent" match="any">
262
+        <text variable="title" font-style="italic"/>
263
+      </else-if>
264
+      <else>
265
+        <text variable="title"/>
266
+      </else>
267
+    </choose>
268
+  </macro>
269
+  <macro name="publisher">
270
+    <choose>
271
+      <if type="speech" match="any">
272
+        <text variable="publisher-place"/>
273
+      </if>
274
+      <else-if type="post thesis" match="none">
275
+        <group delimiter=", ">
276
+          <choose>
277
+            <if type="book chapter report" match="any">
278
+              <text variable="publisher"/>
279
+            </if>
280
+            <else-if type="patent">
281
+              <group delimiter=", ">
282
+                <text variable="authority"/>
283
+                <text variable="publisher"/>
284
+              </group>
285
+            </else-if>
286
+            <else-if type="broadcast interview" match="all" variable="container-title"/>
287
+            <else-if type="manuscript" match="any">
288
+              <group delimiter=" ">
289
+                <text variable="archive"/>
290
+                <text variable="archive_location" prefix="(" suffix=")"/>
291
+              </group>
292
+              <text variable="publisher-place"/>
293
+            </else-if>
294
+            <else-if type="article-journal article-magazine article-newspaper post-weblog" match="none">
295
+              <text variable="publisher"/>
296
+            </else-if>
297
+          </choose>
298
+        </group>
299
+      </else-if>
300
+    </choose>
301
+  </macro>
302
+  <macro name="event">
303
+    <choose>
304
+      <if variable="container-title" match="none">
305
+        <choose>
306
+          <if variable="event-title">
307
+            <text variable="event-title"/>
308
+          </if>
309
+          <else-if type="speech" match="any">
310
+            <text variable="publisher"/>
311
+          </else-if>
312
+        </choose>
313
+      </if>
314
+    </choose>
315
+  </macro>
316
+  <macro name="extra">
317
+    <choose>
318
+      <if type="book thesis" match="any">
319
+        <choose>
320
+          <if match="any" is-numeric="number-of-volumes">
321
+            <group delimiter=" ">
322
+              <number variable="number-of-volumes"/>
323
+              <label variable="number-of-volumes" form="short"/>
324
+            </group>
325
+          </if>
326
+          <else>
327
+            <text variable="number-of-volumes" prefix="[" suffix="]"/>
328
+          </else>
329
+        </choose>
330
+      </if>
331
+      <else-if type="legal_case" match="all" variable="references">
332
+        <group delimiter=", " prefix="(" suffix=")">
333
+          <text variable="authority"/>
334
+          <date date-parts="year" form="text" variable="issued">
335
+            <date-part name="year"/>
336
+          </date>
337
+          <date delimiter=" " variable="issued">
338
+            <date-part name="day"/>
339
+            <date-part name="month"/>
340
+          </date>
341
+        </group>
342
+      </else-if>
343
+      <else-if type="article-journal" match="any">
344
+        <choose>
345
+          <if match="none" variable="container-title">
346
+            <text variable="genre"/>
347
+          </if>
348
+        </choose>
349
+      </else-if>
350
+    </choose>
351
+  </macro>
352
+  <macro name="issued">
353
+    <choose>
354
+      <if match="any" variable="original-date">
355
+        <choose>
356
+          <if type="musical_score book song chapter" match="any">
357
+            <group prefix="(" suffix=")">
358
+              <date date-parts="year" form="text" variable="issued"/>
359
+              <text variable="year-suffix"/>
360
+            </group>
361
+          </if>
362
+          <else>
363
+            <group prefix="(" suffix=")">
364
+              <date delimiter="" variable="original-date">
365
+                <date-part name="year"/>
366
+              </date>
367
+              <text variable="year-suffix"/>
368
+              <date delimiter=" " variable="original-date" prefix=", ">
369
+                <date-part name="day" form="ordinal"/>
370
+                <date-part name="month"/>
371
+              </date>
372
+            </group>
373
+          </else>
374
+        </choose>
375
+      </if>
376
+      <else-if match="any" is-uncertain-date="issued">
377
+        <choose>
378
+          <if type="map" match="any">
379
+            <date form="text" variable="issued" prefix="(" suffix="?)"/>
380
+          </if>
381
+          <else>
382
+            <group delimiter=" " prefix="(" suffix=")">
383
+              <text term="circa" form="short"/>
384
+              <date variable="issued">
385
+                <date-part name="year"/>
386
+              </date>
387
+            </group>
388
+          </else>
389
+        </choose>
390
+      </else-if>
391
+      <else-if match="any" variable="status">
392
+        <group delimiter="-" prefix="(" suffix=")">
393
+          <text variable="status"/>
394
+          <text variable="year-suffix"/>
395
+        </group>
396
+      </else-if>
397
+      <else-if variable="issued">
398
+        <choose>
399
+          <if type="legal_case" match="all" variable="references"/>
400
+          <else-if type="bill legal_case" match="any">
401
+            <group prefix="(" suffix=").">
402
+              <date date-parts="year" form="text" variable="issued">
403
+                <date-part name="year"/>
404
+              </date>
405
+              <date delimiter=" " variable="issued" prefix=", ">
406
+                <date-part name="day"/>
407
+                <date-part name="month"/>
408
+              </date>
409
+            </group>
410
+          </else-if>
411
+          <else-if type="legislation" match="any"/>
412
+          <else-if type="dataset" match="any">
413
+            <group prefix="(" suffix=")">
414
+              <date delimiter="" variable="issued">
415
+                <date-part name="year"/>
416
+              </date>
417
+              <text variable="year-suffix" prefix="-"/>
418
+              <date delimiter="" variable="issued" prefix=", ">
419
+                <date-part name="day"/>
420
+                <date-part name="month" prefix=" "/>
421
+              </date>
422
+            </group>
423
+          </else-if>
424
+          <else>
425
+            <group prefix="(" suffix=").">
426
+              <date variable="issued">
427
+                <date-part name="year"/>
428
+              </date>
429
+              <text variable="year-suffix"/>
430
+              <choose>
431
+                <if type="article-journal bill book chapter graphic legal_case legislation paper-conference thesis patent" match="none">
432
+                  <group prefix=", ">
433
+                    <date variable="issued">
434
+                      <date-part name="day" form="ordinal"/>
435
+                      <date-part prefix=" " name="month"/>
436
+                    </date>
437
+                    <choose>
438
+                      <if type="entry-encyclopedia" match="any">
439
+                        <text variable="issue" prefix=", "/>
440
+                      </if>
441
+                    </choose>
442
+                  </group>
443
+                </if>
444
+              </choose>
445
+            </group>
446
+          </else>
447
+        </choose>
448
+      </else-if>
449
+      <else-if type="manuscript" match="all" variable="issue">
450
+        <text variable="issue" prefix="[" suffix="]."/>
451
+      </else-if>
452
+      <else>
453
+        <group prefix=" (" suffix=")">
454
+          <choose>
455
+            <if type="legislation" match="any"/>
456
+            <else-if type="graphic" match="none">
457
+              <text term="no date" form="short"/>
458
+              <text variable="year-suffix" prefix="-"/>
459
+            </else-if>
460
+          </choose>
461
+        </group>
462
+      </else>
463
+    </choose>
464
+  </macro>
465
+  <macro name="issued-sort">
466
+    <choose>
467
+      <if type="article-journal bill book chapter graphic legal_case legislation motion_picture paper-conference report song" match="none">
468
+        <date variable="issued">
469
+          <date-part name="year"/>
470
+          <date-part name="month"/>
471
+          <date-part name="day"/>
472
+        </date>
473
+      </if>
474
+      <else>
475
+        <date variable="issued">
476
+          <date-part name="year"/>
477
+        </date>
478
+      </else>
479
+    </choose>
480
+  </macro>
481
+  <macro name="issued-year">
482
+    <choose>
483
+      <if match="any" is-uncertain-date="issued">
484
+        <choose>
485
+          <if type="map" match="any">
486
+            <group>
487
+              <date form="text" variable="issued" suffix="?"/>
488
+            </group>
489
+          </if>
490
+          <else>
491
+            <group delimiter=" ">
492
+              <text term="circa" form="short"/>
493
+              <date variable="issued">
494
+                <date-part name="year"/>
495
+              </date>
496
+            </group>
497
+          </else>
498
+        </choose>
499
+        <text variable="year-suffix"/>
500
+      </if>
501
+      <else-if match="any" variable="status">
502
+        <group delimiter="-">
503
+          <text variable="status"/>
504
+          <text variable="year-suffix"/>
505
+        </group>
506
+      </else-if>
507
+      <else-if variable="issued">
508
+        <choose>
509
+          <if type="legislation" match="any"/>
510
+          <else>
511
+            <group delimiter="/">
512
+              <date variable="original-date" form="text"/>
513
+              <group>
514
+                <date variable="issued">
515
+                  <date-part name="year"/>
516
+                </date>
517
+                <text variable="year-suffix"/>
518
+              </group>
519
+            </group>
520
+          </else>
521
+        </choose>
522
+      </else-if>
523
+      <else>
524
+        <choose>
525
+          <if type="legislation" match="any">
526
+            <group delimiter=" ">
527
+              <text variable="container-title"/>
528
+              <text variable="section" prefix="(" suffix=")"/>
529
+            </group>
530
+          </if>
531
+          <else>
532
+            <group delimiter="-">
533
+              <text term="no date" form="short"/>
534
+              <text variable="year-suffix"/>
535
+            </group>
536
+          </else>
537
+        </choose>
538
+      </else>
539
+    </choose>
540
+  </macro>
541
+  <macro name="edition">
542
+    <choose>
543
+      <if is-numeric="edition">
544
+        <group delimiter=" ">
545
+          <number variable="edition" form="ordinal"/>
546
+          <text term="edition" form="short"/>
547
+        </group>
548
+      </if>
549
+      <else>
550
+        <text variable="edition"/>
551
+      </else>
552
+    </choose>
553
+  </macro>
554
+  <macro name="translation-illustration">
555
+    <choose>
556
+      <if variable="translator illustrator" match="any">
557
+        <group delimiter=", ">
558
+          <names variable="translator" delimiter=", " prefix=" ">
559
+            <name and="text" delimiter-precedes-last="never" initialize-with=". "/>
560
+            <label form="short" prefix=", "/>
561
+          </names>
562
+          <names variable="illustrator">
563
+            <name and="text" delimiter-precedes-last="never" initialize-with="."/>
564
+            <label form="short" prefix=", "/>
565
+          </names>
566
+        </group>
567
+      </if>
568
+    </choose>
569
+  </macro>
570
+  <macro name="locators">
571
+    <choose>
572
+      <if type="article-journal article-magazine review-book interview article" match="any">
573
+        <group prefix=", " delimiter=", ">
574
+          <group>
575
+            <text variable="volume" font-style="italic"/>
576
+            <text variable="issue" prefix="(" suffix=")"/>
577
+          </group>
578
+          <text variable="page"/>
579
+          <text variable="archive_location"/>
580
+        </group>
581
+      </if>
582
+      <else-if type="article-newspaper">
583
+        <text variable="publisher-place" prefix=" (" suffix=")"/>
584
+        <group delimiter=", " prefix=", ">
585
+          <text variable="section" prefix="section "/>
586
+          <text variable="page"/>
587
+        </group>
588
+      </else-if>
589
+      <else-if type="book paper-conference entry-encyclopedia chapter entry-dictionary musical_score map figure" match="any">
590
+        <group prefix=" (" suffix=")" delimiter=", ">
591
+          <group delimiter=", ">
592
+            <text macro="edition"/>
593
+            <text macro="translation-illustration"/>
594
+          </group>
595
+          <group delimiter=" ">
596
+            <label variable="volume" form="short"/>
597
+            <number variable="volume" form="numeric"/>
598
+          </group>
599
+          <group delimiter=" ">
600
+            <label variable="chapter-number" form="short"/>
601
+            <number variable="chapter-number"/>
602
+          </group>
603
+          <group delimiter=" ">
604
+            <text term="version"/>
605
+            <text variable="version"/>
606
+          </group>
607
+          <group delimiter=" ">
608
+            <label variable="page" form="short"/>
609
+            <text variable="page"/>
610
+          </group>
611
+        </group>
612
+        <choose>
613
+          <if type="book" match="any">
614
+            <text variable="number" prefix=" (" suffix=")"/>
615
+            <group prefix=" [" suffix="]">
616
+              <text variable="genre"/>
617
+              <text variable="medium"/>
618
+            </group>
619
+          </if>
620
+        </choose>
621
+      </else-if>
622
+      <else-if type="legal_case" match="any">
623
+        <group delimiter=" " prefix=" ">
624
+          <text variable="number"/>
625
+          <choose>
626
+            <if match="none" variable="references page">
627
+              <text variable="authority" prefix="(" suffix=")"/>
628
+            </if>
629
+            <else-if match="none" variable="references">
630
+              <text variable="authority"/>
631
+            </else-if>
632
+          </choose>
633
+          <text variable="page"/>
634
+        </group>
635
+        <text variable="source" prefix=". "/>
636
+      </else-if>
637
+      <else-if type="treaty" match="any">
638
+        <group delimiter=", ">
639
+          <group delimiter=" " prefix=", ">
640
+            <label variable="volume" form="short"/>
641
+            <text variable="volume"/>
642
+          </group>
643
+          <group delimiter=" ">
644
+            <label variable="page" form="short"/>
645
+            <text variable="page"/>
646
+          </group>
647
+          <group delimiter=" " prefix=" ">
648
+            <text term="issue" form="short"/>
649
+            <text variable="issue"/>
650
+          </group>
651
+        </group>
652
+      </else-if>
653
+      <else-if type="song" match="any">
654
+        <text variable="number" prefix=" (épisode " suffix=")"/>
655
+      </else-if>
656
+    </choose>
657
+  </macro>
658
+  <macro name="citation-locator">
659
+    <group>
660
+      <choose>
661
+        <if locator="chapter">
662
+          <label variable="locator" form="long" text-case="capitalize-first"/>
663
+        </if>
664
+        <else>
665
+          <label variable="locator" form="short"/>
666
+        </else>
667
+      </choose>
668
+      <text variable="locator" prefix=" "/>
669
+    </group>
670
+  </macro>
671
+  <macro name="container">
672
+    <group>
673
+      <choose>
674
+        <if type="chapter paper-conference entry-encyclopedia entry-dictionary song musical_score figure broadcast interview" match="any">
675
+          <choose>
676
+            <if match="any" variable="container-title">
677
+              <text term="in" text-case="capitalize-first" suffix=" "/>
678
+            </if>
679
+          </choose>
680
+        </if>
681
+        <else-if type="map" match="all" variable="container-author">
682
+          <text term="in" text-case="capitalize-first" suffix=" "/>
683
+        </else-if>
684
+      </choose>
685
+      <text macro="container-contributors"/>
686
+      <text macro="secondary-contributors"/>
687
+      <text macro="container-title"/>
688
+    </group>
689
+  </macro>
690
+  <macro name="container-title">
691
+    <choose>
692
+      <if type="bill legislation legal_case treaty report webpage" match="none">
693
+        <text variable="container-title" font-style="italic"/>
694
+      </if>
695
+      <else-if type="legal_case treaty report" match="any">
696
+        <choose>
697
+          <if match="none" variable="references">
698
+            <text variable="container-title"/>
699
+          </if>
700
+        </choose>
701
+      </else-if>
702
+      <else>
703
+        <group delimiter=" ">
704
+          <choose>
705
+            <if variable="container-title">
706
+              <choose>
707
+                <if type="legislation" match="none">
708
+                  <text variable="volume"/>
709
+                  <text variable="container-title"/>
710
+                  <group delimiter=" ">
711
+                    <text term="section" form="symbol"/>
712
+                    <text variable="section"/>
713
+                  </group>
714
+                </if>
715
+              </choose>
716
+            </if>
717
+          </choose>
718
+        </group>
719
+      </else>
720
+    </choose>
721
+  </macro>
722
+  <macro name="original-date">
723
+    <choose>
724
+      <if type="song musical_score book chapter" match="any">
725
+        <group prefix="(" suffix=")">
726
+          <text value="Publication originale en "/>
727
+          <date variable="original-date">
728
+            <date-part name="year"/>
729
+          </date>
730
+        </group>
731
+      </if>
732
+      <else-if type="treaty" match="any">
733
+        <choose>
734
+          <if match="any" variable="original-date">
735
+            <group delimiter=" " suffix=".">
736
+              <text value="Entrée en vigueur le"/>
737
+              <date form="text" variable="issued">
738
+                <date-part name="day" form="ordinal"/>
739
+              </date>
740
+            </group>
741
+          </if>
742
+        </choose>
743
+      </else-if>
744
+    </choose>
745
+  </macro>
746
+  <macro name="title-extra">
747
+    <choose>
748
+      <if type="thesis" match="any">
749
+        <text variable="archive_location" prefix="(Publication n&amp;#7506;  " suffix=") "/>
750
+        <group delimiter=", " prefix="[" suffix="]">
751
+          <group delimiter=" ">
752
+            <text term="version"/>
753
+            <text variable="version"/>
754
+          </group>
755
+          <text variable="genre"/>
756
+          <text variable="publisher"/>
757
+        </group>
758
+      </if>
759
+      <else-if type="article-journal" match="any">
760
+        <choose>
761
+          <if match="any" variable="container-title">
762
+            <text variable="genre" prefix="[" suffix="]"/>
763
+          </if>
764
+        </choose>
765
+        <group delimiter=" " prefix="(" suffix=")">
766
+          <text term="version"/>
767
+          <text variable="version"/>
768
+        </group>
769
+      </else-if>
770
+      <else-if type="report" match="any">
771
+        <group delimiter=" ">
772
+          <text variable="number" prefix="(" suffix=")"/>
773
+          <group delimiter=" " prefix="[" suffix="]">
774
+            <text variable="genre"/>
775
+            <text variable="medium"/>
776
+          </group>
777
+          <group delimiter=" " prefix=". ">
778
+            <text term="number" text-case="capitalize-first"/>
779
+            <text variable="archive_location"/>
780
+          </group>
781
+        </group>
782
+      </else-if>
783
+      <else-if type="webpage dataset" match="any">
784
+        <group delimiter=" " prefix="(" suffix=")">
785
+          <text term="version"/>
786
+          <text variable="version"/>
787
+        </group>
788
+        <group delimiter=" " prefix=" ">
789
+          <text variable="number" prefix="(" suffix=")"/>
790
+          <text variable="genre" prefix="[" suffix="]"/>
791
+        </group>
792
+      </else-if>
793
+      <else-if type="patent" match="any">
794
+        <group delimiter=" " prefix="(" suffix=")">
795
+          <text variable="genre"/>
796
+          <text variable="number" font-style="normal"/>
797
+        </group>
798
+      </else-if>
799
+      <else-if type="song musical_score" match="any">
800
+        <choose>
801
+          <if match="any" variable="composer">
802
+            <group delimiter=";  " prefix=" [" suffix="]">
803
+              <group delimiter=" ">
804
+                <text term="author" form="verb" text-case="capitalize-first"/>
805
+                <names variable="author">
806
+                  <name and="text" delimiter-precedes-last="never"/>
807
+                </names>
808
+              </group>
809
+              <text variable="medium"/>
810
+              <text variable="genre"/>
811
+            </group>
812
+          </if>
813
+          <else>
814
+            <text variable="medium" prefix="[" suffix="]"/>
815
+            <text variable="genre" prefix="[" suffix="]"/>
816
+          </else>
817
+        </choose>
818
+      </else-if>
819
+      <else-if type="legislation bill" match="any">
820
+        <group delimiter=" ">
821
+          <text variable="number" prefix="c. "/>
822
+          <text variable="section" prefix="(" suffix=")"/>
823
+          <text variable="authority"/>
824
+        </group>
825
+      </else-if>
826
+      <else-if type="review-book" match="any">
827
+        <group delimiter=" " prefix="[" suffix="]">
828
+          <text variable="reviewed-title" font-style="italic" prefix="Compte rendu du livre " suffix=","/>
829
+          <text term="by"/>
830
+          <names variable="reviewed-author">
831
+            <name and="text" delimiter-precedes-last="never" initialize-with="."/>
832
+          </names>
833
+        </group>
834
+      </else-if>
835
+      <else-if type="broadcast" match="any">
836
+        <group delimiter=" ">
837
+          <group delimiter=" " prefix="(" suffix=")">
838
+            <text term="number" form="short"/>
839
+            <text variable="number"/>
840
+          </group>
841
+          <group prefix="[" suffix="]">
842
+            <text variable="medium"/>
843
+            <text variable="genre"/>
844
+          </group>
845
+        </group>
846
+      </else-if>
847
+      <else>
848
+        <choose>
849
+          <if type="musical_score book article" match="none">
850
+            <group delimiter=". ">
851
+              <choose>
852
+                <if type="manuscript" match="none">
853
+                  <text variable="archive" prefix=". "/>
854
+                </if>
855
+              </choose>
856
+              <group delimiter=" " prefix="[" suffix="]">
857
+                <text variable="medium"/>
858
+                <text variable="genre"/>
859
+              </group>
860
+              <group delimiter=" : ">
861
+                <text term="scale" text-case="capitalize-first"/>
862
+                <text variable="scale"/>
863
+              </group>
864
+              <number variable="number-of-pages"/>
865
+            </group>
866
+          </if>
867
+        </choose>
868
+      </else>
869
+    </choose>
870
+  </macro>
871
+  <macro name="container-title-extra">
872
+    <choose>
873
+      <if type="map" match="all">
874
+        <text variable="collection-title" prefix=". "/>
875
+        <text variable="number" prefix=", "/>
876
+      </if>
877
+      <else-if type="article" match="any">
878
+        <text variable="number" prefix=" (" suffix=")"/>
879
+        <choose>
880
+          <if match="none" variable="author editor">
881
+            <text variable="genre" prefix=". [" suffix="]"/>
882
+          </if>
883
+          <else>
884
+            <text variable="genre" prefix=" [" suffix="]"/>
885
+          </else>
886
+        </choose>
887
+      </else-if>
888
+    </choose>
889
+  </macro>
890
+  <citation et-al-min="3" et-al-use-first="1" et-al-subsequent-min="3" et-al-subsequent-use-first="1" disambiguate-add-year-suffix="true" collapse="year">
891
+    <sort>
892
+      <key macro="author-short"/>
893
+      <key macro="issued-sort"/>
894
+    </sort>
895
+    <layout prefix="(" suffix=")" delimiter="&#160;; ">
896
+      <group delimiter=", ">
897
+        <text macro="author-short"/>
898
+        <text macro="issued-year"/>
899
+        <text macro="citation-locator"/>
900
+      </group>
901
+    </layout>
902
+  </citation>
903
+  <bibliography delimiter-precedes-last="never" et-al-min="21" et-al-use-first="19" et-al-use-last="true" hanging-indent="true">
904
+    <sort>
905
+      <key macro="author"/>
906
+      <key macro="issued-sort" sort="ascending"/>
907
+      <key macro="title"/>
908
+    </sort>
909
+    <layout>
910
+      <group suffix=".">
911
+        <group delimiter=". ">
912
+          <text macro="author"/>
913
+          <text macro="issued"/>
914
+          <text macro="title" prefix=" "/>
915
+        </group>
916
+        <text macro="title-extra" prefix=" "/>
917
+        <text macro="container" prefix=". "/>
918
+        <text macro="container-title-extra"/>
919
+        <text macro="locators"/>
920
+        <group delimiter=", " prefix=". ">
921
+          <text macro="event"/>
922
+          <text macro="publisher"/>
923
+        </group>
924
+      </group>
925
+      <text macro="extra" prefix=" " suffix="."/>
926
+      <text macro="access" prefix=" "/>
927
+      <text macro="original-date" prefix=" "/>
928
+    </layout>
929
+  </bibliography>
930
+</style>
... ...
@@ -0,0 +1,113 @@
1
+<!DOCTYPE html>
2
+<html xmlns="http://www.w3.org/1999/xhtml" lang="$lang$" xml:lang="$lang$"$if(dir)$ dir="$dir$"$endif$>
3
+
4
+<head>
5
+  $-- head
6
+  ${../components/head.html()}
7
+
8
+  $-- JSON-LD
9
+
10
+${if(header-includes)}
11
+$for(header-includes)$
12
+  $header-includes$
13
+$endfor$
14
+${endif}
15
+<script src="https://hypothes.is/embed.js" async></script>
16
+</head>
17
+<body>
18
+$-- top-of-the-page includes
19
+$--------------------------------------------------------------------
20
+$for(include-before)$
21
+$include-before$
22
+$endfor$
23
+<header>
24
+  <!-- Top navigation (sitenav) -->
25
+  ${../components/site-nav.html()}
26
+
27
+$if(top)$
28
+$-- si top est true, cela signifie que je veux la navigation supérieure
29
+$-- donc pas top au sens de couverture, mais au sens de en-haut
30
+$-- only print title block if this is NOT the top page
31
+$else$
32
+  <!-- Top navigation (sitenav) -->
33
+  $--${../components/metadata.html()}
34
+
35
+<h1 class="title">$title$</h1>
36
+<blockquote class="metadata">
37
+$if(subtitle)$
38
+<p class="subtitle">$subtitle$</p>
39
+$endif$
40
+$if(author)$
41
+<p class="author">
42
+  $if(author.url)$
43
+    <a href="$author.url$">${author.full}</a>
44
+  $else$
45
+    $author$
46
+  $endif$
47
+</p>
48
+$endif$
49
+$if(date)$
50
+<p class="date $if(toc)$before-toc$endif$"><time datetime="$date$">$date$</time></p>
51
+$endif$
52
+$if(abstract)$
53
+<div class="abstract-title">$abstract-title$</div>
54
+<p>
55
+$abstract$
56
+</p>
57
+$endif$
58
+</blockquote>
59
+
60
+$endif$
61
+</header>
62
+
63
+$if(toc)$
64
+<main id="main-toc">
65
+<h2>${toc-title}</h2>
66
+$table-of-contents$
67
+</main>
68
+$endif$
69
+
70
+${if(top)}
71
+
72
+  <!-- TOC for chapters -->
73
+  ${../components/toc-nav.html()}
74
+
75
+<nav id="$idprefix$TOC" role="doc-toc">
76
+  $if(return-url)$
77
+  <a href="$return-url$">$if(return-text)$$return-text$$else$← Return$endif$</a><br>
78
+  $endif$ 
79
+  <strong>$if(toc-title)$$toc-title$$else$Contents$endif$</strong><label for="contents">⊕</label>
80
+  <input type="checkbox" id="contents">
81
+  $table-of-contents$
82
+</nav>
83
+
84
+${endif}
85
+
86
+<main>
87
+$body$
88
+</main>
89
+
90
+$if(return-url)$
91
+<footer>
92
+<p class="signoff">
93
+  <a href="$return-url$">$if(return-text)$$return-text$$else$← Return$endif$</a>
94
+</p>
95
+</footer>
96
+$endif$
97
+<script>
98
+;(function() {
99
+  // Non-essential if user has JavaScript off. Just makes checkboxes look nicer.
100
+  var selector = '.task-list > li > input[type="checkbox"]';
101
+  var checkboxes = document.querySelectorAll(selector);
102
+  Array.from(checkboxes).forEach((checkbox) => {
103
+    var wasChecked = checkbox.checked;
104
+    checkbox.disabled = false;
105
+    checkbox.addEventListener('click', (ev) => {ev.target.checked = wasChecked});
106
+  });
107
+})();
108
+</script>
109
+$for(include-after)$
110
+$include-after$
111
+$endfor$
112
+</body>
113
+</html>