Hi,
For the Hibernate docs it might be fine since it's non-profit derivative
work.
But I always follow this rule on my blog or in my book because it's better
to be safe than sorry.
The "fair use" might give you a safety hook but ultimately it is the
license agreement that matters the most.
In the JPA spec case we are fine because of the following clause:
"(iii) excerpting
brief portions of the Specification in oral or written communications which
discuss the Specification provided
that such excerpts do not in the aggregate constitute a significant portion
of the Specification."
Vlad
On Thu, Jan 7, 2016 at 12:21 PM, Hardy Ferentschik <hardy(a)hibernate.org>
wrote:
Hi,
> > The JPA specs are under copyright, so instead of quoting we should just
> > provide the section and
> > make a summary in our own wording.
>
> I don't think that's needed, in addition it'd do more harm than good.
> The specific wording makes a difference, summarizing it in your own
> words is already an interpretation which may or may not alter the
> exact semantics.
+1 I would have the same fear. As Gunnar is saying, the specific wording
might be important.
For what it's worth, I quote quite regularly from the Bean Validation spec
when answering Validator/Bean Validation questions. As long as you make
clear
where it is coming from, I don't see a problem here.
--Hardy