OASIS XML Localisation Interchange File Format (XLIFF) TC

  • 1.  CSPRD03 #237: mtc:match default attribute value is missing

    Posted 03-12-2014 02:07
    CSPRD03 #237: For mtc:match, the schema doesn’t reflect the specified default value ‘no’.   I propose to add the missing default value, unless I hear dissent by the end of the week.   Thanks,   Tom  


  • 2.  RE: [xliff] CSPRD03 #237: mtc:match default attribute value is missing

    Posted 03-12-2014 03:12
    Hi Tom,   Sorry: I’m probably missing something. What default value ‘no’ are you talking about? mtc:match has quite a few attributes but none seem to have default values (or have a ‘no’ value).   Thanks, -yves     From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Tom Comerford Sent: Tuesday, March 11, 2014 8:08 PM To: xliff@lists.oasis-open.org Subject: [xliff] CSPRD03 #237: mtc:match default attribute value is missing   CSPRD03 #237: For mtc:match, the schema doesn’t reflect the specified default value ‘no’.   I propose to add the missing default value, unless I hear dissent by the end of the week.   Thanks,   Tom  


  • 3.  RE: [xliff] CSPRD03 #237: mtc:match default attribute value is missing

    Posted 03-12-2014 03:47
    Yves,   It seems that some of the intended keystrokes remained in my brain, where apparently you couldn’t see them. Sorry for the omission.   To state it more completely: The element mtc:match has an attribute ‘reference’. In the spec, its default is ‘no’ but this isn’t reflected in the schema. The proposed solution is to add the missing default value.   Regards,   Tom     From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Yves Savourel Sent: Tuesday, March 11, 2014 11:12 PM To: xliff@lists.oasis-open.org Subject: RE: [xliff] CSPRD03 #237: mtc:match default attribute value is missing   Hi Tom,   Sorry: I’m probably missing something. What default value ‘no’ are you talking about? mtc:match has quite a few attributes but none seem to have default values (or have a ‘no’ value).   Thanks, -yves     From: xliff@lists.oasis-open.org [ mailto:xliff@lists.oasis-open.org ] On Behalf Of Tom Comerford Sent: Tuesday, March 11, 2014 8:08 PM To: xliff@lists.oasis-open.org Subject: [xliff] CSPRD03 #237: mtc:match default attribute value is missing   CSPRD03 #237: For mtc:match, the schema doesn’t reflect the specified default value ‘no’.   I propose to add the missing default value, unless I hear dissent by the end of the week.   Thanks,   Tom  


  • 4.  RE: [xliff] CSPRD03 #237: mtc:match default attribute value is missing

    Posted 03-12-2014 04:40
    Quite right: I see it now. +1   Thanks, -yves     From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Tom Comerford Sent: Tuesday, March 11, 2014 9:47 PM To: Yves Savourel; xliff@lists.oasis-open.org Subject: RE: [xliff] CSPRD03 #237: mtc:match default attribute value is missing   Yves,   It seems that some of the intended keystrokes remained in my brain, where apparently you couldn’t see them. Sorry for the omission.   To state it more completely: The element mtc:match has an attribute ‘reference’. In the spec, its default is ‘no’ but this isn’t reflected in the schema. The proposed solution is to add the missing default value.   Regards,   Tom     From: xliff@lists.oasis-open.org [ mailto:xliff@lists.oasis-open.org ] On Behalf Of Yves Savourel Sent: Tuesday, March 11, 2014 11:12 PM To: xliff@lists.oasis-open.org Subject: RE: [xliff] CSPRD03 #237: mtc:match default attribute value is missing   Hi Tom,   Sorry: I’m probably missing something. What default value ‘no’ are you talking about? mtc:match has quite a few attributes but none seem to have default values (or have a ‘no’ value).   Thanks, -yves     From: xliff@lists.oasis-open.org [ mailto:xliff@lists.oasis-open.org ] On Behalf Of Tom Comerford Sent: Tuesday, March 11, 2014 8:08 PM To: xliff@lists.oasis-open.org Subject: [xliff] CSPRD03 #237: mtc:match default attribute value is missing   CSPRD03 #237: For mtc:match, the schema doesn’t reflect the specified default value ‘no’.   I propose to add the missing default value, unless I hear dissent by the end of the week.   Thanks,   Tom  


  • 5.  Re: [xliff] CSPRD03 #237: mtc:match default attribute value is missing

    Posted 03-12-2014 12:29
    +1 Dr. David Filip ======================= LRC CNGL LT-Web CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Wed, Mar 12, 2014 at 4:39 AM, Yves Savourel < ysavourel@enlaso.com > wrote: Quite right: I see it now. +1   Thanks, -yves     From: xliff@lists.oasis-open.org [mailto: xliff@lists.oasis-open.org ] On Behalf Of Tom Comerford Sent: Tuesday, March 11, 2014 9:47 PM To: Yves Savourel; xliff@lists.oasis-open.org Subject: RE: [xliff] CSPRD03 #237: mtc:match default attribute value is missing   Yves,   It seems that some of the intended keystrokes remained in my brain, where apparently you couldn’t see them. Sorry for the omission.   To state it more completely: The element mtc:match has an attribute ‘reference’. In the spec, its default is ‘no’ but this isn’t reflected in the schema. The proposed solution is to add the missing default value.   Regards,   Tom     From: xliff@lists.oasis-open.org [ mailto:xliff@lists.oasis-open.org ] On Behalf Of Yves Savourel Sent: Tuesday, March 11, 2014 11:12 PM To: xliff@lists.oasis-open.org Subject: RE: [xliff] CSPRD03 #237: mtc:match default attribute value is missing   Hi Tom,   Sorry: I’m probably missing something. What default value ‘no’ are you talking about? mtc:match has quite a few attributes but none seem to have default values (or have a ‘no’ value).   Thanks, -yves     From: xliff@lists.oasis-open.org [ mailto:xliff@lists.oasis-open.org ] On Behalf Of Tom Comerford Sent: Tuesday, March 11, 2014 8:08 PM To: xliff@lists.oasis-open.org Subject: [xliff] CSPRD03 #237: mtc:match default attribute value is missing   CSPRD03 #237: For mtc:match, the schema doesn’t reflect the specified default value ‘no’.   I propose to add the missing default value, unless I hear dissent by the end of the week.   Thanks,   Tom