Sender: |
|
Date: |
Tue, 5 Feb 2019 10:32:18 -0500 |
Reply-To: |
|
Message-ID: |
|
Subject: |
|
MIME-Version: |
1.0 |
Content-Transfer-Encoding: |
quoted-printable |
In-Reply-To: |
|
Content-Type: |
text/plain; charset="UTF-8" |
From: |
|
Parts/Attachments: |
|
|
On Tue, Feb 5, 2019 at 6:20 AM Peter Armitage <[log in to unmask]>
wrote:
>
> Also, as you noted on Feb. 1st, “[a]t 11 Colonies the Apiary automatically
> comes under a Commercial classification and must meet the requirement of 3
> miles from another commercial beekeepers apiary. MT in 2018 had nearly
> 6000 registered apiary locations which are located by GPS or to the nearest
> quarter section. THE MAPS ARE PUBLIC, ONLINE" (my emphasis in caps).
>
> The public nature of your apiary locations is of interest to me. How is
> the public right to know about apiary locations reconciled with your
> privacy rights which are embedded in the State of Montana Constitution,
> Article II, section 10?
>
> In my part of North America (Newfoundland and Labrador), we have privacy
> legislation which makes it impossible for government to publicize apiary
> locations. One of the absurd consequences of this is that we have not been
> able to know the location of quarantine zones. In 2016 we had two or more
> quarantine zones established around apiaries with packaged bees imported
> from Western Australia. The IDs of the importing beekeepers and their
> apiaries were a personal and state secret. Nonetheless, their IDs were
> determined by other means, not communications from government or the beeks
> themselves. In one case, I’m pretty certain the quarantine was established
> in an area with nearby apiaries and overlapping hb flight zones. Moreover,
> any beek could move colonies in and out of the quarantine zone without
> knowledge of the existence of the quarantine. Personal privacy trumped the
> interests of other beekeepers. I can’t see this changing without a
> legal/court challenge, but who wants to spend the bucks on that?
>
This issue is of particular interest to me with my work in building
software systems for beekeepers and my engagement with the broader
technology ecosystem. It seems to me that many systems are built (and
maybe legislation created) that do not take into consideration legitimate
privacy concerns. These systems and the legislation/organizations that
prompt their development then end up containing information that they don't
really need to do their job and creates a privacy liability. We (hive
tracks people) recently wrote a couple of articles in Bee Culture about
data sharing and the risks associated with it for both hobby and commercial
beekeepers and presented ideas for addressing the issue.
There are technology solutions that can preserve the privacy of individuals
while also serving up data to address the problems you have been
discussing. But these solutions require time/energy/$ to be created by
people/orgs who want the systems to meet those requirements.
James
--
James Wilkes
Hive Tracks <http://www.hivetracks.com> CEO and Chief Science and
Technology Officer
***********************************************
The BEE-L mailing list is powered by L-Soft's renowned
LISTSERV(R) list management software. For more information, go to:
http://www.lsoft.com/LISTSERV-powered.html
|
|
|