Add x-override-allowed to indicate annotations can be overridden by customer / merge

[Fannon]

Just a draft / WIP:

Requirement has come up to annotate on meta level which annotations make sense to override when CSN Interop files are merged. This can happen e.g. when a customer creates some override extensions, most notably overriding a UI facing label for a property or entity.

@stewsk will find out which annotations are affected.

@maiargu - we'll have to add this to the spec-toolkit as allowed and defined x- attribute and maybe also indicating this on the generated documentation (? not sure.). We also need to ensure that the spec extensions are exported as JSON Schema in a way that our stakeholders can retrieve them, e.g. as NPM dependency or HTTP download.

[stewsk]

@Fannon

@stewsk will find out which annotations are affected.

??? Did I miss this point in the discussion we had?

[Fannon]

@Fannon

@stewsk will find out which annotations are affected.

??? Did I miss this point in the discussion we had?

@stewsk - I meant which annotations should have x-override-allowed: true assigned to them. Or is it just the EnduserText.label for now?

[frankejoe]

@Fannon : the action item is on me to create an initial proposal of annotations.

[Fannon]

@Fannon : the action item is on me to create an initial proposal of annotations.

Ah, sorry - i had the wrong mention. Sorry @stewsk !