KERML — Definition of property "typing" seems incomplete/inconsistent

"typing" seems to be non-navigable owned end of the association between Feature and FeatureTyping.
However, it is used in a constraint: deriveFeatureType - this seems a little odd.

No change

In KerML, it is allowable to have FeatureTyping relationships that are not owned by the Feature being typed, and these relationships can be added in parts of a model that are not "close" to where the typed Feature is declared. The property typing is non-navigable so that such FeatureTypings can be declared without having to update a navigable owned property of either the typed Feature or the Type typing the Feature. (On the other hand, the property ownedTyping is navigable.)

However, when computing the types of a Feature it is necessary to take into account all the FeatureTypings for that Feature whether they are owned by the Feature or not. Using typing instead of ownedTyping in deriveFeatureType handles this. Note that it is specifically allowable in OCL to "navigate" across non-navigable association ends (even though, admittedly, it is an optional conformance point for tools to navigate "non-navigable" associations – see OCL 2.4 specification, Clause 2).