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

[Annie Burgess]

Hi John, all -

The thread didn't end with a resolution. Based on your proposed solution
(CEDAR), I wonder if others think that is a potential path forward OR if
we should set up space (outside of email) for more discussion about Mark's
previous questions related to hosting on the ESIP wiki:

*1. **Is there a management layer around*





*http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery
<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery>?2.
Is there a controlled document that manages any change to the list of names
of the attributes and their definitions?3. How would a change be managed?
* an addition of a new attribute name?*
*  * a new attribute name? *
*4. From the perspective of managing the information, what happens once a
change is agreed?*




* * What content is changed? * Is there a controlled document that is
considered the authoritative source? * Is a change made to a live web page
by an authorized user? * Is there a record of these changes? * Is there a
'tag' that points to a particular release? (how may we compare ACDD-1.1
with ACDD-1.3)*

Annie Burgess, PhD

ESIP Lab Director | Earth Science Information Partners (ESIP)

www http://esipfed.org | phone 585.738.7549

*Sign up for the monthly ESIP Lab update here <http://eepurl.com/dtKL8z>.*

*See the most recent update here
<https://mailchi.mp/esipfed/esip-lab-a-virtual-earth-science-tech-space-2668717>.*




On Sun, Sep 16, 2018 at 4:52 PM John Graybeal via Esip-documentation <
esip-documentation at lists.esipfed.org> wrote:

> Hi Erin, all,
>
> Did this ever get addressed?  If you are just talking about defining
> fields in a computable form, I could put the whole thing into CEDAR (
> metadatacenter.org) fairly quickly. Unfortunately the specification this
> produces is in JSON Schema, not triples.  But it would be on-line and
> public, and you could host the schema file on the ESIP site.
>
> John
>
>
> ---------------------------------------
> John Graybeal
> jbgraybeal at mindspring.com
> 650-450-1853
>
>
> On Jun 4, 2018, at 06:17, Erin Robinson via Esip-documentation <
> esip-documentation at lists.esipfed.org> wrote:
>
> Hi Martin - We used to have semantic mediawiki working which would have
> spit out RDF triples for these things. It seems to be not working with our
> last upgrade. We will figure out a solution ASAP for a machine-readable
> file and get this to you.
>
> E
>
> Erin Robinson
> Executive Director
> ESIP - Earth Science Information Partners
> esipfed.org | 314.369.9954
>
> On Sun, May 27, 2018 at 9:26 AM, Martin Desruisseaux <
> martin.desruisseaux at geomatys.com> wrote:
>
>> Le 27/05/2018 à 14:20, Ted Habermann a écrit :
>>
>>
>> Not sure what this looks like in XML, JSON, or CSV… Would MarkDown work?
>> Seems more natural…
>>
>> The intent is not to replace the wiki. It would be a copy of tables below
>> "Global Attributes" section (only the tables, not the discussion before it)
>> for consumption by machines rather than human. It could be something like
>> that (other formats like CSV or XML would work as well, I'm neutral on
>> that):
>>
>> title = A short phrase or sentence describing the dataset. In many discovery systems (…)summary = A paragraph describing the dataset, analogous to an abstract for a paper.keywords = A comma-separated list of key words and/or phrases. Keywords may be (…)
>>
>> It would allow external projects to insert automatically this
>> documentation in their project at build time (in Apache SIS, I would use a
>> custom javadoc tag for that purpose). If ESIP update their documentation,
>> the updates would be reflected in external project documentation too.
>>
>> The inconvenient is that if the wiki is updated, ESIP would need to
>> remember to update above file accordingly, and conversely.
>>
>>     Martin
>>
>>
>>
> _______________________________________________
> Esip-documentation mailing list
> Esip-documentation at lists.esipfed.org
> http://lists.deltaforce.net/mailman/listinfo/esip-documentation
>
>
> _______________________________________________
> Esip-documentation mailing list
> Esip-documentation at lists.esipfed.org
> https://lists.esipfed.org/mailman/listinfo/esip-documentation
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.esipfed.org/pipermail/esip-documentation/attachments/20180918/a89e248b/attachment.html>