<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=iso-8859-15"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><base href="x-msg://478/"><style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.apple-style-span
        {mso-style-name:apple-style-span;}
span.apple-converted-space
        {mso-style-name:apple-converted-space;}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle21
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.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=FR link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Mmmh, to be checked with official W3C online SKOS documentation, but to me it seems that the answer is no.. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I think using SKOS a collection allows ‘collection member’ and ‘concept members’, and a concept scheme allows ‘concept’ members only. In other words you wouldn’t be able to create one ‘software catalogue’ concept scheme that contains SKOS collection of terms.. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Cheers,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Olivier<o:p></o:p></span></p><div><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"'>De :</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Lowry, Roy K. [mailto:rkl@bodc.ac.uk] <br><b>Envoyé :</b> mardi 7 décembre 2010 09:25<br><b>À :</b> John Graybeal; Lauret Olivier<br><b>Cc :</b> seavox@mailman.nerc-liv.ac.uk<br><b>Objet :</b> RE: [Seavox] L221 boundaries<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-GB>Thanks John,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>I think I’m with you and Olivier here. I can also see issues with METAFOR model annotation documents being populated with sensors and water samples collected by software (on the basis that if a mistake is physically possible, somebody will make it).<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB> A related question to anybody with knowledge/interest in SKOS is. If the software catalogue and device catalogue are considered SKOS concept schemes, could those schemes be considered members of a SKOS collection?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>Cheers, Roy. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p><div><div><p class=MsoNormal><b><span lang=EN-GB>From:</span></b><span lang=EN-GB> John Graybeal [mailto:jbgraybeal@mindspring.com] <br><b>Sent:</b> 06 December 2010 21:56<br><b>To:</b> Lauret Olivier<br><b>Cc:</b> Lowry, Roy K.; seavox@mailman.nerc-liv.ac.uk<br><b>Subject:</b> Re: [Seavox] L221 boundaries<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>Concur. The characteristics of interest for the terms are likely to be different as well -- maybe 'author' is similar to 'manufacturer', but the model number equivalent will often be quite a different kind of thing. <o:p></o:p></span></p><div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>john<o:p></o:p></span></p><div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p><div><div><p class=MsoNormal><span lang=EN-GB>On Dec 6, 2010, at 06:54, Lauret Olivier wrote:<o:p></o:p></span></p></div><p class=MsoNormal><span lang=EN-GB><br><br><br><o:p></o:p></span></p><div><div><p class=MsoNormal><span lang=EN-GB>Hello Roy,<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>I would personally vote for keep L221 like it is, and add one or several new SKOS file(s) to include such data production vocabularies.<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>I guess in short-term it’s easier to put all extensions into L221, but I’m afraid in long-term you could regret it..<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>Cheers,<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>Olivier.<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p></div><div><div><div><p class=MsoNormal><b><span lang=EN-GB>De :</span></b><span lang=EN-GB> <a href="mailto:seavox-bounces@biwebs1.nerc-liv.ac.uk">seavox-bounces@biwebs1.nerc-liv.ac.uk</a> [mailto:seavox-bounces@biwebs1.nerc-liv.ac.uk] <b>De la part de</b> Lowry, Roy K.<br><b>Envoyé :</b> lundi 6 décembre 2010 14:27<br><b>À :</b> <a href="mailto:seavox@mailman.nerc-liv.ac.uk">seavox@mailman.nerc-liv.ac.uk</a><br><b>Objet :</b> [Seavox] L221 boundaries<o:p></o:p></span></p></div></div></div><div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p></div><div><div><p class=MsoNormal><span lang=EN-GB>Dear All,<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-GB>The L221 list is currently being built as ‘Terms for distinct sampling or measuring devices that may be identified in the real world in terms of manufacturer and model number.’ A question has been raised within BODC as to whether this should be extended to include software involved in data production. If so, should this be restricted to software that generates data like numerical models or should it include processing software used to work up data such as SeaSoft?<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-GB>Opinions and/or advice welcome.<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-GB>Cheers, Roy.<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-GB><br>-- <br>This message (and any attachments) is for the recipient only. NERC <br>is subject to the Freedom of Information Act 2000 and the contents <br>of this email and any reply you make may be disclosed by NERC unless <br>it is exempt from release under the Act. Any material supplied to <br>NERC may be stored in an electronic records management system.<o:p></o:p></span></p><p align=center style='text-align:center'><span lang=EN-GB>Cliquez <a href="https://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg==">ici</a> si ce message est indésirable (pourriel).<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><br>-- <br>This message (and any attachments) is for the recipient only. NERC <br>is subject to the Freedom of Information Act 2000 and the contents <br>of this email and any reply you make may be disclosed by NERC unless <br>it is exempt from release under the Act. Any material supplied to <br>NERC may be stored in an electronic records management system. _______________________________________________<br>Seavox mailing list<br><a href="mailto:Seavox@mailman.nerc-liv.ac.uk">Seavox@mailman.nerc-liv.ac.uk</a><br><a href="http://mailman.nerc-liv.ac.uk/mailman/listinfo/seavox">http://mailman.nerc-liv.ac.uk/mailman/listinfo/seavox</a><o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p><div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p><div><p class=MsoNormal><span lang=EN-GB>John Graybeal <<a href="mailto:jgraybeal@ucsd.edu">mailto:jgraybeal@ucsd.edu</a>> <o:p></o:p></span></p></div><div><div><p class=MsoNormal><span lang=EN-GB>phone: 858-534-2162<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>System Development Manager<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>Ocean Observatories Initiative Cyberinfrastructure Project: <a href="http://ci.oceanobservatories.org">http://ci.oceanobservatories.org</a><o:p></o:p></span></p></div><p class=MsoNormal><span lang=EN-GB>Marine Metadata Interoperability Project: <a href="http://marinemetadata.org">http://marinemetadata.org</a> <o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-GB><br>-- <br>This message (and any attachments) is for the recipient only. NERC <br>is subject to the Freedom of Information Act 2000 and the contents <br>of this email and any reply you make may be disclosed by NERC unless <br>it is exempt from release under the Act. Any material supplied to <br>NERC may be stored in an electronic records management system.<o:p></o:p></span></p></div></body></html>