https://wiki.code4lib.org/index.php?action=history&feed=atom&title=Technical_implications_of_the_The_Lyon_DeclarationTechnical implications of the The Lyon Declaration - Revision history2026-04-28T14:58:51ZRevision history for this page on the wikiMediaWiki 1.26.2https://wiki.code4lib.org/index.php?title=Technical_implications_of_the_The_Lyon_Declaration&diff=42040&oldid=prevStuartyeates: start article2014-11-12T02:32:11Z<p>start article</p>
<p><b>New page</b></p><div>This is a wiki page looking at some of the implications of the [http://www.lyondeclaration.org/ The Lyon Declaration] to technical work in libraries. The hope is that we can use the Lyon Declaration to push what is already best practise<br />
<br />
{| class="wikitable"<br />
|-<br />
! Clause<br />
! Text<br />
! Implication<br />
|-<br />
| 6a <br />
| Acknowledging the public's right to access information and data, while '''respecting the right to individual privacy.'''<br />
| Since HTTP offers no privacy, this implies a right to access via HTTPS<br />
|-<br />
| 6a <br />
| Acknowledging the '''public's right to access information and data''', while respecting the right to individual privacy.<br />
| Since HTTPS is certainly a barrier to accessing inforamtion, particularly for those in the third world or on very out-of-date platforms, this implies a right to access via HTTP.<br />
|-<br />
| <br />
| <br />
| <br />
|}</div>Stuartyeates