W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > September 2017

Re: New action on UCR group / Proposal for requirement numbering

From: Jaroslav Pullmann <jaroslav.pullmann@fit.fraunhofer.de>
Date: Sun, 24 Sep 2017 01:53:31 +0200
To: kcoyle@kcoyle.net
Message-ID: <1d71-59c6f400-3-ff70610@138388038>
Cc: public-dxwg-wg@w3.org <public-dxwg-wg@w3.org>

 Dear Karen, dear all, 

 there were some discussions on the numbering approach for requirements, among others: 
 
  1) continuous index: R1 ... RN:
  PROS:
 - straightforward
  CONS: 
  - possibly high index numbers, potential for mistakes 
  - absolute index prevents distributed work (editors rely on mutual changes of single shared index)
  - purely numerical index, no relation among items

 2) discrete index groups based on requirement's topic: RVers1 ... RVersN, RProv1 ... RProvN

 This approach involve the following steps:

 a) for each requirement identify a topic / main tag, e.g. "version". The assumption here is, that there should be at least
 one such tag (otherwise to be create) and there a requirement should be focused enough to map naturally to a single one

 b) create ID using tag's mnemonic abbreviation and current index: "RVers2". The index increments by group, not globally

 PROS: 
 - easy to maintain small, "local" index
 - distributed work possible
 - items are naturally related
 - makes use of and evaluates tagging
 CONS: 
 - requires to decide on requirements main topic (which is indeed o.k.)   

 Personally I am in favor of option 2) and provided a sample numbering of the whole requirement set here: 

      https://rawgit.com/jpullmann/dxwg/gh-pages/ucr/index.html

 The example surely needs polishing but is stable enough to ask for discussion of this approach in our next telcon. 

     Best regards
   Jaro

On Tuesday, September 19, 2017 00:33 CEST, Karen Coyle <kcoyle@kcoyle.net> wrote: 
 
> After the call ended today I realized that I missed an opportunity to
> create an action around Alejandra's suggestion that the UCR document

> might need numbering for the requirements as well as their brief
> headings. I will now create an action item with the description:
> 
> Explore numbering of requirements within the heading areas in UCR document
> 
> Because the tracker only takes one name, I'll assign this to a member of
> the UCR group but the implication is that it is a group task. Note that
> it says "explore" because the UCR group should come back to us if this
> turns out to be overly burdensome.
> 
> Thanks, kc & Caroline
> -- 
> Karen Coyle
> kcoyle@kcoyle.net http://kcoyle.net
> m: 1-510-435-8234 (Signal)
> skype: kcoylenet/+1-510-984-3600
> 
 
 
 
-- 
Jaroslav Pullmann
Fraunhofer Institute for Applied Information Technology FIT
User-Centered Ubiquitous Computing
Schloss Birlinghoven | D-53757 Sankt Augustin | Germany
Phone: +49-2241-143620 | Fax: +49-2241-142146 
Received on Saturday, 23 September 2017 23:54:10 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 October 2019 00:15:38 UTC