- From: Arle Lommel <arle.lommel@dfki.de>
- Date: Fri, 31 Aug 2012 10:09:33 +0200
- To: Felix Sasaki <fsasaki@w3.org>
- Cc: Yves Savourel <ysavourel@enlaso.com>, public-multilingualweb-lt@w3.org
- Message-Id: <AF7F6327-59C3-4FDC-8DB5-8ECCF93F3F36@dfki.de>
If we move to decimals between 0 and 1 (inclusive) I think we need to review any other numerics outside the quality categories to make sure that we follow the same convention so that there is a consistent ITS 2.0 approach. I don't know right off where else we have comparable numerics, but it is something to remember. -Arle On Aug 31, 2012, at 10:03 AM, Felix Sasaki <fsasaki@w3.org> wrote: > Hi Yves, all, > > 2012/8/30 Yves Savourel <ysavourel@enlaso.com> > Hi all, > > I've added the attributes locQualityPrecisVote and locQualityPrecisVotePointer to the data category. > http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20.html#lqprecis > > > - The name is not great maybe we should have locQualityPrecisVotingScore and locQualityPrecisRangeScore but this is getting just too long and probably confusing. > > - I've adapted an example to show the voting, but a better one are certainly welcome. > > - Currently we can use either vote or score not both. This allows to share the threshold. Hopefully this is fine. Otherwise we may have to also have a threshold for the voting. > > - We've talked about harmonizing the scores/ranges in general. Currently locQualityPrecisScore is an integer between 0 and 100 (inclusive). Should we move to a decimal between 0 and 1? > > Good idea, that fits to yesterday's conclusion > > http://www.w3.org/2012/08/30-mlw-lt-irc.html#T15-03-05 > > Best, > > Felix > > > Cheers, > -yves > > > > > > > -- > Felix Sasaki > DFKI / W3C Fellow >
Received on Friday, 31 August 2012 08:10:03 UTC