Standard Categories for AlpineBits DestinationData
Considering that different DestinationData servers shall provide different sets of categories, clients will be challenged to build mappings when consuming data from multiple servers.
In order to ease the efforts on the client side, we could consider further developing the set of standard categories listed/defined by the DestinationData standard.
To investigate and define a more extensive and detailed list of categories that must be supported by all implementations of the DestinationData standard.
Implementations would still be free to add their own categories, but they must use DestinationData defined categories whenever applicable. For example, if a server supports the category 'example:SportsEvent' it must also use the equivalent 'schema:SportsEvent'. In addition, the 'example:SportsEvent' category must have a relationship 'parents' to the 'schema:SportsEvent' category in that server. Likewise, the 'schema:SportsEvent' category must have a relationship 'children' to the 'example:SportsEvent' category.
All implementations must provide the DestinationData-defined categories in their categories endpoint.