trans-ws message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: XLIFF schema
- From: Stephen.Flinter@connectcgs.com
- To: trans-ws@lists.oasis-open.org
- Date: Fri, 15 Oct 2004 12:58:24 +0100
All,
I'm currently working on modifying the
WSTrans XML Schema document to take account of the count-group issue as
recently agreed.
My preference is to reference and import
the XLIFF schema document directly (as opposed to copying the relevant
element definitions into my schema doc). However, when I do that
I am getting errors from my XML schema validator that the XLIFF schema
is not valid. One potential cause of this is the <documentation>
elements that are used in the schema. For example:
<xsd:enumeration
value="paramnotes">
<xsd:annotation>
<xsd:documentation>
Indicates notes pertaining to the parameters in the
<source>.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
According to my understanding of the
XML schema the <documentation> element accepts any well formed XML
text. This includes straightforward text, and other XML markup, as
long as it's well formed.
The example above is NOT well formed,
as you have a <source> tag within the <documentation> element,
but no closing </source> tag.
To my mind you either have to supply
a closing </source> tag, or escape the angle brackets: <source>
(which is not really readable).
Is this an issue that the XLIFF group
is aware of? I haven't posted this message to the XLIFF group, as
I haven't really followed the discussions there, and don't want to make
an ass of myself if this has already been discussed (or my understanding
of XML schema is wrong :-).
BTW, I've been using this schema, as
referenced by the XLIFF homepage: http://www.oasis-open.org/committees/xliff/documents/xliff-core-1.1.xsd
Anyone know what the score is?
Steve
PS on a separate note, I feel that the
namespace that you've chosen for schema is not ideal:
urn:oasis:names:tc:xliff:document:1.1.
Most Java based libraries for generating
an object-based representation of an XML schema use the schema namespace
as the package name for the generated classes. The XLIFF namespace
does not translate to a valid Java (or C#) package name - the problem is
with the final 1.1.
If possible, I would suggest that you
consider changing the namespace to:
urn:oasis:names:tc:xliff:document:v1_1
---------------------------------------------
Stephen Flinter
Connect Global Solutions
[t] +353 (0)1 882 9038
[f] +353 (0)1 882 9050
[m] +353 87 798 1228
[e] stephen.flinter@connectcgs.com
[w] www.connectcgs.com
--------------------------------------------
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]