wsrp-wsia message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: [wsrp-wsia] WSRP-Markup Subcommittee Meeting Minutes
- From: Rex Brooks <rexb@starbourne.com>
- To: wsrp-wsia@lists.oasis-open.org
- Date: Thu, 27 Feb 2003 07:09:30 -0800
Title: WSRP-Markup Subcommittee Meeting
Minutes
Here are the minutes of the first
teleconference meeting of the WSRP-Markup Subcommittee
February 26, 2003
USA Toll Free Number: 1-888-481-3032
USA Toll Number: 1-617-801-9600
Roll Call:
Rex Brooks
Co-Chair
Andre Kramer Co-Chair
Richard Jacob
Walter Heanel
The meeting convened at 8:05 am PST, 11:05 am EST, 5:05 pm CET. Rex
Brooks chaired the meeting and took notes for the minutes. Rex also
indicated that he had taken the Kavi training and would attend to the
tasks required for that.
This was the first meeting of record for this subgroup, which is
tasked with exploring the areas of markup for inclusion in v. 1.1-2.x
of the Web Service for Remote Portlets Specification.
The first item on the agenda was to determine what the charter for the
WSRP Markup Subcommittee ought to be and how it should be framed. It
was agreed that this group should collect the markup types and
fragments which are thought to be necessary or desirable for
inclusion, determine what accommodation is required for this and then
assess priorities for inclusion. It was also agreed that a list of
deliverables is also needed. As to how the charter should be framed,
Richard Jacob suggested that we look at the charter for the
Interoperability Subcommittee as a model, and this was agreed. Rex
Brooks said he would be willing to draft a charter for the WSRP Markup
Subcommittee based on the WSRP Interoperabiity Subcommittee model
which follows:
Interoperability Subcommittee Charter Model
The purpose of the WSRP Interoperability Subcommittee is coordinate
first interoperability test between various implementations of the
WSRP v1 specification. This allows participants to check their
implementations and their ìinterpretationî of the WSRP v1
specification. This group should closely align with the WSRP
Conformance Subcommittee to assure valid testing scenarios. Secondly,
these tests should allow the subgroup to find practical
problems/issues in the WSRP v1 specification.
Name
The name of this subcommittee shall be the OASIS WSRP Interoperability
subcommittee.
Mailing-List
The mailing list shall be the wsrp-interop defined at the OASIS
site.
Purpose
The aim of this subcommittee will be:
Define a set of tests closely related to the WSRP Conformance
subcommittee
Start initial testing of communication flow between various
implementations
Allow participants to validate their implementations
Inform WSRP TC of vague or incomplete portions of the v1
specification
Deliverables
The deliverables of this subcommittee will be:
Publish access points of implementations participating in the
interoperability testing.
Report the interoperability results
Matrix of current status per participant
Documentation of problems/issues
Documentation of the interoperability tests
Rex Brooks said he would submit the charter this week as well as
recording the minutes.
Richard introduced Walter, who is new to the TC, and this SC, as a
specialist in VoiceXML, which had been included in the initial set of
markup types offered as examples this group will assess. Walter was
welcomed.
Most of the rest of this meeting was devoted to drawing up a first
list of tasks, (not listed by priority) which follows:
* Determine what markup types and fragments are currently used or
will be in the near term, and how they work with the current WSRP
Specification, including, (but not restricted to) HTML/XHTML/CSS, WAP,
VoiceXML, SVG, SMIL, Proprietary/Application MIMEtypes such as Flash
and VRML/X3D, and device-specific protocol markup types and
fragments;
* Specifically explore i-mode and Compact HTML (cHTML) for inclusion
as markup types and fragments
* Determine how to harmonize the spec with longer term future
technologies and device capabiities;
* Determine if recommended best practices or requirements need to be
specified, such as requiring that html table text must go into a
Column Tag Table Cell;
* Define Markup Fragments for what can be used and in what form,
i.e. how these will work with the specification;
* Explore HTML Scripting and using namespacing for use with
scripting languages, including the question of suggesting best
practices or requirements for using ASP, JSP, and PHP;
ª Explore the question of defining templates for markup types,
MIMEtypes, markup fragments,
etc;
* Determine how best to coordinate our work with other standards
bodies and specifications.
The members of the group were asked to consider which markup areas
they could specialize in for these various tasks.
The meeting was then adjourned.
Ciao,
Rex
--
Rex Brooks
Starbourne Communications Design
1361-A Addison, Berkeley, CA 94702 *510-849-2309
http://www.starbourne.com * rexb@starbourne.com
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC