Skip to content

Make system name mandatory for classification requirement #145

@pasi-paasiala

Description

@pasi-paasiala

According to this example it is possible to create a classification requirement that is accepted if an object has any classification. That is, it is possible to have this kind of requirement:

            <requirements>
                <classification minOccurs="1" maxOccurs="1" />
            </requirements>

My interpretation of this is that if an object happens to have exactly one classification of any kind, the requirement is met. I don't see that this is a feasible case. I'd propose to make the system obligatory in classification.

Metadata

Metadata

Assignees

Labels

schemaIssues that impact the schema file

Type

No type
No fields configured for issues without a type.

Projects

Status

Todo

Relationships

None yet

Development

No branches or pull requests

Issue actions