OASIS XML Localisation Interchange File Format (XLIFF) TC

  • 1.  Version Control Commit by Tom.Comerford

    Posted 03-17-2014 05:39
    Author: Tom.Comerford Date: 2014-03-17 05:40:47 +0000 (Mon, 17 Mar 2014) New Revision: 490 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/?rev=490&sc=1 Modified: trunk/xliff-20/attributes/attributes.xml trunk/xliff-20/attributes/candidates_type.xml trunk/xliff-20/attributes/canoverlap.xml trunk/xliff-20/attributes/fs.xml trunk/xliff-20/attributes/hex.xml trunk/xliff-20/attributes/name.xml trunk/xliff-20/attributes/ref.xml trunk/xliff-20/attributes/srcdir.xml trunk/xliff-20/attributes/subFs.xml trunk/xliff-20/elements/candidates/match.xml trunk/xliff-20/elements/change-tracking/item.xml trunk/xliff-20/elements/glossary/definition.xml trunk/xliff-20/elements/glossary/glossentry.xml trunk/xliff-20/elements/glossary/term.xml trunk/xliff-20/elements/glossary/translation.xml trunk/xliff-20/elements/inline/sc.xml trunk/xliff-20/elements/metadata/meta.xml trunk/xliff-20/elements/metadata/metadata.xml trunk/xliff-20/elements/metadata/metagroup.xml trunk/xliff-20/elements/resourceData/res_source.xml trunk/xliff-20/elements/resourceData/res_target.xml trunk/xliff-20/elements/size_restriction/data.xml trunk/xliff-20/elements/size_restriction/normalization.xml trunk/xliff-20/elements/size_restriction/profiles.xml trunk/xliff-20/elements/structural/file.xml trunk/xliff-20/elements/structural/group.xml trunk/xliff-20/elements/structural/notes.xml trunk/xliff-20/elements/structural/skeleton.xml trunk/xliff-20/elements/structural/unit.xml Log: various minor edits for consistency (240)


  • 2.  RE: [xliff] Version Control Commit

    Posted 03-17-2014 11:09
    Hi Tom, all, I'm getting error with the latest changed schemas. -- 1) for <xliff> we now have: <xs:attribute name="version" use="required" default="2.0"/> But use cannot be required if there is a default according both the default JVM XSD processor and oXygen. It needs to be set to optional if we have a default. And I think we have not selected to make it a default attribute. If it was optional we could end up validating any version of a document with any version of the schemas and have a hard time guessing whether reported issues would come from the document or from having the wrong schema. I think we need to remove the default value. -- 2) in resource_data.xsd we don't have the import of xml.xsd any more. That causes a new error for the JVM XSD processor: org.xml.sax.SAXParseException; lineNumber: 53; columnNumber: 52; src-resolve.4.2: Error resolving component 'xml:lang'. It was detected that 'xml:lang' is in namespace ' http://www.w3.org/XML/1998/namespace ', but components from this namespace are not referenceable from schema document 'null'. If this is the incorrect namespace, perhaps the prefix of 'xml:lang' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'null'. oXygen doesn't give an error, but generates a warning. Adding back the import solves both issues. Cheers, -yves


  • 3.  RE: [xliff] Version Control Commit

    Posted 03-17-2014 16:15
    Yves, For the version attribute, I've updated the spec to remove the default value, consistent with your update to the schema. As for the missing import, thanks for catching that -- I removed it in error. Regards, Tom


  • 4.  RE: [xliff] Version Control Commit

    Posted 03-17-2014 16:26
    Thanks Tom.