[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] Question about modules and namespaces
I agree. I think identifying the prefixes as best practice makes sense, in terms of human readability, interoperability between non-XML based agents (gasp).
But I think making it a conformance requirement (which nobody has proposed) would be heavy-handed.
From: firstname.lastname@example.org [mailto:email@example.com]
On Behalf Of Dr. David Filip
Ryan, the namespace prefix cannot be prescribed in XML, it's by definition arbitrary and what matters is the declaration, it's just a "model" prefix if u want.
What is normatively prescribed is the *fragid* prefix. And the fragid prefix is intentionally the same in each module as the model namespace prefix that is used for that module namespace throughout the spec for consistency and clarity reasons
On Fri, Aug 21, 2015 at 9:34 PM, Ryan King <firstname.lastname@example.org> wrote:
I’m curious about modules and namespace declarations. In the test-suite file posted at https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/test-suite/core/in-out/toRewrite1_out.xlf I see the namespace for <validation> declared on the element itself and therefore doesn’t use the “val” prefix:
This is equivalent to:
But it is also equivalent to
Is there a reason why modules are prescribed a specific prefix? After all, it is the namespace that makes the actual difference, not the prefix. I just want to make sure I am not missing some nuance here.