ISO/IEC 23007-1:2010/Amd 1:2012
(Amendment)Information technology — Rich media user interfaces — Part 1: Widgets — Amendment 1: Widget extensions
Information technology — Rich media user interfaces — Part 1: Widgets — Amendment 1: Widget extensions
Technologies de l'information — Interfaces d'utilisateur au support riche — Partie 1: Widgets — Amendement 1: Extensions de widget
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 23007-1
First edition
2010-11-01
AMENDMENT 1
2012-01-15
Information technology — Rich media
user interfaces —
Part 1:
Widgets
AMENDMENT 1: Widget extensions
Technologies de l'information — Interfaces d'utilisateur au support
riche —
Partie 1: Widgets
AMENDEMENT 1: Extensions de widget
Reference number
ISO/IEC 23007-1:2010/Amd.1:2012(E)
©
ISO/IEC 2012
---------------------- Page: 1 ----------------------
ISO/IEC 23007-1:2010/Amd.1:2012(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2012
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2012 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 23007-1:2010/Amd.1:2012(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
Amendment 1 to ISO/IEC 23007-1:2010 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia
information.
This Amendment introduces extensions for advanced widgets and improves interoperability between widget
managers.
© ISO/IEC 2012 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 23007-1:2010/Amd.1:2012(E)
Information technology — Rich media user interfaces —
Part 1:
Widgets
AMENDMENT 1: Widget extensions
At the end of 6.1, add:
In order to be discoverable by other widget managers and recognizable as an MPEG-U conformant
implementation, an MPEG-U widget manager shall advertise a service of type “urn:mpeg:mpeg-
u:standard-service:widget-manager” on all the service and discovery protocols that it supports to
manage the services offered or required by the widgets.
Using this service, widget managers shall support the reception of a “startWidget” message, with either a
“widgetUrl” or a “widgetUUID” parameter, as strings, and optionally with a “widgetContext”, a string
containing the widget context information as defined in Clause 11. The widget manager shall reply to this
message with an integer parameter called “errorCode”, whose value is 0 if the widget was successfully
loaded and any other value if the loading failed.
Using this service, widget managers shall support the reception of a “requestCapabilitiesList”
message with no parameter. The widget manager shall reply with a message containing a description of the
processing capabilities of the widget manager. The description shall be formatted as a string in the
“capabilities” parameter and may be empty. The format of this parameter may be given in the
“capabilitiesType” in the form of a mime type. If this parameter is omitted, the default value is
“application/xml”.
Using this service, a widget manager can also query and request migration of widgets from another widget
manager. The list of widgets can be retrieved using the listWidgets message, which allows a remote
widget manager to query the list of possible widgets from the target widget manager. The reply contains a list
of (numerical) codes, a list of widget names as a space-separated list of quoted strings, and an optional list of
space-separated list of UUIDs.
NOTE The selection of the widgets to be listed is implementation specific: a widget manager may decide to only list
some activated widgets or all widgets installed, whether activated or not.
A widget manager can then request the migration of a widget from the target widget manager using the
getWidget message. This message instructs the target widget manager to trigger the migration of the widget
whose code is provided. The target widget manager then sends a startWidget message to the widget
manager originating this message. The following error codes are defined:
- errorCode 0: success
- errorCode 1: requested widget is no longer available
- errorCode 2: target widget manager denied sending of the widget
- errorCode 3: any other error.
NOTE The target widget manager may refuse to migrate a widget for security reasons. The mechanisms used by
such a widget manager to certify other widget managers are outside the scope of this specification.
NOTE The default value for capabilitiesType is ‘application/xml’ as most capability description standards use XML
documents (e.g W3C CC/PP, MPEG-21 UED).
© ISO/IEC 2012 – All rights reserved 1
---------------------- Page: 4 ----------------------
ISO/IEC 23007-1:2010/Amd.1:2012(E)
The following code uses the syntax described in Clause 10 to describe this service. But, a widget shall not
have this interface in its manifest and widget managers shall fail to load any widget, which has such interface
in its manifest.
serviceProvider=”true” multipleBindings=”true”>
At end of 7.2 Widget life cycle, add:
The widget manager shall maintain a set of known widgets: a known widget is a widget that the widget
manager has checked that it can be rendered. One use of this set is to search fo
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.