Well we keep the issue list out of Kavi,
it’s a simple xml file. So depending on what sort of facilities are
available on the docs.oasis website that might be a possibility.
From: Doug Davis
[mailto:dug@us.ibm.com]
Sent: Friday, December 02, 2005
12:01 AM
To: Marc Goodner
Cc: Anish Karmarkar;
ws-rx-editors@lists.oasis-open.org
Subject: RE: [ws-rx-editors]
Pending Issues for the WSRMP document and plan
A web interface to modify the values of the list would
be best - but I think that might be pushing the boundaries of Kavi's
hi-techness :-)
-Doug
|
"Marc Goodner"
<mgoodner@microsoft.com>
12/01/2005 07:46 PM
|
|
To
|
"Anish Karmarkar"
<Anish.Karmarkar@oracle.com>, <ws-rx-editors@lists.oasis-open.org>
|
|
cc
|
|
|
Subject
|
RE: [ws-rx-editors] Pending Issues for the
WSRMP document and plan
|
|
Well
what do you know. We may have a use for an attribute I never use in
the issue list, edstatus. If we start using that
with an alternate xsl
it would be just what we need. However, that would
require each editor
to update the issue list accordingly. That would
be a lot easier if we
could update the issue list without a man in the
middle approach.
Not that Robin isn't responsive, I just don't want
to abuse his
kindness.
-----Original Message-----
From: Anish Karmarkar
[mailto:Anish.Karmarkar@oracle.com]
Sent: Thursday, December 01, 2005 12:34 PM
To: ws-rx-editors@lists.oasis-open.org
Subject: Re: [ws-rx-editors] Pending Issues for
the WSRMP document and
plan
Yes, that would great, as long as it is ok with
you if the editors
update the status once they are done with a
particular issue.
-Anish
--
Marc Goodner wrote:
> Would a different view of the issue list
help? We could put together
an
> alternative stylesheet to use if that
presents a more useful view of
it.
>
> -----Original Message-----
> From: Anish Karmarkar
[mailto:Anish.Karmarkar@oracle.com]
> Sent: Thursday, December 01, 2005 12:06 PM
> To: Yalcinalp, Umit
> Cc: ws-rx-editors@lists.oasis-open.org
> Subject: Re: [ws-rx-editors] Pending Issues
for the WSRMP document and
> plan
>
> I do have cycles in the coming days and can
work on the drafts (feel
bad
>
> for not being able to work on them for the
past 2 weeks or so).
>
> Can we create a editors' TODO list (unless
folks think that this is
too
> much trouble than it is worth)? This would
speed up task allocation as
> well as ensure that we don't miss anything
that the TC has agreed on.
>
> I would be more than happy to maintain the
TODO list.
>
> What do you think?
>
> -Anish
> --
>
>
> Yalcinalp, Umit wrote:
>
>>Folks,
>>
>>Sorry about the delay in sending this out.
I wrote the email last
>
> night,
>
>>but has been sitting in my drafts folder
:-(.
>>
>>Based on my conversation with Gil today,
he will do some tidying up in
>
>
>>the wsrmp wd 02 (editors area) tomorrow.
>>
>>I have the following pending issues that
need to be integrated
>>
>>I022
>>I024
>>I054
>>I072
>>I073
>>I074
>>
>>I will not be able to work on anything
until Friday, unfortunately.
>
> This
>
>>is a bad week overall.
>>
>>I would be happy to do a sweep regarding
parameters that span multiple
>
>
>>issues. Gil, would you be able to check in
the updates by Friday
>>morning, if at all possible and can you
let me know which issues you
>>were planning to address in the editing.
>>
>>I promise to post the changes to next
Tuesday. This should give ample
>>opportunity to review the spec by next
Thursday for sanity and we can
>>post a copy to the tc. This gives the tc a
week to read the spec prior
>
>
>>to the f2f.
>>
>>Would this plan be acceptable to everyone?
If any of you have cycles
>
> to
>
>>work on the closing the issues this week,
that is great. Just let me
>>know. Otherwise, I will stick to the plan
outlined and let the tc
>
> know.
>
>>Apologies for the late notice.
>>
>>--umit
>>
>>
>>----------------------
>>
>>Dr. Umit Yalcinalp
>>Standards Architect
>>NetWeaver Industry Standards
>>SAP Labs, LLC
>>umit.yalcinalp@sap.com
>>Tel: (650) 320-3095
>>