Task #3686 (closed)
Opened 13 years ago
Closed 9 years ago
Development Guidelines for data model
Reported by: | caitlin | Owned by: | hflynn |
---|---|---|---|
Priority: | minor | Milestone: | 5.1.2 |
Component: | Documentation | Version: | 4.4.9 |
Keywords: | schema | Cc: | jburel, sbesson, ajpatterson |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description
Moved from http://www.ome-xml.org/ticket/100
I suggest you create and document some style rules for development of the schemata. This will help others who wish to write reusable local extensions, new collaborators who may come into the project later, as well as present collaborators in future expansions or changes. Suggestions of the kind of rules to address:
- A consistent approach for when to use attributes and when to use subelements
- An ordering principle or set of principles for subelements and attributes, for example required elements first, then alphabetical. In the schema, for the definitions of each element, order subelements either according to the SAME principle as they are organized in the top level definitions (grouped by top level definition), or else order them all together without regard to the top level by some other ordering principle (like alphabetical).
- Make a clear distinction between “unknown,” “other,” and null values. Make an unknown value on all enumerated lists, to avoid invalidation when you import metadata from less-complete file types.
- Rules for consistency in capitalization, punctuation, and spaces
- No abbreviations or plural nouns in element or attribute names.
- My recommendation on language in general is to create new terms to define new concepts, and use familiar terms only if the generally accepted definition will be fulfilled in the model. I know that is a bit subjective, but please see the ticket “Experimental conditions” for an example of why I am mentioning this.
Change History (7)
comment:1 Changed 13 years ago by ajpatterson
- Keywords schema added
comment:2 Changed 11 years ago by ajpatterson
- Component changed from General to Documentation
- Owner set to hflynn
comment:3 Changed 10 years ago by hflynn
- Summary changed from Development Guidelines to Development Guidelines for data model
- Version set to 4.4.9
comment:4 Changed 10 years ago by jamoore
Referencing ticket #10274 has changed sprint.
comment:5 Changed 10 years ago by hflynn
- Cc jburel sbesson ajpatterson added
- Milestone changed from Unscheduled to 5.1.0
Development process guidance can be added to new schema changes doc in Contributing section.
comment:6 Changed 9 years ago by hflynn
- Cc changed from jburel, sbesson, ajpatterson, to jburel, sbesson, ajpatterson
- Status changed from new to accepted
Should probably include some of this within https://trello.com/c/6BUPmEP5/231-update-https-www-openmicroscopy-org-site-support-contributing-schema-changes-html
comment:7 Changed 9 years ago by hflynn
- Resolution set to duplicate
- Status changed from accepted to closed
Managed via Trello now.
@ajpatterson, should this go into the Model documentation at some point? Or do you think it belongs in the Data Model section of the OMERO developer docs? We should probably revisit how these are divided up now we have the Model docs in sphinx actually, I'll make a ticket for that.