Open maryi opened 8 years ago
both those changes sound fine to me
Thanks @maryi
In the case of scale I am flexible. We could use the numbers to describe the low, medium and high range. So low (1-5), medium (6-10), large (10+) or something similar if its important to stay within the DB number descriptions.
For nascence I think its important to use the terms from the report (Routine tasks, Most tasks are routine, Most tasks will be new, Work is Developing) Since as we have discussed nascence is a problematic descriptor, I dont know if user could easily describe these in terms of low, medium, high. The notion of routine, most routine, most new, developing might make more sense IMO.
i see your point @mpaskevi .. and I think I agree with you. Nascence has not been an easy descriptor to work with, but if we leave it as low, medium and high we are leaving more space for ambiguity.
ok, updated List of applications for Nascence descriptor
Hey team, As i said in our last meeting i'm cheking that the descriptors we have in the report are the same as the ones in the list of applications. i found that some descriptors were using a slightly different voabulary so I just changed that (e.g. in service type, software download and should be free software download).
In other cases, I found descriptors that we had decided not to use with applications, such as the case as Phisical distribution -this one was replaced by AWARENESS MECHANISMS. In these cases, I just marked the header with red, so you guys know that we shouldn't be using that... If there is anything you think we SHOULD be using, please bring that up here for discussion.
Now, what is this issue for? I have two special cases: