Resource Property Vocabulary 1.0 (ATR)

Approved Technical Report 2013-12-17

This version: http://openurc.org/TR/res-prop-vocab1.0-20131217/
Latest version: http://openurc.org/TR/res-prop-vocab1.0/
Previous draft version: http://openurc.org/TR/res-prop-vocab1.0-20131203/ (changes marked)
Latest approved version: (none)
Editor: Gottfried Zimmermann, Parikshit Thakur
List of current openURC Technical Reports: http://openurc.org/TR/
Copyright 2013, openURC Alliance

Abstract

This document specifies a core set of generic and resource type-specific properties that are recommended to be used in the URC ecosystem. This applies to resources that are stored on the resource server, as well as for others like devices in the network.

This specification is directed in particular to resource authors (for describing their resources upon uploading to a resource server) and developers of UCHs and UCH components such as UIPMs, TDMs and TAs (for querying matching resources from a resource server).

Status of this Document

This is an Approved Technical Report, provided to the public by the openURC Alliance. It was developed by the Technical Committee, in compliance with the TC procedures.

This document has been reviewed by the openURC Alliance members and by the public, and is endorsed by the openURC Board of Directors as an Approved Technical Report. It is a stable document and may be used as reference material or cited from other documents.

Comments on this document can be sent to the public comments list res-prop-vocab-comments@openurc.org. The archives for the comments list are publicly available. Comments received on this document cannot result in changes to this version (except for editorial fixes), but may be addressed in future versions of this document. The Technical Committee does not plan to make formal responses to comments.


Table of Contents:


1. Introduction

This document specifies a core set of generic and resource type-specific properties that are recommended to be used in the URC ecosystem. This applies to resources that are stored on the resource server, as well as for others like devices in the network. This specification is directed in particular to resource authors (for describing their resources upon upload to a resource server) and developers of UCHs and UCH components such as UIPMs, TDMs and TAs (for querying matching resources from a resource server).

Other (non-core) property names may be used to describe resources, as long as the property names do not conflict with the core set defined in this document. In order to avoid potential conflicts with future versions of core properties and with other non-core properties, the use of author-owned URIs as namespaces for non-core property names is strongly recommended.

Resources are stored on the resource server with their metadata. Metadata is expressed as a set of resource properties attached to a resource. A resource property name is a string representing an (absolute) URI (not a URI reference which may be relative) [RFC 3986], being a concatenation of a namespace identifier and a property name. Often, the property name is represented as fragment component of the URI, but that is not required.

Matching of property names shall be case-insensitive. The value of a property shall be a string. Note that specific encoding rules may apply when coding a property name (and value) in a given context (for example as URI component, or inside XML content).

One property may occur multiple times for a resource, but with different values, thus expressing that each value applies to the resource (AND operation).

A property may have one or multiple descriptors, allowing for variations of the property value along the descriptors' value spaces (e.g. language codes). The purpose of a descriptor is to find the most relevant property value among alternatives. A descriptor name shall be a string (e.g. "lang" for language), and its value a string (e.g. "en" for the English language code). Since descriptors are specific to properties, this specification defines descriptors in the context of the properties that they apply to.

A human understandable description should be available for each property name at its URI which should be resolvable. A good practice is to describe a set of properties (called "vocabulary") in an RDF schema file, with a property's URI consisting of the location of the RDF schema file and the property name as fragment identifier (e.g. "http://openurc.org/ns/res#forTargetInstance" is described in the RDF schema file at http://openurc.org/ns/res).

2. Generic Properties

The following properties describe resources of all types, where applicable.

Property Name Description Values Usage
http://openurc.org/ns/res#name Globally unique identifier (URI) of a resource. Note that multiple versions of one resource may exist (see http://purl.org/dc/terms/modified below).

Note: Arguably, the property http://www.w3.org/1999/02/22-rdf-syntax-ns#about (attribute 'rdf:about') [ISO/IEC 24752-5] could be used as property name for a globally unique identifier. However, there is a slight difference between the meaning of http://www.w3.org/1999/02/22-rdf-syntax-ns#about and http://openurc.org/ns/res#name in that http://www.w3.org/1999/02/22-rdf-syntax-ns#about assigns a resource to a structured set of property-value pairs (called "description") rather than specifying the name of the resource itself.

URI [RFC 3986], not necessarily resolvable required for resources that are stored on a resource server
http://purl.org/dc/terms/modified [DCMI Terms]

Date on which the resource was changed most recently. Used to identify the version of a resource.

xsd:dateTime [XSD Datatypes] in any of the following formats:
  • 2013-10-30Thh:mm:ssZ
  • 2013-10-30Thh:mm:ss+zz:zz
  • 2013-10-30Thh:mm:ss-zz:zz

Example: "2008-08-14T15:40:02+02:00"

required for resources that are stored on a resource server
http://openurc.org/ns/res#type Type of resource with regard to the URC ecosystem.

For packaged resources (e.g. provided as a zip file), the http://openurc.org/ns/res#type property reflects the resource type of the index file. See property http://openurc.org/ns/res#indexFile below.

URI [RFC 3986], recommended to be resolvable. See sections below for type-specific values. required
http://openurc.org/ns/res#subtype Subtype of resource regard to the URC ecosystem. URI [RFC 3986], recommended to be resolvable. See sections below for type-specific values. optional
http://openurc.org/ns/res#mimeType MIME type [RFC 2046] of the resource. This property is used by the resource server to determine the MIME type for a resource served to a client upon resource retrieval [RES-SERV-HTTP]. MIME type [RFC 2046], from any of the following trees [RFC 4288]: recommended for resources that are stored on a resource server
http://openurc.org/ns/res#filename File name of the uploaded resource.

This helps in recognizing the resource file when downloaded from the resource server.

In the Windows API (with some exceptions), the maximum length for a path is MAX_PATH, which is defined as 260 characters.

Use any character in the current code page for a name, including Unicode characters and characters in the extended character set (128–255), except for the following reserved characters:

  1. < (less than)
  2. > (greater than)
  3. : (colon)
  4. " (double quote)
  5. / (forward slash)
  6. \ (backslash)
  7. | (vertical bar or pipe)
  8. ? (question mark)
  9. * (asterisk)
  10. Integer value zero, sometimes referred to as the ASCII NUL character.
  11. Characters whose integer representations are in the range from 1 through 31, except for alternate data streams where these characters are allowed. For more information about file streams, see File Streams.
  12. Any other character that the target file system does not allow.
required for resources that are stored on a resource server
http://purl.org/dc/terms/conformsTo Conformance to a standard [DCMI Terms]. URI [RFC 3986], not necessarily resolvable. See sections below for type-specific values. recommended for resources that comply to a standard
http://openurc.org/ns/res#instanceId Instance identifier for the resource. Applicable to devices in a network, in particular. xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#dynamicLibClass Name of the main class of a resource that is a dynamic library file. Applies only to certain types of dynamic libraries (e.g. JAR files). xsd:string [XSD Datatypes] optional
http://purl.org/dc/elements/1.1/title A name given to the resource [DCMI Terms].

A language tag may be specified as the value of the descriptor "lang" [RFC 4646] [IANA Language Tags].

The title can be used as a human-readable label for the resource (class).

xsd:string [XSD Datatypes], recommended to be short (not exceeding 5 words). recommended
http://purl.org/dc/elements/1.1/description Human readable description of the resource [DCMI Terms].

A language tag should be specified as the value of the descriptor "lang" [RFC 4646] [IANA Language Tags].

xsd:string [XSD Datatypes], may be long. optional
http://purl.org/dc/elements/1.1/language A language of the resource, if applicable [DCMI Terms]. Language tag [RFC 4646], as registered in [IANA Language Tags] optional
http://purl.org/dc/elements/1.1/creator An entity primarily responsible for making the resource [DCMI Terms]. xsd:string [XSD Datatypes] optional
URI of creator. URI [RFC 3986] - should be resolvable. recommended
http://purl.org/dc/elements/1.1/publisher An entity responsible for making the resource available [DCMI Terms] xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#publisherUri URI of publisher. URI [RFC 3986] - should be resolvable. recommended
http://purl.org/dc/elements/1.1/contributor An entity responsible for making contributions to the resource (other than the creator) [DCMI Terms]. xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#contributorUri URI of contributor. URI [RFC 3986] - should be resolvable. optional
http://openurc.org/ns/res#serialNumber Serial number of a resource instance. xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#upc Universal Product Code (UPC) of a resource. xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#indexFile Path and name of index/main file of the resource (applicable if resource is provided as file package, e.g. zip file). The index file is the entry point for accessing the aggregated resource.

If property http://openurc.org/ns/res#indexFile is used, property http://openurc.org/ns/res#indexFileMimeType (see below) is required.

Path and file name for the index file as part of the resource package.

Examples: "/index.html", "/main/start.php"

recommended if resource is provided as package (e.g. zip file) with a dedicated index file
http://openurc.org/ns/res#indexFileMimeType Specifies the MIME type of the index file of the resource. MIME type [RFC 2046]. required if http://openurc.org/ns/res#indexFile is specified
http://openurc.org/ns/res#iconResource Specifies the retrieval URI of an existing icon resource type (http://openurc.org/restypes#icon).

An icon of size 50x50 pixels is recommended

Resource retrieval URI optional
http://openurc.org/ns/res#subscriptionPackage

Specifies a class of products by a publisher that a user can subscribe to as a package.

xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#operatingSystem Specifies the operating system applicable to the resource. xsd:string [XSD Datatypes]

Examples: "ARM-Linux", "Win32", "Win64"

optional

2.1. Generic Properties for URC Resources

The following properties apply to traditional URC resources, as based on [ISO/IEC 24752], [UCH] and [URC-HTTP].

http://openurc.org/ns/res#forTargetName Specifies the target (class) name for which the resource can be applied. URI [RFC 3986], not necessarily resolvable. optional
http://openurc.org/ns/res#forTargetInstance Specifies the target instance for which the resource can be applied [ISO/IEC 24752-5]. If not specified, the resource can be applied to all target instances. xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#forSocketName Specifies the socket name for which the resource can be applied. URI [RFC 3986], not necessarily resolvable optional

2.2. Generic Properties for URC Light Resources

The following properties apply to URC Light resources, for the purpose of extending or replacing elements in Web pages.

http://openurc.org/ns/res#urclEltRef Element reference, consisting of URI for the Website, and the id of the element to be replaced by the resource URI of the form websiteUrl#id required if resource applicable for URC Light
http://openurc.org/ns/res#urclClass Item class of the resource for use in the URC Light framework. URC Light class name (xsd:string) required if resource applicable for URC Light
http://openurc.org/ns/res#urclMode Mode of application for the resource in the URC Light framework. replace = replace the original element

extend = extend the original element

required if resource application for URC Light

3. Properties from External Vocabularies

Other property names from metadata vocabularies, in particular from those listed in this section, may be used as generic resource properties, if applicable. However, these are not considered to be "core properties" in the URC ecosystem, as are the other properties listed in this document.

3.1. Properties from Dublin Core Metadata Initiative

Property names may be the full URLs taken from [DCMI Terms].

Example: Property name "http://purl.org/dc/elements/1.1/subject"

4. Resource Type Specific Properties

This section defines resource type specific core properties for resources. The type of a resource is determined by the property http://openurc.org/ns/res#type.

In this section, whenever a generic property (see section Generic Properties) is reiterated for a specific resource type, the type-specific definition overwrites the generic one (but only if not otherwise noted).

4.1. Target Description Properties

Target descriptions are defined in [ISO/IEC 24752-4].

Target descriptions are described by generic resource properties (see section Generic Properties), and any of the following properties:

Property Name Description Values Usage
http://openurc.org/ns/res#name Globally unique identifier (URI) of the target (the value of the 'about' attribute on the <target> element of the target description).

Note: There is just one name for both, the target (class) and its description.

URI [RFC 3986], not necessarily resolvable required
http://openurc.org/ns/res#type URC-specific type of resource. "http://openurc.org/restypes#targetdesc" required
http://openurc.org/ns/res#subtype Subtype of resource regard to the URC ecosystem. "http://openurc.org/restypes#targetdesc-template" for target description templates. optional
http://openurc.org/ns/res#deviceType Device class. Each device class corresponds to one "template" socket. URI [RFC 3986], not necessarily resolvable.

The following device type URIs are pre-defined:

  • http://openurc.org/devicetypes#tv
  • http://openurc.org/devicetypes#airConditioner
  • http://openurc.org/devicetypes#microwave
  • http://openurc.org/devicetypes#mp3Player
  • http://openurc.org/devicetypes#audioSystem
  • http://openurc.org/devicetypes#audioVideoPlayer
  • http://openurc.org/devicetypes#cassettePlayer
  • http://openurc.org/devicetypes#cdPlayer
  • http://openurc.org/devicetypes#vcr
  • http://openurc.org/devicetypes#dvcPlayer
  • http://openurc.org/devicetypes#videoPlayerRecorder
  • http://openurc.org/devicetypes#videoProjector
  • http://openurc.org/devicetypes#vs
  • http://openurc.org/devicetypes#digitalSatelliteBox
  • http://openurc.org/devicetypes#eib
  • http://openurc.org/devicetypes#wil
  • http://openurc.org/devicetypes#ssd
  • http://openurc.org/devicetypes#surroundSoundProcessor
  • http://openurc.org/devicetypes#videoConferenceDevice
  • http://openurc.org/devicetypes#tuner
  • http://openurc.org/devicetypes#projector
  • http://openurc.org/devicetypes#amplifier
  • http://openurc.org/devicetypes#homeTheater
  • http://openurc.org/devicetypes#preampTuner
  • http://openurc.org/devicetypes#digitalCamera
  • http://openurc.org/devicetypes#audioSwitcher
  • http://openurc.org/devicetypes#antennaRotator
  • http://openurc.org/devicetypes#lineDoublerAndAvController
  • http://openurc.org/devicetypes#dimmer
  • http://openurc.org/devicetypes#temperaturSensor
  • http://openurc.org/devicetypes#radiatorThermostat
  • http://openurc.org/devicetypes#motionSensor
  • http://openurc.org/devicetypes#powerSwitch
recommended
http://purl.org/dc/terms/conformsTo Conformance to a standard [DCMI Terms]. "http://openurc.org/ns/targetdesc-2/isoiec24752-4-2013" required
http://openurc.org/ns/res#mimeType MIME type for target description. "application/urc-targetdesc+xml" [ISO/IEC 24752-4] required

4.2. Socket Description Properties

Socket descriptions are defined in [ISO/IEC 24752-2].

Socket descriptions are described by generic resource properties (see section Generic Properties), and any of the following properties:

Property Name Description Values Usage
http://openurc.org/ns/res#name Globally unique identifier (URI) of the socket (the value of the 'about' attribute on the <uiSocket> element in the socket description).

Note: There is just one name for both, the socket and its description.

URI [RFC 3986], not necessarily resolvable required
http://openurc.org/ns/res#type URC-specific type of resource. "http://openurc.org/restypes#uisocketdesc" required
http://purl.org/dc/terms/conformsTo Conformance to a standard [DCMI Terms]. "http://openurc.org/ns/uisocketdesc-2/isoiec24752-2-2013" required
http://openurc.org/ns/res#mimeType MIME type for target description. "application/urc-uisocketdesc+xml" [ISO/IEC 24752-2] required
http://openurc.org/ns/res#forTargetName Target name(s) that the socket belongs to (as specified by the 'http://openurc.org/res#name' property of a URC-compatible target). May occur multiple times if a socket (description) belongs to multiple targets. URI [RFC 3986], not necessarily resolvable recommended

4.3. Resource Sheet Properties

Resource Sheets are defined in [ISO/IEC 24752-5].

Resource sheets are described by generic resource properties (see section Generic Properties), and any of the following properties:

Property Name Description Values Usage
http://openurc.org/ns/res#name Globally unique identifier (URI) for the resource sheet. This is the value of the 'rdf:about' attribute on the <ResSheet> element in the resource sheet. URI [RFC 3986], not necessarily resolvable required
http://openurc.org/ns/res#type URC-specific type of resource. "http://openurc.org/restypes#ressheet" required
http://purl.org/dc/terms/conformsTo Conformance to a standard [DCMI Terms]. "http://openurc.org/ns/res/isoiec24752-5-2013" required
http://openurc.org/ns/res#mimeType Specifies the MIME type of the resource sheet. "application/urc-ressheet+xml" [ISO/IEC 24752-5] recommended
http://purl.org/dc/elements/1.1/format Specifies an atomic resource format that applies to at least one atomic resource in the described resource sheet [ISO/IEC 24752-5].

NOTE: This property is different from http://openurc.org/ns/res#mimeType in that it specifies the MIME type of the resource's components rather than the resource's MIME type.

MIME type [RFC 2046], from any of the following trees [RFC 4288]: recommended if resource sheet contains atomic resources with a single MIME type (e.g. "image/jpeg").
http://purl.org/dc/elements/1.1/type Specifies an atomic resource type that applies to at least one atomic resource in the described resource sheet [ISO/IEC 24752-5]. One of the following: Collection, Dataset, Event, Image, InteractiveResource, MovingImage, PhysicalObject, Service, Software, Sound, StillImage, Text [DCMI Terms]. recommended if resource sheet contains atomic resources for a single type (e.g. "Text").
http://openurc.org/ns/res#forLang Specifies a language that is used in a use context of at least one Atomic Resource Description in the Resource Sheet described [ISO/IEC 24752-5]. Language tag [RFC 4646], as registered in [IANA Language Tags] recommended if resource sheet contains atomic resources for a single language.
http://openurc.org/ns/res#forDomain Specifies a domain (given as URI) that is used in a use context for at least one Atomic Resource in the described Resource Sheet [ISO/IEC 24752-5]. URI [RFC 3986] for a target name, socket name or UIID name, not necessarily resolvable recommended if resource sheet contains atomic resources
http://openurc.org/ns/res#role

Specifies a role URI that is used in a use context of at least one Atomic Resource in the described Resource Sheet [ISO/IEC 24752-5].

URI [RFC 3986], not necessarily resolvable.

[ISO/IEC 24752-5] defines the following set of pre-defined roles. Other roles may be used.

  • http://openurc.org/ns/res#label
  • http://openurc.org/ns/res#help, http://openurc.org/ns/res#help-purpose, or http://openurc.org/ns/res#help-effect
  • http://openurc.org/ns/res#accesskey
  • http://openurc.org/ns/res#keyword
  • http://openurc.org/ns/res#location
recommended if resource sheet contains atomic resources with a single role

4.3.1. Resource Sheet Package Properties

If a resource sheet refers to externally stored resources, it may be provided as a package together with the external resources, e.g. as zip file. In this case, resource sheet packages are described by resource sheet properties (see section Resource Sheet Properties), and any of the following properties:

Property Name Description Values Usage
http://openurc.org/ns/res#type URC-specific type of resource. "http://openurc.org/restypes#ressheet" required
http://openurc.org/ns/res#mimeType MIME type for resource sheet package. MIME type [RFC 2046] of the package file.

Example: "application/zip"

required
http://openurc.org/ns/res#indexFile Path and name of the contained resource sheet (applicable if resource sheet is provided as part of a file package, e.g. zip file).

If property http://openurc.org/ns/res#indexFile is used, property http://openurc.org/ns/res#indexFileMimeType (see below) is required.

Path and file name for the resource sheet file as part of the resource package.

Examples: "/English.rsheet", "/main/Main.rsheet"

recommended if resource is provided as package (e.g. zip file) with a dedicated index file
http://openurc.org/ns/res#indexFileMimeType Specifies the MIME type of the resource sheet file of the package. "application/urc-ressheet+xml" [ISO/IEC 24752-5] required if resource sheet is provided as part of a package

4.4. Grouping Sheet Properties

Grouping sheets are described by generic resource properties (see section Generic Properties), and any of the following properties:

Property Name Description Values Usage
http://openurc.org/ns/res#name Globally unique identifier (URI) for the grouping sheet. This is the value of the 'rdf:about' attribute on the <GrpSheet> element in the grouping sheet. URI [RFC 3986], not necessarily resolvable required
http://openurc.org/ns/res#type URC-specific type of resource. "http://openurc.org/restypes#grpsheet" required
http://purl.org/dc/terms/conformsTo Conformance to a standard [DCMI Terms]. required
http://openurc.org/ns/res#forLang It specifies a language context that applies to one or more groupings in the grouping sheet. Language tag [RFC 4646], as registered in [IANA Language Tags] recommended if a grouping intended to be used for a specific languate.
http://openurc.org/ns/res#forDomain Specifies a domain that is used in at least one Grouping Resource in the grouping sheet. URI [RFC 3986] for a socket name, not necessarily resolvable required
http://openurc.org/ns/res#mimeType MIME type for grouping sheet “application/urc-grpsheet+xml” required

4.5. TDM Properties

Target Discovery Modules (TDMs) are specified in [UCH].

TDMs are described by generic resource properties (see section Generic Properties), and any of the following properties:

Property Name Description Values Usage
http://openurc.org/ns/res#type Type of resource with regard to the URC ecosystem. "http://openurc.org/restypes#tdm" [UCH] required
http://purl.org/dc/terms/conformsTo Specifies the version-specific URL of the UCH specification that the TDM conforms to [UCH]. Version URL of a UCH spec version, e.g. "http://openurc.org/TR/uch1.0/". required
http://openurc.org/ns/res#runtimePlatform Specifies the runtime environment Platform-specific identifier, case-insensitive.

Examples: "java", "gnu-c", "gnu-cpp", ".net"

Note: A version number is recommended. See #runtimePlatformVersion below.

required
http://openurc.org/ns/res#runtimePlatformVersion Specifies the runtime environment's version Version number of the runtime platform, e.g. "1.6".

Note: Typically the resource will also run on more recent versions.

recommended
http://openurc.org/ns/res#mimeType MIME type [RFC 2046] of the TDM. Any registered [IANA MIME Types] or unregistered MIME type. recommended
http://openurc.org/ns/res#devicePlatform Identifier for the device platform of the TDM. Platform-specific identifier.

Pre-defined values are:

  • UPnP
  • Z-Wave
recommended

4.6. TA Properties

Target Adapters (TAs) are specified in [UCH].

TAs are described by generic resource properties (see section Generic Properties), and the following properties:

Property Name Description Values Usage
http://openurc.org/ns/res#type Type of resource with regard to the URC ecosystem. "http://openurc.org/restypes#ta" [UCH] required
http://openurc.org/ns/res#runtimePlatform Specifies the runtime environment Platform-specific identifier, e.g. "java", "cpp", ".net" required
http://openurc.org/ns/res#runtimePlatformVersion Specifies the runtime environment's version Version number of the runtime platform, e.g. "1.6". Note: Typically the resource will also run on more recent versions. recommended
http://purl.org/dc/terms/conformsTo Specifies the version-specific URL of the UCH specification that the TA conforms to [UCH]. Version URL of a UCH spec, e.g. "http://openurc.org/TR/uch1.0/". required
http://openurc.org/ns/res#mimeType MIME type [RFC 2046] of the TA. Any registered [IANA MIME Types] or unregistered MIME type. recommended
http://openurc.org/ns/res#devicePlatform Identifier for the device platform of the TA. Platform-specific identifier, e.g. "UPnP". recommended
http://openurc.org/ns/res#forTargetName Specifies the target (class) name for which the TA works with. The value "*" specifies that the TA works with all target classes. URI [RFC 3986], not necessarily resolvable. recommended
http://openurc.org/ns/res#forTargetInstance Specifies the target instance for which the TA can be applied [ISO/IEC 24752-5]. If not specified, the TA can be applied to all target instances. xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#deviceUpc Universal Product Code (UPC) of the target device that the TA applies to. xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#deviceSerialNumber Serial number of the target device that the TA applies to.

Note: This property restricts the use of the TA to single instances of targets. Cf. http://openurc.org/ns/res#forTargetInstance.

xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#tdUri URI of the target description pertaining to the TA. If relative, it is based on the location of the TA (or where it was retrieved from). URI [RFC 3986], absolute or relative, must be resolvable. optional

4.6.1. TA Properties for UPnP Platform

TAs for the UPnP platform are described by TA's generic resource properties (see section Generic Properties), TA properties (see section TA Properties), and the following properties:

Property Name Description Values Usage
http://openurc.org/ns/res#devicePlatform Identifier for the device platform of the TA. "UPnP" required
http://openurc.org/ns/res#deviceType UPnP device type, as given in the UPnP XML Device Description, as content of <deviceType>. URN [UPNP ARCHITECTURE] recommended
http://openurc.org/ns/res#deviceCreator Device manufacturer name, as given in the UPnP XML Device Description, as content of <manufacturer>. xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#deviceCreatorUrl Device manufacturer URL, as given in the UPnP XML Device Description, as content of <manufacturerURL>. URI [RFC 3986] - should be resolvable optional
http://openurc.org/ns/res#deviceModelName Device model name, as given in the UPnP XML Device Description, as content of <modelName>. xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#deviceModelNumber Device model number, as given in the UPnP XML Device Description, as content of <modelNumber>. xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#deviceModelUrl Device model URL, as given in the UPnP XML Device Description, as content of <modelURL>. URI [RFC 3986] - should be resolvable optional
http://openurc.org/ns/res#deviceUpc Universal Product Code (UPC) of the device, as given in the UPnP XML Device Description, as content of <UPC>. xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#deviceSerialNumber Device serial number, as given in the UPnP XML Device Description, as content of <serialNumber>.

Note: Should only be used if the TA is specific to a particular target instance.

xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#deviceUdn Unique Device Name (UDN), as given in the UPnP XML Device Description, as content of <UDN>.

Note: Should only be used if the TA is specific to a particular target instance.

xsd:string [XSD Datatypes] optional

4.7. UIPM Properties

User Interface Protocol Modules (UIPMs) are specified in [UCH].

UIPMs are described by generic resource properties (see section Generic Properties), and any of the following properties:

Property Name Description Values Usage
http://openurc.org/ns/res#type Type of resource with regard to the URC ecosystem. "http://openurc.org/restypes#uipm" [UCH] required
http://purl.org/dc/terms/conformsTo Specifies the version-specific URL of the UCH specification that the UIPM conforms to [UCH]. Version URL of a UCH spec, e.g. "http://openurc.org/TR/uch1.0/". required
http://openurc.org/ns/res#runtimePlatform Specifies the runtime environment Platform-specific identifier, e.g. "java", "cpp", ".net" required
http://openurc.org/ns/res#runtimePlatformVersion Specifies the runtime environment's version Version number of the runtime platform, e.g. "1.6". Note: Typically the resource will also run on more recent versions. recommended
http://openurc.org/ns/res#mimeType MIME type [RFC 2046] of the UIPM. Any registered [IANA MIME Types] or unregistered MIME type. recommended
http://openurc.org/ns/res#forTargetName Specifies the target (class) name for which the UIPM can be applied.

Note that, if multiple URI entries exist for this property, the UIPM is applicable to any one of a set of (alternate) targets.

URI [RFC 3986], not necessarily resolvable.

"*": target-generic UIPM - applies to any target class (but only one at a time).

"all": UIPM applies to the complete set of all targets.

required
http://openurc.org/ns/res#forTargetInstance Specifies the target instance for which the UIPM can be applied [ISO/IEC 24752-5]. If not specified, the resource can be applied to all target instances.

Note: Use only if the UIPM is specific to a particular target instance.

xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#forSocketName Specifies the name (URI) of a socket that the UIPM maps to.

Note that, if there are multiple URI entries of this property, the UIPM maps to the set of specified sockets (at the same time).

URI [RFC 3986], not necessarily resolvable.

"*": socket-generic UIPM - applies to any socket (but only one at a time).

"all": UIPM applies to the set of all sockets of the target.

optional
http://openurc.org/ns/res#urlScheme Specifies a scheme for controllers to connect to the UIPM via a URL.

Can be used by the UIPM as 'scheme' parameter in function IUIPMListener.startUriService() [UCH], if UIPM communicates with controllers via URLs.

Scheme component of URI [RFC 3986].

Examples: "http", "ftp", "urn", "vnc".

optional
http://openurc.org/ns/res#urlPortNo Specifies a port number for controllers to connect to the UIPM via a URL.

Can be used by the UIPM as 'port' parameter in function IUIPMListener.startUriService() [UCH], if UIPM communicates with controllers via URLs.

Port number.

For example, "80" is the default port number for HTTP.

optional
http://openurc.org/ns/res#urlBasePath Specifies a base path for controllers to connect to the UIPM via a URL.

Can be used by the UIPM as 'basePath' parameter in function IUIPMListener.startUriService() [UCH], if UIPM communicates with controllers via URLs.

Some first part of path component of a URI [RFC 3986], starting with a slash ("/").

For example, the base path "/UCH/URC-HTTP" with HTTP means that all HTTP requests to the UCH that begin with "http://ip-address/UCH/URC-HTTP" should be serviced (dispatched) to the UIPM.

optional
http://openurc.org/ns/res#protocolShortName Specifies a short name for the user interface protocol that the UIPM offers to controllers.

Can be used by the UIPM as 'protocolShortName' parameter in function IUIPMListener.addCompatibleUI() [UCH], if UIPM communicates with controllers via URLs.

Any values allowed for the 'shortName' attribute of a <protocol> element in a UIList [UCH].

Examples: "HTTP/HTML", "RDP", "VNC", "CE-HTML-1.0", "URC-HTTP", "XRT".

optional
http://purl.org/dc/terms/conformsTo Specifies the version-specific URL of the URC-HTTP protocol specification that the UIPM conforms to [UCH] (only applicable to URC-HTTP UIPMs, ie. Version URL of a UCH spec version, e.g. "http://openurc.org/TR/uch1.0/". required

4.7.1. URC-HTTP UIPM Properties

A URC-HTTP UIPM is a UIPM that offers the URC-HTTP protocol as an interface to clients/controllers.

A URC-HTTP UIPM is described by generic resource properties (see section Generic Properties), and any of the following properties:

Property Name Description Values Usage
http://purl.org/dc/terms/conformsTo Specifies the version-specific URL of the URC-HTTP protocol specification that the UCH conforms to [URC-HTTP].

Note: This property is in addition to http://purl.org/dc/terms/conformsTo on UIPMs (see section UIPM Properties). For URC-HTTP UIPMs, http://purl.org/dc/terms/conformsTo shall thus occur twice (but with different values).

Version URL of a URC-HTTP spec, e.g. "http://openurc.org/TR/urc-http-protocol2.0/". required
http://openurc.org/ns/res#protocolShortName Specifies a short name for the user interface protocol that the UIPM offers to controllers/clients. "URC-HTTP" required

4.8. UIPM Client Properties

UIPM clients are applications and scripts that are interfacing with the UCH via some UIPM. Some UIPM clients may be simple web pages (typically HTML pages with embedded scripts or objects running on any web browser) that can be retrieved from the UCH's web server.

Property Name Description Values Usage
http://openurc.org/ns/res#type Type of resource with regard to the URC ecosystem. "http://openurc.org/restypes#uipm-client" [UCH] required
http://openurc.org/ns/res#wrapsProtocolShortName Specifies a short name for the user interface protocol that the UIPM client uses in interfacing with the UIPM. Any values allowed for the 'shortName' attribute of a <protocol> element in a UIList [UCH].

Examples: "HTTP/HTML", "RDP", "VNC", "CE-HTML-1.0", "URC-HTTP", "XRT".

required
http://openurc.org/ns/res#protocolShortName Specifies a short name for the user interface protocol that the UIPM client offers (as a wrapper to a protocol that the UIPM offers). Any values allowed for the 'shortName' attribute of a <protocol> element in a UIList [UCH].

Examples: "HTTP/HTML", "RDP", "VNC", "CE-HTML-1.0", "URC-HTTP", "XRT".

recommended
http://openurc.org/ns/res#mimeType MIME type [RFC 2046] of the resource. This property is used by the resource server to determine the MIME type for a resource served to a client upon resource retrieval [RES-SERV-HTTP]. MIME type [RFC 2046].

Some UIPM client resources may be provided as a file package (e.g. zip file), consisting of all files needed by the controller to run the UIPM client.

recommended
http://openurc.org/ns/res#indexFile Path and name of index file of the UIPM client (applicable if UIPM client is provided as file package). The index file is the entry point for controllers for using the UI protocol, as specified by the property http://openurc.org/ns/res#protocolShortName. Path and file name for the index file as part of the UIPM client package.

Examples: "/index.html", "/main/start.php"

required if UIPM client resource is provided as package with an index file
http://openurc.org/ns/res#indexFileMimeType Specifies the MIME type of the index file of the UIPM client resource. MIME type [RFC 2046].

Examples: "text/html", "application/xhtml+xml", "application/ce-html+xml", "application/x-ce-html+xml"

required if UIPM client resource is provided as package with an index file
http://openurc.org/ns/res#userAgentSubstring Specifies suitable Web client platforms for running the UIPM client, by giving a substring that must occur as part of the user agent string (in a case-insensitive string comparison). If the substring occurs, the UIPM client should be made available to the user, otherwise not. Any string that can occur as user agent string or substring thereof. Lower/upper case don't matter.

Examples: "iPhone", "iPad", "Android".

recommended
http://openurc.org/ns/res#forTargetName Specifies the target (class) name for which the UIPM client can be applied.

Note that, if multiple URI entries exist for this property, the UIPM client is applicable to any one of a set of (alternate) targets.

URI [RFC 3986], not necessarily resolvable.

"*": target-generic UIPM client - applies to any target class (but only one at a time).

"all": UIPM client applies to the complete set of all targets.

required
http://openurc.org/ns/res#forSocketName Specifies the name (URI) of a socket that the UIPM client maps to.

Note that, if there are multiple URI entries of this property, the UIPM client maps to the set of specified sockets (at the same time).

URI [RFC 3986], not necessarily resolvable.

"*": socket-generic UIPM client - applies to any socket (but only one at a time).

"all": UIPM client applies to the set of all sockets of the target.

optional
http://openurc.org/ns/res#iconResource Specifies the retrieval URI of an already existing icon resource type (http://openurc.org/restypes#icon).

For visual icons, at least one icon of size 50x50 pixels is recommended.

Note: There may be multiple icon resources specified for a resource (different sizes, visual/auditory/tactile icons, etc.). The caller can query the properties for each of them through the query interface.

Resource retrieval URI recommended

4.8.1. URC-HTTP Client Properties

A URC-HTTP client is a client of a URC-HTTP UIPM, i.e. an application or script that interfaces with the UCH via the URC-HTTP protocol [URC-HTTP] provided by the URC-HTTP UIPM.

A URC-HTTP Client is described by generic resource properties (see section Generic Properties), and any of the following properties:

Property Name Description Values Usage
http://purl.org/dc/terms/conformsTo Specifies the version-specific URL of the URC-HTTP protocol specification that the UCH conforms to [URC-HTTP]. Version URL of a URC-HTTP spec, e.g. "http://openurc.org/TR/urc-http-protocol2.0/". required
http://openurc.org/ns/res#wrapsProtocolShortName Specifies a short name for the user interface protocol that the UIPM client uses in interfacing with the UIPM. "URC-HTTP" required
http://openurc.org/ns/res#forSocketName Specifies the name (URI) of a socket that the UIPM client maps to.

Note that, if there are multiple URI entries of this property, the UIPM client maps to the set of specified sockets (at the same time).

URI [RFC 3986], not necessarily resolvable.

"*": socket-generic UIPM client - applies to any socket (but only one at a time).

"all": UIPM client applies to the set of all sockets of the target.

required

4.9. UCH Properties

A Universal Control Hub (UCH) is specified in [UCH].

A UCH is described by generic resource properties (see section Generic Properties), and any of the following properties:

Property Name Description Values Usage
http://openurc.org/ns/res#type Type of resource with regard to the URC ecosystem. "http://openurc.org/TR/uch/" [UCH] required
http://purl.org/dc/terms/conformsTo Specifies the version-specific URL of the UCH specification that the UCH conforms to [UCH]. Version URL of a UCH spec, e.g. "http://openurc.org/TR/uch1.0/". required
http://openurc.org/ns/res#baseUri Base URI for the location of the UCH. URI [RFC 3986] - should be resolvable optional
http://openurc.org/ns/res#uchInstanceId Globally unique Instance identifier for the UCH, using the MAC address of the UCH system. String in the format "UCH-macAddress", e.g. "UCH-00-1C-F0-D0-AC-00" required

4.10. Target Instance Properties

Note that this specification distinguishes between URC-compatible targets, as defined in [ISO/IEC 24752-1], and UCH-internal targets, as defined in [UCH] (which are not URC-compatible).

4.10.1. URC-Compatible Target Properties

This section applies to URC-compatible targets, as defined in [ISO/IEC 24752-1].

URC-compatible targets are described by generic resource properties (see section Generic Properties), if applicable, and any of the following properties:

Property Name Description Values Usage
http://openurc.org/ns/res#name Unique identifier for target class. This is the value of the ‘about’ attribute in the target description. URI [RFC 3986], not necessarily resolvable required
http://openurc.org/ns/res#type Type of resource with regard to the URC ecosystem. "http://openurc.org/restypes#target" required
http://openurc.org/ns/res#instanceId Instance identifier for the target. xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#friendlyName Friendly name for the device instance. xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#description Name of the target description (see section Target Description Properties, property 'http://openurc.org/ns/res#name') that describes the target. This is the same as the name of the target class (see section 4.1, property 'http://openurc.org/ns/res#name'). URI [RFC 3986], not necessarily resolvable optional
http://openurc.org/ns/res#descriptionAt Resolvable URI for a target description file. URI [RFC 3986], must be resolvable optional

4.10.2. UCH-Internal Target Properties

This section applies to targets that are connected to Target Adapters [UCH]. These targets are devices or services on the network that can be remotely controlled through a UCH, but are not URC compatible.

UCH-internal targets are described by generic resource properties (see section Generic Properties), if applicable, and any of the following properties:

Property Name Description Values Usage
http://openurc.org/ns/res#name Unique identifier for the class of the target. Maybe equal to modelUri (see below). URI [RFC 3986], not necessarily resolvable required
http://openurc.org/ns/res#type Type of resource with regard to the URC ecosystem. "http://openurc.org/TR/uch/#target" [UCH] required
http://openurc.org/ns/res#instanceId Instance identifier for the target. xsd:string [XSD Datatypes] required
http://openurc.org/ns/res#friendlyName Friendly name for the device instance. xsd:string [XSD Datatypes] required
http://openurc.org/ns/res#devicePlatform Identifier for the device platform of the target. Platform-specific identifier, e.g. "UPnP". recommended
http://openurc.org/ns/res#deviceType Type of the device. Platform-specific. optional
http://openurc.org/ns/res#modelName Device model name. Platform-specific. optional
http://openurc.org/ns/res#modelNumber Device model number. Platform-specific. optional
http://openurc.org/ns/res#modelUri URI identifying the device model. URI [RFC 3986], not necessarily resolvable optional

4.11. Client Instance Properties

Client instances are devices on the network that act as controllers to a UIPM [UCH].

NOTE: Client instances are actual devices, different from the UIPM Clients (software to be loaded on the client instances).

Clients (and their users) are described by generic resource properties (see section Generic Properties), if applicable, and any of the following properties:

Property Name Description Values Usage
http://openurc.org/ns/res#type Type of resource with regard to the URC ecosystem. "http://openurc.org/TR/uch/#client" [UCH] required
http://openurc.org/ns/res#instanceId Instance identifier for the client. This may be the IP address of the controller. xsd:string [XSD Datatypes] required
http://openurc.org/ns/res#authorizationCode An authorization code for opening a session. The authorization code may have been provided by the UCH. xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#friendlyName Friendly name for the client instance. xsd:string [XSD Datatypes] optional
http://openurc.org/ns/res#devicePlatform Identifier for the device platform of the client. Platform-specific identifier, e.g. "UPnP". optional
http://openurc.org/ns/res#deviceType Type of the client device. Platform-specific. optional
http://openurc.org/ns/res#modelName Device model name. Platform-specific. optional
http://openurc.org/ns/res#modelNumber Device model number. Platform-specific. optional
http://openurc.org/ns/res#modelUri URI identifying the device model. URI [RFC 3986], not necessarily resolvable optional

4.12. Configuration File Properties

Configuration files are used by URC ecosystem components that have some kind of generic behavior that can be configured for specific contexts. For example, a configuration file for a TA could specify IR codes for device-communication, as they map to the elements of the device's socket.

In general, configuration files should be described with the same set of properties as for the component they configure. For example, a TA configuration file would use the properties as specified in TA Properties.

There is one exception: A configuration file shall have a 'http://openurc.org/ns/res#type' property value that is distinct from that of the component it configures. It is recommended to use a 'http://openurc.org/ns/res#type' property value that is derived from (or extends) the 'http://openurc.org/ns/res#name' property value of the component. For example, if a TA's 'http://openurc.org/ns/res#name' property has value "http://example.com/ta/platform", all pertaining configuration files could have a 'http://openurc.org/ns/res#type' property with value "http://example.com/ta/platform/configfile".

4.12.1. Properties for IR/serial Code Files

IR or serial code files specify the IR/serial codes for legacy devices. For each socket element of a legacy device, an IR or serial code is defined.

TODO: Specify file format for IR/serial code file.

Property Name Description Values Usage
http://openurc.org/ns/res#type Type of resource with regard to the URC ecosystem. One of the following:
  • "http://openurc.org/TR/uch/#irconfig" (for IR configuration file)
  • "http://openurc.org/TR/uch/#serialconfig" (for serial configuration file)
required
http://openurc.org/ns/res#uchInstanceId Instance identifier of a UCH that this resource can be used on. There may be multiple occurrences of this property, each for one UCH that the resource can be applied on. String in the format "UCH-macAddress", e.g. "UCH-00-1C-F0-D0-AC-00" optional

4.13. Icon Resource Properties

An Icon Resource is a coherent list of key-value pairs [UCH], describing a specific icon.

Icon Resources are described by generic resource properties (see section Generic Properties), if applicable, and any of the following properties:

Property Name Description Values Usage
http://openurc.org/ns/res#type Type of resource with regard to the URC ecosystem. http://openurc.org/restypes#icon required

http://openurc.org/ns/res#subtype

Subtype of icon resource. http://openurc.org/ns/res#visualIcon

http://openurc.org/ns/res#auditoryIcon

http://openurc.org/ns/res#tactileIcon

recommended
http://openurc.org/ns/res#depth Bit depth of the image, if applicable. Integer value e.g. 8, 24, etc. recommended
http://openurc.org/ns/res#height Image height in pixels, if applicable. Integer value recommended
http://openurc.org/ns/res#width Image width in pixels, if applicable. Integer value recommended
http://purl.org/dc/elements/1.1/title A name given to the resource [DCMI Terms].

A language tag may be specified as the value of the descriptor "lang" [RFC 4646] [IANA Language Tags].

The title can be used as a human-readable label for the resource (class).

xsd:string [XSD Datatypes], recommended to be short (not exceeding 5 words). required
http://openurc.org/ns/res#mimeType Mime type of the icon (visual, auditory or tactile) Example: image/png, image/jpeg, image/gif, audio/mp3, etc. required

4.14. Video Resource Properties

A Video Resource is a coherent list of key-value pairs [UCH], describing a video resource.

Video Resources are described by generic resource properties (see section Generic Properties), if applicable, and any of the following properties:

Property Name Description Values Usage
http://openurc.org/ns/res#type Type of resource with regard to the URC ecosystem. http://openurc.org/restypes#video required
http://openurc.org/ns/res#resolution Mode of resolution low = 160 x 120 pixels (width x height)

medium = 320 x 240 pixels (width x height)

high = 640 x 480 pixels (width x height)

recommended for videos with appropriate resolution
http://openurc.org/ns/res#height Video height in pixels, if applicable. Integer value required
http://openurc.org/ns/res#width Video width in pixels, if applicable. Integer value required
http://openurc.org/ns/res#mimeType

MIME type [RFC 2046] of the resource. This property is used by the resource server to determine the MIME type for a resource served to a client upon resource retrieval [RES-SERV-HTTP].

Mime type of the video. Examples: video/mp4, video/webm, video/ogv, etc. required
http://openurc.org/ns/res#iconResource URI for an image that can be used as poster for the video resource. Specifies the retrieval URI of an Icon Resource (see section Icon Resource Properties).

For example, the image could be used for the 'poster' attribute of the <video> element in HTML5.

Note: There may be multiple icon resources specified for a resource (different sizes, visual/auditory/tactile icons, etc.). The caller can query the properties for each of them through the query interface. At a minimum, a visual icon of size 50x50 is recommended.

Resource retrieval URI recommended
http://openurc.org/ns/res#includesAudio Whether the video resource has audio. true = with audio, false = no audio optional
http://purl.org/dc/elements/1.1/title A name given to the resource [DCMI Terms].

A language tag may be specified as the value of the descriptor "lang" [RFC 4646] [IANA Language Tags].

The title can be used as a human-readable label for the resource (class).

xsd:string [XSD Datatypes], recommended to be short (not exceeding 5 words). optional
http://purl.org/dc/elements/1.1/language A language of the video resource, if applicable [DCMI Terms].

Note: The language applies to the audio. If multiple audio tracks are provided in the video resource, the property should be repeated to mention all languages.

Language tag [RFC 4646], as registered in [IANA Language Tags]. recommended

4.14.1. Sign Language Video Resource Properties

A Sign Language Video Resource is a coherent list of key-value pairs [UCH], describing a video resource depicting an information in sign language.

Sign Language Video Resources are described by generic resource properties (see section Generic Properties), and by video resource properties (see section Video Resource Properties), if applicable, and any of the following properties:

Property Name Description Values Usage

http://openurc.org/ns/res#subtype

Subtype of a video resource. http://openurc.org/restypes#signLanguageVideo required
http://openurc.org/ns/res#includesAudio Whether the video resource has audio.

NOTE: This indicates if the sign language interpreter speaks along signing, and if their speaking is recorded in the audio track of the video.

true = with audio, false = no audio required
http://openurc.org/ns/res#interpreterIcon URI for an image that can be used as poster for the sign language interpreter in the video resource. Specifies the retrieval URI of an Icon Resource (see section Icon Resource Properties).

Note: There may be multiple icon resources specified for a resource (different sizes, visual/auditory/tactile icons, etc.). The caller can query the properties for each of them through the query interface. At a minimum, a visual icon of size 50x50 is recommended.

Resource retrieval URI recommended
http://openurc.org/ns/res#interpreterName A name for the sign language interpreter. xsd:string recommended
http://openurc.org/ns/res#interpreterType Whether the sign language interpreter is a human or a computer-generated avatar. avatar, human recommended
http://purl.org/dc/elements/1.1/language A language of the resource, if applicable [DCMI Terms]. Language tag [RFC 4646], as registered in [IANA Language Tags].

Notes:

  • Sign languages have their own language tags.
  • Sign language videos with spoken audio should have two language properties: one for the sign language identifier, and one with the spoken language identifier.
required

5. User Profile Content

A user profile is a coherent list of key-value pairs [UCH], describing a specific user. It consists of public and private content (key-value pairs).

NOTE: The content of a user profile (key-value pairs) is similar to the concept of resource properties, but with an important difference: The user profile content is internal to a user profile, and should only be visible to users that have access to the user profile. In contrast, resource properties are external to a resource, and are visible to all users that have the right to query the resource. Therefore a user profile should not be construed as "resource", and should be stored on a dedicated user profile server rather than the resource server.

5.1. GPII Common Terms Registry

Whenever possible, user profile content should be described in terms of the GPII terms (for the description of user preferences), as specified in [GPII Common Terms Registry].

5.2. Additional Properties

In addition to the GPII preference terms, the following properties may be used inside a user profile to describe a user's needs and preferences.

Key Name Description Values Usage
http://openurc.org/ns/userprof#languages The natural languages preferred by the user as an ordered list (most important first), separated by commas. Comma-separated list of language tags, as defined in ISO 639-1, 639-2 or 639-3 optional
http://openurc.org/ns/userprof#uipm-favorite-publisher Preferred publisher of the user. Used to filter UIPMs and UIPM client resources by property http://purl.org/dc/elements/1.1/publisher.

Note: If this property occurs multiple times, the values are ORed.

See values for http://purl.org/dc/elements/1.1/publisher. optional
http://openurc.org/ns/userprof#uipm-favorite-subscriptionPackage Preferred subscription package of the user. Used to filter UIPMs and UIPM client resources by property http://openurc.org/ns/res#subscriptionPackage.

Note: If this property occurs multiple times, the values are ORed.

See values for http://openurc.org/ns/res#subscriptionPackage. optional
http://openurc.org/ns/userprof#uipm-favorite-name Preferred UIPM or UIPM client resource name, as given by its property http://openurc.org/ns/res#name.

Note: If this property occurs multiple times, the values are ORed.

See values for http://openurc.org/ns/res#name. optional

6. Device Profile Content

A device profile is a coherent list of key-value pairs [UCH], describing a specific device. It consists of public and private content (key-value pairs).

6.1. GPII Common Terms Registry

Whenever possible, device profile content should be described in terms of the GPII terms (for the description of devices and platforms), as specified in [GPII Common Terms Registry].

6.2. Additional Properties

In addition to the GPII terms, the following properties may be used inside a device profile to describe a device and platform.

Key Name Description Values Usage
http://openurc.org/ns/res#accept-language Refer Accept Language HTTP Header [RFC 2616]

Acceptable languages for response.

Tags for Identifying Languages [RFC 5646]

Example: "en-US"

optional

7. References

7.1. Normative References

For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

[DCMI Terms]
DCMI Metadata Terms, http://dublincore.org/documents/dcmi-terms/.
[GPII Common Terms Registry]
http://wiki.gpii.net/index.php/Common_Terms_Registry
[IANA Language Tags]
IANA: Language Subtag Registry, http://www.iana.org/assignments/language-subtag-registry.
[IANA MIME Types]
IANA: MIME Media Types, http://www.iana.org/assignments/media-types/.
[RFC 2046]
IETF RFC 2046, Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types, Nov. 1996, http://www.ietf.org/rfc/rfc2046.txt
[RFC 3986]
IETF RFC 3986, Uniform Resource Identifier (URI): Generic Syntax, January 2005, http://www.ietf.org/rfc/rfc3986.txt
[RFC 4288]
IETF RFC 4288, Media Type Specifications and Registration Procedures, Dec. 2005, http://www.ietf.org/rfc/rfc4288.txt
[RFC 4646]
IETF RFC 4646, Tags for Identifying Languages, Sep. 2006, http://www.ietf.org/rfc/rfc4646.txt
[RFC 2616]
IETF RFC 2616, Hypertext Transfer Protocol - HTTP 1.1, June 1999, http://www.ietf.org/rfc/rfc2616.txt
[RFC 5646]
IETF RFC 5646, Tags for Identifying Languages, Sept. 2009 http://www.ietf.org/rfc/rfc5646.txt
[UCH]
URC Consortium: Universal Control Hub Specification. Latest specification available at: http://openurc.org/TR/uch/
[XSD Datatypes]
W3C Recommendation: XML Schema Part 2: Datatypes, W3C Recommendation 02 May 2001, http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/

7.2. Informative References

For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

[ISO/IEC 24752-1]
Information Technology - User Interfaces - Universal Remote Console - Part 1: Framework. ISO, 2013.
[ISO/IEC 24752-2]
Information Technology - User Interfaces - Universal Remote Console - Part 2: User Interface Socket Description. ISO, 2013.
[ISO/IEC 24752-4]
Information Technology - User Interfaces - Universal Remote Console - Part 4: Target Description. ISO, 2013.
[ISO/IEC 24752-5]
Information Technology - User Interfaces - Universal Remote Console - Part 5: Resource Description. ISO, 2013.
[URC-HTTP]
URC Consortium: URC-HTTP Protocol Specification. Latest specification available at: http://www.openurc.org/TR/urc-http-protocol/
[RES-SERV-HTTP]
Resource Server HTTP Interface specification, URC Consortium. Latest specification available at: http://openurc.org/TR/res-serv-http/