# Resource

Uri:
  file:///var/lib/snapd/desktop/applications/snapd-desktop-integration_snapd-desktop-integration.desktop


Uri:
  urn:theme-icon:/snap/snapd-desktop-integration/current/usr/share/icons/hicolor/scalable/apps/app-center.svg


Uri:
  file:///home/adminek/Downloads/Zarz%C4%85dzenie%2057%20wprowadzenie%20zaktualizowanych%20Standard%C3%B3w%20Ochrony%20Ma%C5%82oletnich.pdf


Uri:
  file:///home/adminek/Downloads/Zarz%C4%85dzenie%2061%20w%20spr.%20uprz%C4%85tni%C4%99cia%20sal%20lekcyjnych%20i%20zapleczy.pdf


# rdfs:Resource

rdfs:label: deprecated
rdfs:comment:
  If this property is assigned, the subject class, property, or resource, is deprecated and should not be used in production systems any longer. It may be removed without further notice. This property is a Tracker extension


rdfs:label: Coverage
rdfs:comment:
  The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.


rdfs:label: Data Object
rdfs: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.


rdfs:label: Data Source
rdfs: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...)


rdfs:label: Information Element
rdfs:comment:
  A unit of content the user works with. This is a superclass for all interpretations of a DataObject.


rdfs:label: URL
rdfs:comment:
  URL pointing at the location of the resource. 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.


rdfs: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


rdfs:comment:
  The date of the last modification of the original content (not its corresponding DataObject or local copy). Compare with nie:lastModified


rdfs:label: Language
rdfs:comment:
  Language the InformationElement is expressed in. Users are encouraged to use the two-letter code specified in the RFC 3066


rdfs:label: Plain-text content
rdfs:comment:
  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.


rdfs:comment:
  A common superproperty for all properties that point at legal information about an Information Element


rdfs:comment:
  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).


rdfs: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


rdfs:comment:
  Dependency relation. A piece of content depends on another piece of data in order to be properly understood/used/interpreted


rdfs:comment:
  The current version of the given data object. Exact semantics is unspecified at this level. Use more specific subproperties if needed


rdfs: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


rdfs:comment:
  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


rdfs: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


rdfs: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


rdfs: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


rdfs: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)


rdfs: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


rdfs: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


rdfs:comment:
  The type of the license. Possible values for this field may include 'GPL', 'BSD', 'Creative Commons' etc.


rdfs: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


rdfs: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)


rdfs: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


rdfs:comment:
  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


rdfs:comment:
  In the context of the social semantic desktop the textual annotation provided via rdfs:comment is meant for technical users, the textual annotation here is aimed at average users and is meant to be used to define custom descriptions of resources on the desktop


rdfs:comment:
  Annotation for a resource in the form of a numeric rating (float value), allowed values are between 1 and 10 whereas 0 is interpreted as not set


rdfs:label: deprecated
rdfs:comment:
  If this property is assigned, the subject class, property, or resource, is deprecated and should not be used in production systems any longer. It may be removed without further notice.


rdfs:label: Is related
rdfs:comment:
  This property defines a symmetric relation between any two resources. In order for this property to be used legally, the relationship must be symmetric.


rdfs:label: Role
rdfs: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.


rdfs:label: Affiliation
rdfs:comment:
  Aggregates three properties defined in RFC2426. Originally all three were attached directly to a person. One person could have only one title and one role within one organization. This class is intended to lift this limitation.


rdfs:label: ContactGroup
rdfs:comment:
  A group of Contacts. Could be used to express a group in an addressbook or on a contact list of an IM application. One contact can belong to many groups.


rdfs:label: ContactList
rdfs:comment:
  A contact list, this class represents an addressbook or a contact list of an IM application. Contacts inside a contact list can belong to contact groups.


rdfs:label: ContactMedium
rdfs: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.


rdfs:label: PostalAddress
rdfs: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.


rdfs:label: ModemNumber
rdfs:comment:
  A modem phone number. Inspired by the (TYPE=modem) parameter of the TEL property as defined in RFC 2426 sec  3.3.1.


rdfs:label: PagerNumber
rdfs:comment:
  A pager phone number. Inspired by the (TYPE=pager) parameter of the TEL property as defined in RFC 2426 sec  3.3.1.


rdfs:label: VoicePhoneNumber
rdfs: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


rdfs:label: VideoTelephoneNumber
rdfs:comment:
  A Video telephone number. A class inspired by the TYPE=video parameter of the TEL property defined in RFC 2426 sec. 3.3.1


rdfs:label: IsdnNumber
rdfs:comment:
  An ISDN phone number. Inspired by the (TYPE=isdn) parameter of the TEL property as defined in RFC 2426 sec  3.3.1.


rdfs:label: ParcelDeliveryAddress
rdfs:comment:
  Parcel Delivery Addresse. Class inspired by TYPE=parcel parameter of the ADR property defined in RFC 2426 sec. 3.2.1


rdfs:label: FaxNumber
rdfs:comment:
  A fax number. Inspired by the (TYPE=fax) parameter of the TEL property as defined in RFC 2426 sec  3.3.1.


rdfs:label: CarPhoneNumber
rdfs:comment:
  A car phone number. Inspired by the (TYPE=car) parameter of the TEL property as defined in RFC 2426 sec  3.3.1.


rdfs:label: PcsNumber
rdfs:comment:
  Personal Communication Services Number. A class inspired by the TYPE=pcs parameter of the TEL property defined in RFC 2426 sec. 3.3.1


rdfs:label: InternationalDeliveryAddress
rdfs:comment:
  International Delivery Addresse. Class inspired by TYPE=intl parameter of the ADR property defined in RFC 2426 sec. 3.2.1


rdfs:label: BbsNumber
rdfs:comment:
  A Bulletin Board System (BBS) phone number. Inspired by the (TYPE=bbsl) parameter of the TEL property as defined in RFC 2426 sec  3.3.1.


rdfs:label: CellPhoneNumber
rdfs:comment:
  A cellular phone number. Inspired by the (TYPE=cell) parameter of the TEL property as defined in RFC 2426 sec  3.3.1. Usually a cellular phone can accept voice calls as well as textual messages (SMS), therefore this class has two superclasses.


rdfs:label: DomesticDeliveryAddress
rdfs:comment:
  Domestic Delivery Addresse. Class inspired by TYPE=dom parameter of the ADR property defined in RFC 2426 sec. 3.2.1


rdfs:label: nameFamily
rdfs:comment:
  The family name of an Object represented by this Contact. These applies to people that have more than one given name. The 'first' one is considered 'the' given name (see nameGiven) property. All additional ones are considered 'additional' names. The name inherited from parents is the 'family name'. e.g. For Dr. John Phil Paul Stevenson Jr. M.D. A.C.P. we have contact with: honorificPrefix: 'Dr.', nameGiven: 'John', nameAdditional: 'Phil', nameAdditional: 'Paul', nameFamily: 'Stevenson', honorificSuffix: 'Jr.', honorificSuffix: 'M.D.', honorificSuffix: 'A.C.P.'. These properties form an equivalent of the compound 'N' property as defined in RFC 2426 Sec. 3.1.2


rdfs:label: nameGiven
rdfs:comment:
  The given name for the object represented by this Contact. See documentation for 'nameFamily' property for details.


rdfs:label: nameAdditional
rdfs:comment:
  Additional given name of an object represented by this contact. See documentation for 'nameFamily' property for details.


rdfs:label: fullname
rdfs:comment:
  To specify the formatted text corresponding to the name of the object the Contact represents. An equivalent of the FN property as defined in RFC 2426 Sec. 3.1.1.


rdfs:label: url
rdfs: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.


rdfs:label: creator
rdfs:comment:
  Creator of a data object, an entity primarily responsible for the creation of the content of the data object.


rdfs:label: region
rdfs:comment:
  Region. Inspired by the fifth part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1


rdfs:label: key
rdfs:comment:
  An encryption key attached to a contact. Inspired by the KEY property defined in RFC 2426 sec. 3.7.2


rdfs:label: nameHonorificSuffix
rdfs:comment:
  A suffix for the name of the Object represented by the given object. See documentation for the 'nameFamily' for details.


rdfs:label: contactUID
rdfs:comment:
  A value that represents a globally unique  identifier corresponding to the individual or resource associated with the Contact. An equivalent of the 'UID' property defined in RFC 2426 Sec. 3.6.7


rdfs:label: country
rdfs:comment:
  A part of an address specifying the country. Inspired by the seventh part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1


rdfs:label: nameHonorificPrefix
rdfs:comment:
  A prefix for the name of the object represented by this Contact. See documentation for the 'nameFamily' property for details.


rdfs:label: extendedAddress
rdfs:comment:
  An extended part of an address. This field might be used to express parts of an address that aren't include in the name of the Contact but also aren't part of the actual location. Usually the streed address and following fields are enough for a postal letter to arrive. Examples may include ('University of California Campus building 45', 'Sears Tower 34th floor' etc.) Inspired by the second part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1


rdfs:label: hasIMAccount
rdfs:comment:
  Indicates that this Instant Messaging account has the specified Instant Messaging address in the contact list.


rdfs:label: hasLocation
rdfs:comment:
  Geographical location of the contact. Inspired by the 'GEO' property specified in RFC 2426 Sec. 3.4.2


rdfs:label: nickname
rdfs:comment:
  A nickname of the Object represented by this Contact. This is an equivalen of the 'NICKNAME' property as defined in RFC 2426 Sec. 3.1.3.


rdfs:label: containsContact
rdfs:comment:
  A property used to group contacts into contact groups. This property was NOT defined in the VCARD standard. See documentation for the 'ContactList' class for details


rdfs:label: imID
rdfs:comment:
  Identifier of the IM account. Examples of such identifier might include ICQ UINs, Jabber IDs, Skype names etc.


rdfs:label: imAccountAddress
rdfs:comment:
  Instant Messaging address of this IM account. The user 'me' can send and receive messages from this IM address.


rdfs:label: note
rdfs:comment:
  A note about the object represented by this Contact. An equivalent for the 'NOTE' property defined in RFC 2426 Sec. 3.6.2


rdfs:label: representative
rdfs:comment:
  An object that represent an object represented by this Contact. Usually this property is used to link a Contact to an organization, to a contact to the representative of this organization the user directly interacts with. An equivalent for the 'AGENT' property defined in RFC 2426 Sec. 3.5.4


rdfs:label: streetAddress
rdfs:comment:
  The streed address. Inspired by the third part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1


rdfs:label: hasPhoneNumber
rdfs:comment:
  A number for telephony communication with the object represented by this Contact. An equivalent of the 'TEL' property defined in RFC 2426 Sec. 3.3.1


rdfs:label: photo
rdfs:comment:
  Photograph attached to a Contact. The DataObject refered to by this property is usually interpreted as an nfo:Image. Inspired by the PHOTO property defined in RFC 2426 sec. 3.1.4


rdfs:label: birthDate
rdfs:comment:
  Birth date of the object represented by this Contact. An equivalent of the 'BDAY' property as defined in RFC 2426 Sec. 3.1.5.


rdfs:label: hasEmailAddress
rdfs:comment:
  An address for electronic mail communication with the object specified by this contact. An equivalent of the 'EMAIL' property as defined in RFC 2426 Sec. 3.3.1.


rdfs:label: postalcode
rdfs:comment:
  Postal Code. Inspired by the sixth part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1


rdfs:label: org
rdfs:comment:
  Name of an organization or a unit within an organization the object represented by a Contact is associated with. An equivalent of the 'ORG' property defined in RFC 2426 Sec. 3.5.5


rdfs:label: voiceMail
rdfs:comment:
  Indicates if the given number accepts voice mail. (e.g. there is an answering machine). Inspired by TYPE=msg parameter of the TEL property defined in RFC 2426 sec. 3.3.1


rdfs:label: contactGroupName
rdfs:comment:
  The name of the contact group. This property was NOT defined in the VCARD standard. See documentation of the 'ContactGroup' class for details


rdfs:label: locality
rdfs:comment:
  Locality or City. Inspired by the fourth part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1


rdfs:label: sound
rdfs:comment:
  Sound clip attached to a Contact. The DataObject refered to by this property is usually interpreted as an nfo:Audio. Inspired by the SOUND property defined in RFC 2425 sec. 3.6.6.


rdfs:label: hobby
rdfs:comment:
  A hobby associated with a PersonContact. This property can be used to express hobbies and interests.


rdfs:label: hasPostalAddress
rdfs:comment:
  The default Address for a Contact. An equivalent of the 'ADR' property as defined in RFC 2426 Sec. 3.2.1.


rdfs:label: imAccountType
rdfs:comment:
  Type of the IM account. This may be the name of the service that provides the IM functionality. Examples might include Jabber, ICQ, MSN etc


rdfs:label: pobox
rdfs:comment:
  Post office box. This is the first part of the value of the 'ADR' property as defined in RFC 2426, sec. 3.2.1


rdfs:label: displayname
rdfs:comment:
  The user-visible name of this account. This SHOULD be chosen by the user at account creation time. The account creation user interface is responsible for setting a reasonable default value in the user's locale; something like	'Jabber (bob@example.com)' would be sensible.


rdfs:label: FileDataObject
rdfs: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.


rdfs:label: Software
rdfs:comment:
  A piece of software. Examples may include applications and the operating system. This interpretation most commonly applies to SoftwareItems.


rdfs:label: Media
rdfs: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).


rdfs:label: DataContainer
rdfs: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.


rdfs:label: RemotePortAddress
rdfs:comment:
  An address specifying a remote host and port. Such an address can be interpreted in many ways (examples of such interpretations include mailboxes, websites, remote calendars or filesystems), depending on an interpretation, various kinds of data may be extracted from such an address.


rdfs:label: MediaFileListEntry
rdfs: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.


rdfs:label: CompressionType
rdfs:comment:
  Type of compression. Instances of this class represent the limited set of values allowed for the nfo:compressionType property.


rdfs:label: Icon
rdfs:comment:
  An Icon (regardless of whether it's a raster or a vector icon. A resource representing an icon could have two types (Icon and Raster, or Icon and Vector) if required.


rdfs:label: PlainTextDocument
rdfs:comment:
  A file containing plain text (ASCII, Unicode or other encodings). Examples may include TXT, HTML, XML, program source code etc.


rdfs:label: Folder
rdfs:comment:
  A folder/directory. Examples of folders include folders on a filesystem and message folders in a mailbox.


rdfs:label: Filesystem
rdfs:comment:
  A filesystem. Examples of filesystems include hard disk partitions, removable media, but also images thereof stored in files.


rdfs:label: SoftwareService
rdfs:comment:
  A service published by a piece of software, either by an operating system or an application. Examples of such services may include calendar, addresbook and mailbox managed by a PIM application. This category is introduced to distinguish between data available directly from the applications (Via some Interprocess Communication Mechanisms) and data available from files on a disk. In either case both DataObjects would receive a similar interpretation (e.g. a Mailbox) and wouldn't differ on the content level.


rdfs:label: SoftwareItem
rdfs:comment:
  A DataObject representing a piece of software. Examples of interpretations of a SoftwareItem include an Application and an OperatingSystem.


rdfs:label: Presentation
rdfs:comment:
  A Presentation made by some presentation software (Corel Presentations, OpenOffice Impress, MS Powerpoint etc.)


rdfs:label: RemoteDataObject
rdfs:comment:
  A file data object stored at a remote location. Don't confuse this class with a RemotePortAddress. This one applies to a particular resource, RemotePortAddress applies to an address, that can have various interpretations.


rdfs:label: PaginatedTextDocument
rdfs:comment:
  A file containing a text document, that is unambiguously divided into pages. Examples might include PDF, DOC, PS', DVI etc.


rdfs:label: Spreadsheet
rdfs:comment:
  A spreadsheet, created by a spreadsheet application. Examples might include Gnumeric, OpenOffice Calc or MS Excel.


rdfs:label: EmbeddedFileDataObject
rdfs: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.


rdfs:label: Attachment
rdfs:comment:
  A file attached to another data object. Many data formats allow for attachments: emails, vcards, ical events, id3 and exif...


rdfs:label: MediaStream
rdfs:comment:
  A stream of multimedia content, usually contained within a media container such as a movie (containing both audio and video) or a DVD (possibly containing many streams of audio and video). Most common interpretations for such a DataObject include Audio and Video.


rdfs:label: Bookmark Folder
rdfs:comment:
  A folder with bookmarks of a webbrowser. Use nfo:containsBookmark to relate Bookmarks. Folders can contain subfolders, use containsBookmarkFolder to relate them.


rdfs:label: FilesystemImage
rdfs:comment:
  An image of a filesystem. Instances of this class may include CD images, DVD images or hard disk partition images created by various pieces of software (e.g. Norton Ghost)


rdfs:label: Bookmark
rdfs: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.


rdfs:label: DeletedResource
rdfs: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.


rdfs:label: Website
rdfs:comment:
  A website, usually a container for remote resources, that may be interpreted as HTMLDocuments, images or other types of content.


rdfs:label: count
rdfs:comment:
  A common superproperty for all properties signifying the amount of atomic media data units. Examples of subproperties may include sampleCount and frameCount.


rdfs:label: channels
rdfs:comment:
  Number of channels. This property is to be used directly if no detailed information is necessary. Otherwise use more detailed subproperties.


rdfs:label: Heading
rdfs:comment:
  Specifies the direction of travelling while capturing image/video. The range of values from 0.00 to 359.99 (where 0 is due North, 90 is East, 180 South and 270 is West)


rdfs:label: Tilt
rdfs:comment:
  Vertical inclination of the camera while capturing the image, in angles starting on 0 as horizontal, positive numbers pointing up, negative angles pointing down


rdfs:label: fileSize
rdfs:comment:
  The size of the file in bytes. For compressed files it means the size of the packed file, not of the contents. For folders it means the aggregated size of all contained files and folders


rdfs:label: programmingLanguage
rdfs:comment:
  Indicates the name of the programming language this source code file is written in. Examples might include 'C', 'C++', 'Java' etc


rdfs:label: permissions
rdfs:comment:
  A string containing the permissions of a file. A feature common in many UNIX-like operating systems.


rdfs:label: hashAlgorithm
rdfs:comment:
  Name of the algorithm used to compute the hash value. Examples might include CRC32, MD5, SHA, TTH etc.


rdfs:label: bitDepth
rdfs: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


rdfs:label: averageBitrate
rdfs:comment:
  The average overall bitrate of a media container. (i.e. the size of the piece of media in bits, divided by it's duration expressed in seconds).


rdfs:label: Media list entry
rdfs:comment:
  A certain item belongs to a media list. This can reflect that a song is in a playlist, an image or video in an Album


rdfs:label: last played position
rdfs:comment:
  Position in the media (in seconds) where the play was paused. Positive number, being 0 the beginning of the media.


rdfs:label: Time offset within media container (seconds)
rdfs:comment:
  Specifies the start offset of this resource within a larger file, such as a single song within a recording of a radio broadcast or a CD rip.


rdfs:label: Region of interest X
rdfs:comment:
  Coordinate X where the region starts. It is normalized (values between 0 and 1) to the width of the picture. Starting in the upper left corner.


rdfs:label: Region of interest Y
rdfs:comment:
  Coordinate y where the region starts. It is normalized (values between 0 and 1) to the height of the picture. Starting in the upper left corner.


rdfs:label: Region of interest type
rdfs:comment:
  Content in the area. There is a predefined set of contents in the spec: http://www.metadataworkinggroup.org


rdfs:label: Region of interest refers to
rdfs:comment:
  Link to an item that is represented in the region. The 'type' of the region can give a clue of what exact content is linked in this property


rdfs:label: Music CD identifier
rdfs:comment:
  Music CD identifier to for databases like FreeDB.org. This frame is intended for music that comes from a CD, so that the CD can be identified in databases such as the CDDB. The frame consists of a binary dump of the Table Of Contents, TOC, from the CD, which is a header of 4 bytes and then 8 bytes/track on the CD plus 8 bytes for the 'lead out' making a maximum of 804 bytes. The offset to the beginning of every track on the CD should be described with a four bytes absolute CD-frame address per track, and not with absolute time.


rdfs:label: Radio station
rdfs:comment:
  The Radio station in user terms: BBC3, Radio5, YLEX, ... It is linked with 1 or more carriers (different FM frenquencies, online sources in different qualities, etc.). Some RDS information is represented with nie properties, nie:identifier for PI, nie:title for PS


rdfs:label: PTY
rdfs:comment:
  PTY Code (content description) as integer. RDS specs define the translations into human readable descriptions for various languages


rdfs:label: Encoding of the radio
rdfs:comment:
  Encoding of the radio. It is a property of the streaming, that it is known before hand, so the applications can choose the encoding they understand.


rdfs:label: Alternative media
rdfs:comment:
  Link between to different version of the same media. This is used for instances in uPnp where the server can provide the same video in different resolutions and codecs


rdfs:label: Feed entry
rdfs:comment:
  Represents feed entry. May have enclosures attached and certain settings that allow deviation from feed channel's setup


rdfs:label: Resource settings
rdfs:comment:
  Represents settings applied to a feed channel or a feed entry. How often it is updated, through which connection type it is delivered, when data expires and so on


rdfs:label: Default in group
rdfs:comment:
  Different enclosures can represent the same resource in different formats/resolutions. This representations are grouped using the nie:identifier property and this property identify the default between them.


rdfs:label: Expiry Interval
rdfs:comment:
  Expiry interval for feed channel, it tells time that a message in a channel can live. Interpreted as minutes


rdfs:label: Is removable
rdfs:comment:
  Flag to indicate if this instance is removable. This restriction is not enforced by tracker; it is API responsability to honor the value


rdfs:label: Radius
rdfs:comment:
  Radius from the center to define an area. Some applications can use it in 2D sense, making then a circle instead of a sphere


rdfs:label: nil
rdfs:comment:
  The empty list, with no items in it. If the rest of a list is nil then the list has no more items in it.


