Currently, the specification is not clear if there are any rules to user-defined facets that avoid ambiguity or conflicts with existing RAML features. Therefore, we should add the following clarifications:
a) you can not start facet name with ( (this is needed to avoid ambiguity with annotations).
b) you can not redeclare built-in facets for example you can not declare facet with name properties in the type which inherits from object type.
c) you can not redeclare facets which were defined earlier in hierarchy any more. this also means that you can not inherit facets with same name from two different types (done to make spec rules a bit simpler)
Currently, the specification is not clear if there are any rules to user-defined facets that avoid ambiguity or conflicts with existing RAML features. Therefore, we should add the following clarifications:
a) you can not start facet name with
(
(this is needed to avoid ambiguity with annotations). b) you can not redeclare built-in facets for example you can not declare facet with nameproperties
in the type which inherits from object type. c) you can not redeclare facets which were defined earlier in hierarchy any more. this also means that you can not inherit facets with same name from two different types (done to make spec rules a bit simpler)