There are many schemes for representing structured information in which there is a hierarchical organisation of what in Freebase are Properties. The particular stimulus for this posting is REM (the Register of Ecological Models) - see this typical entry - but the same thing can be found in many domains where the relevant community has (for example) developed an XML-based markup language to represent objects within the domain. Note t...
more
There are many schemes for representing structured information in which there is a hierarchical organisation of what in Freebase are Properties. The particular stimulus for this posting is REM (the Register of Ecological Models) - see this typical entry - but the same thing can be found in many domains where the relevant community has (for example) developed an XML-based markup language to represent objects within the domain.
Note that, in the example pointed to above, there are at least 2 levels of nesting, e.g.
- II. Technical information
- II.1 Executables
- II.2 Source-code
In contrast, Freebase currently restricts you to a flat list of Properties.
Is there any chance that the ability to group Properties hierarchically could be added to Freebase?
As well enabling a better mapping on to existing bodies of information, this would have the distinct advantage that the UI could present the information in a collapsible tree, allowing the person browsing to expand or minimise partocular Property groups (at any level). This would be useful when particular Types have many Properties.
