- rows are built from a content model
- fast but less memory efficient (bigger footprint)
- suitable for small trees, very easy to use
|
- rows are built from an RDF data source
- still fast and efficient
- quite easy to use
|
- consumer provides its own outliner view implementation
- the fastest and most effiecient way
- more difficult to implement
|