| Subject | Object |
|---|---|
| skos:ConceptScheme |
A concept scheme may be defined to include concepts from different sources.@en,
A concept scheme may be defined to include concepts from different sources.@en,
A concept scheme may be defined to include concepts from different sources.@en,
A concept scheme may be defined to include concepts from different sources.@en,
A concept scheme may be defined to include concepts from different sources.@en,
A concept scheme may be defined to include concepts from different sources.@en,
A concept scheme may be defined to include concepts from different sources.@en,
A concept scheme may be defined to include concepts from different sources.@en
|
| skos:Collection |
Labelled collections can be used where you would like a set of concepts to be displayed under a 'node label' in the hierarchy.@en,
Labelled collections can be used where you would like a set of concepts to be displayed under a 'node label' in the hierarchy.@en,
Labelled collections can be used where you would like a set of concepts to be displayed under a 'node label' in the hierarchy.@en,
Labelled collections can be used where you would like a set of concepts to be displayed under a 'node label' in the hierarchy.@en,
Labelled collections can be used where you would like a set of concepts to be displayed under a 'node label' in the hierarchy.@en,
Labelled collections can be used where you would like a set of concepts to be displayed under a 'node label' in the hierarchy.@en,
Labelled collections can be used where you would like a set of concepts to be displayed under a 'node label' in the hierarchy.@en,
Labelled collections can be used where you would like a set of concepts to be displayed under a 'node label' in the hierarchy.@en
|
| skos:OrderedCollection |
Ordered collections can be used where you would like a set of concepts to be displayed in a specific order, and optionally under a 'node label'.@en,
Ordered collections can be used where you would like a set of concepts to be displayed in a specific order, and optionally under a 'node label'.@en,
Ordered collections can be used where you would like a set of concepts to be displayed in a specific order, and optionally under a 'node label'.@en,
Ordered collections can be used where you would like a set of concepts to be displayed in a specific order, and optionally under a 'node label'.@en,
Ordered collections can be used where you would like a set of concepts to be displayed in a specific order, and optionally under a 'node label'.@en,
Ordered collections can be used where you would like a set of concepts to be displayed in a specific order, and optionally under a 'node label'.@en,
Ordered collections can be used where you would like a set of concepts to be displayed in a specific order, and optionally under a 'node label'.@en,
Ordered collections can be used where you would like a set of concepts to be displayed in a specific order, and optionally under a 'node label'.@en
|
| skos:inScheme |
A concept may be a member of more than one concept scheme.@en,
A concept may be a member of more than one concept scheme.@en,
A concept may be a member of more than one concept scheme.@en,
A concept may be a member of more than one concept scheme.@en,
A concept may be a member of more than one concept scheme.@en,
A concept may be a member of more than one concept scheme.@en,
A concept may be a member of more than one concept scheme.@en,
A concept may be a member of more than one concept scheme.@en
|
| skos:notation |
By convention, skos:notation is used with a typed literal in the object position of the triple.@en,
By convention, skos:notation is used with a typed literal in the object position of the triple.@en,
By convention, skos:notation is used with a typed literal in the object position of the triple.@en,
By convention, skos:notation is used with a typed literal in the object position of the triple.@en,
By convention, skos:notation is used with a typed literal in the object position of the triple.@en,
By convention, skos:notation is used with a typed literal in the object position of the triple.@en,
By convention, skos:notation is used with a typed literal in the object position of the triple.@en,
By convention, skos:notation is used with a typed literal in the object position of the triple.@en
|
| skos:note |
This property may be used directly, or as a super-property for more specific note types.@en,
This property may be used directly, or as a super-property for more specific note types.@en,
This property may be used directly, or as a super-property for more specific note types.@en,
This property may be used directly, or as a super-property for more specific note types.@en,
This property may be used directly, or as a super-property for more specific note types.@en,
This property may be used directly, or as a super-property for more specific note types.@en,
This property may be used directly, or as a super-property for more specific note types.@en,
This property may be used directly, or as a super-property for more specific note types.@en
|
| skos:semanticRelation |
This property should not be used directly, but as a super-property for all properties denoting a relationship of meaning between concepts.@en,
This property should not be used directly, but as a super-property for all properties denoting a relationship of meaning between concepts.@en,
This property should not be used directly, but as a super-property for all properties denoting a relationship of meaning between concepts.@en,
This property should not be used directly, but as a super-property for all properties denoting a relationship of meaning between concepts.@en,
This property should not be used directly, but as a super-property for all properties denoting a relationship of meaning between concepts.@en,
This property should not be used directly, but as a super-property for all properties denoting a relationship of meaning between concepts.@en,
This property should not be used directly, but as a super-property for all properties denoting a relationship of meaning between concepts.@en,
This property should not be used directly, but as a super-property for all properties denoting a relationship of meaning between concepts.@en
|
| skos:broader |
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en,
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en,
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en,
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en,
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en,
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en,
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en,
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en
|
| skos:narrower |
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en,
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en,
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en,
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en,
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en,
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en,
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en,
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.@en
|
| skos:broaderTransitive |
By convention, skos:broaderTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en,
By convention, skos:broaderTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en,
By convention, skos:broaderTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en,
By convention, skos:broaderTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en,
By convention, skos:broaderTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en,
By convention, skos:broaderTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en,
By convention, skos:broaderTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en,
By convention, skos:broaderTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en
|
| skos:narrowerTransitive |
By convention, skos:narrowerTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en,
By convention, skos:narrowerTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en,
By convention, skos:narrowerTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en,
By convention, skos:narrowerTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en,
By convention, skos:narrowerTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en,
By convention, skos:narrowerTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en,
By convention, skos:narrowerTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en,
By convention, skos:narrowerTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.@en
|