Proceedings Third IEEE Workshop on Mobile Computing Systems and Applications
DOI: 10.1109/mcsa.2000.895383
|View full text |Cite
|
Sign up to set email alerts
|

A device-independent representation for services

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 11 publications
(5 citation statements)
references
References 9 publications
0
5
0
Order By: Relevance
“…A different approach for showing the user interface in the controller device is to have a service interface description that can be read by a controller to dynamically generate a suitable user interface (graphical, speech, gesture, command line, etc.). For example, (Roman, Beck, & Gefflaut, 2000) developed a device independent, XML-based, language for representation of services and the respective dynamic interface generation for mobile devices. The service description language allows the definition of a list of methods with parameters, which can be invoked by the client.…”
Section: Abstract Ui Descriptionmentioning
confidence: 99%
“…A different approach for showing the user interface in the controller device is to have a service interface description that can be read by a controller to dynamically generate a suitable user interface (graphical, speech, gesture, command line, etc.). For example, (Roman, Beck, & Gefflaut, 2000) developed a device independent, XML-based, language for representation of services and the respective dynamic interface generation for mobile devices. The service description language allows the definition of a list of methods with parameters, which can be invoked by the client.…”
Section: Abstract Ui Descriptionmentioning
confidence: 99%
“…So is MOCA's invocation model for remote services based on dynamically downloaded bytecode, RMI or IIOP and custom Java classloaders, all together not available on typical wireless information devices. As the authors state in [15], MOCA addresses mainly back-end application logic, and a typical MOCA application is either implementing "traditional Java technologies such as the AWT" or "on the use of servlets that are hosted under MOCA", which are both too heavyweight for small mobile devices. The aspect of context-awareness (see section 3) is not handled within MOCA.…”
Section: Service Discovery and Interaction On Mobile Devicesmentioning
confidence: 99%
“…Java Bytecode, JavaScript) or abstract rendering directives (e.g. XML/XSLT files defining a GUI as a service front-end [15]) Note that it must be ensured that a proper execution handler for the code snippet exists on the mobile device (e.g. Java VM, Scripting handler or Renderer).…”
Section: Code Snippet Depositionmentioning
confidence: 99%
“…The work of Manuel Roman et al [13] focuses on enabling access to services from many different devices. This they achieve by having a single XML file describe both the service functionality and the user interface in a device independent manner, and using a device specific XSL style sheet to map user interface components to platform-dependent resources.…”
Section: Related Workmentioning
confidence: 99%