Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add field for background color #102

Open
paulmenzel opened this issue May 8, 2019 · 1 comment
Open

Add field for background color #102

paulmenzel opened this issue May 8, 2019 · 1 comment

Comments

@paulmenzel
Copy link

paulmenzel commented May 8, 2019

I was told, there is a field missing for storing what color the background(?) has. How could such a field be added to the specification?

@mtbc
Copy link
Member

mtbc commented May 9, 2019

https://www.openmicroscopy.org/Schemas/Documentation/Generated/OME-2016-06/ome.html shows the current model's XML schema. What do you think should have a background color defined? (There are all kinds of element.) Can you tell us a bit more about your use case? (Note that ROIs' shapes each have a fillColor and a strokeColor.)

Model changes aren't undertaken lightly because they pervade the whole software stack up through Bio-Formats and OMERO into our users' client applications. However, we do of course make rounds of changes and in the meantime we collect ideas for improving the model.

In some cases elements are introduced into only the OMERO object model without yet including them further down the stack but it generally works out best to keep OMERO aligned with the OME Data Model.

It may help to note that in some applications the more freeform aspects of the model are used to add data without waiting for a new schema. For example, use of structured annotations in a specific namespace can be used to encode data that is recognized and intepreted by custom clients or local scripts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants