byteSize
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.
- Comment
- 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.
- Domain
- DataObject
- Label
- byteSize
- MaxCardinality
- 1
- Range
- integer
characterSet
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.
- Comment
- 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.
- Domain
- InformationElement
- Label
- characterSet
- MaxCardinality
- 1
- Range
- string
- Comment
- A user comment about an InformationElement.
- Domain
- InformationElement
- Label
- comment
- Range
- string
contentCreated
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.
- Comment
- 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.
- Domain
- InformationElement
- Label
- contentCreated
- MaxCardinality
- 1
- Range
- dateTime
- SubPropertyOf
- created
- informationElementDate
- modified
contentLastModified
The date of the last modification of the original content (not its corresponding DataObject or local copy). Compare with nie:lastModified.
- Comment
- The date of the last modification of the original content (not its corresponding DataObject or local copy). Compare with nie:lastModified.
- Domain
- InformationElement
- Label
- contentLastModified
- MaxCardinality
- 1
- Range
- dateTime
- SubPropertyOf
- informationElementDate
- lastModified
- modified
contentSize
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.
- Comment
- 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.
- Domain
- InformationElement
- Label
- contentSize
- MaxCardinality
- 1
- Range
- integer
- Comment
- Content copyright
- Label
- copyright
- Range
- string
- SubPropertyOf
- Access Rights
- legal
coreGraph
Connects the data object with the graph that contains information about it. Deprecated in favor of a more generic nao:isDataGraphFor.
- Comment
- Connects the data object with the graph that contains information about it. Deprecated in favor of a more generic nao:isDataGraphFor.
- Deprecated
- true
- Domain
- DataObject
- Label
- coreGraph
- Range
- InstanceBase
created
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.
- Comment
- 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.
- Domain
- DataObject
- Label
- created
- MaxCardinality
- 1
- Range
- dateTime
- SubPropertyOf
- created
- Date Created
- modified
Data Source Graph
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.
- Comment
- 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.
- Label
- Data Source Graph
- SubClassOf
- InstanceBase
- Comment
- Represents a number of applicable modes for a data source.
- Domain
- DataSource
- Label
- Data Source Mode
- Range
- Mode
DataObject
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.
- Comment
- 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.
- Label
- DataObject
- SubClassOf
- Resource
DataSource
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...)
- Comment
- 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...)
- Label
- DataSource
- SubClassOf
- Resource
- Comment
- Marks the provenance of a DataObject, what source does a data object come from.
- Domain
- DataObject
- Label
- dataSource
- MinCardinality
- 1
- Range
- DataSource
- SubPropertyOf
- Source
depends
Dependency relation. A piece of content depends on another piece of data in order to be properly understood/used/interpreted.
- Comment
- Dependency relation. A piece of content depends on another piece of data in order to be properly understood/used/interpreted.
- Label
- depends
- Range
- DataObject
- SubPropertyOf
- relatedTo
description
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.
- Comment
- 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.
- Domain
- InformationElement
- Label
- description
- Range
- string
- SubPropertyOf
- description
- Description
- Comment
- Software used to "generate" the contents. E.g. a word processor name.
- Domain
- InformationElement
- Label
- generator
- Range
- string
generatorOption
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.
- Comment
- 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.
- Domain
- InformationElement
- Label
- generatorOption
hasLogicalPart
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)
- Comment
- 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)
- Domain
- InformationElement
- InverseProperty
- isLogicalPartOf
- Label
- hasLogicalPart
- Range
- InformationElement
- SubPropertyOf
- Has Part
hasPart
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.
- Comment
- 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.
- Domain
- InformationElement
- InverseProperty
- isPartOf
- Label
- hasPart
- Range
- DataObject
- SubPropertyOf
- Has Part
- relatedTo
- UserVisible
- false
html content
The HTML content of an information element. This property can be used to store text including formatting in a generic fashion.
- Comment
- The HTML content of an information element. This property can be used to store text including formatting in a generic fashion.
- Domain
- InformationElement
- Label
- html content
- MaxCardinality
- 1
- Range
- string
identifier
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.
- Comment
- 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.
- Domain
- InformationElement
- Label
- identifier
- Range
- string
- SubPropertyOf
- identifier
- Identifier
InformationElement
A unit of content the user works with. This is a superclass for all interpretations of a DataObject.
- Comment
- A unit of content the user works with. This is a superclass for all interpretations of a DataObject.
- Label
- InformationElement
- SubClassOf
- Resource
informationElementDate
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.
- Comment
- 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.
- Domain
- InformationElement
- Label
- informationElementDate
- Range
- dateTime
- SubPropertyOf
- Date
- Comment
- Links the DataObject with the InformationElement it is interpreted as.
- Domain
- DataObject
- InverseProperty
- isStoredAs
- Label
- interpretedAs
- Range
- InformationElement
isLogicalPartOf
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)
- Comment
- 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)
- Domain
- InformationElement
- InverseProperty
- hasLogicalPart
- Label
- isLogicalPartOf
- Range
- InformationElement
- SubPropertyOf
- Is Part Of
isPartOf
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.
- Comment
- 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.
- Domain
- DataObject
- InverseProperty
- hasPart
- Label
- isPartOf
- Range
- InformationElement
- SubPropertyOf
- Is Part Of
- UserVisible
- false
- Comment
- Links the information element with the DataObject it is stored in.
- Domain
- InformationElement
- InverseProperty
- interpretedAs
- Label
- isStoredAs
- Range
- DataObject
keyword
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.
- Comment
- 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.
- Domain
- InformationElement
- Label
- keyword
- Range
- string
language
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
- Comment
- 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
- Domain
- InformationElement
- Label
- language
- MaxCardinality
- 1
- Range
- string
- SubPropertyOf
- Language
lastModified
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.
- Comment
- 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.
- Domain
- DataObject
- Label
- lastModified
- MaxCardinality
- 1
- Range
- dateTime
- SubPropertyOf
- Date
- lastModified