<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi again, Roy (and all)<br>
<br>
A minor, maybe even frivolous, point: is it a given that a vehicle
is limited to <br>
either water or air, or will there be a time when drones can go
underwater, or <br>
move across land? <br>
<br>
I'm raising this point because we routinely deploy SBE39s as
back-up air temp <br>
sensors on our buoys, which raises questions when we describe the
instrument. <br>
That's led me to think that including the medium in an
instrument/platform <br>
definition isn't necessarily a good idea.<br>
<br>
Cheers - Nan<br>
<br>
<br>
On 3/24/15 9:47 AM, Isenor, Anthony wrote:<br>
</div>
<blockquote
cite="mid:DADA8585A3648344B2E0E1D28FF8F4E290D8FDDE@ATL-E02.atlantic.drdc-rddc.gc.ca"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (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;}
@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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
.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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I
would consider that to be a “tethered” platform; where as a
UAV in my mind is capable of more maneuverability.
Interesting though, because I am now wondering if your
winged kite should be distinguished from an aerostat (a
tethered balloon).<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I
also think it worthwhile to maintain UAV as a search target.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US"></Anthony><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><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""
lang="EN-US">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US"> John Graybeal
[<a class="moz-txt-link-freetext" href="mailto:jbgraybeal@mindspring.com">mailto:jbgraybeal@mindspring.com</a>]
<br>
<b>Sent:</b> March-24-15 10:07 AM<br>
<b>To:</b> Roy Lowry<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:seavox@mailman.nerc-liv.ac.uk">seavox@mailman.nerc-liv.ac.uk</a><br>
<b>Subject:</b> Re: [Seavox] L06 extension<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Yes, my 'unmanned aircraft' name could just
as well be 'unmanned aerial vehicle (UAV)'.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">So is one of those flying kites that
Google et al put up for energy generation or network
coverage a UAV too, do you figure? <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><a moz-do-not-send="true"
href="http://www.google.com/makani/">http://www.google.com/makani/</a><o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">John<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mar 24, 2015, at 03:44, Lowry,
Roy K. <<a moz-do-not-send="true"
href="mailto:rkl@bodc.ac.uk">rkl@bodc.ac.uk</a>>
wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">Dear All,<br>
<br>
I'm happy with this suggestion, except I'd like to keep
the reference to unmanned aerial vehicle (UAV) as a
search target. As Nan says we can add finer grained
codes should the need arise.<br>
<br>
Unless there are any objections make the changes on
Thursday (26).<br>
<br>
Cheers, Roy.<br>
<br>
-----Original Message-----<br>
From: John Graybeal [<a moz-do-not-send="true"
href="mailto:jbgraybeal@mindspring.com">mailto:jbgraybeal@mindspring.com</a>]<br>
Sent: 17 March 2015 04:01<br>
To: Lowry, Roy K.<br>
Cc: Nan Galbraith; <a moz-do-not-send="true"
href="mailto:seavox@mailman.nerc-liv.ac.uk">seavox@mailman.nerc-liv.ac.uk</a><br>
Subject: Re: [Seavox] L06 extension<br>
<br>
Thoughts without conclusions....<br>
<br>
I think an autonomous aircraft is one that doesn't
require remote piloting of any sort -- it's not just
human-independent, it's self-contained.<br>
<br>
Whereas a remotely piloted aircraft is one that can be
remotely piloted at all, even if there may be a human
pilot aboard?<br>
<br>
At first I didn't realize the last sentence in each
definition was meant to bridge both definitions. It's
useful but maybe there's another path that is clearer:
actually define the term 'unmanned aircraft' as "Any
heavier-than-air aircraft that is not occupied by
people; may be a remotely piloted aircraft or an
autonomous aircraft. Also referred to as a drone."<br>
<br>
I also like to stay ahead of usage (i.e., setting up
additional codes up front), but common usage doesn't
always follow the path of greatest terminological
distinction. So sometimes there's an advantage to seeing
where the paths go before you pour the sidewalks, I
guess.<br>
<br>
Hopefully helping,<br>
<br>
John<br>
<br>
P.S. By the way, I'm sure unmanned autonomous aircraft
exist today -- I saw some science done with one off the
California coast, in fact. In the US, if it isn't in
flight lanes (under 100 feet I think) and isn't
commercial, it's arguably legal, if I recall correctly.
They did some cool observing patterns with it to measure
the CODAR/HF RADAR signal coverage. (And I bet the
military have a few, too!)<br>
<br>
<br>
<br>
On Mar 10, 2015, at 06:58, Lowry, Roy K. <<a
moz-do-not-send="true" href="mailto:rkl@bodc.ac.uk">rkl@bodc.ac.uk</a>>
wrote:<br>
<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">Thanks Nan,<br>
<br>
I was trying to follow the International Civil Aviation
Authority classification, which has two types: remotely
piloted and autonomous. As you say, if this granularity
proves too coarse we can add child concepts in the
future.<br>
<br>
In my initial e-mail I was aiming to just cover
remotely-piloted with the new code. Or do you think I
should set up the additional code for fully-autonomous
now as well? This would give us:<br>
<br>
remotely piloted aircraft<br>
RPA<br>
A heavier-than-air aircraft without a human pilot aboard
that is controlled remotely by a human pilot. Also
referred to, together with computer-controlled aircraft,
as a drone or unmanned aerial vehicle (UAV).<br>
<br>
autonomous aircraft<br>
A heavier-than-air aircraft without a human pilot aboard
that is controlled by on-board or remote computers. Also
referred to, together with aircraft piloted remotely by
a human, as a drone or unmanned aerial vehicle (UAV).<br>
<br>
My reasons for including UAV (so hard not to type
AUV!!!!!) and drone for that matter was to provide a
target for free text searches - many of these have been
implemented to include the alternative label and
definition as well as the preferred label.<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: Nan Galbraith [<a moz-do-not-send="true"
href="mailto:ngalbraith@whoi.edu">mailto:ngalbraith@whoi.edu</a>]<br>
Sent: 10 March 2015 13:30<br>
To: <a moz-do-not-send="true"
href="mailto:seavox@mailman.nerc-liv.ac.uk">seavox@mailman.nerc-liv.ac.uk</a><br>
Subject: Re: [Seavox] L06 extension<br>
<br>
Hi Roy -<br>
<br>
Yes, I agree, this seems like it will be needed soon, if
it isn't already.<br>
<br>
My only concern is whether you'll need to differentiate
between the many types of unmanned aerial vehicles that
may be in use, or can these be added later as
subclasses?<br>
<br>
Last point - is there such a thing as a non-human pilot?
Can an RPA be piloted by a computer, and does that make
a difference to its function as a platform?<br>
<br>
Like Bob, I thought UAV was probably the acronym you'd
want in the definition (or, do you need to supply an
acronym there at all?).<br>
<br>
Cheers -<br>
<br>
Nan<br>
<br>
On 3/10/15 8:48 AM, Robert C. Groman wrote:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">Roy,<br>
<br>
I think you meant to write UAV for "unmanned aerial
vehicle", since<br>
AUV is an abbreviation for "autonomous underwater
vehicle".<br>
<br>
Cheers, Bob<br>
<br>
On 3/10/2015 7:29 AM, Lowry, Roy K. wrote:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">Dear All,<br>
I've had a request to extend the platform type (L06) to
include an<br>
additional child entry under 'non-buoyant aircraft' for
unmanned<br>
aerial vehicles, sometimes referred to as drones. These
are a<br>
platform type that has entered scientific (as opposed to
military)<br>
use since the vocabulary was last revised and so an
extension seems<br>
reasonable. The simplest approach to take would be to
add:<br>
remotely piloted aircraft<br>
RPA<br>
A heavier-than-air aircraft without a human pilot aboard
that is<br>
controlled remotely by a human pilot. Also referred to
as a drone or<br>
unmanned aerial vehicle (AUV).<br>
This leaves the way open for autonomous aircraft as a
future L06<br>
addition should the associated legal and liability
issues be resolved.<br>
Comments or alternative suggestions?<br>
Cheers, Roy.<o:p></o:p></p>
<p class="MsoNormal"><br>
<br>
--<br>
*******************************************************<br>
* Nan Galbraith (508) 289-2444 *<br>
* Upper Ocean Processes Group Mail Stop 29 *<br>
* Woods Hole Oceanographic Institution *<br>
* Woods Hole, MA 02543 *<br>
*******************************************************<br>
<br>
<br>
<br>
_______________________________________________<br>
Seavox mailing list<br>
<a moz-do-not-send="true"
href="mailto:Seavox@mailman.nerc-liv.ac.uk">Seavox@mailman.nerc-liv.ac.uk</a><br>
<a moz-do-not-send="true"
href="http://mailman.nerc-liv.ac.uk/mailman/listinfo/seavox">http://mailman.nerc-liv.ac.uk/mailman/listinfo/seavox</a><br>
<br>
This message (and any attachments) is for the recipient
only. NERC is subject to the Freedom of Information Act
2000 and the contents of this email and any reply you
make may be disclosed by NERC unless it is exempt from
release under the Act. Any material supplied to NERC may
be stored in an electronic records management system.<br>
<br>
_______________________________________________<br>
Seavox mailing list<br>
<a moz-do-not-send="true"
href="mailto:Seavox@mailman.nerc-liv.ac.uk">Seavox@mailman.nerc-liv.ac.uk</a><br>
<a moz-do-not-send="true"
href="http://mailman.nerc-liv.ac.uk/mailman/listinfo/seavox">http://mailman.nerc-liv.ac.uk/mailman/listinfo/seavox</a><o:p></o:p></p>
<p class="MsoNormal"><br>
<br>
This message (and any attachments) is for the recipient
only. NERC is subject to the Freedom of Information Act
2000 and the contents of this email and any reply you
make may be disclosed by NERC unless it is exempt from
release under the Act. Any material supplied to NERC may
be stored in an electronic records management system.<br>
<br>
_______________________________________________<br>
Seavox mailing list<br>
<a moz-do-not-send="true"
href="mailto:Seavox@mailman.nerc-liv.ac.uk">Seavox@mailman.nerc-liv.ac.uk</a><br>
<a moz-do-not-send="true"
href="http://mailman.nerc-liv.ac.uk/mailman/listinfo/seavox">http://mailman.nerc-liv.ac.uk/mailman/listinfo/seavox</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Seavox mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Seavox@mailman.nerc-liv.ac.uk">Seavox@mailman.nerc-liv.ac.uk</a>
<a class="moz-txt-link-freetext" href="http://mailman.nerc-liv.ac.uk/mailman/listinfo/seavox">http://mailman.nerc-liv.ac.uk/mailman/listinfo/seavox</a></pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
*******************************************************
* Nan Galbraith Information Systems Specialist *
* Upper Ocean Processes Group Mail Stop 29 *
* Woods Hole Oceanographic Institution *
* Woods Hole, MA 02543 (508) 289-2444 *
*******************************************************
</pre>
</body>
</html>