Re: [emergency] Agenda: 4/6 Call

[Rex Brooks <rexb@starbourne.com>]

Title: Re: [emergency] Agenda: 4/6 Call

Hi Folks,

2. We have an offer to publish an issue of the Java Locations Service Newsletter, this week or next:

http://www.jlocationservices.com/ 

3. While I may be getting ahead of myself, I took the liberty of adapting a handy tool from WSRP TC which we can discuss if there is time and interest, or set aside for later, or ignore altogether, but having a template for a web-viewable change request or feature proposal seemed like a decent idea to me. That combined with the Excel Issues List just gives us a means to track work. I will explain the template if it comes up.

Ciao,

Rex

At 8:50 AM -0400 4/6/04, R. Allen Wyke wrote:

> 1. CAP Spec: now that CAP has passed the
> voting at OASIS and the results of that voting has been posted
> (http://lists.oasis-open.org/archives/members/200404/msg00000.html),
> we now need to make some final decisions about what edits to make on
> the document itself. As Art pointed out in his email
> (http://lists.oasis-open.org/archives/emergency/200403/msg00157.html),
> we have the opportunity to "prepare the final version for
> publication" as stated in the TC Guidelines
> (http://www.oasis-open.org/committees/guidelines.php#spectostand). It
> also states that these changes can not be changes to the normative
> statements in the document. That being said, Bob brought up concerns
> about the schema
> (http://lists.oasis-open.org/archives/emergency/200403/msg00123.html),
> which we need to discuss. As I mentioned in an earlier post
> (http://lists.oasis-open.org/archives/emergency/200403/msg00165.html),
> Jamie is planning on joining our call today, so we can seek input from
> him as to how to best handle since the schema is certainly
> normative.
>
> 2. CAP Evangelization: excuse the topic naming, but I had to come up
> with something that made sense :) Anyway, its time to work on the
> promotional aspect of CAP. I had a brief chat with EIC Chair Matt
> Walton yesterday, and they are of course also excited about the work.
> Given the interest across multiple groups, at the last meeting we
> agreed Rex would be the point man
> (http://lists.oasis-open.org/archives/emergency/200403/msg00116.html)
> for incoming media/press requests. I also sent out a note
> (http://lists.oasis-open.org/archives/emergency/200404/msg00026.html)
> on the OASIS Media Guidelines
> (http://www.oasis-open.org/committees/guidelines.php#media) just to
> make sure everyone remembers that any requests for interviews about
> the TC work have to be coordinated with OASIS, which Rex (as agreed
> the primary point person) and I (helping as he needs) will be
> facilitating. If any of you have questions regarding this, then let's
> arrange a call with Carol Geyer to ensure we are following their
> process. In addition, it is even more important now for us to work on
> the Implementer's Guide and Test Scenarios, as those help bring CAP
> full circle.
>
> 3. CAP Future: we have some good comments, suggestions, and concerns
> that have been circulated on the list and have been put in the
> spreadsheet in the Doc Repository. While we certainly do not have to
> determine timelines or strategy yet regarding CAP 1.NEXT, we might as
> well being thinking about it.
>
> 4. IF SC: Update on their work product (ie: the documents and their
> summary) and when it will be circulated.
>
> The other SCs do not really have any Action Items that have not
> already been mentioned, but if there is something notable to talk to
> the group about, then by all means bring it up.
>
> As for the Charter and Requirements Document, with the energetic
> discussions that have occurred since the last meeting I felt it would
> be wise to hold off throwing yet another iron on the fire (literally),
> so unless there is any objection, I propose we hold on those 2 things
> until we all get CAP at an agreed upon place.
>
> See you all at noon Eastern Time!
>
> --
> R. Allen Wyke
> Chair, OASIS Emergency Management TC
> emergency-tc@earthlink.net
>
>
> To unsubscribe from this mailing list (and be removed from the roster
> of the OASIS TC), go to
> http://www.oasis-open.org/apps/org/workgroup/emergency/members/leave_workgroup.php.

-- 

Rex Brooks
GeoAddress: 1361-A Addison, Berkeley, CA, 94702 USA, Earth
W3Address: http://www.starbourne.com
Email: rexb@starbourne.com

Tel: 510-849-2309

Fax: By Request

Title: Change Request or Feature Template

Change Request or Feature Proposal

[Insert Change Request or Feature Title Here]

Owner	[owner name]
Release	[targeted release]
Status

Version History
Date	Author	Version	Description

---

Contents

1. Problem statement
2. Use cases
3. Feature scope
4. Milestone/Schedule

---

Problem Statement

This section provides a summary description for the problem this feature

will solve.

---

Use Cases

This section describes 1 or more use cases that illustrate the problem described

above.

---

Feature Scope

This section describes the scope and limits of this design.  It should

include both a description of what is in scope and what is out of scope.

---

Milestone/Schedule

This section describes a set of discernable milestones for this design.  It

is followed by a table that sets a schedule for these milestones.

Milestone	Proposed Date	Delivered