OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

oaxal-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [oaxal-comment] Missing relationships between standards in OAXALgraphics


Hi Rodolfo,

Thank you for your feedback. It is much appreciated.

OAXAL is a reference architecture that encourages the use of Open 
Standards, and is not a definitive proscription. With regards to the 
diagrams they represent the maximum integration of standards. Please 
note the text in section 2, just before section 2.1:

OAXAL allows for some variation in how the standards are used and 
integrated. OAXAL variants may not use all of the standards enumerated 
above.

The current reference model lists full interoperability of the 
enumerated standards of necessity. If you choose say not to include 
xml:tm, then your implementation and interaction of the standards will 
be different. The role of the reference architecture is to enumerate the 
full list of standards and explain their interaction. Any specific 
recommendations as to the exact implementations of variants are the 
domain of a 'best practices' document which will be produced subsequently.

Rodolfo M. Raya wrote:
> Images 2, 5 and 9 of the latest draft are incomplete. 
>   
OAXAL is a reference architecture that encourages the use of Open 
Standards, and is not a definitive proscription. With regards to the 
diagrams they represent the maximum integration of standards. Please 
note the text in section 2, just before section 2.1:

OAXAL allows for some variation in how the standards are used and 
integrated. OAXAL variants may not use all of the standards enumerated 
above.

The current reference model lists full interoperability of the 
enumerated standards of necessity. If you choose say not to include 
xml:tm, then your model will have different connections. It is not 
within the remit of the reference architecture to list all possible 
permutations. What it must do is to define the relationships of the 
enumerated standards which figures 2, 5 and 9 do. The same response 
applies to the items listed below.
> Source XML Content and XLIFF standard should be connected by an arrow.
> The relationship is established in section 3.3, where XLIFF files are
> generated from XML Content.
>
> SRX and XLIFF should also be connected by an arrow. The relationship is
> established in section 3.3, where SRX is used to segment XLIFF files.
>
> An arrow flowing from TMX to XLIFF is missing. TMX is the standard
> container for the TM data used when adding matches to XLIFF files.
>   
TMX does not input directly to xml:tm nor XLIFF. It is a potential 
product from them. TMX is used to exchange memories and not as a 
substitute for matching via a relational database.
> Notice that images 5 and 9 are identical and the only difference
> between them and image 2 is the background, where Unicode is presented.
> Unicode should be included in images 5 and 9 too.
>
>   
I wanted to give some more emphasis to the core Localization standards 
as well as trying not to repeat the same figure (although it appears 
twice as figure 5 and 9 as you rightly point out). Figure 5 and 9 are 
identical, but both serve to illustrate the case in point in both places 
where they appear and so are repeated. The first figure shows both 
Unicode and XML as the background for the other standards. Once 
established there was no need to repeat this in the subsequent figures, 
where the emphasis is on the interplay of the standards.

Best Regards and thank you again for your comments,

AZ
> Regards,
> Rodolfo
>   

-- 
email - azydron@xml-intl.com
smail - c/o Mr. A.Zydron
	PO Box 2167
        Gerrards Cross
        Bucks SL9 8XF
	United Kingdom
Mobile +(44) 7966 477 181
FAX    +(44) 1753 480 465
www - http://www.xml-intl.com

This message contains confidential information and is intended only for
the individual named.  If you are not the named addressee you may not
disseminate, distribute or copy this e-mail.  Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses.  The sender therefore does not
accept liability for any errors or omissions in the contents of this
message which arise as a result of e-mail transmission.  If verification
is required please request a hard-copy version. Unless explicitly stated
otherwise this message is provided for informational purposes only and
should not be construed as a solicitation or offer.


begin:vcard
fn;quoted-printable:Andrzej Zydro=C5=84
n;quoted-printable:Zydro=C5=84;Andrzej
email;internet:azydron@xml-intl.com
tel;work:+441494558106
tel;home:+441494532343
tel;cell:+447966477181
x-mozilla-html:FALSE
version:2.1
end:vcard



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]