| |||||||||
Changed: | |||||||||
< < | docx pdf | ||||||||
> > | docx pdf | ||||||||
Current draft with pointers to topics to discuss * release v1.0-20110305-2: | |||||||||
Changed: | |||||||||
< < | docx pdf | ||||||||
> > | docx pdf | ||||||||
The authors could not agree on some important points; others were still
being worked on at the time the current draft of the specification
was released. It was therefore decided to post them on the twiki
(see pages below) for an open discussion. We need to finalize these
soon and we ask for your help. Please find below the list of topics
with indicated the two different perspectives among the co-authors.
Please provide your comments not in this page, but in each of the topic pages listed below:
I am a bit bothered by Collection and I don't know where it came from. If I read the draft correctly, this is an amalgam of datacenter, observatory, telescope, and instrument. This is not necessarily how repositories organize their data. It would be cleaner to keep the concepts separate. I still object to forcing spectral limits in m. If we really (really) want to force a single unit, Hz makes much more sense. Wavelength is unnatural for frequency as well as energy-based data. I am not sure that bibliographic references are helpful since they are likely to be incomplete and unevenly covered. Better leave that to bibliographic services. Event lists are not by themselves multi-file. However, many datasets are by their nature multi-file. What do we do then with the access format, or even datatype? It may be good to say explicitly that exposure time also takes into account deadtime (I mean, excludes it). Release date does not explicitly say "public release" which is confusing. One has to read much further to find out that that is really what is meant. -- ArnoldRots - 22 Mar 2011
|
| |||||||||
Changed: | |||||||||
< < |
| ||||||||
> > |
| ||||||||
I am a bit bothered by Collection and I don't know where it came from. If I read the draft correctly, this is an amalgam of datacenter, observatory, telescope, and instrument. This is not necessarily how repositories organize their data. It would be cleaner to keep the concepts separate. I still object to forcing spectral limits in m. If we really (really) want to force a single unit, Hz makes much more sense. Wavelength is unnatural for frequency as well as energy-based data. I am not sure that bibliographic references are helpful since they are likely to be incomplete and unevenly covered. Better leave that to bibliographic services. Event lists are not by themselves multi-file. However, many datasets are by their nature multi-file. What do we do then with the access format, or even datatype? It may be good to say explicitly that exposure time also takes into account deadtime (I mean, excludes it). Release date does not explicitly say "public release" which is confusing. One has to read much further to find out that that is really what is meant. -- ArnoldRots - 22 Mar 2011 <--
|
| |||||||||
Changed: | |||||||||
< < | |||||||||
> > | |||||||||
Added: | |||||||||
> > |
| ||||||||
| |||||||||
Changed: | |||||||||
< < | pdf Current draft with pointers to topics to discuss | ||||||||
> > | |||||||||
Added: | |||||||||
> > | Current draft with pointers to topics to discuss | ||||||||
* release v1.0-20110305-2:
docx
pdf
The authors could not agree on some important points; others were still
being worked on at the time the current draft of the specification
was released. It was therefore decided to post them on the twiki
(see pages below) for an open discussion. We need to finalize these
soon and we ask for your help. Please find below the list of topics
with indicated the two different perspectives among the co-authors.
Please provide your comments not in this page, but in each of the topic pages listed below:
I am a bit bothered by Collection and I don't know where it came from. If I read the draft correctly, this is an amalgam of datacenter, observatory, telescope, and instrument. This is not necessarily how repositories organize their data. It would be cleaner to keep the concepts separate. I still object to forcing spectral limits in m. If we really (really) want to force a single unit, Hz makes much more sense. Wavelength is unnatural for frequency as well as energy-based data. I am not sure that bibliographic references are helpful since they are likely to be incomplete and unevenly covered. Better leave that to bibliographic services. Event lists are not by themselves multi-file. However, many datasets are by their nature multi-file. What do we do then with the access format, or even datatype? It may be good to say explicitly that exposure time also takes into account deadtime (I mean, excludes it). Release date does not explicitly say "public release" which is confusing. One has to read much further to find out that that is really what is meant. -- ArnoldRots - 22 Mar 2011 <--
|
| |||||||||
Added: | |||||||||
> > | |||||||||
Added: | |||||||||
> > | I am a bit bothered by Collection and I don't know where it came from. If I read the draft correctly, this is an amalgam of datacenter, observatory, telescope, and instrument. This is not necessarily how repositories organize their data. It would be cleaner to keep the concepts separate. | ||||||||
Added: | |||||||||
> > | I still object to forcing spectral limits in m. If we really (really) want to force a single unit, Hz makes much more sense. Wavelength is unnatural for frequency as well as energy-based data. | ||||||||
Added: | |||||||||
> > | I am not sure that bibliographic references are helpful since they are likely to be incomplete and unevenly covered. Better leave that to bibliographic services. | ||||||||
Added: | |||||||||
> > | Event lists are not by themselves multi-file. However, many datasets are by their nature multi-file. What do we do then with the access format, or even datatype? | ||||||||
Added: | |||||||||
> > | It may be good to say explicitly that exposure time also takes into account deadtime (I mean, excludes it). | ||||||||
Added: | |||||||||
> > | Release date does not explicitly say "public release" which is confusing. One has to read much further to find out that that is really what is meant. -- ArnoldRots - 22 Mar 2011 | ||||||||
<--
|
| |||||||||
Added: | |||||||||
> > |
| ||||||||
and feel free to add a new item when needed. Thanks.
<--
|
| |||||||||
Added: | |||||||||
> > |
| ||||||||
and feel free to add a new item when needed. Thanks.
<--
|
| ||||||||
Added: | ||||||||
> > | * release v1.0-20110305-2: docx pdf | |||||||
The authors could not agree on some important points; others were still
being worked on at the time the current draft of the specification
was released. It was therefore decided to post them on the twiki
(see pages below) for an open discussion. We need to finalize these
soon and we ask for your help. Please find below the list of topics
with indicated the two different perspectives among the co-authors.
Please provide your comments not in this page, but in each of the topic pages listed below:
<--
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
and feel free to add a new item when needed. Thanks.
<--
|
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
<--
|
| ||||||||
Deleted: | ||||||||
< < | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Deleted: | ||||||||
< < | ||||||||
and feel free to add a new item when needed. Thanks.
<--
|
| ||||||||
Changed: | ||||||||
< < | This is still being defined. | |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | This attribute, and the general issue of dataset identifiers is well defined and has already been in use in existing standards for several years (e.g., ADS dataset identifiers, IVOA dataset identifiers as defined by the Registry, publisher dataset identifiers and others as used in SSA and Spectrum). However some of the authors felt that existing discussion of usage was needed. One serious issue is that the standard currently specifies that obs_publisher_did cannot be used in a WHERE clause, which defeats the whole idea of a dataset identifier being used to persistently identify and later retrieve or access specific datasets. | |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
<--
|
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > | ||||||||
and feel free to add a new item when needed. Thanks.
<--
|
| ||||||||
Added: | ||||||||
> > |
| |||||||
and feel free to add a new item when needed. Thanks.
<--
|
| ||||||||
Deleted: | ||||||||
< < |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Deleted: | ||||||||
< < |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
<--
|
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
<--
|
| ||||||||
Changed: | ||||||||
< < | Without this it could be very difficult for a human user to understand what a specific data product is. While the quantitative fields are essential for global discovery there is still a need for a human looking at the results of a search to understand what a specific data product is. Furthermore obs_title is already a mandatory field for all existing DAL interfaces, e.g., SIA, SSA. If not a mandatory field of ObsCore it should at least be an optional field. | |||||||
> > |
| |||||||
<--
|
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > | This is still being defined. | |||||||
| ||||||||
Added: | ||||||||
> > | This attribute, and the general issue of dataset identifiers is well defined and has already been in use in existing standards for several years (e.g., ADS dataset identifiers, IVOA dataset identifiers as defined by the Registry, publisher dataset identifiers and others as used in SSA and Spectrum). However some of the authors felt that existing discussion of usage was needed. One serious issue is that the standard currently specifies that obs_publisher_did cannot be used in a WHERE clause, which defeats the whole idea of a dataset identifier being used to persistently identify and later retrieve or access specific datasets. | |||||||
and feel free to add a new item when needed. Thanks.
<--
|
| ||||||||
Changed: | ||||||||
< < | The authors could not agree on some important points. It was therefore decided to post them on the twiki (see pages below) for an open discussion. We need to quickly take the necessary decisions and we ask for your help. Please find below the list of topics | |||||||
> > | The authors could not agree on some important points; others were still being worked on at the time the current draft of the specification was released. It was therefore decided to post them on the twiki (see pages below) for an open discussion. We need to finalize these | |||||||
Added: | ||||||||
> > | soon and we ask for your help. Please find below the list of topics | |||||||
with indicated the two different perspectives among the co-authors.
Please provide your comments not in this page, but in each of the topic pages listed below:
<--
|
| ||||||||
Added: | ||||||||
> > | The authors could not agree on some important points. It was therefore decided to post them on the twiki (see pages below) for an open discussion. We need to quickly take the necessary decisions and we ask for your help. Please find below the list of topics with indicated the two different perspectives among the co-authors. | |||||||
Added: | ||||||||
> > | Please provide your comments not in this page, but in each of the topic pages listed below: | |||||||
Added: | ||||||||
> > |
| |||||||
Deleted: | ||||||||
< < |
| |||||||
and feel free to add a new item when needed. Thanks.
<--
|
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > | docx pdf Current draft with pointers to topics to discuss | |||||||
<--
|
<--
| ||||||||
Added: | ||||||||
> > |
| |||||||
<--
|