Re: [ebxml-msg] issues list

[Christopher Ferris <chris.ferris@sun.com>]

David,

Thanks. You add new items using your favorite XML instance
editor. I used XED[1], XMLSpy and XML Authority can also
do the trick. There's also an XML mode for emacs[2] or you
can struggle through using any old text editor such as vi
and cut-n-paste techniques.

Each issue has the following form in XML:

<issue>
<issue-num>1</issue-num>
<title>title page</title>
<locus>line 15/16</locus>
<section>title page</section>
<priority>editorial</priority>
<topic>spec</topic>
<originator><a href='mailto:chris.ferris@sun.com'>Chris Ferris</a></originator>
<responsible></responsible>
<description><a href='http://lists.oasis-open.org/archives/ebxml-msg/200201/msg00130.html'>[see 
email]</a>the date cited here should be consistent
     with its adoption as a TC, not the date that the
     document was published to the TC for consideration
     (vote). Given that the ballot is closed as of
     January 18, then the date cited here cannot be
     less than that date.</description>
<status>Active</status>
<proposal></proposal>
<resolution>none</resolution>
</issue>

This basically boils down to:

title: <brief description>
location: <line number of spec>
section: <section number/title>
priority: <editorial|technical|major technical>
topic: <spec|schema>
description: <complete description of issue and reference to
related material as hrefs>

The rest of the info would be supplied by whomever manages
the issue list (Ralph?).

Cheers,

Chris

[1] http://www.cogsci.ed.ac.uk/~ht/xed.html
[2] http://www-106.ibm.com/developerworks/xml/library/x-emacs/

David Fischer wrote:

> This looks nice on the screen.
> 
> How are new items added or modifications made to the current list?  Does this
> have to be done with a text editor?
> 
> Regards,
> 
> David.
> 
> -----Original Message-----
> From: Christopher Ferris [mailto:chris.ferris@sun.com]
> Sent: Wednesday, January 30, 2002 2:36 PM
> To: ebXML Msg
> Subject: [ebxml-msg] issues list
> 
> 
> All,
> 
> As mentioned on the call, I have tweaked the W3C XML Protocol WG
> issues list for our needs, and have established as a baseline the
> issues I raised with my vote on 2.0.
> 
> Attached are the XML, XSLT, DTD and HTML, all of which should be
> posted to our website. We need to be sure that the DTD retains the
> W3C IP disclaimer.
> 
> Comments welcomed. I'll gladly make any necessary changes
> to the schema or styling.
> 
> Cheers,
> 
> Chris
> 
> 
>