Open joshmoore opened 4 years ago
Thank you @joshmoore for bringing this to our attention.
Would the following changes in the header address the concern?
Proposed change version 1
<xsd:schema xmlns="http://www.NamespaceTest.org/Schemas/NBO/2020-11"
targetNamespace="http://www.NamespaceTest.org/Schemas/NBO/2020-11"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:OME="http://www.openmicroscopy.org/Schemas/OME/2016-06" version="3"
elementFormDefault="qualified">
or do we also have to remove any reference to the :OME suffix as in version 2?
Proposed change version 2
<xsd:schema xmlns="http://www.NamespaceTest.org/Schemas/NBO/2020-11"
targetNamespace="http://www.NamespaceTest.org/Schemas/NBO/2020-11"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:NBO="http://www.NamespaceTest.org/Schemas/NBO/2020-11" version="02.00"
elementFormDefault="qualified">
NOTE NBO stands for 4dNulceome Bina Ome extension
@strambc thanks for the two proposals. Looking at it briefly, I do not see any fundamental issue with the version 1. It mostly declares a new 4DN schema under a new namespace but imports the 2016-06 OME schema using the OME:
prefix. This matches my understanding of the 4DN extension.
This layout is the closest to the one described in this section of the ome-model developer documentation. There are a few additional suggestions on this page that might be required including importing the OME schema using xs:import
.
Thank you @sbesson I will take another look at the development guide to make sure we are aligned with the recommendations therein. cc: @Akramhar
After a recent ping from Caterina, I was working through the current proposal. Something occurred to me that I should have raised sooner:
https://github.com/WU-BIMAC/MicroscopyMetadata4DNGuidelines/blob/master/Model/in%20progress/v02-00/4DN-BINA-OME-Microscopy%20Metadata_CORE%2BBASIC.xsd#L44-L48
identify this file as being the official 2016-06 schema and could lead to confusion in the community. We will need a way to make it clear that the XSD files in this repository extend rather than replace the OME Schema.
cc: @sbesson @jburel @jrswedlow