Specifies a containment relationship between two graphs, meaning that the subject graph is included in the object graph
Represents a named graph containing both schematic and instance data
Points to a representation of the declarative semantics for a graph role
Terms and intellectual property rights licensing conditions.
Specifies a minimum value cardinality for a specific property
Represents a specification of the means to achieve a transformation of an input graph into the required graph view
Generic property used to express containment relationships between DataObjects. NIE extensions are encouraged to provide more specific subproperties of this one. It is advisable for actual instances of DataObjects to use those specific subproperties. Note to the developers: Please be aware of the distinction between containment relation and provenance. The isPartOf relation models physical containment, a nie:DataObject (e.g. an nfo:Attachment) is a 'physical' part of an nie:InformationElement (a nmo:Message). Also, please note the difference between physical containment (isPartOf) and logical containment (isLogicalPartOf) the former has more strict meaning. They may occur independently of each other.
Dependency relation. A piece of content depends on another piece of data in order to be properly understood/used/interpreted.
Last modification date of the DataObject. Note that this date refers to the modification of the DataObject itself (i.e. the physical representation). Compare with nie:contentLastModified.
A marker class to identify inverse functional properties
Plain-text representation of the content of a InformationElement with all markup removed. The main purpose of this property is full-text indexing and search. Its exact content is considered application-specific. The user can make no assumptions about what is and what is not contained within. Applications should use more specific properties wherever possible.
A common superproperty for all properties that point at legal information about an Information Element
A unit of content the user works with. This is a superclass for all interpretations of a DataObject.
A core graph metadata property, this defines whether a graph can be freely updated '1' or otherwise '0'
Marks the provenance of a DataObject, what source does a data object come from.
A non-defining property's value is not part of what defines a resource, it rather is part of the resource's state or expresses an opinion about the resource. Whenever comparing resources or sharing them the value of this property should not be taken into account. By default all properties with a resource range are to be treated as non-defining properties unless they are marked as nrl:DefiningProperty.
Date of creation of the DataObject. Note that this date refers to the creation of the DataObject itself (i.e. the physical representation). Compare with nie:contentCreated.
The type of the license. Possible values for this field may include "GPL", "BSD", "Creative Commons" etc.
A marker class to identify reflexive properties
Software used to "generate" the contents. E.g. a word processor name.
A marker class to identify asymmetric properties
Adapted DublinCore: The topic of the content of the resource, as keyword. No sentences here. Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme.
Identifies a graph which is itself a view of another named graph
Generic property used to express 'logical' containment relationships between InformationElements. NIE extensions are encouraged to provide more specific subproperties of this one. It is advisable for actual instances of InformationElement to use those specific subproperties. Note the difference between 'physical' containment (hasPart) and logical containment (hasLogicalPart)
Language the InformationElement is expressed in. This property applies to the data object in its entirety. If the data object is divisible into parts expressed in multiple languages - more specific properties should be used. Users are encouraged to use the two-letter code specified in the RFC 3066
Points to a graph view over the subject named graph
DataObjects extracted from a single data source are organized into a containment tree. This property links the root of that tree with the datasource it has been extracted from
The overall size of the data object in bytes. That means the space taken by the DataObject in its container, and not the size of the content that is of interest to the user. For cases where the content size is different (e.g. in compressed files the content is larger, in messages the content excludes headings and is smaller) use more specific properties, not necessarily subproperties of this one.
A point or period of time associated with an event in the lifecycle of an Information Element. A common superproperty for all date-related properties of InformationElements in the NIE Framework.
A marker class to identify transitive properties
Representation for a standard set of device/application/service modes, corresponding to various sets of modes that are either inbuilt in a device (e.g. inbuilt phone modes such as silent, loud, general, vibrate, etc.) or available for applications and online services (e.g. IM system modes such as busy, available, invisible, etc.)
Generic property used to express 'physical' containment relationships between DataObjects. NIE extensions are encouraged to provide more specific subproperties of this one. It is advisable for actual instances of DataObjects to use those specific subproperties. Note to the developers: Please be aware of the distinction between containment relation and provenance. The hasPart relation models physical containment, an InformationElement (a nmo:Message) can have a 'physical' part (an nfo:Attachment). Also, please note the difference between physical containment (hasPart) and logical containment (hasLogicalPart) the former has more strict meaning. They may occur independently of each other.
The HTML content of an information element. This property can be used to store text including formatting in a generic fashion.
Represents a view specification that is composed of a set of rules which generate the required view from the input graph upon firing
A superclass for all entities from which DataObjects can be extracted. Each entity represents a native application or some other system that manages information that may be of interest to the user of the Semantic Desktop. Subclasses may include FileSystems, Mailboxes, Calendars, websites etc. The exact choice of subclasses and their properties is considered application-specific. Each data extraction application is supposed to provide it's own DataSource ontology. Such an ontology should contain supported data source types coupled with properties necessary for the application to gain access to the data sources. (paths, urls, passwords etc...)
Models a subsumption relationship between two graphs, stating that the object graph is imported and included in the subject graph
Points to the location of the realizer for the external view specification
The current version of the given data object. Exact semantics is unspecified at this level. Use more specific subproperties if needed.
Date when information about this data object was retrieved (for the first time) or last refreshed from the data source. This property is important for metadata extraction applications that don't receive any notifications of changes in the data source and have to poll it regularly. This may lead to information becoming out of date. In these cases this property may be used to determine the age of data, which is an important element of it's dependability.
Represents a named graph containing configuration data
A defining property's value is part of what defines a resource, changing it means means chaning the identity of the resource. The set of values of all defining properties of a resource make up its identify. Whenever comparing resources or sharing them the value of this property should be taken into account. By default all properties with a literal range are to be treated as defining properties unless they are marked as nrl:NonDefiningProperty.
A user comment about an InformationElement.
Represents a number of applicable modes for a data source.
Represents a special named graph that contains metadata for another graph
A named graph containing instance data that can be recreated by analyzing the original resources. Intended to be used by metadata extractors.
Connects the data object with the graph that contains information about it. Deprecated in favor of a more generic nao:isDataGraphFor.
A marker class to identify symmetric properties
Links the DataObject with the InformationElement it is interpreted as.
The mime type of the resource, if available. Example: "text/plain". See http://www.iana.org/assignments/media-types/. This property applies to data objects that can be described with one mime type. In cases where the object as a whole has one mime type, while it's parts have other mime types, or there is no mime type that can be applied to the object as a whole, but some parts of the content have mime types - use more specific properties.
Specifies the precise value cardinality for a specific property
Represents the sum of all information that has been obtained from a data source. Each data source has its own personal information graph. When a data source is deleted, the graph becomes redundant and should also be deleted. If two or more items in two or more data source graphs are determined to be equivalent, they are integrated at the PIMO level, and the integrated representation plus the links to the original items are stored in the pimo:PersonalInformationModel graph.
Points to a representation of the declarative semantics that the view specification realizes
Represents a named graph containing instance data
The date of the content creation. This may not necessarily be equal to the date when the DataObject (i.e. the physical representation) itself was created. Compare with nie:created property.
A linking relation. A piece of content links/mentions a piece of data
Represents a named graph containing schematic data
Represents the default graph, the graph which contains any triple that does not belong to any other named graph
A common superproperty for all settings used by the generating software. This may include compression settings, algorithms, autosave, interlaced/non-interlaced etc. Note that this property has no range specified and therefore should not be used directly. Always use more specific properties.
Characterset in which the content of the InformationElement was created. Example: ISO-8859-1, UTF-8. One of the registered character sets at http://www.iana.org/assignments/character-sets. This characterSet is used to interpret any textual parts of the content. If more than one characterSet is used within one data object, use more specific properties.
Specifies a maximum value cardinality for a specific property
A textual description of the resource. This property may be used for any metadata fields that provide some meta-information or comment about a resource in the form of a passage of text. This property is not to be confused with nie:plainTextContent. Use more specific subproperties wherever possible.
Represents an external view specification, this usually being a program which automatically generates the required view for an input graph
URL of a DataObject. It points to the location of the object. A typial usage is FileDataObject. In cases where creating a simple file:// or http:// URL for a file is difficult (e.g. for files inside compressed archives) the applications are encouraged to use conventions defined by Apache Commons VFS Project at http://jakarta.apache.org/ commons/ vfs/ filesystems.html.
Specifies rules for a view specification that is driven by rules
Specifies a subsumption relationship between two graphs, meaning that the object graph is included in the subject graph
An unambiguous reference to the InformationElement within a given context. Recommended best practice is to identify the resource by means of a string conforming to a formal identification system.
A marker class to identify named graphs that exist within a physical document
Links a metadata graph to the graph that is being described. A unique value is compulsory
The date of the last modification of the original content (not its corresponding DataObject or local copy). Compare with nie:lastModified.
Represents a named graph having the role of an Ontology
Specifies the rule language for a view specification that is driven by rules
Points to the human readable specifications for a representation of some declarative semantics
Links the information element with the DataObject it is stored in.
An abstract class representing all named graph roles
Links two properties and specifies their inverse behaviour
Links two equivalent named graphs. A symmetric property
The size of the content. This property can be used whenever the size of the content of an InformationElement differs from the size of the DataObject. (e.g. because of compression, encoding, encryption or any other representation issues). The contentSize in expressed in bytes.
Date the DataObject was changed in any way. Note that this date refers to the modification of the DataObject itself (i.e. the physical representation). Compare with nie:contentModified.
A unit of data that is created, annotated and processed on the user desktop. It represents a native structure the user works with. The usage of the term 'native' is important. It means that a DataObject can be directly mapped to a data structure maintained by a native application. This may be a file, a set of files or a part of a file. The granularity depends on the user. This class is not intended to be instantiated by itself. Use more specific subclasses.
Links a metadata graph to the graph for which it specifies the core graph properties including the semantics and the graph namespace. A graph can have only one unique core metadata graph
A common superproperty for all relations between a piece of content and other pieces of data (which may be interpreted as other pieces of content).
Generic property used to express 'logical' containment relationships between DataObjects. NIE extensions are encouraged to provide more specific subproperties of this one. It is advisable for actual instances of InformationElement to use those specific subproperties. Note the difference between 'physical' containment (isPartOf) and logical containment (isLogicalPartOf)
A marker class to identify functional properties
An overall topic of the content of a InformationElement
Points to the representation of the view specification required to generate the graph view in question
The date of a modification of the original content (not its corresponding DataObject or local copy). Compare with nie:modified.