<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<p>During the obscore extension session (Wednesday third session,
plenary) this question came by Marco ?</p>
<p> relationship extensions with ObsCore. How do we deal with
extensions attributes in ObsCore 1.2</p>
<p> <span
class="author-a-y2z67zqz69zgz89zz65zsz70zz70zz82zinz79zi">My
answer (after session) : I see this as a multistep thing.</span></p>
<div aria-live="assertive" id="magicdomid10234" class="ace-line">
<ul class="list-bullet3">
<li><span
class="author-a-y2z67zqz69zgz89zz65zsz70zz70zz82zinz79zi"> 1
) Radio extension and maybe others can be published as
endorsed notes. They include a description of how to
discover the extension in regsitry and how to join that to
Obscore. Take care than Common attributes should have same
name and VOTAble attributes and definition<br>
</span></li>
</ul>
</div>
<div aria-live="assertive" id="magicdomid10235" class="ace-line">
<ul class="list-bullet3">
<li><span
class="author-a-y2z67zqz69zgz89zz65zsz70zz70zz82zinz79zi">2
) ObsCore 1.2 in parallel should have a limited scope and
can be developed fast</span></li>
</ul>
</div>
<blockquote>
<div aria-live="assertive" id="magicdomid10236" class="ace-line">
<ul class="list-bullet4">
<li><span
class="author-a-y2z67zqz69zgz89zz65zsz70zz70zz82zinz79zi">include
IVOA product type vocabulary in dataproduct_type FIELD</span></li>
</ul>
</div>
<div aria-live="assertive" id="magicdomid10237" class="ace-line">
<ul class="list-bullet4">
<li><span
class="author-a-y2z67zqz69zgz89zz65zsz70zz70zz82zinz79zi">move
the discovery of Obscore in registry to the table/schema
utype mode in tableset</span></li>
</ul>
</div>
<div aria-live="assertive" id="magicdomid10238" class="ace-line">
<ul class="list-bullet4">
<li><span
class="author-a-y2z67zqz69zgz89zz65zsz70zz70zz82zinz79zi">adopt
additions and all changes which make consensus</span></li>
</ul>
</div>
<div aria-live="assertive" id="magicdomid10239" class="ace-line">
<ul class="list-bullet4">
<li><span
class="author-a-y2z67zqz69zgz89zz65zsz70zz70zz82zinz79zi">describe
in a generic way how any kind of extension can be declared
and joined to the ObsCore 1.2 root table</span></li>
</ul>
</div>
</blockquote>
<div aria-live="assertive" id="magicdomid10240" class="ace-line">
<ul class="list-bullet3">
<li><span
class="author-a-y2z67zqz69zgz89zz65zsz70zz70zz82zinz79zi">3
) Then take time to have ObsCOre 2.0<br>
</span></li>
</ul>
</div>
<blockquote>
<div aria-live="assertive" id="magicdomid10241" class="ace-line">
<ul class="list-bullet4">
<li><span
class="author-a-y2z67zqz69zgz89zz65zsz70zz70zz82zinz79zi">this
step includes all possible attributes of Obscore mandatory
/ optional and all extensions (Radio, HE, Time),</span></li>
</ul>
</div>
<div aria-live="assertive" id="magicdomid10242" class="ace-line">
<ul class="list-bullet4">
<li><span
class="author-a-y2z67zqz69zgz89zz65zsz70zz70zz82zinz79zi"> and
then we organize this in profiles : full, root, radio, HE,
Time and some combination of Time+HE and Time + Radio
(Radio +HE doesn't make sense) and maybe others to come.
Root Obscore is the common mandatory subset<br>
</span></li>
</ul>
</div>
<div aria-live="assertive" id="magicdomid10243" class="ace-line">
<ul class="list-bullet4">
<li><span
class="author-a-y2z67zqz69zgz89zz65zsz70zz70zz82zinz79zi">some
attributes may be part of several profiles (eg Radio and
HE). They share the same definition in the different
profiles </span></li>
</ul>
</div>
<div aria-live="assertive" id="magicdomid10244" class="ace-line">
<ul class="list-bullet4">
<li><span
class="author-a-y2z67zqz69zgz89zz65zsz70zz70zz82zinz79zi">Optional
attributes are those in full which are in none of the
other profiles</span></li>
</ul>
</div>
<div aria-live="assertive" id="magicdomid10245" class="ace-line">
<ul class="list-bullet4">
<li><span
class="author-a-y2z67zqz69zgz89zz65zsz70zz70zz82zinz79zi">Vision
of the full ObsCore as being potentially "restricted" in
several different profiles is more unified, but has
actually the same content than root mandatory + extensions
+ optional. Profiles are restrictions of the full ObsCore<br>
</span></li>
</ul>
</div>
<div aria-live="assertive" id="magicdomid10257" class="ace-line">
<ul class="list-bullet4">
<li><span
class="author-a-y2z67zqz69zgz89zz65zsz70zz70zz82zinz79zi">This
concept of profile was first proposed by Gregory DF in
Sydney (RIG session) and then again by JJ Kavelaars in an
email last winter</span></li>
</ul>
</div>
</blockquote>
<p></p>
</body>
</html>