Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- ContactListDataObject comment "An entity occuring on a contact list (usually interpreted as an nco:Contact)".
- ContactMedium comment "A superclass for all contact media - ways to contact an entity represented by a Contact instance. Some of the subclasses of this class (the various kinds of telephone numbers and postal addresses) have been inspired by the values of the TYPE parameter of ADR and TEL properties defined in RFC 2426 sec. 3.2.1. and 3.3.1 respectively. Each value is represented by an appropriate subclass with two major exceptions TYPE=home and TYPE=work. They are to be expressed by the roles these contact media are attached to i.e. contact media with TYPE=home parameter are to be attached to the default role (nco:Contact or nco:PersonContact), whereas media with TYPE=work parameter should be attached to nco:Affiliation or nco:OrganizationContact.".
- EmailAddress comment "An email address. The recommended best practice is to use mailto: uris for instances of this class.".
- Gender comment "Gender. Instances of this class may include male and female.".
- Hobby comment "Instances of this class represent personal hobbies and interests.".
- IMAccount comment "An account in an Instant Messaging system.".
- IMCapability comment "Capabilities of a cetain IMAccount.".
- IMStatusType comment "The status type of an IMAccount. Based on the Connection_Presence_Type enumeration of the Telepathy project: http://telepathy.freedesktop.org/spec/Connection_Interface_Simple_Presence.html#Enum:Connection_Presence_Type".
- MessagingNumber comment "A number that can accept textual messages.".
- ModemNumber comment "A modem phone number. Inspired by the (TYPE=modem) parameter of the TEL property as defined in RFC 2426 sec 3.3.1.".
- Name comment "A class representing a contact's name. Possesses various attributes.".
- OrganizationContact comment "A Contact that denotes on Organization.".
- PersonContact comment "A Contact that denotes a Person. A person can have multiple Affiliations.".
- PersonName comment "A class representing a person contact's name. Possesses various attributes.".
- PhoneNumber comment "A telephone number.".
- PostalAddress comment "A postal address. A class aggregating the various parts of a value for the 'ADR' property as defined in RFC 2426 Sec. 3.2.1.".
- Role comment "A role played by a contact. Contacts that denote people, can have many roles (e.g. see the hasAffiliation property and Affiliation class). Contacts that denote Organizations or other Agents usually have one role. Each role can introduce additional contact media.".
- VoicePhoneNumber comment "A telephone number with voice communication capabilities. Class inspired by the TYPE=voice parameter of the TEL property defined in RFC 2426 sec. 3.3.1".
- contributor comment "An entity responsible for making contributions to the content of the InformationElement.".
- creator comment "Creator of an information element, an entity primarily responsible for the creation of the content of the data object.".
- hasContactMedium comment "A superProperty for all properties linking a Contact to an instance of a contact medium.".
- url comment "A uniform resource locator associated with the given role of a Contact. Inspired by the 'URL' property defined in RFC 2426 Sec. 3.6.8.".
- Archive comment "A compressed file. May contain other files or folder inside.".
- ArchiveItem comment "A file entity inside an archive.".
- Attachment comment "A file attached to another data object. Many data formats allow for attachments: emails, vcards, ical events, id3 and exif...".
- Audio comment "A file containing audio content".
- Bookmark comment "A bookmark of a webbrowser. Use nie:title for the name/label, nie:contentCreated to represent the date when the user added the bookmark, and nie:contentLastModified for modifications. nfo:bookmarks to store the link.".
- BookmarkFolder comment "A folder with bookmarks of a webbrowser. Use nfo:containsBookmark to relate Bookmarks. Folders can contain subfolders, use containsBookmarkFolder to relate them.".
- CompressionType comment "Type of compression. Instances of this class represent the limited set of values allowed for the nfo:compressionType property.".
- DataContainer comment "A superclass for all entities, whose primary purpose is to serve as containers for other data object. They usually don't have any \"meaning\" by themselves. Examples include folders, archives and optical disc images.".
- DeletedResource comment "A file entity that has been deleted from the original source. Usually such entities are stored within various kinds of 'Trash' or 'Recycle Bin' folders.".
- Document comment "A generic document. A common superclass for all documents on the desktop.".
- EmbeddedFileDataObject comment "A file embedded in another data object. There are many ways in which a file may be embedded in another one. Use this class directly only in cases if none of the subclasses gives a better description of your case.".
- EncryptionStatus comment "The status of the encryption of an InformationElement. nfo:encryptedStatus means that the InformationElement has been encrypted and couldn't be decrypted by the extraction software, thus no content is available. nfo:decryptedStatus means that decryption was successfull and the content is available.".
- FileDataObject comment "A resource containing a finite sequence of bytes with arbitrary information, that is available to a computer program and is usually based on some kind of durable storage. A file is durable in the sense that it remains available for programs to use after the current program has finished.".
- FileHash comment "A fingerprint of the file, generated by some hashing function.".
- Filesystem comment "A filesystem. Examples of filesystems include hard disk partitions, removable media, but also images thereof stored in files such as ISO.".
- Font comment "A font.".
- Image comment "A file containing an image.".
- Media comment "A piece of media content. This class may be used to express complex media containers with many streams of various media content (both aural and visual).".
- MediaFileListEntry comment "A single node in the list of media files contained within an MediaList instance. This class is intended to provide a type all those links have. In valid NRL untyped resources cannot be linked. There are no properties defined for this class but the application may expect rdf:first and rdf:last links. The former points to the DataObject instance, interpreted as Media the latter points at another MediaFileListEntr. At the end of the list there is a link to rdf:nil.".
- MediaList comment "A file containing a list of media files.e.g. a playlist".
- PaginatedTextDocument comment "A file containing a text document, that is unambiguously divided into pages. Examples might include PDF, DOC, PS, DVI etc.".
- Placemark comment "One placemark within a placemark container/file. Use nie:title for the name/label, nao:creator for defining the creator.".
- PlacemarkContainer comment "A data object containing placemark(s). Use nie:contentCreated to represent the date when the user created the dataobject, nao:creator for defining the creator, nie:contentLastModified for modifications. nfo:containsPlacemark to refer to individual placemarks within.".
- PlainTextDocument comment "A file containing plain text (ASCII, Unicode or other encodings). Examples may include TXT, HTML, XML, program source code etc.".
- RasterImage comment "A raster image.".
- Software comment "A piece of software. Examples may include applications and the operating system. This interpretation most commonly applies to SoftwareItems.".
- SourceCode comment "Code in a compilable or interpreted programming language.".
- TextDocument comment "A text document".
- Video comment "A video file.".
- Visual comment "File containing visual content.".
- bitDepth comment "A common superproperty for all properties signifying the amount of bits for an atomic unit of data. Examples of subproperties may include bitsPerSample and bitsPerPixel".
- channels comment "Number of channels. This property is to be used directly if no detailed information is necessary. Otherwise use more detailed subproperties.".
- count comment "A common superproperty for all properties signifying the amount of atomic media data units. Examples of subproperties may include sampleCount and frameCount.".
- depiction comment "Relates an information element to an image which depicts said element.".
- depicts comment "Relates an image to the information elements it depicts.".
- rate comment "A common superproperty for all properties specifying the media rate. Examples of subproperties may include frameRate for video and sampleRate for audio. This property is expressed in units per second.".
- AccessClassification comment "Access classification of a calendar component. Introduced to express \nthe set of values for the ncal:class property. The user may use instances\nprovided with this ontology or create his/her own with desired semantics.\nSee the documentation of ncal:class for details.".
- Alarm comment "Provide a grouping of component properties that define an alarm.".
- AlarmAction comment "Action to be performed on alarm. This class has been introduced to express the limited set of values of the ncal:action property. Please refer to the documentation of ncal:action for details.".
- Attachment comment "An object attached to a calendar entity. This class has been introduced to serve as a structured value of the ncal:attach property. See the documentation of ncal:attach for details.".
- AttachmentEncoding comment "Attachment encoding. This class has been introduced to express the limited vocabulary of values for the ncal:encoding property. See the documentation of ncal:encoding for details.".
- Attendee comment "An attendee of an event. This class has been introduced to serve as the range for ncal:attendee property. See documentation of ncal:attendee for details.".
- AttendeeOrOrganizer comment "A common superclass for ncal:Attendee and ncal:Organizer.".
- AttendeeRole comment "A role the attendee is going to play during an event. This class has been introduced to express the limited vocabulary for the values of ncal:role property. Please refer to the documentation of ncal:role for details.".
- BydayRulePart comment "Expresses the compound value of a byday part of a recurrence rule. It stores the weekday and the integer modifier. Inspired by RFC 2445 sec. 4.3.10".
- Calendar comment "A calendar. Inspirations for this class can be traced to the VCALENDAR component defined in RFC 2445 sec. 4.4, but it may just as well be used to represent any kind of Calendar.".
- CalendarDataObject comment "A DataObject found in a calendar. It is usually interpreted as one of the calendar entity types (e.g. Event, Journal, Todo etc.)".
- CalendarScale comment "A calendar scale. This class has been introduced to provide the limited vocabulary for the ncal:calscale property.".
- CalendarUserType comment "A calendar user type. This class has been introduced to express the limited vocabulary for the ncal:cutype property. See documentation of ncal:cutype for details.".
- Event comment "Provide a grouping of component properties that describe an event.".
- EventStatus comment "A status of an event. This class has been introduced to express\nthe limited set of values for the ncal:status property. The user may\nuse the instances provided with this ontology or create his/her own.\nSee the documentation for ncal:eventStatus for details.".
- Freebusy comment "Provide a grouping of component properties that describe either a request for free/busy time, describe a response to a request for free/busy time or describe a published set of busy time.".
- FreebusyPeriod comment "An aggregate of a period and a freebusy type. This class has been introduced to serve as a range of the ncal:freebusy property. See documentation for ncal:freebusy for details. Note that the specification of freebusy property states that the period is to be expressed using UTC time, so the timezone properties should NOT be used for instances of this class.".
- FreebusyType comment "Type of a Freebusy indication. This class has been introduced to serve as a limited set of values for the ncal:fbtype property. See the documentation of ncal:fbtype for details.".
- Journal comment "Provide a grouping of component properties that describe a journal entry.".
- JournalStatus comment "A status of a journal entry. This class has been introduced to express\nthe limited set of values for the ncal:status property. The user may\nuse the instances provided with this ontology or create his/her own.\nSee the documentation for ncal:journalStatus for details.".
- NcalPeriod comment "A period of time. Inspired by the PERIOD datatype specified in RFC 2445 sec. 4.3.9".
- NcalTimeEntity comment "A time entity. Conceived as a common superclass for NcalDateTime and NcalPeriod. According to RFC 2445 both DateTime and Period can be interpreted in different timezones. The first case is explored in many properties. The second case is theoretically possible in ncal:rdate property. Therefore the timezone properties have been defined at this level.".
- Organizer comment "An organizer of an event. This class has been introduced to serve as a range of ncal:organizer property. See documentation of ncal:organizer for details.".
- ParticipationStatus comment "Participation Status. This class has been introduced to express the limited vocabulary of values for the ncal:partstat property. See the documentation of ncal:partstat for details.".
- RecurrenceFrequency comment "Frequency of a recurrence rule. This class has been introduced to express a limited set of allowed values for the ncal:freq property. See the documentation of ncal:freq for details.".
- RecurrenceIdentifier comment "Recurrence Identifier. Introduced to provide a structure for the value of ncal:recurrenceId property. See the documentation of ncal:recurrenceId for details.".
- RecurrenceIdentifierRange comment "Recurrence Identifier Range. This class has been created to provide means to express the limited set of values for the ncal:range property. See documentation for ncal:range for details.".
- RequestStatus comment "Request Status. A class that was introduced to provide a structure for the value of ncal:requestStatus property. See documentation for ncal:requestStatus for details.".
- TimeTransparency comment "Time transparency. Introduced to provide a way to express\nthe limited vocabulary for the values of ncal:transp property.\nSee documentation of ncal:transp for details.".
- Timezone comment "Provide a grouping of component properties that defines a time zone.".
- Todo comment "Provide a grouping of calendar properties that describe a to-do.".
- TodoStatus comment "A status of a calendar entity. This class has been introduced to express\nthe limited set of values for the ncal:status property. The user may\nuse the instances provided with this ontology or create his/her own.\nSee the documentation for ncal:todoStatus for details.".
- Trigger comment "An alarm trigger. This class has been created to serve as the range of ncal:trigger property. See the documentation for ncal:trigger for more details.".
- TriggerRelation comment "The relation between the trigger and its parent calendar component. This class has been introduced to express the limited vocabulary for the ncal:related property. See the documentation for ncal:related for more details.".
- Weekday comment "Day of the week. This class has been created to provide the limited vocabulary for ncal:byday property. See the documentation for ncal:byday for details.".
- ncalRelation comment "A common superproperty for all types of ncal relations. It is not to be used directly.".
- Agent comment "An agent is the artificial counterpart to nao:Party. It can be a software component or some service.".
- FreeDesktopIcon comment "Represents a desktop icon as defined in the FreeDesktop Icon Naming Standard (http://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html).".
- Party comment "Represents a single or a group of individuals".
- Symbol comment "Represents a symbol, a visual representation of a resource. Typically a local or remote file would be double-typed to be used as a symbol. An alternative is nao:FreeDesktopIcon.".
- Tag comment "Represents a generic tag".
- annotation comment "Generic annotation for a resource".