[Esip-documentation] ACDD adjudication meeting today!
Nan Galbraith via Esip-documentation
esip-documentation at lists.esipfed.org
Tue Oct 14 14:18:04 EDT 2014
I don't think I can make the meeting, but I need to urge you to remove the
word 'original' from Bob S's proposed definition of 'date_created'.
This would be a SUBSTANTIAL change from the original definition, and makes
my existing metadata wrong; furthermore this definition makes the term
useless
for many observational data sets. The date on which a real time data set was
'originally created' is not something anyone keeps track of for real
time data.
Original: The date on which the data was created.
IMHO, this is fine, because it leaves the term 'created' open to the
data-writer's
own common sense.
I also like the idea of adding date_metadata_modified, which, for in
situ data,
completes the timeline information any user really needs.
If the other proposed terms in the time category are approved, I hope
they'll
be 'suggested', not 'recommended', because I think a perfectly
well-documented
NetCDF file can be written without any of them.
On 10/14/14 1:22 PM, John Graybeal via Esip-documentation wrote:
> Hi everyone,
>
> Sorry for the late reminder, but we are having our third and hopefully
> final ACDD adjudication meeting today. It will be at the usual time (2
> PM Eastern, 11 AM Pacific). *Call-in details below* (here's a direct
> webex link
> <https://esipfed.webex.com/esipfed/j.php?MTID=ma90918bfe9b294558a752bf043b4b25a>).
> The results get forwarded to the ESIP Documentation Cluster full
> meeting on Thursday.
>
> We have five topics to approve or discuss, and will deal with them in
> the following order:
>
> (1) *contributor_role*: (row 38, column G of Version Changes
> <https://docs.google.com/spreadsheets/d/19fl5AgGkckG03yTchUjYUp4YnR09Fn1Nqps2KHenkC4/edit#gid=849563469>):
> proposed consent item, updating text
>
> Added the text "Multiple roles should be presented in the same order
> and number as the names in contributor_names." This was to address the
> issue raised: "Need guidance on how to format the role values so they
> are associated with the corresponding name values, such as use same
> index in each attribute array. _Philip jones"
>
> (2) *program *(row 29, columns G/I of Version Changes
> <https://docs.google.com/spreadsheets/d/19fl5AgGkckG03yTchUjYUp4YnR09Fn1Nqps2KHenkC4/edit#gid=849563469>): Newly
> proposed attribute and defintion(s):
>
> original proposal:
> "The overarching program(s) of which the dataset is a part."
> proposed replacement:
>
> "A program consists of a set (or portfolio) of related and possibly
> interdependent projects that meet an overarching objective. Examples:
> GHRSST, NOAA CDR, NASA EOS, JPSS, GOES-R."
>
> (3) Geospatial Bounds attributes:
>
> 3A) *geospatial_bounds* **(row 38, column G of Version Changes
> <https://docs.google.com/spreadsheets/d/19fl5AgGkckG03yTchUjYUp4YnR09Fn1Nqps2KHenkC4/edit#gid=849563469>):
> Newly proposed definition
>
> 3B) *geospatial_vertical_units* (row 45, column G of Version Changes
> <https://docs.google.com/spreadsheets/d/19fl5AgGkckG03yTchUjYUp4YnR09Fn1Nqps2KHenkC4/edit#gid=849563469>):
> Proposed for consent (complex definition)
>
> 3C) *geospatial_vertical_positive * (row 45, column G of Version
> Changes
> <https://docs.google.com/spreadsheets/d/19fl5AgGkckG03yTchUjYUp4YnR09Fn1Nqps2KHenkC4/edit#gid=849563469>):
> Proposed for consent (minor addition)
>
> 3D) *geospatial_*_units* (rows 47 & 49, column G of Version Changes
> <https://docs.google.com/spreadsheets/d/19fl5AgGkckG03yTchUjYUp4YnR09Fn1Nqps2KHenkC4/edit#gid=849563469>):
> Proposed for consent (minor change)
>
> (4) Datestamp and Timestamp attributes
>
> We will work with the Datestamps
> <https://docs.google.com/spreadsheets/d/19fl5AgGkckG03yTchUjYUp4YnR09Fn1Nqps2KHenkC4/edit#gid=1933494942> spreadsheet
> in discussing this item. We will follow this sequence:
> (a) Determine if we can agree on any improvements to date_created,
> date_modified, and date_issued definitions.
> (b) Determine if we can agree on any additional attributes.
> (c) Determine if we can agree on any other changes, e.g., to the
> Attribute Content Guidance.
>
> For 4c, we will use the text in the 1.3 document
> <http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3> for
> the discussion.
>
> (5) Any remaining topics or concerns.
>
> See you on the call.
>
> John
>
> =================
>
> -----------------------------------------------------------------------------------------------
> To Join the online portion of the Personal Conference meeting
> -----------------------------------------------------------------------------------------------
> 1. Go to https://esipfed.webex.com
> 2. Click the "Meeting Center" tab
> 3. Select the YOUR MEETING NAME
> If a password is required, enter the Meeting Password: 23138372
>
> -----------------------------------------------------------------------------------------------
> To start the audio portion of the Personal Conference meeting w/ phone
> -----------------------------------------------------------------------------------------------
> Call-in toll-free number (US/Canada): 1-877-668-4493
> Call-in toll number (US/Canada): +1-408-600-3600
> Call-in toll number (US/Canada)*: +1-571-918-6008
> Global call-in numbers:
> https://esipfed.webex.com/esipfed/globalcallin.php?serviceType=MC&ED=9910728&tollFree=1
> Toll-free dialing restrictions:
> http://www.webex.com/pdf/tollfree_restrictions.pdf
>
> Attendee access code: 231 383 72
>
>
>
> _______________________________________________
> Esip-documentation mailing list
> Esip-documentation at lists.esipfed.org
> http://www.lists.esipfed.org/mailman/listinfo/esip-documentation
--
*******************************************************
* Nan Galbraith Information Systems Specialist *
* Upper Ocean Processes Group Mail Stop 29 *
* Woods Hole Oceanographic Institution *
* Woods Hole, MA 02543 (508) 289-2444 *
*******************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.esipfed.org/pipermail/esip-documentation/attachments/20141014/35d8b118/attachment-0001.html>
More information about the Esip-documentation
mailing list