[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] Attributes for translation candidates
Hi Yves, I have two suggestions: 1) Change the name of "score" to "similarity". That would be clearer. 2) Define an optional module for storing the metadata associated with a match. Perhaps we would need to provide some directions for handling the combination of "score/similarity" with "quality". It may be hard for a user to select the best match from two matches that have these properties: a) similarity="60" quality="90" b) similarity="80" quality = "60" Regards Rodolfo -- Rodolfo M. Raya rmraya@maxprograms.com Maxprograms http://www.maxprograms.com > -----Original Message----- > From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf > Of Yves Savourel > Sent: Monday, February 27, 2012 1:00 AM > To: 'XLIFF TC' > Subject: [xliff] Attributes for translation candidates > > Hi all, > > You can see the potential representation for 'Translation proposals' here: > http://wiki.oasis-open.org/xliff/XLIFF2.0/Feature/Translation%20Proposals > > One things that we have not discussed yet are the attributes. > > To get things started, here is a summary of the possibilities currently in the > wiki: > > --- score - optional(?) - Specifies how similar the source content of the > candidate is to the span of the source content it applies. The values is an > integer between 0 to 100. > > The value 100 indicates that the source candidate is exactly the same as the > source content it applies. We'll have to define what 'exactly the same' means > (white spaces, inline codes, are <mrk> counted or not, etc.) > > The score is obviously a value that is fully meaningful within a set of > candidates coming from the same system. But it can provide some helpful > indication even out of context. > > > --- quality - optional - Provides a measure how good or bad is the translation. > The value is an integer between 0 and 100. > > Like the score, this value is fully meaningful within a set of candidate coming > from the same system. But it can provide some helpful indication even out of > context. > > > --- origin - optional - Provides a human readable label indicating from where > the candidate comes from. > > > --- type - optional - Provides further information on the kind of match the > candidate represents. For example: in-context-exact, generated by MT, > result of an alignment, created by assembly, etc. We'll have to come up with > a list of pre-defined values, and possibly allows for custom ones. > > Example: > > <match score='100' quality='95' type='mt' origin='Microsoft Translator'> > <source>Once upon a time...</source> <target>Il était une fois...</target> > </match> > > Any other attributes needed? Any input/feedback/etc. on the ones > described? > > I suppose we could have a set of 'properties' associated with each <match>: > creation date, author, project, etc. But I'm not sure that can/should be part > of the construct or something tools would customize. > > Thanks, > -yves > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: xliff-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: xliff-help@lists.oasis-open.org
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]