OASIS XML Localisation Interchange File Format (XLIFF) TC

  • 1.  RE: [xliff] 2.0 Validations Module Proposal

    Posted 11-16-2012 09:51
    Hi Ryan,   All possible actions should be defined in the module. It cannot be left open to let end users create custom rule types. Every tool that supports the module should be able of supporting all validation types.   There should be just one <validations> element in each allowed place.     The elements <validation> and <matchExpression> should be combined into one (<matchExpression> can be discarded, as it does not contain any attribute and the regular _expression_ could be the content of <validation>).     The element containing the regular _expression_ should have an xml:space attribute set to preserve by default.   Regards, Rodolfo -- Rodolfo M. Raya Maxprograms http://www.maxprograms.com    


  • 2.  RE: [xliff] 2.0 Validations Module Proposal

    Posted 11-20-2012 00:58




    Thanks Rodolfo for the comments and feedback. See our response inline.
     


    From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org]
    On Behalf Of Rodolfo M. Raya
    Sent: Friday, November 16, 2012 1:51 AM
    To: xliff@lists.oasis-open.org
    Subject: RE: [xliff] 2.0 Validations Module Proposal


     

    Hi Ryan,


     


    All possible actions should be defined in the module. It cannot be left open to let end users create custom rule types. Every tool that supports the module should
    be able of supporting all validation types.
     


    [ryanki] We didn’t see this restriction about modules in the specification, can you point us to it? Would it make more sense if the x- naming convention were
    used? In that case, any tool supporting <validations> that doesn’t have knowledge of the rule could safely ignore it.
     


    There should be just one <validations> element in each allowed place.



     


    [ryanki] Like <notes> and <metadata> we are advocating having a name attribute that would allow you to have more than one “grouping” at the same extension point.
    A scenario for this might be that you have groups of validations where some of them you want to run during one phase of your workflow and others during another.

     


    The elements <validation> and <matchExpression> should be combined into one (<matchExpression> can be discarded, as it does not contain any attribute and the
    regular _expression_ could be the content of <validation>).


     
    [ryanki] Point taken. We’ll make that change.


     


    The element containing the regular _expression_ should have an "xml:space" attribute set to "preserve" by default.
     
    [ryanki] point taken. We’ll make that change.


     


    Regards,


    Rodolfo


    --
    Rodolfo M. Raya
    Maxprograms http://www.maxprograms.com