| Subject | Object |
|---|
| pimo:Agent | "An agent (eg. person, group, software or physical artifact). The Agent class is the class of agents; things that do stuff. A well known sub-class is Person, representing people. Other kinds of agents include Organization and Group.
(inspired by FOAF).
Agent is not a subclass of NAO:Party." |
| pimo:Association | "An association between two or more pimo-things. This is used to model n-ary relations and metadata about relations. For example, the asociation of a person being organizational member is only effectual within a period of time (after the person joined the organization and before the person left the organization). There can be multiple periods of time when associations are valid." |
| pimo:Attendee | "The role of someone attending a social event." |
| pimo:Blog Post | "A blog note. You just want to write something down right now and need a place to do that. Add a blog-note! This is an example class for a document type, there are more detailled ontologies to model Blog-Posts (like SIOC)." |
| pimo:Building | "A structure that has a roof and walls and stands more or less permanently in one place; "there was a three-story building on the corner"; "it was an imposing edifice". (Definition from SUMO)." |
| pimo:City | "A large and densely populated urban area; may include several independent administrative districts; "Ancient Troy was a great city". (Definition from SUMO)" |
| pimo:ClassOrThing | "Superclass of class and thing. To add properties to both class and thing." |
| pimo:ClassOrThingOrPropertyOrAssociation | "Superclass of resources that can be generated by the user." |
| pimo:ClassRole | "Roles of classes in PIMO: concrete instances are Abstract and Concrete." |
| pimo:Collection | "A collection of Things, independent of their class. The items in the collection share a common property. Which property may be modelled explicitly or mentioned in the description of the Collection. The requirement of explicit modelling the semantic meaning of the collection is not mandatory, as collections can be created ad-hoc. Implizit modelling can be applied by the system by learning the properties. For example, a Collection of "Coworkers" could be defined as that all elements must be of class "Person" and have an attribute "work for the same Organization as the user". Further standards can be used to model these attributes." |
| pimo:Contract | "A binding agreement between two or more persons that is enforceable by law. (Definition from SUMO). This is an example class for a document type, there are more detailled ontologies to model Contracts." |
| pimo:Country | "The territory occupied by a nation; "he returned to the land of his birth"; "he visited several European countries". (Definition from SUMO)" |
| pimo:Document | "A generic document. This is a placeholder class for document-management domain ontologies to subclass. Create more and specified subclasses of pimo:Document for the document types in your domain. Documents are typically instances of both NFO:Document (modeling the information element used to store the document) and a LogicalMediaType subclass. Two examples are given for what to model here: a contract for a business domain, a BlogPost for an informal domain." |
| pimo:Event | "Something that happens
An Event is conceived as compact in time. (Definition from Merriam-Webster)" |
| pimo:Group of Persons | "A group of Persons. They are connected to each other by sharing a common attribute, for example they all belong to the same organization or have a common interest. Refer to pimo:Collection for more information about defining collections." |
| pimo:Locatable | "Things that can be at a location. Abstract class, use it as a superclass of things that can be placed in physical space." |
| pimo:Location | "A physical location. Subclasses are modeled for the most common locations humans work in: Building, City, Country, Room, State. This selection is intended to be applicable cross-cultural and cross-domain. City is a prototype that can be further refined for villages, etc. Subclass of a WGS84:SpatialThing, can have geo-coordinates." |
| pimo:Logical Media Type | "Logical media types represent the content aspect of information elements e.g. a flyer, a contract, a promotional video, a todo list. The user can create new logical media types dependend on their domain: a salesman will need MarketingFlyer, Offer, Invoice while a student might create Report, Thesis and Homework. This is independent from the information element and data object (NIE/NFO) in which the media type will be stored. The same contract can be stored in a PDF file, a text file, or an HTML website.
The groundingOccurrence of a LogicalMediaType is the Document that stores the content." |
| pimo:Meeting | "The social act of assembling for some common purpose; "his meeting with the salesman was the high point of his day". (Definition from SUMO)" |
| pimo:Member | "The role of one or multiple persons being a member in one or multiple organizations. Use pimo:organization and pimo:roleHolder to link to the organizations and persons." |
| pimo:Note | "A note. The textual contents of the note should be expressed in the nao:description value of the note." |
| pimo:Organization | "An administrative and functional structure (as a business or a political party). (Definition from Merriam-Webster)" |
| pimo:Person | "Represents a person. Either living, dead, real or imaginary. (Definition from foaf:Person)" |
| pimo:Personal Information Model | "A Personal Information Model (PIMO) of a user. Represents the sum of all information from the personal knowledge workspace (in literature also referred to as Personal Space of Information (PSI)) which a user needs for Personal Information Management (PIM)." |
| pimo:Process Concept | "Concepts that relate to a series of actions or operations conducing to an end. Abstract class. Defines optional start and endtime properties, names taken from NCAL." |
| pimo:Project | "Any piece of work that is undertaken or attempted (Wordnet). An enterprise carefully planned to achieve a particular aim (Oxford Dictionary)." |
| pimo:Role of Person | "A person takes a certain role in a given context. The role can be that of "a mentor or another person" or "giving a talk at a meeting", etc." |
| pimo:Room | "A properPart of a Building which is separated from the exterior of the Building and/or other Rooms of the Building by walls. Some Rooms may have a specific purpose, e.g. sleeping, bathing, cooking, entertainment, etc. (Definition from SUMO)." |
| pimo:Social Event | "A social occasion or activity. (Definition from Merriam-Webster)" |
| pimo:State | "Administrative subdivisions of a Nation that are broader than any other political subdivisions that may exist. This Class includes the states of the United States, as well as the provinces of Canada and European countries. (Definition from SUMO)." |
| pimo:Tag | "Tags in the context of PIMO. A marker class for Things that are used to categorize documents (or other things). Tags must be a kind of Thing and must have a unique label. Documents should not be Tags by default." |
| pimo:Task | "A (usually assigned) piece of work (often to be finished within a certain time). (Definition from Merriam-Webster)" |
| pimo:Thing | "Entities that are in the direct attention of the user when doing knowledge work." |
| pimo:Topic | "A topic is the subject of a discussion or document. Topics are distinguished from Things in their taxonomic nature, examples are scientific areas such as "Information Science", "Biology", or categories used in content syndication such as "Sports", "Politics". They are specific to the user's domain." |
| pimo:association effectual during | "During which time is this association effective? If omitted, the association is always effective. Start time and end-time may be left open, an open start time indicates that the fact is unknown, an open end-time indicates that the end-date is either unknown or the association has not ended.
There can be multiple effectual periods." |
| pimo:association member | "An super-property of all roles that an entity can have in an association. Member is the generic role of a thing in an association. Association subclasses should define sub-properties of this property. Associations can have Things as" |
| pimo:attendee | "A social event is attended by a person." |
| pimo:attending meeting | "the attended meeting" |
| pimo:attends event | "A person attends a social event." |
| pimo:broader topic | "The object topic is more general in meaning than the subject topic. Transitive. Similar to skos:broader." |
| pimo:class role | "Annotating abstract and concrete classes. Implementations may offer the feature to hide abstract classes. By default, classes are concrete. Classes can be declared abstract by setting their classRole to abstract. Instances should not have an abstract class as type (if not inferred)." |
| pimo:contains location | "The subject location contains the object location. For example, a building contains a room or a country contains a city." |
| pimo:created Pimo | "The creator of the Personal Information Model. The human being whose mental models are represented in the PIMO." |
| pimo:creator | "The creator of the Personal Information Model. A subproperty of NAO:creator. The human being whose mental models are represented in the PIMO. Range is an Agent." |
| pimo:datatype property | "The object of statements is a literal, resource, or datatype value describing the subject thing. Users should be able to edit statements defined with this property. Abstract super-property." |
| pimo:duration | "The duration of the process (meeting, event, etc). Difference between start and end time." |
| pimo:end date | "This property specifies the date and time when a process ends. Inspired by NCAL:dtend." |
| pimo:global namespace | "The global namespace of this user using the semdesk uri scheme, based on the Global Identifier of the user. Example semdesk://bob@example.com/things/. See http://dev.nepomuk.semanticdesktop.org/repos/trunk/doc/2008_09_semdeskurischeme/index.html" |
| pimo:grounding for deleted thing | "This NIE Information Element was used as a grounding occurrence for the object Thing. The Thing was then deleted by the user manually, indicating that this Information Element should not cause an automatic creation of another Thing in the future. The object resource has no range to indicate that it was completely removed from the user's PIMO, including the rdf:type statement. Relevant for data alignment and enrichment algorithms." |
| pimo:grounding occurrence | "The subject Thing represents the entity that is described in the object InformationElement. The subject Thing is the canonical, unique representation in the personal information model for the entity described in the object. Multiple InformationElements can be the grounding occurrence of the same Thing, one InformationElement can be the groundingOccurrence of only one Thing." |
| pimo:has deprecated representation | "The subject Thing was represented previously using the object resource. This indicates that the object resource was a duplicate representation of the subject and merged with the subject. Implementations can use this property to resolve dangling links in distributed system. When encountering resources that are deprecated representations of a Thing, they should be replaced with the Thing. The range is not declared as we assume all knowledge about the object is gone, including its rdf:type." |
| pimo:has folder | "Folders can be used to store information elements related to a Thing or Class. This property can be used to connect a Class or Thing to existing Folders. Implementations can suggest annotations for documents stored inside these folders or suggest the folder for new documents related to the Thing or Class." |
| pimo:has group member | "Defines which agents form part of a given person group." |
| pimo:has interest | "Marks a pimo:Tag or a pimo:Topic (its subclass) as an interest of a person or a group." |
| pimo:has location | "The subject thing is currently located at the object location." |
| pimo:has other conceptualization | "Short: hasOtherRepresentation points from a Class in your PIMO to a class in a domain ontology that represents the same class. Longer: hasOtherConceptualization means that a class of real world objects O represented by a concept C1 in the ontology has additional conceptualizations (as classes C2-Cn in different domain ontologies).
This means: IF (O_i is conceptialized by C_j in Ontology_k) AND (O_l is conceptialized by C_m in Ontology_n) THEN (O_i and O_l is the same set of objects).
hasOtherConceptualization is an transitive relation, but not equivalent (not symmetric nor reflexive)." |
| pimo:has other representation | "hasOtherRepresentation points from a Thing in your PIMO to a thing in an ontology that represents the same real world thing.
This means that the real world object O represented by an instance I1 has additional representations (as instances I2-In of different conceptualizations).
This means: IF (I_i represents O_j in Ontology_k) AND (I_m represents O_n in Ontology_o) THEN (O_n and O_j are the same object).
hasOtherRepresentation is a transitive relation, but not equivalent (not symmetric nor reflexive). For example, the URI of a foaf:Person representation published on the web is a hasOtherRepresentation for the person. This property is inverse functional, two Things from two information models having the same hasOtherRepresentation are considered to be representations of the same entity from the real world." |
| pimo:has part | "The object is part of the subject. Like a page is part of a book or an engine is part of a car. You can make sub-properties of this to reflect more detailed relations. The semantics of this relations is the same as skos:narrowerPartitive" |
| pimo:has tag | "The subject's contents describes the object. Or the subject can be seen as belonging to the thing described by the object. Similar semantics as skos:subject." |
| pimo:is defined by | "Each element in a PIMO must be connected to the PIMO, to be able to track multiple PIMOs in a distributed scenario. Also, this is the way to find the user that this Thing belongs to." |
| pimo:is interest Of | "Links interests, as instances of pimo:Tag or a pimo:Topic (its subclass), to a person or a group." |
| pimo:is location of | "The subject location is the current location of the object." |
| pimo:is member of organization | "The subject person or organozation (Agent) is member of the object organization." |
| pimo:is related | "The thing is related to the other thing. Similar in meaning to skos:related. Symmetric but not transitive." |
| pimo:is tag for | "This thing is described further in the object thing. Similar semantics as skos:isSubjectOf." |
| pimo:is writeable | "Defines if this information model can be modified by the user of the system. This is usually false for imported ontologies and true for the user's own PersonalInformationModel." |
| pimo:jabber ID of the user | "Jabber-ID of the user. Used to communicate amongst peers in the social scenario of the semantic desktop. Use the xmpp node identifier as specified by RFC3920, see http://www.xmpp.org/specs/rfc3920.html#addressing-node. The format is the same as e-mail addresses: username@hostname." |
| pimo:local namespace | "The local namespace of this user using the semdesk uri scheme, based on the Local Identifier of the user. Example semdesk://bob@/things/. See http://dev.nepomuk.semanticdesktop.org/repos/trunk/doc/2008_09_semdeskurischeme/index.html" |
| pimo:located within | "The subject location is contained within the object location. For example, a room is located within a building or a city is located within a country." |
| pimo:member of group | "This property can be used to organise agents within groups. Supplemented with an inverse property." |
| pimo:object property | "The object of statements is another Thing. Users should be able to edit statements defined with this property. Abstract super-property." |
| pimo:occurrence | "The subject Thing is represented also in the object resource. All facts added to the object resource are valid for the subject thing. The subject is the canonical represtation of the object. In particual, this implies when (?object ?p ?v) -> (?subject ?p ?v) and (?s ?p ?object) -> (?s ?p ?subject). The class of the object is not defined, but should be compatible with the class of the subject. Occurrence relations can be inferred through same identifiers or referencingOccurrence relations." |
| pimo:organization | "relation to the organization in an OrganizationMember association." |
| pimo:organization has member | "The subject organization has the object person or organization (Agent) as a member." |
| pimo:part of | "This is part of the object. Like a page is part of a book or an engine is part of a car. You can make sub-properties of this to reflect more detailed relations." |
| pimo:referencing occurrence | "The subject thing is described in the object document. Ideally, the document is public and its primary topic is the thing. Although this property is not inverse-functional (because the Occurrences are not canonical elements of a formal ontology) this property allows to use public documents, such as wikipedia pages, as indicators identity. The more formal hasOtherRepresentation property can be used when an ontology about the subject exists." |
| pimo:represented by other slot | "hasOtherSlot points from a clot in your PIMO to a slot in a domain ontology that represents the same connection idea." |
| pimo:role context | "The context where the role-holder impersonates this role. For example, the company where a person is employed." |
| pimo:role holder | "the person taking the role" |
| pimo:root topic | "The root topics of this PersonalInformationModel's topic hierarchy. Every topic that has no pimo:superTopic is a root topic. Semantically equivalent to skos:hasTopConcept." |
| pimo:start date | "This property specifies when the process begins. Inspired by NCAL:dtstart." |
| pimo:sub topic | "The object topic is more specific in meaning than the subject topic. Transitive. Similar in meaning to skos:narrower" |
| pimo:tag label | "The unique label of the tag. The label must be unique within the scope of one PersonalInformationModel. It is required and a subproperty of nao:prefLabel. It clarifies the use of nao:personalIdentifier by restricting the scope to tags. Semantically equivalent to skos:prefLabel, where uniqueness of labels is also recommended." |
| pimo:task due time | "when is this task due? Represented in ISO 8601, example: 2003-11-22T17:00:00" |
| pimo:wiki text | "A wiki-like free-text description of a Thing or a Class. The text can be formatted using a limited set of HTML elements and can contain links to other Things. The format is described in detail in the WIF specification (http://semanticweb.org/wiki/Wiki_Interchange_Format)." |
