<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-AU" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Awesome Steve, thank you
</span><span style="font-family:"Segoe UI Emoji",sans-serif;mso-fareast-language:EN-US">😊</span><span style="mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="mso-ligatures:none">From:</span></b><span lang="EN-US" style="mso-ligatures:none"> tdwg-humboldt <tdwg-humboldt-bounces@lists.tdwg.org>
<b>On Behalf Of </b>Baskauf, Steven James<br>
<b>Sent:</b> Wednesday, 17 May 2023 2:47 PM<br>
<b>To:</b> The Humboldt Core Task Group discussion <tdwg-humboldt@lists.tdwg.org>; wmh6@cornell.edu<br>
<b>Subject:</b> [tdwg-humboldt] Markdown version of isLeastSpecificTargetCategoryQuantityInclusive Guidelines<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Hi folks,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I’ve done a conversion of the isLeastSpecificTargetCategoryQuantityInclusive Guidelines to Markdown. You can see the draft at:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="https://github.com/baskaufs/msc/blob/master/docs/inclusive.md">https://github.com/baskaufs/msc/blob/master/docs/inclusive.md</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">When it’s good enough, I’ll submit it as a pull request to somewhere in the Humboldt repo.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Notes:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">1. In the Google Doc, some text earlier in the doc repeated what was in the Examples section, so I deleted it.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">2. I added the standard status (1.1) and RFC 2119 keyword section (1.2) section. After reading the doc, it seems that only section 3 is normative, so I stated that, and labeled all of the major sections as to whether
they were normative or not. I made a few changes to section 3 so that the RFC 2119 keywords were include where I though they needed to be, so please read that section again to make sure that these prescriptive wordings make sense.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">3. I can’t remember who did the work of writing the doc, so please check the contributors section at the top to make sure I got it right.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">4. I made up an abstract from info in the introduction.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">5. I split the Introduction and Rationale into 2 separate sections to follow the pattern of other TDWG documents: having an initial introductory section, the technical sections (1.1-1.3) then the main text. This seemed
to work out if I split the first paragraph out and used it for the intro and put the rest into rationale.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">IMPORTANT:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I was rigorous in distinguishing between text that referred to abbreviated term IRIs (like dwc:Event) and colloquial use of terms (like “organism”) by putting the abbreviated term IRIs (and literal values) in code markup
as has been standard practice in other documents. However, there were many places in the document where it straddled the fence by using capitalized words like “Event”, “Taxon”, or “Organism”. These either were term IRIs or they weren’t. Since they weren’t
prefixed by a namespace abbreviation, I assumed they were just nouns and not term IRIs and I changed them to lower case. If that was not the intention and “dwc:Event”, “dwc:Taxon”, and “dwc:Organism” were intended, then they should all be re-capitalized and
prepended with a namespace abbreviation. We can discuss what was intended at our meeting tomorrow and I’ll change them as necessary.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">See you in the morning.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Steve<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="mso-ligatures:none">-- <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="mso-ligatures:none">Steven J. Baskauf, Ph.D. he/him/his<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-ligatures:none">Data Science and Data Curation Specialist / Librarian III<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-ligatures:none">Jean & Alexander Heard Libraries, Vanderbilt University<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-ligatures:none">Nashville, TN 37235, USA<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-ligatures:none"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-ligatures:none">Biodiversity Information Standards (TDWG) Executive Committee/Technical Architecture Group Chair<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-ligatures:none"><a href="https://baskauf.github.io/">https://baskauf.github.io/</a><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</body>
</html>