After querying on - say - all SubSettings, the list of URIs of the elements result with the fact that a GET on any SubSetting resource is represented by the GET operation on Element (Because ALL resources have hte same URL pattern pointing to Element services)
This means the html-pages (DUI and debugging pages) of all resources are the most generic Element one, and user does not get to see the specific attributes of the sub-classes.
Note that this is not an issue when requesting RDF formats, since JMH elegently returns the java instances of the correct sub-class of Element.
The only problem is that the Element operations always point to element.jsp.
jadelkhoury
commented
4 years ago
After querying on - say - all SubSettings, the list of URIs of the elements result with the fact that a GET on any SubSetting resource is represented by the GET operation on Element (Because ALL resources have hte same URL pattern pointing to Element services)
This means the html-pages (DUI and debugging pages) of all resources are the most generic Element one, and user does not get to see the specific attributes of the sub-classes.
Note that this is not an issue when requesting RDF formats, since JMH elegently returns the java instances of the correct sub-class of Element. The only problem is that the Element operations always point to element.jsp.