[Esip-documentation] Question on licensing of "Attribute Convention for Data Discovery 1.3" wiki page content

[Erin Robinson]

Hi All - In a quick back and forth with Martin, I expressed ESIP's general
desire to not increase barriers to usage. Martin suggested that an ESIP
hosted machine readable version would solve his issues and also allow for
the synchronization as well as solve Apache Software Foundation legal.

I wonder if someone on this list would be willing to make that conversion
from wiki page to XML, JSON or CSV and post this to an esipfed github repo?
I have added Annie Burgess, ESIP Lab director who can make sure this gets
to our organizational GitHub account.

Thanks in advance -
Erin



Erin Robinson
Executive Director
ESIP - Earth Science Information Partners
esipfed.org | 314.369.9954

On Sat, May 26, 2018 at 4:51 PM, Martin Desruisseaux <
martin.desruisseaux at geomatys.com> wrote:

> Le 26/05/2018 à 03:09, Erin Robinson a écrit :
>
> Hi Martin - Taking this off the list briefly to say I would prefer this be
> as simple as possible that you are able to use the entire quote in SIS and
> to not take a long time with bureaucratic hurdles... Do you have a proposed
> solution that might link back or reference the ACDD quote on ESIP wiki? I
> think this is the spirit of our community even if license may have other
> implications.
>
> The documentation already contains links in the "See Also" section. For
> example in [1], there is a "ESIP reference" below each constant. But for
> now those links were inserted and maintained by hand.
>
> If I copy the definitions verbatim, there is still the synchronization
> issue raised earlier in this thread. Also (even if unlikely), users
> downloading an Apache software presume they are allowed to change anything
> in it, including those definitions. A technical alternative may be to have
> those definitions in a machine-readable file hosted on ESIP. It may be as
> simple as key-value pairs, e.g.
>
> title = An identifier for the data set, provided by and unique within its
> naming authority (… etc …)
>
> Or it may be XML or JSON or CSV, at ESIP choice. I could easily parse
> those files and insert the content automatically at
> documentation-generation time. I think this approach would also satisfy the
> Apache Software Foundation on a legal point of view, since the definitions
> would not be in Apache source tree.
>
>     Thanks again!
>
>         Martin
>
> [1] http://sis.apache.org/apidocs/org/apache/sis/storage/netcdf/AttributeNames.html#TITLE
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deltaforce.net/pipermail/esip-documentation/attachments/20180527/83851fa3/attachment.html>