search

valentinedwv / ioostech

Automatically exported from code.google.com/p/ioostech
0 stars 0 forks source link

Update guidance for observing asset identifiers. #37

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Update the document at 
https://geo-ide.noaa.gov/wiki/index.php?title=IOOS_Conventions_for_Observing_Ass
et_Identifiers  to include new information.  Move document from draft to final 
pending input from SOS Reference Implementation team.

Original issue reported on code.google.com by dpsnowde...@gmail.com on 23 Oct 2012 at 9:49

GoogleCodeExporter commented 8 years ago

Original comment by dpsnowde...@gmail.com on 24 Oct 2012 at 12:57

GoogleCodeExporter commented 8 years ago

Original comment by dpsnowde...@gmail.com on 30 Jan 2013 at 5:04

GoogleCodeExporter commented 8 years ago 
There has been no discussion of this item so I am inclined to close this issue. 
 At this point, I'm not sure exactly what problem would be solved by updating 
the guidance.  There is currently not a uniform application of this guidance 
across the services that currently exist so that's one problem.  Not sure a new 
document would change that though.  I'llclose this if I don't here comments by 
Friday 2/15/2013.

Original comment by dpsnowde...@gmail.com on 13 Feb 2013 at 9:22

GoogleCodeExporter commented 8 years ago 
This issue seemed to be about updating specifically the Geo-IDE asset urn 
document, as opposed to documenting the refined asset urn scheme/conventions we 
discussed and settled on last year. The latter is very important, but I'd say 
it's also taken care of, mostly. See
http://code.google.com/p/ioostech/wiki/SOSGuidelines#Asset_URN_identifiers
Sure, that documentation could be improved; right now it's only a summary, and 
you have to follow the links to Issues (14 & 5) and ioos_tech discussions to 
get all the details.
But whether the Geo-IDE document itself should be updated (or an equivalent, 
very detailed and self-contained page created on the ioostech wiki) is a much 
narrower issue. If you want the latter, keep the issue open. Otherwise I'd 
suggest closing it and leaving the task of improving the asset urn 
documentation as part of the broader task of improving all documentation. My 2 
cents.

Original comment by emilioma...@gmail.com on 14 Feb 2013 at 6:29

GoogleCodeExporter commented 8 years ago

Original comment by dpsnowde...@gmail.com on 19 Feb 2013 at 7:35