Skip to content

Removing table group/table/column compatibility constraints for inherited properties #464

@JeniT

Description

@JeniT

When talking about inherited properties the spec says:

Applications must raise an error if the value of a property in a table description is not compatible with the value of that property on the table group description it appears in. Applications must raise an error if the value of a property in a schema description is not compatible with the value of that property on the table description and table group description it appears in. Applications must raise an error if the value of a property in a column description is not compatible with the value of that property in the schema description, table description, and/or table group description it appears in.

A value for an inherited property on a column or table description is compatible with with an inherited value on the same property on a table or table group description if they are the same value or if the first value is a sub-value of the second value. The definitions of individual inherited properties indicate what values count as sub-values of others.

This was stuff I originally wrote. Having reflected, I propose that we remove these constraints: it should be possible for someone to define that all the values in a table are strings with the language en and then override just for individual columns, for example.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions