<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=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<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;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Thanks for your reply, Markus.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black"><registry-bounces@ivoa.net> on behalf of Markus Demleitner
<a href="mailto:msdemlei@ari.uni-heidelberg.de">msdemlei@ari.uni-heidelberg.de</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in">From there, I'd go back to VOResource, and since the content model of<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">external relationships is quite different from existing<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">relatedResource anyway -- no @ivo-id (right?), instead (probably)<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">relatedIdentifierType --, I'm tempted to say: "Why not have an extra<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">type and perhaps an extra element?" [foreignRelation?]<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I see your point about not wanting to complicate the existing vr:relationship type. I think adding another relationship could also be confusing, since then implementers would have to understand
when to use one over the other and people using the data would have to make a separate query to another table to find all of the possible relations. I do not know which is more confusing. Of course it would also confusing and error-prone to change the attributes
in vr:relationship and to make everyone update their data to reflect this.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">But either way, I'm not convinced yet that there are sufficiently<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">strong use cases to justify a new element or changing<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">relatedResource. After all, if we put in a feature, this brings with<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">it the implicit expectation that our clients will do something with<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">it, and that may be an extra challenge when you introduce lots of<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">different identifier types. <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I agree that this should be driven by use cases, and I do not have a use case now. This was more of an observation based on my experience trying to express things in DataCite. If others
have possible use cases that would be supported by an expanded concept of relationship in the VOResource schema I hope they will share them.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Calibri">Thanks again,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Calibri">Sarah<o:p></o:p></span></p>
</div>
</div>
</body>
</html>