update sect. 4 & 5+ typo correction, harmonize table names #81

loumir · 2025-06-17T15:34:53Z

lighten text in sec. 4 and 5
appendix on new page
table names 'obscore_radio' in appendix and main text.

Bonnarel · 2025-06-18T08:06:42Z

ObsCoreExtensionForRadioData.tex


 Auxiliary datasets such as  \emph{uv} distribution map, dirty beam maps, frequency/amplitude plots, phase/amplitude plots are useful for astronomers to check data quality.

-In that case DataLink \citep{2023ivoa.spec.1215B} may provide a solution to attach these auxiliary data to ObsCore records. The \texttt{semantics} FIELD in the \{link\}
-response  will contain \#auxiliary  for links to these maps or plots while  the \texttt{content\_qualifier} FIELD introduced from 1.1  could contain a term from a defined vocabulary (to be defined) following the IVOA vocabulary definition  \citep{2021ivoa.spec.0525D}.
+In that case,  DataLink \citep{2023ivoa.spec.1215B} may provide a solution to attach these auxiliary data files to ObsCore records. The link , described in  the specification as  \{link\}


La link response c'est la table complete. moi j'enleverai "described in the specification as \link response.

I think it would be clearer if we show an example of the link response with all fields set up .
I did not find any example in the JIVE implementation . may be we can mimic a datalink scenario.

OK I'll create soon

after introducing the example "described in the specification as \link response." should be removed

Bonnarel · 2025-06-18T08:11:45Z

ObsCoreExtensionForRadioData.tex

-When we will have other extensions (for example for time) we may want to 
-discover services which deliver several extensions in addition to obscore 
+When we will have other extensions (for example for time series or high energy data) we may want to 
+discover services which supporting  several extensions in addition to the obscore 


"Which" has also to be removed

Bonnarel · 2025-06-18T08:13:01Z

ObsCoreExtensionForRadioData.tex

 main table.

-This could be done by queries such as  
+Querying ObsTAP services with multiple extensions could be done by querying the relational registry  such as:  


"this way" instead of "such as"

Bonnarel · 2025-07-03T06:36:02Z

ObsCoreExtensionForRadioData.tex

-The largest angular scale is also variable along the spectral range. That's why we bound it with \emph{s\_largest\_angular\_scale\_min} and \emph{s\_largest\_angular\_scale\_max} estimated as  respectively $\lambda\_min/l$ and  $\lambda\_max/l$
-
-
+The largest angular scale is also variable along the spectral range. That's why we bound it with \emph{s\_largest\_angular\_scale\_min} and \emph{s\_largest\_angular\_scale\_max} estimated as  respectively $\lambda\_min/l$ and  $\lambda\_max/l$F


estimated at

Bonnarel · 2025-07-03T06:39:51Z

ObsCoreExtensionForRadioData.tex


 Auxiliary datasets such as  \emph{uv} distribution map, dirty beam maps, frequency/amplitude plots, phase/amplitude plots are useful for astronomers to check data quality.

-In that case DataLink \citep{2023ivoa.spec.1215B} may provide a solution to attach these auxiliary data to ObsCore records. The \texttt{semantics} FIELD in the \{link\}
-response  will contain \#auxiliary  for links to these maps or plots while  the \texttt{content\_qualifier} FIELD introduced from 1.1  could contain a term from a defined vocabulary (to be defined) following the IVOA vocabulary definition  \citep{2021ivoa.spec.0525D}.
+In that case,  DataLink \citep{2023ivoa.spec.1215B} may provide a solution to attach these auxiliary data files to ObsCore records. The link , described in  the specification as  \{link\}


after introducing the example "described in the specification as \link response." should be removed

Bonnarel · 2025-07-03T06:42:20Z

ObsCoreExtensionForRadioData.tex

+all columns described in following tables ~\ref{tab:ExtensionAtt} , ~\ref{tab:ExtensionAtt_interferometry} and \ref{tab:ExtensionAtt_instrumental} must be gathered  in the \verb|ivoa.obscore_radio|
+table, although some of them may be NULL if no value apply . At least a foreign key into \verb|ivoa.obscore| will typically
+make the extension table user-visible. 
+%Additional free columns (such as \emph{f\_min}, \emph{f\_max} ) may also be added.


Why suppressing this

recent discussions about obscore : optional columns need extra processing on the client side .
if we speak about f_min, f_max , they should be properly defined in the standard in order to be comparable .
free is anything while optional is defined ans sometimes not filled.

Bonnarel · 2025-07-03T06:43:45Z

ObsCoreExtensionForRadioData.tex

-When we will have other extensions (for example for time) we may want to 
-discover services which deliver several extensions in addition to obscore 
+When we will have other extensions (for example for time series or high energy data) we may want to 
+discover services which supporting  several extensions in addition to the ObsCore 


remove "which"

Bonnarel · 2025-07-03T06:45:48Z

ObsCoreExtensionForRadioData.tex

@@ -800,14 +751,12 @@ \section{Registry Aspects}
 \hbox{\nolinkurl{ivo://ivoa.net/std/ObsCore#timeExt-1.0}}
 $$

-In addition the schema containing the ObsCore main table and potentially some of the  extensions
+In addition the TAP schema containing the ObsCore main table and potentially some of the  extensions


It is not the TAP_ schema but a tableset schema.

loumir

replaced by 'tableset schema'

Bonnarel

I approve these changes

loumir added 3 commits June 17, 2025 17:31

update sect. 4 & 5+ typo correction, harmonize table names

145d411

update_section_4.5

9a4dd85

end commit

90d05c6

loumir requested a review from Bonnarel June 17, 2025 17:20

Bonnarel reviewed Jun 18, 2025

View reviewed changes

loumir added 2 commits June 18, 2025 11:51

update on sect. 4 &5 : iteration

9ba8807

typo corrections sect.5

71bbd4b

loumir requested a review from Bonnarel June 18, 2025 15:11

scan mode definition update wrt Alessandra suggestion

e424262

Bonnarel requested changes Jul 3, 2025

View reviewed changes

datalink example table and corrections in texte

05cf9fb

loumir requested a review from Bonnarel July 3, 2025 13:19

tableset schema mentionned in registry part

afd2f6f

loumir commented Jul 3, 2025

View reviewed changes

data link table update

35083b7

Bonnarel approved these changes Jul 3, 2025

View reviewed changes

Bonnarel merged commit 2469d06 into ivoa-std:main Jul 3, 2025
1 check passed

		The largest angular scale is also variable along the spectral range. That's why we bound it with \emph{s\_largest\_angular\_scale\_min} and \emph{s\_largest\_angular\_scale\_max} estimated as respectively $\lambda\_min/l$ and $\lambda\_max/l$


		The largest angular scale is also variable along the spectral range. That's why we bound it with \emph{s\_largest\_angular\_scale\_min} and \emph{s\_largest\_angular\_scale\_max} estimated as respectively $\lambda\_min/l$ and $\lambda\_max/l$F

update sect. 4 & 5+ typo correction, harmonize table names #81

update sect. 4 & 5+ typo correction, harmonize table names #81

Uh oh!

Conversation

loumir commented Jun 17, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

loumir left a comment

Choose a reason for hiding this comment

Uh oh!

Bonnarel left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!