From francois.bonnarel at gmail.com Fri Jun 6 00:28:00 2025 From: francois.bonnarel at gmail.com (BONNAREL FRANCOIS gmail) Date: Fri, 6 Jun 2025 00:28:00 +0200 Subject: Extensions and next step of Obscore Message-ID: During the obscore extension session (Wednesday third session, plenary) this question came by Marco ? ? ? ?? relationship extensions with ObsCore. How do we deal with extensions attributes in ObsCore 1.2 My answer (after session) : I see this as a multistep thing. * ?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 * 2 ) ObsCore 1.2 in parallel should have a limited scope and can be developed fast * include IVOA product type vocabulary in dataproduct_type FIELD * move the discovery of Obscore in registry to the table/schema utype mode in tableset * adopt additions and all changes which make consensus * describe in a generic way how any kind of extension can be declared and joined to the ObsCore 1.2 root table * 3 ) Then take time to have ObsCOre 2.0 * this step includes all possible attributes of Obscore mandatory / optional and all extensions (Radio, HE, Time), * ?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 * some attributes may be part of several profiles (eg Radio and HE). They share the same definition in the different profiles * Optional attributes are those in full which are in? none of the other profiles * 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 * 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: