RDF support in Drupal has been implemented with this model in mind:
Node = RDF subject
Field = RDF predicate
Field value = RDF object
This is a wonderful solution for most of Drupal content where the content type is ontologically connected to the field by a predicate.
But what happens when this is not the case? I.e. a field may be added in a content type because it is convenient for data inputting. But this field may not be directly connected to the content type by ontological rules. Which means that although the field appears within the content type, there is no direct predicate to assign to it. However, a predicate may exist to link to an implied piece of data (which should have been a different content type and) which is not entered for convenience. This implied piece of data then offers a predicate for the field (I tried to be clever in the attached image - see if it helps).
In the above case, the current Drupal RDF model does not work unless one creates that implied piece of data as a new content type. This is inconvenient when inputting data.
Has there been any discussion about a more relaxed model where the developer will be able to define more complicated ontological rules between content type and field than a simple predicate?
Or is this simply done by templates at a theme level?
|Indirect linking of content type with field (png)||47.79 KB|