The patch for the attribute.json schema removes the value property, which is the main mechanism by which the attribute.json schema applies a value which isn't an instance of taxonomy_term.json.
This could be deliberate and the result of a desire to restrict the use of the attribute.json schema to only add taxonomy terms, but I felt it worth noting.
The patch also overrides the schema-level description property with the following:
The other_attributes table creates a link between entities other than service and one or more classifications that describe the entity.
I did a hunt around the profile and searched for instances of other_attributes via rg, but got no results; it's only ever mentioned as part of the description of the attribute schema.
I think it's worthwhile to re-add the attribute.value property and remove the override to the schema's description, or at least update it to remove the reference to a non-existant "table".
Also noting that this patch also removes the link_table property; but I think this is a good thing because this property is mostly a convoluted way to satisfy representing linking an individual instance of attribute.json to an arbitrary schema in a normalized representation.
The patch for the
attribute.jsonschema removes thevalueproperty, which is the main mechanism by which theattribute.jsonschema applies a value which isn't an instance oftaxonomy_term.json.This could be deliberate and the result of a desire to restrict the use of the
attribute.jsonschema to only add taxonomy terms, but I felt it worth noting.The patch also overrides the schema-level
descriptionproperty with the following:I did a hunt around the profile and searched for instances of
other_attributesviarg, but got no results; it's only ever mentioned as part of the description of theattributeschema.I think it's worthwhile to re-add the
attribute.valueproperty and remove the override to the schema's description, or at least update it to remove the reference to a non-existant "table".Also noting that this patch also removes the
link_tableproperty; but I think this is a good thing because this property is mostly a convoluted way to satisfy representing linking an individual instance ofattribute.jsonto an arbitrary schema in a normalized representation.