W3C home > Mailing lists > Public > public-swd-wg@w3.org > May 2007

Re: [SKOS] tracking SKOS issues

From: Antoine Isaac <aisaac@few.vu.nl>
Date: Tue, 29 May 2007 18:20:30 +0200
Message-ID: <465C52CE.3020005@few.vu.nl>
To: Thomas Baker <baker@sub.uni-goettingen.de>
CC: SWD Working Group <public-swd-wg@w3.org>

Hi Tom,

As an additional concern about the issues. I have noticed that when 
Alistair moves the issues from the sandbox to the tracker, he forgets 
the existing links between them and candidate (or accepted) 
requirements, as found in the use case and requirement working draft. 
For example ISSUE-37 CustomExtension [2] was linked in the sandbox [3] 
to R-SkosSpecialization

 I would suggest to keep these links (and actually to write them in a 
cleaner way that it was in the sandbox, since they are broken there). 
For example [2] should be linked to the corresponding item from the UCR 
working draft [4] (yes, I've put IDs there!). I think this is very 
useful when the requirement has already been defined, and has a 
different name (Alistair actually changed them). I propose just to add 
the corresponding link in the description of the issue.

Cheers,

Antoine

[1] http://www.w3.org/2006/07/SWD/wiki/SkosIssuesSandbox
[2] http://www.w3.org/2006/07/SWD/track/issues/37
[3] 
http://www.w3.org/2006/07/SWD/wiki/SkosIssuesSandbox#head-d62568af998072a9c31f764dd77d7ba106427f99
[4] http://www.w3.org/TR/skos-ucr/#R-SkosSpecialization
> This week, I proposed the agenda item "SKOS issue resolution
> process" (see Jon's recent posting below [1]), but we did
> not have time in the call, so I'd like to propose the item
> again for next week.
>
> Specifically, Jon suggests some good ground rules (e.g.
> "if it's not in the tracker, it's not an issue").  He also
> points out some weaknesses in the software -- e.g., there
> is apparently no way to see an overview of all SKOS-related
> issues, only of all _open_ SKOS-related issues [2].  (Feature
> requests for Tracker can be submitted to w3t-sys@w3.org.)
>
> I suggest we walk through these points next week and revise
> IssuesProcess [3] accordingly.
>
> Tom
>
> [1] http://lists.w3.org/Archives/Public/public-swd-wg/2007May/0008.html
> [2] http://www.w3.org/2006/07/SWD/track/products/3
> [3] http://www.w3.org/2006/07/SWD/wiki/IssuesProcess
>
>
>
> On Tue, May 08, 2007 at 10:21:08AM -0400, Jon Phipps wrote:
>   
>> Just to clarify (hopefully) a bit...
>>
>> It looks to me like Alistair's template is intended to provide a
>> template for issue _resolution_ as opposed to issue _proposal_. If
>> this is the case then "SKOS issues can be proposed using the
>> [SkosProposalTemplate SKOS Proposal Template]" isn't correct.
>>
>> Our current "Issue Proposal" process seems to be:
>> 1. an email identifying the issue is sent to the list
>> or
>> 1a. working group members may add an issue directly to the issue tracker
>> and/or
>> 1b. working group members may initiate an issue discussion on the wiki
>> by creating a page related to the issue as a child of the
>> SkosDesign[1] page
>> or
>> 1c. the issue is added to the SkosIssuesSandbox [2] page
>> 2. Issues in the sandbox are discussed in the group, so far fairly 
>> informally
>> if accepted as a 'valid' issue then
>> 3. The issue is added to the Issue Tracker
>> 4. Proposed Resolutions to the Issue are added to the wiki as children
>> of the SkosDesign page and an email is sent to the list
>> 5. Proposed Resolutions are put on the agenda for further discussion
>>
>> and then?
>>
>> The first step in this process seems a bit broken.
>>
>> I'd like to suggest that we...
>> * always add new issues by raising the issue on the tracker -- if it's
>> not in the tracker, it's not an issue
>> * anoint someone to be the official watcher of the list who will have
>> the responsibility of adding to the tracker issues raised by
>> non-members
>> * add _all_ of the issues currently in the issues sandbox into the
>> tracker as 'raised' issues without intermediate discussion.
>> * perhaps give each issue in the tracker it's own wiki page as a child
>> of SkosDesign (or SkosDesign/Issues?) to support the current form of
>> wiki-based discussion???
>> * explicitly follow Alistair's current method of attaching the
>> proposed resolution to an issue as a child of the related issue's wiki
>> discussion page as in...
>> http://www.w3.org/2006/07/SWD/wiki/SkosDesign/GroupingConstructs/ProposalOne
>>
>> This also raises a couple of small issues with the Tracker software...
>>
>> 1. Looking at the product page for SKOS [3] there is no way to see any
>> Issues with a status of other than 'Open'. The only way to see Issues
>> with another status is from the non-product-specific pages [4]. It
>> would be helpful if minimally all Issues and their current status were
>> displayed on the product page. The ability to filter that page would
>> be nice too.
>>
>> 2. There's a menu option for 'Resolutions' [5] but I don't see any way
>> to add a Resolution or attach it to an Issue. Is it there and I've
>> just missed it?
>>
>> Cheers,
>> --Jon
>>
>> [1] http://www.w3.org/2006/07/SWD/wiki/SkosDesign
>> [2] http://www.w3.org/2006/07/SWD/wiki/SkosIssuesSandbox
>> [3] http://www.w3.org/2006/07/SWD/track/products/3
>> [4] http://www.w3.org/2006/07/SWD/track/issues
>> [5] http://www.w3.org/2006/07/SWD/track/resolutions
>>     
>
>   
Received on Tuesday, 29 May 2007 16:20:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:07:49 UTC