- From: Phil Ritchie <philr@vistatec.ie>
- Date: Fri, 31 Aug 2012 09:53:26 +0100
- To: Yves Savourel <ysavourel@enlaso.com>
- Cc: <public-multilingualweb-lt@w3.org>
- Message-ID: <OFAB1BEFC2.1E690F59-ON80257A6B.00303455-80257A6B.0030D6A3@vistatec.ie>
My requirement for scores is that I need potentially hundreds of discrete values. For sake of interoperability I'm happy to map to a range but I don't want to end up "loosing precision" amongst my values as a consequence: i.e. 0-2000 of my scores map to 0-1 ITS and thus give values such as 0.897, 0.898, etc. My request would be to standardise on 0-100 decimal. Phil. From: Yves Savourel <ysavourel@enlaso.com> To: <public-multilingualweb-lt@w3.org>, Date: 30/08/2012 21:59 Subject: [ACTION-208] Add voting support to Locationzation Quality Précis 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? Cheers, -yves ************************************************************ This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately by e-mail. www.vistatec.com ************************************************************
Received on Friday, 31 August 2012 08:54:04 UTC