Currently Content Describers register themselves on particular resources or classes
I wonder if we will also want to register them on properties. Take for example that the StadiumDescriber essentially checks if there is an event on at the Stadium, and an alternative HasEventDescriber would be more generic
In this example and in many cases, the StadiumDescriber is better, since the context of the Stadium is relevant in the output content. To counter this point we could add a reverse property eventVenue to access the Stadium in HasEventDescriber, and piped the content through that, but I fear that our generic HasEventDescriber would be getting increasingly complicated, in particular to manage contradictions
My instinct is that the best approach for now would be to provide both, but to attempt to match on the Resources, and if we can't, look to the properties
Currently Content Describers register themselves on particular resources or classes
I wonder if we will also want to register them on properties. Take for example that the
StadiumDescriberessentially checks if there is an event on at the Stadium, and an alternativeHasEventDescriberwould be more genericIn this example and in many cases, the
StadiumDescriberis better, since the context of the Stadium is relevant in the output content. To counter this point we could add a reverse propertyeventVenueto access the Stadium inHasEventDescriber, and piped the content through that, but I fear that our genericHasEventDescriberwould be getting increasingly complicated, in particular to manage contradictionsMy instinct is that the best approach for now would be to provide both, but to attempt to match on the Resources, and if we can't, look to the properties