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


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

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

Subject: [xliff] More Notes from Today's meeting

More Notes from Today's meeting. These are very broad


We propose that we will be able to use XLIFF as a secondary namespace on an
XML document. As Gerard's proposal. There was a lot of enthusiasm for this

Formal Extensibility
1 Namespaces
1.1 Agreement this is a good thing
1.2 How
1.2.1 Namespaces within XLIFF document
1.2.2 Entension registry
	Extension point
	E.g. Someone sees cType XLIFF as not sufficient and put in cType
1.2.3 <xliff xmlns:ctype Novell="htttp://blahh">
2 Meeting agreed
2.1 Extend attribute values
2.2 Extend attribute
2.3 Extend elements with structure
2.4 Will revise current lists values and attributes
2.5 Spec to define which attributes are extensible
2.6 Define conformance issues in spec (business rule)
3 ISO 12620
4 Formal guidelines on extending XLIFF
5 Open Lists
5.1 Close some lists
5.2 Extend via private namespaces
5.3 All lists will not be closed
5.4 It is better to have a formal way of extension as it provides a method
for validation
5.5 Xliffdatatypes might be a namespace where the lists are externalised
6 Prop/ Context group
6.1 No structure data
6.2 Note defined
7 Eric's Proposal

Peter Reynolds, Software Development Manager, Berlitz GlobalNET
3, West Pier Business Campus, Dun Laoghaire, Co. Dublin, Ireland
Tel: +353-1-202-1280
Fax: +353-1- 202-1299
Web Site: http//www.berlitzglobalnet.com
"Don't just translate it, BerlitzIT" http//www.berlitzIT.com 

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

Powered by eList eXpress LLC