Schema Documentation
Classes
-
-
pimos:Hidden(rdfs:Resource)
-
Instances of this class (x type Hidden) and instances of subclasses of Hidden (x type Y, Y subClassOf Hidden) are not to be rendered in generic user interfaces.
-
-
pimos:InformationResource(rdfs:Resource)
-
Instances of this class are information resources in the sense of http-range-14. IE answering http GET requests to the URI is returned with a 2XX answer. Typically, they are HTML documents, images, or other content found on the web.
Properties
-
dc:title (rdf:Property)
-
pimos:hasAfterExperimental (rdf:Property)
-
The object of this statement is after the subject of this statement, in the background indicated in the hasBackground metadata of triples created with this statement class. Experimental: this may be replaced with lists. To be further specified. There will be a decision within 2006.
- range:
rdfs:Resource
-
pimos:hasBeforeExperimental (rdf:Property)
-
The object of this statement is before the subject of this statement, in the background indicated in the hasBackground metadata of triples created with this statement class. Experimental: this may be replaced with lists. To be further specified. There will be a decision within 2006.
- range:
rdfs:Resource
-
pimos:hasContext (rdf:Property)
-
The object is the "parent" of this subject thing. In user interfaces we recommend to render the object as parent of the subject, for example in a tree view or nested view. A thing can have multiple contexts.
- range:
rdfs:Resource
-
pimos:hasDescribingdata (rdf:Property)
-
The subject resource is described by the object node. The object is an essential description of the subject. Visualizations should render describing data as one visual item together with the subject. A property should either be a subpropertyof hasDescribingData, hasRelated, or hasMetadata.
-
pimos:hasDetail (rdf:Property)
-
The object is the "child" of this subject thing. In user interfaces we recommend to render the object as child of the subject, for example in a tree view or nested view. A thing can have multiple details. Typcial, a thing has many details.
- range:
rdfs:Resource
-
pimos:hasMetadata (rdf:Property)
-
Statements using this property are not intended to be rendered to the user. A property should either be a subpropertyof hasDescribingData, hasRelated, or hasMetadata.
-
pimos:hasRelated (rdf:Property)
-
A resource with which there is an associative semantic relationship. Any property like context/detail, foaf:knows, etc is a sub-property of this. A property should either be a subpropertyof hasDescribingData, hasRelated, or hasMetadata.
- range:
rdfs:Resource
-
pimos:hasSource (rdf:Property)
-
A directed backlink without further semantics. An equivalent to a hyperlink. The object rsource has a link to the subject. In a visualization, hasSource links would be shown by default as incoming hyperlinks.
- range:
rdfs:Resource
-
pimos:hasTarget (rdf:Property)
-
A directed link with no further semantics. HasTarget is the superproperty of all directed (non symmetric) properties. In a visualization, hasTarget links would be shown by default as outgoing hyperlinks.
- range:
rdfs:Resource
-
pimos:hasTerm (rdf:Property)
-
a unique Term for the resource. Is an Inverse Functional Property in the domain of one users, two subjects having the same hasTerm statement are the same === that the statements are created by the same user.
- range:
rdfs:Literal
-
pimos:hasWikiname (rdf:Property)
- range:
rdfs:Literal
-
rdfs:label (rdf:Property)
Generated by Schemadoc