...
| Collections ontology | ORE ontology | ||
|---|---|---|---|
| – | unordered and ordered collections are represented by two separate class constructs, Bag and List respectively | + | unordered and ordered collections are represented by the same class construct, Aggregation |
| + | item property names are easy to understand (e.g., index, itemContent, nextItem) | – | item property names are cryptic (e.g., proxyFor, proxyIn, next) |
| – | order is determined by an item property pointing to the next item, i.e., nextItem. | – | order is determined by an item property pointing to the next item, i.e., next |
| +– | URI can be associated directly to for the item is not associated with the collection class (e.g., List, Bag). URI can be associated directly to the collection class through co:element. co:element is defined through a chain: has sub-property chains [has item o has item content]. That means that the inference layer can resolve both (Paolo). Examples do not show this. | + | URI for the item is associated with the collection class (i.e., Aggregation) via of the aggregates property. |
| + | URI for the item is associated with the item class (i.e., Item) via the itemContent property. | + | URI for the item is associated with the item class (i.e., Proxy) via the proxyFor property. |
...