<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Outlook is a terrible mail client. In case it wasn’t clear, I was quoting from the current FITS standard. To repeat, from section 4.1.2.3:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><i>“The mandatory FITS keywords defined in this Standard
</i>must<i> </i>not<i> appear more than once within a header. All other keywords that have a value
</i>should<i> </i>not<i> appear more than once. If a keyword does appear multiple times with different values, then the value is indeterminate.”</i><i><o:p></o:p></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">And REFERENC= T violates section 4.4.2.3. Also, rather than define a separate table for each type of metadata, FITS could retire the entire header metadata model (beyond structural keywords) in favor of whatever normalized set of metadata
bintables can best represent a complete modern data model.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Many discussions over the years, e.g., at ADASS, have been in support of building near-eternal astronomical data archives. During the early days of FITS, this was supported by its documentation being published in paper journals. I don’t
know what digital journals are planning for long-term preservation, but they certainly should plan for their intellectual property to survive their own inevitable bankruptcies whenever some vulture capitalist comes along.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Note that abstract submission is open for ADASS XXXIII: <a href="https://adass2023.lpl.arizona.edu">
https://adass2023.lpl.arizona.edu</a>, registration will open soon. This discussion is already a good start at the agenda for the FITS BoF. Somebody should submit an abstract.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Remind me not to be buried in the Netherlands.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Rob<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">On 8/4/23, 1:16 AM, "fitsbits" wrote:</p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
Why not define an extension table "REFERENCES"?<br>
This will allow multiple references to the same underlying data<br>
as well as references to multiple data sets, e.g. calibration tables<br>
used to reduce the current data.<br>
<br>
A row in the table might include the following columns:<br>
<br>
RELEVANCE (To what does this reference refer.)<br>
TYPE (DOI, ESO Archive, VIZIER ...)<br>
REFERENCE (specific link)<br>
KEYWORDS (necessary keys to find data in an archive)<br>
<br>
..<br>
<br>
<br>
You might include a keyword:<br>
REFERENC = T<br>
in the main header to indicate that the table exists.<br>
<br>
As to DOI dropping links if you don't pay the rent, this reminds me of <br>
the<br>
Dutch graveyard policy of disinterring the remains of deceased whose<br>
relatives have not paid the rent and dumping them in a common bone pit.<br>
<br>
However, it is absurd to think that any archive is eternal. What<br>
happens to astronomical literature links if Springer or IOPscience go <br>
bankrupt?<br>
<br>
<br>
Walter<br>
<br>
On 2023-08-04 09:43, Mark Calabretta via fitsbits wrote:<br>
> Record-valued keywords, e.g. DPj and DQi as defined in WCS Paper IV,<br>
> are multiply defined by design.<br>
> <br>
> As the original FITS specification did not prohibit multiply defined<br>
> keywords, the "once FITS always FITS" principle deems that they cannot<br>
> subsequently be prohibited.<br>
> <br>
> I see no reason not to allow multiply defined keywords, provided that it<br>
> is known in advance that a particular keyword may be multiply defined so<br>
> that header parsing software is prepared for the possibility.<br>
> <br>
> Mark Calabretta<br>
> <br>
> <br>
> <br>
> On Thu, 3 Aug 2023 17:18:33 +0000<br>
> "Seaman, Robert Lewis - \(rseaman\) via fitsbits"<br>
> <fitsbits@listmgr.nrao.edu> wrote:<br>
> <br>
> That seems a bit dismissive of the whole notion of DOIs. Also,<br>
> thoughts about duplicate keywords?<br>
> <br>
> <br>
> The mandatory FITS keywords defined in this Standard must not appear<br>
> more than once within a header. All other keywords that have a value<br>
> should not appear more than once. If a keyword does appear multiple<br>
> times with different values, then the value is indeterminate.<br>
> <br>
> Rob<br>
> <br>
> _______________________________________________<br>
> fitsbits mailing list<br>
> fitsbits@listmgr.nrao.edu<br>
> <a href="https://listmgr.nrao.edu/mailman/listinfo/fitsbits">https://listmgr.nrao.edu/mailman/listinfo/fitsbits</a><br>
<br>
_______________________________________________<br>
fitsbits mailing list<br>
fitsbits@listmgr.nrao.edu<br>
<a href="https://listmgr.nrao.edu/mailman/listinfo/fitsbits">https://listmgr.nrao.edu/mailman/listinfo/fitsbits</a></p>
</div>
</div>
</body>
</html>