<div dir="ltr">I definitely support the move to using a separate annotation property for examples in DwC. However, I would strongly encourage you to reuse an existing property, rather than make up a new one for DwC. It seems like either skos:example or iao:example of usage would work. iao:example of usage is what we use in BCO, so that would make it compatible.<br><br>Ramona<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">------------------------------------------------------<br>Ramona L. Walls, Ph.D.<br>Scientific Analyst, The iPlant Collaborative, University of Arizona<br>Research Associate, Bio5 Institute, University of Arizona<br>Laboratory Research Associate, New York Botanical Garden</div></div></div>
<br><div class="gmail_quote">On Thu, Feb 5, 2015 at 8:26 AM, Éamonn Ó Tuama [GBIF] <span dir="ltr"><<a href="mailto:eotuama@gbif.org" target="_blank">eotuama@gbif.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link="blue" vlink="purple" lang="EN-GB"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">RDF/SKOS notation makes items like labels, definitions, examples very explicit:<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><skos:Concept rdf:about="<a href="http://purl.org/dc/terms/accessRights" target="_blank">http://purl.org/dc/terms/accessRights</a>"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><skos:historyNote rdf:about="modified" dc:date="2008/01/14"/><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><skos:prefLabel xml:lang="fr">Droits d'accès</skos:prefLabel><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><skos:definition xml:lang="en">Information about who can access the resource ....<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><skos:example xml:lang="de">Zugriffsrechte können Informationen ... <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"></skos:Concept><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">The use of SKOS for describing property terms is discussed on page 4 of the TDWG Vocabulary Management Task Group (VoMaG) report [1]. Does use of SKOS in this context bring any semantic baggage?<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Éamonn<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">[1] <a href="http://www.gbif.org/resources/2246" target="_blank">http://www.gbif.org/resources/2246</a><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" lang="EN-US">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" lang="EN-US"> <a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a> [mailto:<a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a>] <b>On Behalf Of </b>John Wieczorek<br><b>Sent:</b> 05 February 2015 15:35<br><b>To:</b> Markus Döring<br><b>Cc:</b> TDWG Content Mailing List; Ramona Walls<br><b>Subject:</b> Re: [tdwg-content] Darwin Core Proposal - term content recommendations to comments<u></u><u></u></span></p></div><div><div class="h5"><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">I thought you would, since you mentioned it independently even before Ramona did. :-)<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">On Thu, Feb 5, 2015 at 11:32 AM, Markus Döring <<a href="mailto:m.doering@mac.com" target="_blank">m.doering@mac.com</a>> wrote:<u></u><u></u></p><div><p class="MsoNormal">I like that idea, John!<u></u><u></u></p><div><div><div><p class="MsoNormal"><u></u> <u></u></p><div><div><p class="MsoNormal">On 05 Feb 2015, at 15:30, John Wieczorek <<a href="mailto:tuco@berkeley.edu" target="_blank">tuco@berkeley.edu</a>> wrote:<u></u><u></u></p></div><p class="MsoNormal"><br><br><u></u><u></u></p><div><p class="MsoNormal">Dear all,<u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">We have been musing about how to make it easy to mark up examples in human-readable renditions, and how best to enable that in the RDF as source. I think, Ramona, that the separate example usage annotations solve multiple real problems that we have right now and align us well with how we would like to manage Darwin Core in BCO. Thus, though it may not be necessary for Darwin Core at this time, I think it will actually help us.<u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Thus, I would like to formally amend the original proposal. Specifically, I would add a new attribute dwcattributes:example. I would add an instance of this attribute for every example in every Darwin Core term. All examples would be removed from the definitions and comments. The recommendations on controlled vocabularies would still be moved consistently to the comments as in the original proposal.<u></u><u></u></p></div></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Given this proposed amendment, I'll change the end-date for commentary on this proposal to 5 Mar 2015.<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Cheers,<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">John<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div></div><div><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">On Wed, Jan 21, 2015 at 12:12 AM, Ramona Walls <<a href="mailto:rlwalls2008@gmail.com" target="_blank">rlwalls2008@gmail.com</a>> wrote:<u></u><u></u></p><div><p class="MsoNormal">This is a good idea. In theory the recommendation could go into a separate annotation (e.g., we use "example of usage" in BCO), but I don't think that is necessary for DwC at this juncture.<br><br>Ramona<u></u><u></u></p><div><div><p class="MsoNormal"><br clear="all"><u></u><u></u></p><div><div><p class="MsoNormal">------------------------------------------------------<br>Ramona L. Walls, Ph.D.<br>Scientific Analyst, The iPlant Collaborative, University of Arizona<br>Research Associate, Bio5 Institute, University of Arizona<br>Laboratory Research Associate, New York Botanical Garden<u></u><u></u></p></div></div><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">On Tue, Jan 20, 2015 at 4:00 AM, <<a href="mailto:tdwg-content-request@lists.tdwg.org" target="_blank">tdwg-content-request@lists.tdwg.org</a>> wrote:<u></u><u></u></p><p class="MsoNormal">When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of tdwg-content digest..."<br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Mon, 19 Jan 2015 14:58:06 +0100<br>From: John Wieczorek <<a href="mailto:tuco@berkeley.edu" target="_blank">tuco@berkeley.edu</a>><br>Subject: [tdwg-content] Darwin Core Proposal - term content<br> recommendations to comments<br>To: TDWG Content Mailing List <<a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a>><br>Message-ID:<br> <CAHwKGGc7sK3Dg8KTN_NYe4S+OYk=<a href="mailto:YE%2B-dRxjKPS-dNnGhAvjMw@mail.gmail.com" target="_blank">YE+-dRxjKPS-dNnGhAvjMw@mail.gmail.com</a>><br>Content-Type: text/plain; charset="utf-8"<u></u><u></u></p><div><div><p class="MsoNormal"><br><br>Dear all,<br><br>During the process of reviewing the recent set of changes to the Darwin<br>Core standard in early November 2014, it was proposed to make the<br>definitions and comments for terms more consistent in their treatment of<br>content recommendations. The specific proposal is logged in the Darwin Core<br>issue tracker as <a href="https://github.com/tdwg/dwc/issues/26" target="_blank">https://github.com/tdwg/dwc/issues/26</a>.<br><br>The gist of the proposal is that recommendations on how to populate a term<br>are often in the definition whereas we would like them to be consistently<br>in the comments section. The list of affected terms is given below for<br>reference.<br><br>This message is to elicit responses from any who might have a reason to<br>recommend against these changes, which are not semantic in nature. We will<br>leave this proposal open for commentary until 19 February 2015 unless<br>further discussion arises resulting in amendments.<br><br>Cheers,<br><br>John<br><br><br>The following terms have recommendations in the definitions, which we would<br>like to move to comments:<br><br>datasetID<br>occurrenceID<br>sex<br>lifeStage<br>reproductiveCondition<br>behavior<br>establishmentMeans<br>occurrenceStatus<br>organismID<br>organismScope<br>materialSampleID<br>eventID<br>eventDate<br>eventTime<br>locationID<br>higherGeographyID<br>continent<br>waterBody<br>islandGroup<br>island<br>country<br>countryCode<br>municipality<br>locality<br>minimumDistanceAboveSurfaceInMeters<br>maximumDistanceAboveSurfaceInMeters<br>locationAccordingTo<br>decimalLatitude<br>decimalLongitude<br>geodeticDatum<br>coordinateUncertaintyInMeters<br>pointRadiusSpatialFit<br>verbatimCoordinates<br>verbatimLatitude<br>verbatimLongitude<br>verbatimCoordinateSystem<br>verbatimSRS<br>footprintWKT<br>footprintSRS<br>footprintSpatialFit<br>georeferencedDate<br>georeferenceVerificationStatus<br>geologicalContextID<br>identificationID<br>dateIdentified<br>identificationVerificationStatus<br>taxonID<br>scientificName<br>subgenus<br>taxonRank<br>nomenclaturalCode<br>taxonomicStatus<br>measurementID<br>measurementType<br>measurementUnit<br>measurementDeterminedDate<br>relationshipOfResource<br>relationshipEstablishedDate<br><br>while the following terms already have the recommendations in the comments:<br><br>institutionID<br>collectionID<br>basisOfRecord<br>dynamicProperties<br>recordedBy<br>preparations<br>disposition<br>associatedMedia<br>associatedReferences<br>associatedSequences<br>associatedTaxa<br>otherCatalogNumbers<br>associatedOccurrences<br>associatedOrganisms<br>previousIdentifications<br>higherGeography<br>georeferencedBy<br>georeferenceSources<br>typeStatus<br>identifiedBy<br>identificationReferences<br>higherClassification<br>measurementDeterminedBy<u></u><u></u></p></div></div><p class="MsoNormal" style="margin-bottom:12.0pt">-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <a href="http://lists.tdwg.org/pipermail/tdwg-content/attachments/20150119/38ca5b70/attachment-0001.html" target="_blank">http://lists.tdwg.org/pipermail/tdwg-content/attachments/20150119/38ca5b70/attachment-0001.html</a><u></u><u></u></p></div></div></div></div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>_______________________________________________<br>tdwg-content mailing list<br><a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a><br><a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><u></u><u></u></p></div><p class="MsoNormal"><u></u> <u></u></p></div><p class="MsoNormal">_______________________________________________<br>tdwg-content mailing list<br><a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a><br><a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><u></u><u></u></p></div><p class="MsoNormal"><u></u> <u></u></p></div></div></div></div></div><p class="MsoNormal"><u></u> <u></u></p></div></div></div></div></div></blockquote></div><br></div>