tfmorris
commented
9 months ago I think changing the name of the field is fine, but the concept isn't unique to Freebase so I think it's worth keeping the explanatory text saying that this doesn't need to be all the types, but rather just those which are informative to the user in their decision making process. If the service has types like Thing or Object, or types which are just used for administrative uses, those are unlikely to be useful to the user.
When returned in suggest responses (and only there), entities currently have a "notable" field containing a list of types. Because this notion was specific to Freebase, I propose to remove this "notable" field and replace it by a "type" field (still accepting a list of types), for consistency with the stated data model.