Hi Rodolfo, What a great question. After a bit of thought, I kind of feel that extensibility means full extensibility, including elements from our own modules. In fact, I might go as far as to say including elements from our core (but I could be talked out of that one). So I leaning toward namespace ##any - and processContents'"skip" (but I could possibly be talked into lax). I am very interested in watching this thread to see what others think. It's tricky. Thanks, Bryan ________________________________________ From:
xliff@lists.oasis-open.org [
xliff@lists.oasis-open.org] On Behalf Of Rodolfo M. Raya [
rmraya@maxprograms.com] Sent: Tuesday, September 11, 2012 5:43 AM To:
xliff@lists.oasis-open.org Subject: [xliff] Extensions and modules Hi, Extension points in the core XML Schema are currently defined by allowing elements from “##other” namespaces. By default, “##other” includes the namespaces we use for our modules. Do we want the elements defined in XLIFF modules to be freely used as custom extensions? If the answer to the above question is “no”, then I’ll add the corresponding processing expectations to the specification document. Regards, Rodolfo -- Rodolfo M. Raya
rmraya@maxprograms.com Maxprograms
http://www.maxprograms.com