Closed YoucTagh closed 6 months ago
Alternatively, in the definition of ex:isProfilesDefault
, specify that the range domain of the property is altr:Representation
.
I think adding the domain is the best way to go - backwards compatible and stronger ontologically. I will create a PR for this.
closed with #69
To be more explicit, I suggest to use
ex:isProfileDefaultRepresentation
instead ofex:isProfilesDefault
to indicate if the representation is the default representation of that profile in A.4.2 Extensions.