This is the issue list for version 0.9 of the Extensible Issues Tracking System (ExIT).
Please send issues regarding ExIT to Ian Jacobs and/or Philippe Le Hegaret.
This issues list is compatible with version 0.9 of ExIT.
Color key: error warning note
| Id: Title | State | Type | Ack. |
|---|---|---|---|
| melton5 : A Tool vs A Kit to Build a Tool | no decision (accepted) | request | |
| kay2 : Allow description with the discussion element | no decision (raised) | request | |
| melton1 : Useless and confusing self-referencing link | agreed | clarification | No reply from reviewer |
| melton2 : Inability to submit comments using the ExIT system | agreed | clarification | No reply from reviewer |
| melton3 : Unclear form field when attempting to "Create new issue from scratch" | agreed | clarification | No reply from reviewer |
| melton4 : Unclear structure of XML document containing the actual issues | agreed | editorial | No reply from reviewer |
| ashok-1 : Global variable or parameter "uri-to-issues-xml" cannot be defined more than once with the same import precedence | agreed | error | No reply from reviewer |
| kay1 : Recording follow-up discussions | agreed | request | No reply from reviewer |
| jacobs1 : Switch to UTF-8 in /2004 space | agreed | request | No reply from reviewer |
| walsh1 : Proposed ExIT schema improvements | agreed | proposal | Agreement |
<p>ExIT not ready for end users out of the box (e.g., due to requirement to use make, etc.).</p>
The change that I now need urgently is a "description" element as part of a "discussion". At present I can point to the minutes where something was discussed, but I want to summarize the content of the discussion, because locating the discussion in the minutes is usually quite hard.
In the HTML file produced by the ExIT system, there is (early in the file) a table containing a listing of issues. The first text in each row is the document ID, in blue and underlined. That text has, of course, an associated reference, which "points to" text later in the HTML file that contains the details of the issue (using a fragment identifier).
The first text of the issue details is a repetition of the issue ID, also in blue and underlined. This text also has an associated reference that "points to" itself -- in fact, this link is identical to the link in the preceding table! It is confusing to most users to have a link that is so completely useless because it is completely self-referencing. I recommend that this second link be changed into ordinary text (perhaps with the issue ID set in a different color or point size or font weight for distinction).
Remove link from issue id, add link to end of title.
The sumbitter understood the "Create issue" function to mean "Submit an issue to this issues list" whereas the intent of the function is that it simplify issue creation for the list managers.
Clarification in the documentation and Web pages that the system is for list managers; doesn't sent issues to a list.
<p>Among the form fields that appear to be mandatory in the "Create new issue from scratch" are fields labelled "Raised by (Name)", "Raised by (URI)", "Raised on (YYYY-MM-DD)", all of which are reasonably self-explanatory (although the "(URI)" fields would be confusing if the EXiT system did not pre-fill the field with "mailto:"). However, there is a fourth field labelled "Raised (URI)" that is confusing to me. There is no documentation that I have been able to locate that suggests the meaning of that field, nor can I guess the meaning by looking at the XML associated with an issues list. Please offer some explanation (to me specifically, in response to this message, but also to other users by means of some sort of documentation) of that fourth field. </p>
Clarification on Web page of meaning of form fields.
<p>I have examined every piece of information that I can locate about the ExIT system, but I have not been able to locate a DTD or an XML Schema that would tell me exactly what the permitted content of each element in the issues.xml document is, nor what attributes are allowed or required for such elements. </p>
Improved links in exit home page and documentation. Clarified in documentation that schema is for issues list data validation.
I'm trying to run it with both MSXSL and Saxon and
I get errors in compiling the stylesheet. The error
messages are a bit different for the two processors but
both complain about duplicate parameter
declarations.Duplicate declarations, duplicate file inclusions, and unused file inclusions were confusing saxon and MSXML. The system should work now.
It's not clear how one is intended to record follow-up discussions. We capture the original comment under "raised", but there is typically then further discussion on the list, during which the comment might be refined. Where are these follow-up messages supposed to go?
Default charset in /2004 will be UTF-8.
Scripts changed so that generated files are labeled as UTF-8 in meta element. Include a ".htaccess" file in installation package (exit.zip) to declare character encoding. Still need to add that to documentation. No xml declaration generated (since that leads to problems with internet explorer). This means that in offline mode there will be problems, but not when served from the Web. All of this will be documented.
Three proposals regarding ExIT schema
"If it was a conscious choice, nevermind"
Last update: $Date: 2004/01/25 16:20:34 $
This page was generated as part of the Extensible Issue Tracking System (ExIT)
Copyright © 2003 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.