Reserved Attribute Names

[SundermannC]

Motivation

Type 1 (Global attributes):
Some attributes/properties are relevant across many kinds of variability models. Ensuring that these properties are interpreted accordingly and not cause conflicts because of inconsistent usage.

Type 2 (Project/Context Defined attributes):
Another use case may be some kind of template that defines consistent behavior of attributes for multiple variability models.
Specify "scheme" for certain attribute names.

Examples

Type 1:

• Abstract: No corresponding implementation artifact
• Hidden: Not shown in configuration editor

Type 2:

• Price should always be a positive integer
• Mail should always be strings following this regex

Open Questions

• Should (Type 1/Type 2/both) be handled from UVL or in another language?
• Incorporate type 1 attributes in grammar (dedicated keywords) vs catalogue that provides specification
• Handling in tools? Warnings vs errors
• How to specify schemes?
• Where to store schemes?