<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
Hi Ron,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
ArchivesSpace doesn't require that both Begin and End fields are populated when the date type is Inclusive. We have a handful of dates in our database with an expression of "after" or "post" a particular year, where we've set the Begin to that year and left
the End null. As far as indexing is concerned it gets us where we'd like to be.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
(Whether the ways we've done this in the past is DACS-compliant is a discussion for another time.) -k<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Ron Van den
Branden <Ron.VandenBranden@antwerpen.be><br>
<b>Sent:</b> Thursday, October 13, 2022 11:52 AM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?</font>
<div> </div>
</div>
<style>
<!--
@font-face
{font-family:Wingdings}
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
@font-face
{font-family:"Segoe UI Symbol"}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_MsoHyperlink
{color:#0563C1;
text-decoration:underline}
p.x_MsoListParagraph, li.x_MsoListParagraph, div.x_MsoListParagraph
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
span.x_E-mailStijl21
{font-family:"Calibri",sans-serif;
color:windowtext}
.x_MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:70.85pt 70.85pt 70.85pt 70.85pt}
div.x_WordSection1
{}
ol
{margin-bottom:0cm}
ul
{margin-bottom:0cm}
-->
</style>
<div lang="NL-BE" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="x_WordSection1">
<p class="x_MsoNormal"><span style="">Hi Kate,</span></p>
<p class="x_MsoNormal"><span style=""> </span></p>
<p class="x_MsoNormal"><span lang="EN-US" style="">I realize my analysis might have been biased by a data-oriented view on our current data, which contains quite a number of archival objects with only a start date, and some with only an end date. I’ve asked
my colleagues, and open-ended dates are indeed uncommon for </span><span lang="EN-US">resources, accessions, archival, or digital objects: they’ll be mostly ranges with a known start and end date.
</span><span lang="EN-US" style=""></span></p>
<p class="x_MsoNormal"><span lang="EN-US" style=""> </span></p>
<p class="x_MsoNormal"><span lang="EN-US" style="">How to interpret these single dates in our data is probably a matter of internal interpretation on our end, but still: what is the intended/preferred notation in ArchivesSpace? If the creation time span for
a subseries is determined as e.g. 1969, how should this be encoded:</span></p>
<ul type="disc" style="margin-top:0cm">
<li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US" style="">Single date</span></li><ul type="circle" style="margin-top:0cm">
<li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US" style="">Begin date = 1969</span></li></ul>
<li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US" style="">Inclusive date</span></li><ul type="circle" style="margin-top:0cm">
<li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US" style="">Begin date = 1969</span></li><li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US" style="">End date = 1969</span></li></ul>
</ul>
<p class="x_MsoNormal"><span lang="EN-US" style="">?</span></p>
<p class="x_MsoNormal"><span lang="EN-US" style=""> </span></p>
<p class="x_MsoNormal"><span lang="EN-US" style="">Best,</span></p>
<p class="x_MsoNormal"><span lang="EN-US" style=""> </span></p>
<p class="x_MsoNormal"><span lang="EN-US" style="">Ron</span></p>
<p class="x_MsoNormal"><span lang="EN-US" style=""> </span></p>
<div style="border:none; border-left:solid blue 1.5pt; padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0cm 0cm 0cm">
<p class="x_MsoNormal"><b><span lang="NL">Van:</span></b><span lang="NL"> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org>
<b>Namens </b>Bowers, Kate A.<br>
<b>Verzonden:</b> donderdag 13 oktober 2022 16:57<br>
<b>Aan:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Onderwerp:</b> Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?</span></p>
</div>
</div>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"><span lang="EN-US">Can you explain the case for open-ended dates for resources, accessions, archival, or digital objects?
</span></p>
<p class="x_MsoNormal"><span lang="EN-US"> </span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0cm 0cm 0cm">
<p class="x_MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>>
<b>On Behalf Of </b>Ron Van den Branden<br>
<b>Sent:</b> Thursday, October 13, 2022 10:32 AM<br>
<b>To:</b> <a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a><br>
<b>Subject:</b> [Archivesspace_Users_Group] how to encode open-ended date ranges?</span></p>
</div>
</div>
<p class="x_MsoNormal"><span lang="EN-US"> </span></p>
<p class="x_MsoNormal">Hi,</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"><span lang="EN-US">We’re in the process of migrating data to ArchivesSpace, and one thing I’m still struggling with is how to encode open-ended date ranges, using standardized dates only. In other words: how to express:</span></p>
<ul type="disc" style="margin-top:0cm">
<li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">the fact that only a start date is known</span></li><li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">or the fact that only an end date is known</span></li></ul>
<p class="x_MsoNormal"><span lang="EN-US">…while still indicating this known date is the start / end of a range whose other end is not known; as opposite to expressing a precise singular/punctual date.</span></p>
<p class="x_MsoNormal"><span lang="EN-US"> </span></p>
<p class="x_MsoNormal"><span lang="EN-US">Given the fact that ArchivesSpace currently uses 2 distinct date models for accessions, resources/archival objects and digital objects vs agents (see
<a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__www.mail-2Darchive.com_archivesspace-5Fusers-5Fgroup-40lyralists.lyrasis.org_msg05341.html%26d%3DDwMGaQ%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3Dwwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY%26m%3DhwhUWCl8DmiVBAr8KCWWuvqIpF5qGU38NpEyKdpmIIC_b1sDZ08xKIYeni9Jn1Sz%26s%3DcH9UvNvbKkbEcG88o6pqGcf3-0l_7L5sIV0c3bplsR8%26e%3D&data=05%7C01%7Ckmc35%40psu.edu%7C41415742bb1344a9c63b08daad32e962%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638012731654163667%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=m7TjWVJkrdOrGrS5Fuz8nkD067qwgpZ4IJlE9tEa%2Bxk%3D&reserved=0" originalsrc="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.mail-2Darchive.com_archivesspace-5Fusers-5Fgroup-40lyralists.lyrasis.org_msg05341.html&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=hwhUWCl8DmiVBAr8KCWWuvqIpF5qGU38NpEyKdpmIIC_b1sDZ08xKIYeni9Jn1Sz&s=cH9UvNvbKkbEcG88o6pqGcf3-0l_7L5sIV0c3bplsR8&e=" shash="QTkOm2hFLEOA3t7nER1/BaZMrtlMZhNfiX+AVydj2bE+qzlvw9XqmqEZVt8SPBrPZfpwfxiR0nmr2msikVnjYwBHBL/SaI1bPKrwm3LKGnVJSXOK0TigrOAk8RIgoiPrJjUodKr7nYhXSJOzG/J/PJmGqEXB7aPGlphSE510TJM=">
https://www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html</a>), I’ll outline the observations and options I’m seeing.</span></p>
<p class="x_MsoNormal"><span lang="EN-US"> </span></p>
<p class="x_MsoNormal"><span lang="EN-US">[1] Accessions, resources, archival objects, digital objects:</span></p>
<ul type="disc" style="margin-top:0cm">
<li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">“Single” date only offers a single date field, labeled “Begin”</span></li><li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">“Inclusive” date offers both a “Begin” and “End” date field, only one of which is required
</span></li></ul>
<p class="x_MsoNormal"><span lang="EN-US">Would this be a good strategy:</span></p>
<ul type="disc" style="margin-top:0cm">
<li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">“singular/punctual” dates: “single” date, one value as “Begin” date</span></li><li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">date range: “inclusive” date, start and end dates as “Begin” and “End” dates, respectively</span></li><li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">open-ended date range: “inclusive” date, with known date as either “Begin” or “End” date</span></li></ul>
<p class="x_MsoNormal"><span lang="EN-US">?</span></p>
<p class="x_MsoNormal"><span lang="EN-US">This leads me to the question whether in practice “single” dates are used at all for anything except accession dates, creation dates of digital objects, or as dates for only the lowest-level archival objects?</span></p>
<p class="x_MsoNormal"><span lang="EN-US"> </span></p>
<p class="x_MsoNormal"><span lang="EN-US">[2] Agents:</span></p>
<ul type="disc" style="margin-top:0cm">
<li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">“Single” date only offers a single date field, which can be labeled as either “Begin” or “End”</span></li><li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">“Inclusive” date offers both a “Begin” and “End” date field, of which “Begin” is mandatory</span></li></ul>
<p class="x_MsoNormal"><span lang="EN-US">Would this be a good strategy:</span></p>
<ul type="disc" style="margin-top:0cm">
<li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">“singular/punctual” dates: “single” date, one value as either “Begin” or “End” date</span></li></ul>
<p class="x_MsoListParagraph"><span lang="EN-US">Note: in EAC output, the begin/end qualification is dismissed: both are exported without distinction as e.g.
<br>
<date localType="existence" standardDate="2022-10-08">2022-10-08</date></span></p>
<ul type="disc" style="margin-top:0cm">
<li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">date range: “inclusive” date, start and end dates as “Begin” and “End” dates, respectively</span></li></ul>
<ul type="disc" style="margin-top:0cm">
<li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">open-ended date range: ?
<br>
</span><span lang="EN-US" style="font-family:Wingdings">è</span><span lang="EN-US"> problem if only end date is known, since begin date is mandatory</span></li></ul>
<p class="x_MsoNormal"><span lang="EN-US">In other words: how would one differentiate between, e.g.:</span></p>
<ul type="disc" style="margin-top:0cm">
<li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">birth date of a living person (1990 - )</span></li><li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">birth date of a deceased person, whose death date is unknown (1800 - ?)</span></li><li class="x_MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">death date of a person whose birth date is unknown (? - 1950)</span></li></ul>
<p class="x_MsoNormal"><span lang="EN-US">?</span></p>
<p class="x_MsoNormal"><span lang="EN-US"> </span></p>
<p class="x_MsoNormal"><span lang="EN-US">The documentation in the ArchivesSpace Help Center merely documents the different fields, but I couldn’t find much guidance on how to use them in practice. The DACS, EAD, and EAC documentation is rather sparse as well
regarding open-ended date ranges. Therefore, any guidance on this matter would be much appreciated!</span></p>
<p class="x_MsoNormal"><span lang="EN-US"> </span></p>
<p class="x_MsoNormal"><span lang="EN-US">Best,</span></p>
<p class="x_MsoNormal"><span lang="EN-US"> </span></p>
<p class="x_MsoNormal"><span lang="EN-US">Ron</span></p>
<p class="x_MsoNormal"><span lang="EN-US"> </span></p>
<p class="x_MsoNormal" style="line-height:125%"><b><span style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis</span></b><span style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D"></span></p>
<p class="x_MsoNormal" style="line-height:125%"><span style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving</span><span style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif">
<span style="color:#4D4D4D">| Musea en Erfgoed </span></span></p>
<p class="x_MsoNormal" style="line-height:125%"><span style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">Minderbroedersstraat 22, 2000 Antwerpen</span></p>
<p class="x_MsoNormal"><span style="font-size:9.0pt; font-family:"Segoe UI Symbol",sans-serif; color:#4D4D4D">✉</span><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:#4D4D4D"> Grote Markt 1, 2000 Antwerpen</span></p>
<p class="x_MsoNormal"><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:#4D4D4D">gsm +32 0485 02 80 50 | tel. +32 3 222 93 30</span><span style="font-size:9.0pt; color:black"></span></p>
<p class="x_MsoNormal" style="line-height:125%"><a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__www.letterenhuis.be_%26d%3DDwMGaQ%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3Dwwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY%26m%3DhwhUWCl8DmiVBAr8KCWWuvqIpF5qGU38NpEyKdpmIIC_b1sDZ08xKIYeni9Jn1Sz%26s%3DRCdANiyeGbpOaHKErHK7dN3hVi4Xjiqw7EG9JmMGEIM%26e%3D&data=05%7C01%7Ckmc35%40psu.edu%7C41415742bb1344a9c63b08daad32e962%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638012731654163667%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=wTieV%2BJ%2BPeqgzQlOe9gvWIxIQx0BorVs8pSYhGSyhsg%3D&reserved=0" originalsrc="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.letterenhuis.be_&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=hwhUWCl8DmiVBAr8KCWWuvqIpF5qGU38NpEyKdpmIIC_b1sDZ08xKIYeni9Jn1Sz&s=RCdANiyeGbpOaHKErHK7dN3hVi4Xjiqw7EG9JmMGEIM&e=" shash="Q/1FamvUdomng4YgGGikWQE28Ia3mpI3FYbrvHVKHLkvzM1EFxch4MHFEQGT0MxeDBYaobVsFucFPk5xtBTWEiXAGb0xMXyZDp56oZyuRcVhXnt6Y8RZwc4UD6H0/gK7nb5vfQQ5iEGV8EikgtosIrOhlxwzlDyaZVIr8D2iu+A="><span style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">letterenhuis.be</span></a><span style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">
| </span><a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__www.instagram.com_letterenhuis_%26d%3DDwMGaQ%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3Dwwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY%26m%3DhwhUWCl8DmiVBAr8KCWWuvqIpF5qGU38NpEyKdpmIIC_b1sDZ08xKIYeni9Jn1Sz%26s%3D23CBQ1OTniE_zIpk904UheXNdpIsl_Gs62ZkcZgRQN4%26e%3D&data=05%7C01%7Ckmc35%40psu.edu%7C41415742bb1344a9c63b08daad32e962%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638012731654163667%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pwO5GPTDJjdm6BYQwxWfIx1wYTJNnk21Hj2dM2hPPyY%3D&reserved=0" originalsrc="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.instagram.com_letterenhuis_&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=hwhUWCl8DmiVBAr8KCWWuvqIpF5qGU38NpEyKdpmIIC_b1sDZ08xKIYeni9Jn1Sz&s=23CBQ1OTniE_zIpk904UheXNdpIsl_Gs62ZkcZgRQN4&e=" shash="YSFRGxvI5RmuuVB+oAjIElMUxzE+9UFvhJcOtI6lRgvbDxwgjMX3cxUxrdude67GqOv9vM7C4THJg4537zz9D4oA16oSlXkex0L8G4qWwVlS8E6BU0Te9HaLQXSwnA6H6g6qOYg+BCQhvLOPAryo9jp4bgUppvC0mb/bEOZbA7o="><span style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">instagram</span></a><span style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">
| </span><a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__www.facebook.com_Letterenhuis%26d%3DDwMGaQ%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3Dwwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY%26m%3DhwhUWCl8DmiVBAr8KCWWuvqIpF5qGU38NpEyKdpmIIC_b1sDZ08xKIYeni9Jn1Sz%26s%3DVas9PGIxYEolJnQuVo9qEE1hue_eztFb4vZEFEOLCUE%26e%3D&data=05%7C01%7Ckmc35%40psu.edu%7C41415742bb1344a9c63b08daad32e962%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638012731654163667%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zRktsxgbwAd4erlyNcR3ULfHLEQBMYw6vRZMhctZk3M%3D&reserved=0" originalsrc="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_Letterenhuis&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=hwhUWCl8DmiVBAr8KCWWuvqIpF5qGU38NpEyKdpmIIC_b1sDZ08xKIYeni9Jn1Sz&s=Vas9PGIxYEolJnQuVo9qEE1hue_eztFb4vZEFEOLCUE&e=" shash="szAvaffOWthr3Ca5PlLkUbpT59C3dqbh5BF27P9zft62oS7AZG5IZ00W/0HsxC+Fwp81aYtau95Px0Zu5wN1SSCBez2oIzlB1zHrYAlw0WhhM1cz2Mvgkoy2kfepB7yuZICkOWiPrq5uiQN1FSMxpq5XiH5E7FufLpm1izHWxoI="><span style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">facebook</span></a></p>
<p class="x_MsoNormal" style="line-height:125%"><span style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D"> </span></p>
<p class="x_MsoNormal" style="line-height:125%"><b><span style="font-size:7.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">Proclaimer</span></b><span style="font-size:7.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D"></span></p>
<p class="x_MsoNormal" style="line-height:125%"><span style="font-size:7.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk
om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk officiële documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader
waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopiëren.</span></p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"> </p>
</div>
</div>
</div>
</body>
</html>