[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: IANA registration for Media Type application/xliff+xml
Hello David,About an hour ago I received word from IANA (ICANN) that the IESG/IETF final review of the application for media type registration had now passed expert review, and was approved. So it's published, per references below. Thanks for your work supplying the technical content for the registration, and for your patience as we worked through the formal review process.In a couple early versions of the application, your name (as spec lead editor) was included, but I was asked to remove that content.The XLIFF spec itself at OS level is still referenced multiple times, by URI reference, where you are named as editor:http://docs.oasis-open.org/xliff/xliff-core/v2.1/os/xliff-core-v2.1-os.htmlBest wishes,- Robin--Robin Cover
OASIS, Director of Information Services
Email: robin@oasis-open.org
Staff bio: http://www.oasis-open.org/people/staff/robin-cover===========Media Typesxhtml+xml application/xhtml+xml [W3C][Robin_Berjon]xliff+xml application/xliff+xml [OASIS][Robin_Cover]xml application/xml [RFC7303]Removed: Provisional RegistrationProvisional Standard Media Type Registry(now null, was:application/xliff+xml OASIS [Robin_Cover]Source now:(registered 2018-04-06, last updated 2018-04-06)Name: Robin CoverEmail: robin&oasis-open.orgMedia type name: applicationMedia subtype name: xliff+xmlRequired parameters: N/AOptional parameters: N/AEncoding considerations: binarySame as encoding considerations of application/xml as specified inRFC 7303, Section 3 "Encoding Considerations"Security considerations: XLIFF is a format used for localization andtranslation of textual data, and as such does not itself includefacilities for executable content.Apart from all of the security considerations described inRFC 7303 Section 10 ("Security Considerations"), XLIFF Version 2.0and higher has the following Security considerations:Extensibility: XLIFF permits extensions. Hence it is possiblethat application xliff+xml may describe content that has securityimplications beyond those described here.Direct external reference mechanisms: An XLIFF document has anumber of attributes of the type URI or IRI, all of which may bedereferenced and some of them should be dereferenced. Therefore,the security issues of RFC 3987 Section 8 should be considered.In addition, the contents of resources identified by file: URIscan in some cases be accessed, processed and returned as results.More details can be found in the Detailed Security Considerationssection of the specification "A.1.1 Detailed SecurityConsiderations".The XLIFF format does not offer any internal mechanisms to provideprivacy, convey trust or verify the integrity of XLIFF documents.If such features are needed varies from case to case.Implementations that will process documents in cases where one ormore of these features are required need to implement that outsideof the XLIFF format. Transport privacy may for example be providedby SSL/TLS. Storage privacy could be implemented by encrypting theXLIFF content using XML encryption or some other appropriatemeans. Likewise the trust and integrity checks could beimplemented using XML signatures or by some other technology thatis appropriate for the particular implementation.Interoperability considerations: Same as interoperabilityconsiderations described in RFC 7303Also, interoperability requirements are specified throughout thespecification and summarized in its Conformance Section.Published specification: XLIFF Version 2.1 (OASIS Standard,13-February-2018) atApplications which use this media: XLIFF conformant applications,according to the Conformance Section of the specificationFragment identifier considerations: Generic XML processors won't beable to resolve XLIFF fragment identifiers, as the fragmentidentification syntax is specific for XLIFF and has been definedin its Fragment Identification section as of csd03/csprd03 ofXLIFF Version 2.0;Restrictions on usage:: N/AAdditional information:1. Deprecated alias names for this type: N/A2. Magic number(s): N/A3. File extension(s): xlf4. Macintosh file type code: "TEXT"5. Object Identifiers: N/AGeneral Comments: N/APerson to contact for further information:1. Name: Robin Cover2. Email: robin&oasis-open.orgIntended usage: CommonAuthor/Change controller: OASIS
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]