DCS vocabulary of Mobile ontology provides more details for domains related to disctributed communication sphere, such as devices, networks, modalities. every input with buttons or pads associated with certain functions input captured through cameras additional pen gesture interpreter The dcs:WiFiNetwork class represents networks which use WiFi as underlying technology. Responsible: Claudia Villalonga The dcs:InformationService class represents the services which provide some information. Responsible: Claudia Villalonga Responsible: Eric Clavier The dcs:DeviceCapability class represents the physical characteristics of instances of the class dcs:Device. Examples of such characteristics are size of the screen or the amount of memory available. The dcs:DeviceCapability can be used to model a direct link from a specific device to a specific device characteristics as it is done in certain device capability specifications such as UaProf. Responsible: Claudia Villalonga "physical characteristics" added by S.Meissner to seperate the fixed properties of a physical device from the more flexible properties of a renderer (hardware vs. software) visual specific capabilities getter methods for time related attributes of SMIL elements alpha numerical displays (7-digit-display) haptic specific capabilities additional gesture recognizer The dcs:Terminal is a SPICE device with which the user is logged into the SPICE platform and that allows the user to make use of the SPICE services and other features of the SPICE platform through the Dynamic Desktop. The dcs:Terminal is a subclass of core:Device. Responsible: Claudia Villalonga fully alphanumerical keyboard like QWERTY keyboard Responsible:: Eric Clavier MultimodalityDevice is a device which supports more than one modality. introduced by Stefan Meissner (UniS) 2 system service that captures user input and transcodes the input message to MDCS compliant format (EMMA) (introduced by S. Meissner, UniS) The dcs:Capability class represents characteristics of other class instances, e.g., specific devices or networks. Responsible: Claudia Villalonga all audio output every visual output via screens, beamers etc. The dcs:GSMNetwork class represents the mobile telephony GSM networks. Responsible: Claudia Villalonga The default location to store music files. Responsible: Eric Clavier The dcs:AddressBook class contains the user's contact list that is stored on the terminal or teminal part, such as a SIM card. Responsible: Eric Clavier The location folder to store document files. Responsible: Eric Clavier natural language output (synthesised speech) non-speech acoustic signals, like coded sounds (beeps) or keywords controls the entire SMIL presentation getter methods for device specific attributes SMIL standard requires (MDCS will provide some more) Responsible: Eric Clavier The dcs:DcsService class represents services hosted in devices that are part of a DCS (e.g. the Bluetooth Personal Area Network service or the UPnP TV service). This class DOESN'T represent platform or end-user services. The dcs:DcsService class is a subclass of the class dcs:DcsResource. Responsible: Claudia Villalonga The dcs:SIMCard class represents SIM cards such as used in mobile phones. Responsible: Eric Clavier functions MDCS offers for handling media objects (videos, audios, images, text) Responsible: Eric Clavier MDCS is able to control each element (par, seq, media object) of a SMIL presentation audio specific capabilities Formerly known as dcs:ModalityService renamed by S.Meissner (UniS) the RendererService provides ModalityCapabilities now Renderers are software components running on a host device. They provide decoding and de-multiplexing of multimedia content with typical codecs. services supporting creation and editing of SMIL media objects services supporting creation and editing of SMIL presentations Responsible: Eric Clavier tactile feedback like vibration or mechanical actuation The location folder to store application files. Responsible: Eric Clavier pressure sensitive touchpads three dimensional motion detector sensors (Wii controller) The location folder to store application files. Responsible: Eric Clavier still image output The dcs:BluetoothNetwork class represents networks which use Bluetooth as underlying technology. Responsible: Claudia Villalonga The dcs:UMTSNetwork class represents the mobile telephony UMTS networks. Responsible: Claudia Villalonga The dcs:vCardAddressBook class contains the user's contact list that is stored on the terminal or teminal part, such as a SIM card. Each contact of the user is expressed using the vCard format. Responsible: Eric Clavier non speech output, beeps or other signal tones The dcs:NetworkCapability class represents characteristics of instances of the class dcs:Network. Examples of such characteristics are network coverage or its delay rate. The dcs:NetworkCapability can be used to model a direct link from a specific network to a specific network characteristics as it is done in certain network capability specifications such as the IEEE 802 specification. Responsible: Claudia Villalonga used by the MDCS for triggering the SMIL renderers (introduced by Stefan Meissner, UniS) (elaborated with Pablo Cesar, CWI) addditional mouse gesture interpreter The dcs:KnowledgeService class represents the services which provide knowledge information. Responsible: Claudia Villalonga Responsible: Eric Clavier The dcs:DistributedCommunicationSphere class identifies of a communication sphere associated with a particular person at a particular point of time. The scope of communication sphere is in defining machine-oriented resources around a person, such as networks, devices, services. Responsible: Claudia Villalonga natural language voice input The dcs:EmbeddedDevice class represents really simple devices that are nested into other non-communication-devices and that don't provide an user interface. The dcs:EmbeddedDevice class is a subclass of the class core:Device. Responsible: Claudia Villalonga par element only The dcs:QoS represents the quality a service has. The quality can be understood as it is traditionally in telecommunications (i.e., broadband) or in a wider sense. Responsible: UniS based on the SMIL 2.1 and EMMA standards (Pablo Cesar and Stefan Meissner) 1 The dcs:ModalityDevice class represents devices that provide modalities. The dcs:ModalityDevice class is a subclass of the class core:Device. Responsible: Claudia Villalonga, Stefan Meissner supports fully alphabetical handwriting recognizer The dcs:ContextService class represents the services which provide context information. Responsible: Claudia Villalonga motion picture output Responsible: Eric Clavier numerical keypad like a phone's dialpad getter methods for presentation layout specific attributes and a service for switching between layouts media objects only, out of prentation's sync media objects only, out of prentation's sync The default location to store picture files. Responsible: Eric Clavier The dcs:SensorNode class represents sensors. The dcs:SensorNode class is a subclass of the class core:Device. Responsible: Claudia Villalonga all audio input (introduced by S. Meissner, UniS) The dcs:Availability class displays whether a DCS resource (person, terminal, network, etc.) is available. Availability presumably can change over time. Responsability: UniS cursor contolling devices like mouse, trackstick, joystick or joyball The dcs:Network class represents Networks to which the user of a DCS can connect. The dcs:Network class is a subclass of the class dcs:DcsResource. Responsible: Claudia Villalonga 1 1 1 The dcs:DCSResource class represents resources that can be part of a DCS. Responsible: Claudia Villalonga The dcs:belongsTo property relates a devices with the owner of such device Responsible: Neos The dcs:containsResource properties relates the DCS of a user with the different resources that are part of it. Responsible: Claudia Villalonga The property dcs:hasNetworkCapability assigns a network to a specific capability. Responsible: Claudia Villalonga The dcs:canBeAccessedViaNetwork property relates a device to the networks that can provide access to it. These access networks can be the networks to which the device is connected or other networks that can reach the device through other networks. Responsible: Claudia Villalonga The property dcs:hasCapability assigns a DCS resource to a specific capability. Responsible: Claudia Villalonga The dcs:associatedWith property indicates that a file is related to a folder Responsible: Eric Clavier The dcs:uses property relates user with the devices he is using Responsible: Claudia Villalonga The dcs:hasAddressBook property relates a terminal with the Addess Book it is equipped with Responsible: Eric Clavier The dcs:isCapabilityOfResource property relates capabilities with the DCS resource. Responsible: Claudia Villalonga every ModalityService must be supported by control capabilities (introduced by Stefan Meissner, UniS) The dcs:isPartOfDcs property relates a resource with the different DCS in which it is contained. Responsible: Claudia Villalonga The dcs:isCapabilityOfNetwork property relates capabilities with the network Responsible: Claudia Villalonga The dcs:availableAt property relates an address book with the terminal that hostes it Responsible: Eric Clavier The dcs:providesAccessToDevice property relates a network to all the devices that can be accessed through it. The accessible devices can be devices connected directly to the network or other devices that are not connected directly to the network but that can be accessed through other networks. Responsible: Claudia Villalonga The dcs:owns property relates the owner to the devices he owns Responsible: Neos The dcs:isBeingUsedBy property relates device with the user that is making use of it Responsible: Claudia Villalonga The dcs:isConnectedToNw property relates a Device or Network to the Networks it is directly connected. Responsible: Claudia Villalonga