<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2"> </HEAD> <BODY> On Mon, 2005-02-21 at 10:02 +1000, Asgeir Frimannsson wrote: Hi, <BLOCKQUOTE TYPE=CITE> <PRE> The <prop> element is deprecated in XLIFF 1.1, in favour of custom namespace elements. </PRE> </BLOCKQUOTE> <PRE> </PRE> The XLIFF specification is contradictory. Section 2.5 deals with extensibility and says: <BLOCKQUOTE> At times, it may be useful to extend the set of information available in an XLIFF document by inserting constructs defined in various other XML vocabularies. You can add non-XLIFF elements, as well as attributes and attribute values. Adding elements and attributes use the namespace mechanism [<A HREF="file:///home/rmraya/Documents/xliff/xliff-specification.htm#refXMLNames">XML Names</A>]. Adding attribute values generally involves preceding the value by an "<TT>x-</TT>" (e.g. <TT><context context-type='x-for-engineers'></TT>). </BLOCKQUOTE> <BLOCKQUOTE> Although XLIFF offers this extensibility mechanism, in order to avoid a nimiety of information and increase interoperability between tools, it is strongly recommended to use XLIFF capabilities whenever possible, rather than to create non-standard user-defined elements or attributes. </BLOCKQUOTE> To me, the second paragraph means: <BLOCKQUOTE> We have deprecated xxx element/attribute in favor of custom namespaces, but as we don't know how to deal with the interoperability problems generated by using custom namespaces,  we strongly recommend you to use the elements/attributes  already available. </BLOCKQUOTE> Regards, Rodolfo <TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%"> <TR> <TD> -- Rodolfo M. Raya <<A HREF="mailto:rodolfo@heartsome.net">rodolfo@heartsome.net</A>> Heartsome Holdings Pte. Ltd. </TD> </TR> </TABLE> </BODY> </HTML>