From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: remove DRM
Date: Tue, 16 May 2023 09:19:26 -0400 [thread overview]
Message-ID: <fc9f55bb-b7c8-6c69-e8f9-e6c390963c7b@usa.net> (raw)
In-Reply-To: <646371e9.050a0220.c7b5.0786-ATjtLOhZ0NVl57MIdRCFDg@public.gmane.org>
On 5/16/23 8:07 AM, Rich Cook wrote:
> No it wouldn't. Since I paid for the product. Which is public domain
> because it is a government publication.
For what it's worth - that's not actually relevant in many places. The
law is against removing the DRM, not against making it easy to pirate,
or sharing it, etc. Ownership status doesn't matter.
Of course: I am not a laywer, double-check your relevant statues,
excptions, case law, etc.
Daniel T. Staal
--
---------------------------------------------------------------
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------
prev parent reply other threads:[~2023-05-16 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 11:00 Rich Cook
[not found] ` <4b2ac7e9-8656-4d21-b9c8-59808739fa54n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-16 11:02 ` Sukil Etxenike arizaleta
[not found] ` <4120942c-9419-3a39-3dc2-c05a681948f3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-05-16 12:07 ` Rich Cook
2023-05-16 11:05 ` Leonard Rosenthol
[not found] ` <CALu=v3+1LOQbZFfV4zW3jD0R1OTmpmrzrQ7gJMsGUZ6Lr1MS-g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-05-16 12:07 ` Rich Cook
[not found] ` <646371e9.050a0220.c7b5.0786-ATjtLOhZ0NVl57MIdRCFDg@public.gmane.org>
2023-05-16 13:19 ` Daniel Staal [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc9f55bb-b7c8-6c69-e8f9-e6c390963c7b@usa.net \
--to=dstaal-jdbf3xikgs8@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).