Subject: [Disman] Fw: [members] OASIS TC Call for Participation: OASIS Remote Control XML Technical Committee

From: "Randy Presuhn" <[email-masked]>
Date: Fri, 19 Aug 2005 12:01:07 -0700

Hi -

I don't know how many of you from the disman list are also on the ops-nm list,
but this note from Bert looked like it would be of interest to many involved in
disman and related work.  Would the RCXML interpreter be a good candidate
for implementations of the script MIB?

Randy

======================================
> From: "Wijnen, Bert (Bert)" <[email-masked]>
> To: <[email-masked]>
> Sent: Friday, August 19, 2005 3:59 AM
> Subject: FW: [members] OASIS TC Call for Participation: OASIS Remote Control XML Technical Committee
>
> FYI.
> It sort of overlaps with some of our NetConf and SNMP/MIB work.
>
> Comments welcome
>
> Bert
>
> -----Original Message-----
> From: James Bryce Clark [mailto:[email-masked]]
> Sent: Friday, August 19, 2005 04:58
> To: [email-masked]; [email-masked]
> Cc: [email-masked]
> Subject: [members] OASIS TC Call for Participation: OASIS Remote Control XML Technical Committee
> Importance: High
>
>
> To: [email-masked],[email-masked]
> Subject: [tc-announce]
>
>      A new OASIS technical committee is being formed. The OASIS Remote Control XML Technical Committee has been proposed by the
members of OASIS listed below.  The proposal (below) meets the requirements of the OASIS TC Process [1].  The TC name, statement of
purpose, scope, list of deliverables, audience, and language specified in the proposal will constitute the TC's official charter.
Submissions of technology for consideration by the TC, and the beginning of technical discussions, may occur no sooner than the TC's
first meeting.
>
>      This TC will operate under our 2005 IPR Policy.[2]  The eligibility requirements for becoming a participant in the TC at the
first meeting (see details below) are that:
>      (a) you must be an employee of an OASIS member organization or an individual member of OASIS;
>      (b) the OASIS member must sign the OASIS membership agreement (see [3]);
>      (c) you must notify the TC chair of your intent to participate at least 15 days prior to the first meeting, which members may
do by using the "Join this TC" button on the TC's public page at [4]; and
>      (d) you must attend the first meeting of the TC, at the time and date fixed below.
>      Of course, it also will be possible to join the TC at a later time.
>
>      Standards always are improved by broad participation.  Non-OASIS members who wish to participate may contact us about joining
OASIS [3].  Our rules and structure are designed to promote inclusiveness. We look forward to assisting parties interested in
joining the community of implementers, technologists, academics and end-users working on OASIS standardization projects.  All also
are welcome to take advantage of the public resources maintained for each TC: a mail list archive, document repository and public
comments facility, all of which will be available via the TC's public home page at [4]. Archives of the TC's mail list and public
comment lists, as with all OASIS TCs, will be visible at [5].
>
>      Further information generally related to the topic area addressed by this TC may be found on the Cover Pages at  "Standards
for Automated Resource Management in the Computing Environment":
> http://xml.coverpages.org/computingResourceManagement.html <http://xml.coverpages.org/computingResourceManagement.html>
>
>      Please feel free to forward this announcement to any other appropriate lists.  OASIS is an open standards organization; we
encourage your feedback. JBC
>
> ~ James Bryce Clark
> ~ Director, Standards Development, OASIS
> ~ [email-masked]
>
> [1] http://oasis-open.org/committees/process.shtml <http://oasis-open.org/committees/process.shtml>
> [2] http://www.oasis-open.org/who/intellectualproperty.php <http://www.oasis-open.org/who/intellectualproperty.php>
> [3] See http://www.oasis-open.org/join/ <http://www.oasis-open.org/join/>
> [4] http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=remote-control
<http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=remote-control>
> [5] http://lists.oasis-open.org/archives/ <http://lists.oasis-open.org/archives/>
>
> ~   James Bryce Clark
> ~   Director, Standards Development, OASIS
> ~   [email-masked]
>
> ====
> OASIS REMOTE CONTROL XML TC
>
> a. Name
>
> OASIS Remote Control XML (RCXML) Technical Committee
>
> b. Statement of purpose
>
> The purpose of the proposed Technical Committee is to develop a set of XML standards to support control of devices to be accessed
and controlled remotely.  There are a growing number of devices available and under development that can be controlled remotely,
including a wide variety of household and industrial implements, and using a broad variety of transmission methods (including
infrared, radiofrequency and other methods).   However, there is not yet a dominant standard for the commands and command syntax for
this control.  XML provides a suitable and very flexible framework for this content.
>
> The problem to be solved is standardization of the growing number of independent product-specific solutions to the control problem
as products and devices proliferate. The standards to be developed should address as wide a range of controllable devices as
possible.  However, it is not possible to anticipate the complete range of commands and syntax that will be needed as new devices
are developed.  For example, it is easy to anticipate that there will be a need for an "ON" or "OFF" command, or for a need to map
"settable" controls on the device to a logically controllable identifier, and to also be able to map the domain of acceptable
settings (either discrete or continuously variable over a range) to that identifier.  However, there likely will be devices in the
future with controls not easily accommodated by this first level of syntax.  The proposed standard should anticipate this by
defining the procedure for periodic expansion and extension.
>
> This Committee will propose RCXML (Remote Control XML). The RCXML technology will allow users to interact with any appliance which
can be controlled by remote control such as TV's, PVR's, VCR's, lighting, heating/cooling systems, security systems, watering
systems etc from a remote location.  Any appliance which has the RCXML interpreter as a middleware can be operated through the RCXML
scenario sent via wire/wireless network.  Even a remote control service provider that doesn't have detailed information about a
certain device should be able to develop and provide control service based on RCXML.
>
> 1) International Standard Technology
> In Korea, RCXML is already being adopted as the domestic standard under TTA's support (Telecommunications Technology Association,
Korea).  Approval of this standard internationally should encourage a broader range of electric/electronic device manufacturers to
apply it to their products. The result will be that the provider can easily create a business model for new service, and, since this
is based on XML, it will be readily available on a standardized and readily tooled basis.
>
> 2)  Low Communication Load
> RCXML, as contributed, currently anticipates only a low communication bandwidth.  Because of this, it can more easily control AV
Digital Appliances (Digital TV, Digital STB, PVR (Personal Video Recorder), etc) than it can more complex Information Appliances
(PC, etc).
> Even though a high speed communication network (ADSL, VDSL, etc) may be installed at home, this network is most often used for
Information Appliances, and may not be suitable or available for the control of common appliances at home. But RCXML is a small
volume protocol, so it can be delivered through telephone line (via modem) unlike a high bandwidth network.  It is not necessarily
reliant on a PC remote control system based on HTTP.
>
> 3)  Small Interpreter
> RCXML does not require a large number of important tags, so it should be very easy to develop a standard interpreter. Compared to
other platforms such as Java Virtual Machine, its size will be small so that it would be easy to embed the system on very simple
devices .
>
> 4)  Web Based Language
> Use of XML will enable development of the service and the platform (appliances to be controlled) separately in WEB/WAP (World Wide
Web -and- Wireless Access Protocol) environments, so it is well suited for personalized approaches. T his service may be delivered
through the web or the telephone line to provide WEB/WAP control through RCXML regardless of the device and the maker.
>
> In the end, through the standardization of RCXML, it is hoped that manufacturers will embed the RCXML interpreter on all relevant
devices they sell.
>
> c. Scope
>
> The TC will develop and publish the syntax definition of XML schemas to enable the control of devices remotely.  Since it cannot
be completely known what devices may be developed in the future which may be candidates for remote control, the TC will also develop
the procedure for extending this syntax to accommodate devices which may require additional syntax not included in the initial
definition.  Since the native code requirements for future devices to be controlled cannot be known, only the surface syntax that
they must accommodate for control will be defined, the interpreters for each device being left to the device developers.
>
> The TC anticipates a contribution of the RCXML Technical Specification ver. 0.5 Rev.1.02 as a starting point.
>
> d.  Deliverables
>
> The TC shall produce two deliverables, 1) the recommended syntax definition (with examples and clarifying notes) for RCXML, and 2)
the recommended procedure for extending it in the future as needed.  The delivery date for both shall be six months from the start
date for the TC.  The TC may also choose to define specific extensions after completing the first two deliverables
>
> e. IPR Mode
>
> RF on Limited Terms Mode (as specified in the OASIS IPR Policy)
>
> f.  Anticipated audience
>
> The anticipated audience (users) of RCXML will be the developers of devices that may be controlled remotely, those who would want
to create control instruments or offer control routines or control services for those devices, and their respective industry and
distributor associations.
>
> g.  Language
>
> The TC will conduct its business in English. The TC may elect to form subcommittees that produce localized documentation of the
TC's work in additional languages.
>
> ====
> The following is non-normative information for the purposes of starting the TC, and will not be part of the TC's charter.
>
> a.  Similar and applicable work
>
> The committee will evaluate and if relevant seek liaison with other potnetiallt related standards projects including:
>   -- the OASIS OBIX TC (relating to building device controls) [*1]
>   -- Other standards and projects that describe the location and statefulness of resources on a network, such as the OASIS DCML
[*2], OASIS WSDM [*3] and OASIS WSRF [*4] TCs
>   -- The Universal Plug and Play (UPnP) Forum [*5]
>   -- Other standards efforts relating to the control of devices, if identified
>
> [*1] http://www.oasis-open.org/committees/obix/ <http://www.oasis-open.org/committees/obix/>
> [*2] http://www.oasis-open.org/committees/dcml-frame/ <http://www.oasis-open.org/committees/dcml-frame/>
> [*3] http://www.oasis-open.org/committees/wsdm/ <http://www.oasis-open.org/committees/wsdm/>
> [*4] http://www.oasis-open.org/committees/wsrf/ <http://www.oasis-open.org/committees/wsrf/>
> [*5] http://www.upnp.org <http://www.upnp.org/>
>
> b. Anticipated contributions
>
> RCXML Technical Specification ver. 0.5 Rev.1.02
>
> c.  Proposed working title / acronym for the specification(s)
>
> RCXML
>
> d.  First meeting
>
>     Date: Monday, September 19, 2005 (Americas) / Tuesday, September 20, 2005 (Europe-Asia)
>     Time:  16h00 (4p) Pacific US, 19h00 (7p) Eastern,  01h00 CET/MESZ, 04h30 New Delhi, 08h00 Seoul/JST, 09h00 Sydney
>    Face to Face or Conference Call: Conference Call
>     If F2F, location: N/A
>     Meeting Sponsor:  From among co-proposers
>
> e.  On-going meeting schedule
>
> It is proposed that the TC would meet by telephone at monthly intervals following the initial meeting;  the exact time and date
for each subsequent meeting to be specified as part of the business conducted at any meeting.  Additional meetings may be scheduled,
if needed, by vote of the TC.  Sponsors for meetings will be solicited from participating members.
>
> f.  Proposers
>
> Young Hwan Huh, Acogito, [email-masked]
> Seung-Yun Lee, Electronics Telecommunications Research Institute, [email-masked]
> Dong Pil Lee, Voceweb.com, [email-masked]
> Fred O'Neal, PhD, Acogito, [email-masked]
> Jason Chung, Ph.D, idisplay.tv, Inc., [email-masked]
> Jung In Choi, Voceweb.com, [email-masked]
>
> g.  TC Convener
>
> Fred O'Neal, PhD, Acogito, [email-masked]
>
> h. Proposed TC chair or co-chairs
>
> Young Hwan Huh, Acogito, [email-masked]
> Fred O'Neal, PhD, Acogito, [email-masked]
>
> END
>
> --------------------------------------------------------------------- This email list is used solely by OASIS for official
consortium communications. Opt-out requests may be sent to [email-masked], however, all members are strongly
encouraged to maintain a subscription to this list.