<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Aptos, "Aptos_EmbeddedFont", "Aptos_MSFontService", Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
I wanted to highlight a use case for vocabularies that does not align well with the CDIF SKOS recommendation. I'm not sure it really affects anything about CDIF, but I'm logging it here anyway, Maybe, the recommendation is that I don't use the word "vocabulary"
in this case.</div>
<div style="font-family: Aptos, "Aptos_EmbeddedFont", "Aptos_MSFontService", Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, "Aptos_EmbeddedFont", "Aptos_MSFontService", Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
APPN is encouraging its partner nodes to produce spreadsheets listing the names and properties for key components of their persistent physical infrastructure (growth facilities, platforms and sensors) and for concepts that the node will reuse across datasets
(observed variables). </div>
<div style="font-family: Aptos, "Aptos_EmbeddedFont", "Aptos_MSFontService", Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, "Aptos_EmbeddedFont", "Aptos_MSFontService", Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Each row in one of these spreadsheets will be an instance of a class in a schema.org-compliant APPN schema (based on the MIAPPE minimum-information model, SOSA, schema.org and other ontologies).</div>
<div style="font-family: Aptos, "Aptos_EmbeddedFont", "Aptos_MSFontService", Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, "Aptos_EmbeddedFont", "Aptos_MSFontService", Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
APPN will publish the content of these spreadsheets via Research Vocabularies Australia. This will mean that every row will receive a URI that resolves to a landing page or linked data with all the properties for the instance. This is part of our plan for linking
all data from our nodes as a single navigable linked-data graph. A central node will harvest the metadata from all APPN datasets and offer services based on these linkages. Effectively, we're using this approach to publish class-specific PIDs for entities
that don't merit a DOI, ORCID, ROR or RAiD. </div>
<div style="font-family: Aptos, "Aptos_EmbeddedFont", "Aptos_MSFontService", Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, "Aptos_EmbeddedFont", "Aptos_MSFontService", Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
I don't want to coerce these sets of instances into a skos:ConceptScheme, but I've been treating them as a controlled vocabulary. Is there anything I need to consider or adjust to avoid a (minor) collision with CDIF?</div>
<div style="font-family: Aptos, "Aptos_EmbeddedFont", "Aptos_MSFontService", Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, "Aptos_EmbeddedFont", "Aptos_MSFontService", Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Thanks,</div>
<div style="font-family: Aptos, "Aptos_EmbeddedFont", "Aptos_MSFontService", Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, "Aptos_EmbeddedFont", "Aptos_MSFontService", Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Donald</div>
<div class="elementToProof" id="Signature">
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<p class="elementToProof" style="text-align: left; background-color: rgb(255, 255, 255); margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="font-family: Arial, Helvetica, sans-serif; font-size: 8pt; color: rgb(82, 138, 45);"><b>Donald Hobern</b></span><span style="font-family: Arial, Helvetica, sans-serif; font-size: 8pt; color: black;"><br>
Data Management Director, Australian Plant Phenomics Network<b><br>
</b>University of Adelaide - working from Canberra, ACT</span></p>
<p class="elementToProof" style="text-align: left; background-color: rgb(255, 255, 255); margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="font-family: Arial, Helvetica, sans-serif; font-size: 8pt; color: black;"><b>P</b> (04) 20511471 |
</span><span style="font-family: Arial, Helvetica, sans-serif; font-size: 8pt; color: rgb(101, 141, 27);"><a style="color: rgb(101, 141, 27); margin-top: 0px; margin-bottom: 0px;" class="OWAAutoLink" id="OWA2acfe088-9fae-1823-f0b9-ab46c18c257b" target="_blank" href="http://www.plantphenomics.org.au/">plantphenomics.org.au</a></span><span style="font-family: Arial, Helvetica, sans-serif; font-size: 8pt; color: black;">
| </span><span style="font-family: Arial, Helvetica, sans-serif; font-size: 8pt; color: rgb(101, 141, 27);"><a style="color: rgb(101, 141, 27); margin-top: 0px; margin-bottom: 0px;" class="OWAAutoLink" id="OWAa3e2a47a-ee3f-e1cf-9dab-57ef6ec28c43" target="_blank" href="https://www.plantphenomics.org.au/news/#news-from-our-blog">subscribe
to our news</a></span><span style="font-family: Arial, Helvetica, sans-serif; font-size: 8pt; color: black;"> </span></p>
<div class="elementToProof" style="line-height: normal; margin: 0cm 0cm 8pt; font-family: Arial, Helvetica, sans-serif; font-size: 8pt; color: black;">
<img style="max-width: 798px;" id="image_1" data-outlook-trace="F:1|T:1" src="cid:124bd19a-911b-4b97-9ea0-04518bc339c1"></div>
<div class="elementToProof" style="margin-top: 1em; margin-bottom: 1em; font-family: Arial, Helvetica, sans-serif; font-size: 8pt;">
<span style="color: rgb(82, 138, 45);">APPN acknowledges the Traditional Custodians of Country throughout Australia and their connections to land, sea and community. We pay our respect to their Elders past and present and extend that respect to all Aboriginal
and Torres Strait Islander peoples today.</span><span style="color: black;"><br>
The Australian Plant Phenomics Network (APPN) is supported by the Australian Governments National Collaborative Research Infrastructure Strategy (</span><span style="color: rgb(153, 159, 163);"><a data-auth="NotApplicable" data-linkindex="3" style="color: rgb(153, 159, 163);" rel="noopener noreferrer" class="OWAAutoLink" id="OWA0d6fe7c2-3bba-54d7-3321-25ddf0e8dbfa" target="_blank" href="https://www.education.gov.au/national-collaborative-research-infrastructure-strategy-ncris">NCRIS</a></span><span style="color: black;">)<br>
APPN National Head Office at the </span><span style="color: rgb(153, 159, 163);"><a data-auth="NotApplicable" data-linkindex="4" style="color: rgb(153, 159, 163);" rel="noopener noreferrer" class="OWAAutoLink" id="OWA79ceb96a-a55d-fc5e-e236-685c8ea3f8e3" target="_blank" href="https://www.thewaite.org/">University
of Adelaide</a></span><span style="color: black;"> (UoA - CRICOS provider number 00123M). This email (and any attachment) is confidential and may also be privileged or otherwise exempt from disclosure. It is intended only for the addressee. If you are not
the intended recipient, please delete it and do not send it on, copy it or disclose its contents. No assurance is given about the security of information sent electronically. Think green and read on the screen.</span></div>
</div>
</body>
</html>