Skip to content

Refactor specification for Repository XML Schema #76

Description

@kleihan

Chapter 3 of the specification contains the description of the repository schema. The first 4 subchapters (3.1-3.4) define the root element and global elements such as pedigree and annotations. Some of the subchapters of Chapters 3.1-3.4 are proposed to be moved further down (see below). The subsequent chapters 3.5-3.12 describe the main elements types, some of them in their own section (e.g. fields) and others in a message context (e.g. components).

The proposal is to reorder and refactor these subchapters to start with the smallest element (datatypes) and end with the largest element (sections). Higher-level features should come after that and be ordered by complexity.

Furthermore, the concept of scenarios should be described in a single subchapter at the end and not as integral part of the individual element descriptions. This should make it easier for a beginner to get a basic understanding of Orchestra.

The new order is proposed as follows (they could also be partially grouped, e.g. into basic and advanced topics):

  1. Datatypes
  2. Code Sets
  3. Fields
  4. Components
  5. Groups
  6. Messages
  7. Categories (from Chapter 3.3.1)
  8. Sections (from Chapter 3.3.1)
  9. Member Presence
  10. Expressions
  11. Naming Rules (from Chapter 3.2.3)
  12. Support for XInclude (from Chapter 3.1.4)
  13. Scenarios
  14. Workflows
  15. Semantic Concepts

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions