[Esip-discovery] Reminder: ESIP Discovery Telecon Tuesday, December 11 at 4:00 ET / 3:00 CT / 2:00 MT / 1:00 PT

Thu Dec 13 15:17:27 EST 2012

As it stands right now, things that are registered in the ESIP Commons are
done under CC 0 License meaning they are free for use, remix and repurpose
(I just gave a talk last night on this, so it's fresh) as long as
attribution is given.  This means that an agency like NASA can take the
document cite that it came from ESIP, modify, if needed, to fit NASA - SPG
specific needs. At this point, the evolution of the doc may fork and that
is ok, by collaborating up front and creating a doc with larger than NASA
buy-in to begin with, NASA has saved $$ having to work through this alone.

There would be some overhead if the agency decides to keep up with ESIP
modifications/updates, but I'd still argue the expense of maintaining a
current version is much less then having to come up with the content
internally from scratch and then ensure it's viable/in synch with larger
community (an example would be working with Drupal vs. building your own
CMS and hoping it works...)

Just my 2 cents.

E

On Thu, Dec 13, 2012 at 2:41 PM, Mattmann, Chris A (388J) <
chris.a.mattmann at jpl.nasa.gov> wrote:

>  Hey Guys,
>
>  My opinion here is that it depends on if there is a single master
> document, and how copies, interpretations and replicas are handled and
> governed. There is probably nothing to say that there couldn't be multiple
> versions (and interpretations) of the same document, hosted at different
> institutions. This introduces overhead as to which one someone is using,
> but there are less technical impediments to that (the answers to which have
> been engineered by the same folks participating in these conversations,
> funny enough). Ultimately the answer to that will be probably be driven
> socially, economically, or by other means at least in these distributed
> organizations (NASA, ESIP, etc.) :)
>
>  Cheers,
> Chris
>
>   From: <Hua>, "Hook (388C)" <hook.hua at jpl.nasa.gov>
> Date: Thursday, December 13, 2012 10:39 AM
> To: Erin Robinson <erinrobinson at esipfed.org>, Christopher Lynnes <
> christopher.s.lynnes at nasa.gov>
>
> Cc: Chris Lynnes <lynnes at eosdata.gsfc.nasa.gov>, "
> esip-discovery at lists.esipfed.org" <esip-discovery at lists.esipfed.org>
> Subject: Re: [Esip-discovery] Reminder: ESIP Discovery Telecon Tuesday,
> December 11 at 4:00 ET / 3:00 CT / 2:00 MT / 1:00 PT
>
>   This raises an interesting question of where should the master document
> (and therefore citation) be hosted? The organization that is creating a
> spec (ESIP), or the organization approving of the spec (NASA SPG)?
>
>  For this case being an RFC for an ESIP Discovery spec, I'm more inclined
> for ESIP to host the citation on ESIP Commons.
>
>  One benefit of ESIP Commons is that there would be a DOI for the
> document.
>
>  Also SPG is a NASA-oriented process, while the Discovery RFC is broader.
> Interesting questions…
>
>  --Hook
>
>
>
>   From: Erin Robinson <erinrobinson at esipfed.org>
> Date: Thu, 13 Dec 2012 13:03:28 -0500
> To: Christopher Lynnes <christopher.s.lynnes at nasa.gov>
> Cc: Chris Lynnes <lynnes at eosdata.gsfc.nasa.gov>, "
> esip-discovery at lists.esipfed.org" <esip-discovery at lists.esipfed.org>
> Subject: Re: [Esip-discovery] Reminder: ESIP Discovery Telecon Tuesday,
> December 11 at 4:00 ET / 3:00 CT / 2:00 MT / 1:00 PT
>
>  Just because SPG adopts doesn't preclude it from also being ESIP adopted.
> My point in bringing this up is that having it adopted by both may enable
> other orgs to adopt as well, hypothetically if NOAA had an equivalent of
> SPG and also wanted to adopt. This is similar to what's happening with the
> ESIP Data Citation Guidelines - ESIP approved and in the last year they
> were adopted by other orgs who want their own data citation guidelines.
>
>
>
>
>
> On Thu, Dec 13, 2012 at 1:00 PM, Lynnes, Christopher S. (GSFC-6102) <
> christopher.s.lynnes at nasa.gov> wrote:
>
>>
>>  On Dec 13, 2012, at 12:43 PM, Erin Robinson wrote:
>>
>> All -
>>
>>  Are the approved RFC's something that should go into the ESIP Commons?
>> I'm thinking that citing an esipfed website may be more appropriate than a
>> google doc.
>>
>>  Further - it would be great to have an identifier and recommended
>> citation for others that may run across the RFC and also want to cite it
>> beyond core members of this group.
>>
>>  Thoughts?
>>
>>
>>  It's a logical place for it, but SPG already has their own publication
>> mechanism and site.  In this case, perhaps a compromise would be for us to
>> author a How-To article based on the RFC.
>>
>>
>>  E
>>
>> *Erin Robinson*
>> Information and Virtual Community Director
>> Foundation for Earth Science | 314.369.9954 | erinrobinson at esipfed.org
>> www.esipfed.org
>> [image: Facebook]<http://www.facebook.com/pages/Federation-of-Earth-Science-Information-Partners-ESIP/150015055044779>
>>  [image: Twitter] <http://www.twitter.com/ESIPFed> [image: Vimeo]<http://www.vimeo.com/esipfed>
>>
>>
>>
>> On Thu, Dec 13, 2012 at 12:25 PM, Ruth Duerr <rduerr at nsidc.org> wrote:
>>
>>> Hi Hook, Chris, James,
>>>
>>>  I am referencing the RFC in a paper I am writing. Is it fair to say
>>> that this RFC will be submitted to the NASA SPG for approval?  Also, what
>>> will the reference look like?  At the moment I am thinking:
>>>
>>> 1.        Lynnes, C., Hua, H., and J. Gallagher. ESIP Discovery
>>> Conventions. (in preparation).
>>> https://docs.google.com/document/d/1ymt5vsP2jw2YMVnc2B8uEI0BKTHcT4jSNVQzruLIFPA/edit
>>> Thanks,
>>>
>>>  Ruth
>>>
>>>
>>>    On Dec 11, 2012, at 12:49 PM, Hua, Hook (388C) wrote:
>>>
>>>  For our second topic today, we will be setting up a mechanism to track
>>> the implemented feature sets of the ESIP Discovery RFC [1]. To jump start
>>> our discussion, I've created an initial version of a spreadsheet [2] to
>>> help us track which features of the RFC are supported by each
>>> implementation.
>>>
>>>  [1]
>>> https://docs.google.com/document/d/1ymt5vsP2jw2YMVnc2B8uEI0BKTHcT4jSNVQzruLIFPA/edit
>>> [2]
>>> https://docs.google.com/spreadsheet/ccc?key=0AlQ95ca89UmYdEF2V2pFQjl6WFM3U0lRVGM5eXAzWFE#gid=0
>>>
>>>  We can discuss what else is needed and solicit implementors to help
>>> fill out the spreadsheet.
>>>
>>>  --Hook
>>>
>>>
>>>
>>>   From: Christopher Lynnes <christopher.s.lynnes at nasa.gov>
>>> Date: Tue, 11 Dec 2012 13:10:57 -0600
>>> To: "esip-discovery at lists.esipfed.org" <esip-discovery at lists.esipfed.org
>>> >
>>> Subject: [Esip-discovery] Reminder: ESIP Discovery Telecon Tuesday,
>>> December 11 at 4:00 ET / 3:00 CT / 2:00 MT / 1:00 PT
>>>
>>>   Hi Everyone,
>>> The next Discovery cluster telecon* *is today, Tuesday, December 11 at
>>> 4:00 ET.  Agenda and call details are below and posted on the wiki (
>>> http://wiki.esipfed.org/index.php/Discovery_Telecon_2012-12-11).
>>> If you have additional topics, e-mail this list or you can edit the site
>>> directly.
>>> *Agenda*
>>>
>>>  1) Winter Meeting Planning
>>> 2) Feature Set Tracking for Discovery Implementations
>>>
>>>  *Call Details*
>>>  To start or join the online portion of the meeting:
>>>
>>> https://esipfed.webex.com/mw0306ld/mywebex/default.do?siteurl=esipfed&service=1
>>>
>>>    1. Click join next to the meeting name. (Note: If the meeting has
>>>    not yet started, join will not be visible, and it will say 'Display Info'.
>>>    Wait a minute and refresh screen)
>>>    2. Enter your name and email address
>>>    3. If you are asked for a password, enter the access code: 231 407 50 with
>>>    no spaces or #.
>>>
>>> To join the audio portion of the Conference meeting:
>>> Call-in toll-free number (US/Canada): 1-877-669-3239Attendee access
>>> code: 231 407 50#
>>>
>>>  _______________________________________________
>>> Esip-discovery mailing list
>>> Esip-discovery at lists.esipfed.org
>>> http://www.lists.esipfed.org/mailman/listinfo/esip-discovery
>>>  _______________________________________________ Esip-discovery mailing
>>> list Esip-discovery at lists.esipfed.org
>>> http://www.lists.esipfed.org/mailman/listinfo/esip-discovery
>>> _______________________________________________
>>> Esip-discovery mailing list
>>> Esip-discovery at lists.esipfed.org
>>> http://www.lists.esipfed.org/mailman/listinfo/esip-discovery
>>>
>>>
>>>
>>> _______________________________________________
>>> Esip-discovery mailing list
>>> Esip-discovery at lists.esipfed.org
>>> http://www.lists.esipfed.org/mailman/listinfo/esip-discovery
>>>
>>>
>>  _______________________________________________
>> Esip-discovery mailing list
>> Esip-discovery at lists.esipfed.org
>> http://www.lists.esipfed.org/mailman/listinfo/esip-discovery
>>
>>
>>     --
>> Dr. Christopher Lynnes     NASA/GSFC, Code 610.2    phone: 301-614-5185
>>  "Perfection is achieved, not when there is nothing left to add, but
>> when there is nothing left to take away" -- A. de Saint-Exupery
>>
>>
>>
>>
>>
>>
>>
>  _______________________________________________ Esip-discovery mailing
> list Esip-discovery at lists.esipfed.org
> http://www.lists.esipfed.org/mailman/listinfo/esip-discovery
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.esipfed.org/pipermail/esip-discovery/attachments/20121213/d4d345c9/attachment-0001.html>