Schema xliff.xsd


schema location:  U:\src\TM\XLIFF\xliff.xsd
targetNamespace:  urn:oasis:names:tc:xliff:1.1
 
Elements  Groups  Complex types  Simple types  Attr. groups 
abstract-container  codeContent  annotatedElementType  mimeType  inlineClonableAttribute 
abstract-reference  referenceElements  bilingualReferenceContainerType  inlineMarkupAttributes 
alt-trans  textContent  codeContainerType  inlinePlaceholderAttributes 
author  emptyContainerType  languagePairAttributes 
base64-data  genericContainerType  mimeTypeAttributes 
bin-source  referenceContainerType  optionalIdAttribute 
bin-target  textContainerType  optionalRefAttribute 
bin-unit  requiredIdAttribute 
bpt  requiredRefAttribute 
bx  targetAttributes 
comment  textMimeTypeAttributes 
contact  transUnitAttributes 
context 
coord 
ept 
ex 
font 
g 
glossary 
group 
header 
html-content 
instructions 
it 
link 
mrk 
ph 
resource-context 
size-constraints 
skeleton 
source 
style-guide 
sub 
target 
text-content 
text-resource-context 
trans-unit 
translation-memory 
x 
xliff 


schema location:  http://www.w3.org/2001/xml.xsd
targetNamespace:  http://www.w3.org/XML/1998/namespace
 
Attr. groups 
specialAttrs 


element abstract-container
diagram
namespace urn:oasis:names:tc:xliff:1.1
used by
complexTypes genericContainerType referenceContainerType
annotation
documentation 
An abstract element for internal or external generic data.            
documentation 
The <abstract-container> element is an abstract element for internal orexternal data. Concrete elements must specify this element using asubstitutionGroup attribute in the XML Schema.            

element abstract-reference
diagram
namespace urn:oasis:names:tc:xliff:1.1
type xlf:referenceContainerType
children xlf:contact xlf:abstract-container
used by
group referenceElements
attributes
Name  Type  Use  Default  Fixed  Annotation
language  xs:language        
annotation
documentation 
An abstract element for reference material.            
documentation 
The <abstract-reference> element is an abstract element for referencematerial that may appear in the <header> after all the standardreference elements (<instructions>, <comment>, <style-guide>,<glossary>, and <translation-memory>. Concrete elements mustspecify this element using a substitutionGroup attribute in the XMLSchema.            

element alt-trans
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:annotatedElementType
children xlf:comment xlf:context xlf:resource-context xlf:source xlf:target
used by
element trans-unit
attributes
Name  Type  Use  Default  Fixed  Annotation
match-quality          
documentation 
The match quality of the <alt-trans> element.                            
documentation 
This value is tool specific and can be a score expressed in percentageor an arbitrary value (e.g. match-quality="high").                            
creation-tool  xs:string        
documentation 
The creation-tool attribute is used to specify the signature and version of thetool that created or modified the document.                            
documentation 
OPEN ISSUE: On alt-trans, I think we need to reevaluate creation-tool.What about putting some richer markup (a tool catalog) in the<header> of the xliff document and then allowing alt-trans elementsto refer to that catalog?  This would solve the problem of puttingtool/vendor/version information all over the place.                            
language  xs:language        
origin  xs:string        
documentation 
The origin attribute specifies where a translation match came from;for example, from a previous version of the same product, a differentproduct, a shared translation memory, etc.                            
documentation 
OPEN ISSUE: The meaning of this attribute is not self-evident. Can wecome up with a better name?                            
mime-type  xlf:mimeType        
documentation 
A text/* MIME type as defined in RFC 1341.                
documentation 
CHANGE FROM 1.0: This replaces the datatype attribute.                
annotation
documentation 
A possible translation match.            
documentation 
The <alt-trans> element contains a possible translation in a<target> along with optional context, notes, etc.            
documentation 
All child elements of <alt-trans> pertain to their sibling<target> element.            
documentation 
CHANGE FROM 1.0: removed crc            

element author
diagram
namespace urn:oasis:names:tc:xliff:1.1
annotation
documentation 
The <author> element contains information for the enclosingreference data element's author.            
documentation 
The <author> element is typically used within <instructions> and<comment> elements.            

element base64-data
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xs:base64Binary
attributes
Name  Type  Use  Default  Fixed  Annotation
mime-type  xlf:mimeType  required      
documentation 
The MIME type of the data as defined in RFC 1341.                
documentation 
CHANGE FROM 1.0: This replaces the form attribute on<internal-file>                
md5-checksum  xs:hexBinary        
documentation 
The MD5 checksum of the binary data.                
documentation 
CHANGE FROM 1.0: This replaces the crc attribute on<internal-file> and <external-file>                
annotation
documentation 
Base64 encoded inline binary data.            
documentation 
CHANGE FROM 1.0: This replaces one form of the <internal-file>element. Other binary encodings possible under 1.0 can be added bydeclaring other concrete elements for <internal-data>.            

element bin-source
diagram
namespace urn:oasis:names:tc:xliff:1.1
type xlf:genericContainerType
children xlf:abstract-container
used by
element bin-unit
annotation
documentation 
Binary source data.            
documentation 
The <bin-source> element is the container for the binary sourcedata.            

element bin-target
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:genericContainerType
children xlf:abstract-container
used by
element bin-unit
attributes
Name  Type  Use  Default  Fixed  Annotation
state  xs:NMTOKEN        
documentation 
The status of a particular translation in a <target> or<bin-target> element.                
documentation 
The values for the state attribute are as follows:- needs-translation = The item needs to be translated.- needs-review = The item needs to be reviewed.- needs-resizing = The item needs to be resized or reformatted.                
annotation
documentation 
Binary target data.            
documentation 
The <bin-target> element is the container for the translatedversion of the binary data.            
documentation 
CHANGE FROM 1.0: The <bin-target> element no longer has a mime-typeattribute as this is handled in xlf:genericContainerType.            

element bin-unit
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:annotatedElementType
children xlf:comment xlf:context xlf:resource-context xlf:bin-source xlf:bin-target xlf:trans-unit
used by
element group
attributes
Name  Type  Use  Default  Fixed  Annotation
id  xs:NMTOKEN  required      
documentation 
The id attribute is used as a unique identifier for the given element.                
documentation 
OPEN ISSUE: Are there rules about these that we need to capture,either in the schema or in documentation?  It's important that "diff"tools not get thrown off because one tool decides that it will changeall of the IDs produced by one vendor into a convention that it likesbetter.                
approved  xs:boolean    false    
documentation 
Indicates whether a translation is final.                
translate  xs:boolean    true    
documentation 
Indicates whether or not the text referred to should be translated.                
reformat  xs:boolean    true    
documentation 
Indicates whether the target can be formatted (size, font, etc.)                
annotation
documentation 
A binary unit.            
documentation 
The <bin-unit> element contains a binary object that may or may notbe translatable.            
documentation 
All child elements of <bin-unit> pertain to their sibling<source> element.            
documentation 
CHANGE FROM 1.0: The <bin-unit> element no longer has a mime-typeattribute as this is handled by <bin-source> and <bin-target>deriving from xlf:genericContainerType.            

element bpt
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:codeContainerType
children xlf:sub
used by
group textContent
attributes
Name  Type  Use  Default  Fixed  Annotation
md5-checksum  xs:hexBinary        
documentation 
The MD5 checksum of the format code.              
documentation 
CHANGE FROM 1.0: This replaces the crc attribute on <bpt>,<ept>, <it>, <ph>.              
id  xs:NMTOKEN  required      
documentation 
The id attribute is used as a unique identifier for the given element.                
documentation 
OPEN ISSUE: Are there rules about these that we need to capture,either in the schema or in documentation?  It's important that "diff"tools not get thrown off because one tool decides that it will changeall of the IDs produced by one vendor into a convention that it likesbetter.                
ref  xs:NMTOKEN  required      
documentation 
The ref attribute is used to link different elements that must berelated. For example, a begin to an end markup tag.                
content-type  xs:NMTOKEN        
documentation 
The content-type attribute specifies the content and the type ofresource or style of the data of a markup element.                
annotation
documentation 
A begin paired tag.            
documentation 
The <bpt> element is used to delimit the beginning of a pairedsequence of native codes. Each <bpt> has a corresponding <ept>element within the segment. When possible, the content-type allows you tospecify what kind of attribute the placeholder represents. A list ofpreferred values for the content-type attribute is available.            

element bx
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:emptyContainerType
used by
group textContent
attributes
Name  Type  Use  Default  Fixed  Annotation
id  xs:NMTOKEN  required      
documentation 
The id attribute is used as a unique identifier for the given element.                
documentation 
OPEN ISSUE: Are there rules about these that we need to capture,either in the schema or in documentation?  It's important that "diff"tools not get thrown off because one tool decides that it will changeall of the IDs produced by one vendor into a convention that it likesbetter.                
ref  xs:NMTOKEN        
documentation 
The ref attribute is used to link different elements that may berelated. For example, a reference to its definition, or paragraphsbelonging to the same group, etc.                
content-type  xs:NMTOKEN        
documentation 
The content-type attribute specifies the content and the type ofresource or style of the data of a markup element.                
clonable  xs:boolean    true    
documentation 
This indicates that a copy of the given inline element can be made andplaced in the <target>.                
annotation
documentation 
A begin paired placeholder.            
documentation 
The <bx/> element is used to replace a beginning paired code of theoriginal document. It must be used for paired codes that do notfollow XML well-formedness rules (i.e. no overlapping elements). Ifthe paired codes follow that rule, it is strongly recommended that the<g> element is used because it simplifies processing. The <bx/>element must be followed by a matching <ex/> element. Thesepaired elements are related via their rid attributes. When possible,the content-type allows you to specify what kind of attribute the placeholderrepresents. A list of preferred values for the content-type attribute isavailable.            
documentation 
OPEN ISSUE Should we keep the <bx> and <ex> elements? Why notsimply require broken markup to be escaped, either with entities or inCDATA blocks?            

element comment
diagram
namespace urn:oasis:names:tc:xliff:1.1
type xlf:referenceContainerType
children xlf:contact xlf:abstract-container
used by
complexType annotatedElementType
group referenceElements
attributes
Name  Type  Use  Default  Fixed  Annotation
language  xs:language        
annotation
documentation 
The <comment> element is used to add localisation-related comments.            
documentation 
The content of <comment> may be comments from the translator aboutthe translation, or any comment from anyone involved in processing theXLIFF document.            

element contact
diagram
namespace urn:oasis:names:tc:xliff:1.1
used by
complexType referenceContainerType
attributes
Name  Type  Use  Default  Fixed  Annotation
name  xs:string        
email  xs:string        
phone  xs:string        
annotation
documentation 
The <contact> element contains contact information for theenclosing reference data element.            
documentation 
OPEN ISSUE: Should the attributes be sub-elements instead?            
documentation 
OPEN ISSUE: Is there some OASIS standard for contact information?            
documentation 
OPEN ISSUE: Restrict type of attributes.            

element context
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xs:string
used by
complexType annotatedElementType
attributes
Name  Type  Use  Default  Fixed  Annotation
context-type  xs:NMTOKEN  required      
documentation 
The context-type attribute specifies the context and the type ofresource or style of the data of a given element. For example, todefine if it is a label, or a menu item in the case of resource-typedata, or the style in the case of document-related data.                            
documentation 
The values for the context-type attribute of the <context> elementare as follows:- Database- Element- ElementTitle- Record- RecordTitle                            
match-required  xs:boolean    false    
documentation 
Indicates that any <alt-trans> element of the parent<trans-unit> must have the same <context> as the<trans-unit>.                            
documentation 
CHANGE FROM 1.0: renamed attribute: match-mandatory -> match-required                            
annotation
documentation 
Translation Context.            
documentation 
The <context> element describes the context of a <source> withina <group>, <trans-unit>, <bin-unit>, or a <alt-trans>. Thepurpose of this context information is to allow certain pieces of textto have different translations depending on where they came from. Thetranslation of a piece of text may differ if it is a web form or adialog or an Oracle form or a Lotus form for example. This informationis thus required by a translator when working on the document. Likewise,the information may be used by any tool proposing to automaticallyleverage the text successfully.            
documentation 
Because the <context> element may occur at a very high level, adefault context can be established for all <trans-unit> elementswithin a document. This default can be overridden at many subsequentlevels.            
documentation 
CHANGE FROM 1.0: removed crc            
documentation 
OPEN ISSUE: <context context-type="foobar"> might be turned into atype hierarchy so that we can distinguish between the kinds of typesalluded to in the documentation and so that people can define theirown types in another namespace.  For example:<interface-context>dialog</interface-context> and<linguistic-context>legal</linguistic-context> Is this anybetter than just putting the type into an attribute? Perhaps, ifdividing things up in this way means that we can then enumerate afixed list of values for certain contexts.  That is: I doubt that wecan enumerate everything in <linguistic-context> but we canpossibly agree on values for <interface-context> so that we getconsistency on things like "frame" "window" "dialog" and so forth.            

element coord
diagram
namespace urn:oasis:names:tc:xliff:1.1
used by
element resource-context
attributes
Name  Type  Use  Default  Fixed  Annotation
x  xs:integer        
y  xs:integer        
cx  xs:positiveInteger        
cy  xs:positiveInteger        
annotation
documentation 
The coord attribute specifies the x, y, cx and cy coordinates of the agiven element.            
documentation 
The cx and cy values must represent the width and the height (like inWindows resources). The extraction and merging tools must make theright conversion if the original format uses a top-left/bottom-rightcoordinate system.            

element ept
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:codeContainerType
children xlf:sub
used by
group textContent
attributes
Name  Type  Use  Default  Fixed  Annotation
md5-checksum  xs:hexBinary        
documentation 
The MD5 checksum of the format code.              
documentation 
CHANGE FROM 1.0: This replaces the crc attribute on <bpt>,<ept>, <it>, <ph>.              
id  xs:NMTOKEN  required      
documentation 
The id attribute is used as a unique identifier for the given element.                
documentation 
OPEN ISSUE: Are there rules about these that we need to capture,either in the schema or in documentation?  It's important that "diff"tools not get thrown off because one tool decides that it will changeall of the IDs produced by one vendor into a convention that it likesbetter.                
ref  xs:NMTOKEN  required      
documentation 
The ref attribute is used to link different elements that must berelated. For example, a begin to an end markup tag.                
annotation
documentation 
An end paired tag.            
documentation 
The <ept> element is used to delimit the end of a paired sequenceof native codes. Each <ept> has a corresponding <bpt> elementwithin the segment.            

element ex
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:emptyContainerType
used by
group textContent
attributes
Name  Type  Use  Default  Fixed  Annotation
id  xs:NMTOKEN  required      
documentation 
The id attribute is used as a unique identifier for the given element.                
documentation 
OPEN ISSUE: Are there rules about these that we need to capture,either in the schema or in documentation?  It's important that "diff"tools not get thrown off because one tool decides that it will changeall of the IDs produced by one vendor into a convention that it likesbetter.                
ref  xs:NMTOKEN        
documentation 
The ref attribute is used to link different elements that may berelated. For example, a reference to its definition, or paragraphsbelonging to the same group, etc.                
annotation
documentation 
An end paired placeholder.            
documentation 
The <ex/> element is used to replace a beginning paired code of theoriginal document. It must be used for paired codes that do notfollow XML well-formedness rules (i.e. no overlapping elements). Ifthe paired codes follow that rule, it is strongly recommended that the<g> element is used because it simplifies processing. The <ex/>element must be preceded by a matching <bx/> element. Thesepaired elements are related via their rid attributes.            

element font
diagram
namespace urn:oasis:names:tc:xliff:1.1
used by
elements size-constraints text-resource-context
attributes
Name  Type  Use  Default  Fixed  Annotation
name  xs:NMTOKEN        
size  xs:integer        
weight  xs:NMTOKEN        
annotation
documentation 
The font attribute specifies the font name, size, and weight of thetext for a given element.            
documentation 
The font attribute would generally be used for resource-type data:change of font in document-type data can be marked with the <g>element.            

element g
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:textContainerType
children xlf:g xlf:bpt xlf:ept xlf:ph xlf:it xlf:mrk xlf:x xlf:bx xlf:ex
used by
group textContent
attributes
Name  Type  Use  Default  Fixed  Annotation
id  xs:NMTOKEN  required      
documentation 
The id attribute is used as a unique identifier for the given element.                
documentation 
OPEN ISSUE: Are there rules about these that we need to capture,either in the schema or in documentation?  It's important that "diff"tools not get thrown off because one tool decides that it will changeall of the IDs produced by one vendor into a convention that it likesbetter.                
content-type  xs:NMTOKEN        
documentation 
The content-type attribute specifies the content and the type ofresource or style of the data of a markup element.                
clonable  xs:boolean    true    
documentation 
This indicates that a copy of the given inline element can be made andplaced in the <target>.                
annotation
documentation 
A generic group placeholder.            
documentation 
The <g> element is used to replace any inline code of the originaldocument that has a beginning and an end and can be moved within itsparent structural element. When possible, the content-type allows you tospecify what kind of attribute the placeholder represents. A list ofpreferred values for the content-type attribute is available.  A <g>element can contain another <g> element. In this case, if theembedded group has an id attribute, it must never be moved outsideof its parent group.            

element glossary
diagram
namespace urn:oasis:names:tc:xliff:1.1
type xlf:bilingualReferenceContainerType
children xlf:contact xlf:abstract-container
used by
group referenceElements
attributes
Name  Type  Use  Default  Fixed  Annotation
language  xs:language        
source-language  xs:language        
target-language  xs:language        
annotation
documentation 
The <glossary> element contains the glossary or the location of theglossary.            

element group
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:annotatedElementType
children xlf:comment xlf:context xlf:resource-context xlf:group xlf:trans-unit xlf:bin-unit
used by
elements group xliff
attributes
Name  Type  Use  Default  Fixed  Annotation
id  xs:NMTOKEN        
documentation 
The id attribute is used as a unique identifier for the given element.                
mime-type  xlf:mimeType        
documentation 
A text/* MIME type as defined in RFC 1341.                
documentation 
CHANGE FROM 1.0: This replaces the datatype attribute.                
annotation
documentation 
A group of translation units.            
documentation 
The <group> element specifies a set of elements that must beprocessed together. For example: all the items of a menu, etc. Notethat a <group> element can contain other <group> elements.            
documentation 
All <context>, and <comment> elements pertainto the subsequent elements in the tree but can be overridden within achild element.            
documentation 
A group can be linked to by an inner markup elements (eg. <g>) viathe id attribute.            

element header
diagram
namespace urn:oasis:names:tc:xliff:1.1
children xlf:skeleton xlf:instructions xlf:comment xlf:style-guide xlf:glossary xlf:translation-memory xlf:abstract-reference
used by
element xliff
attributes
Name  Type  Use  Default  Fixed  Annotation
uri  xs:anyURI  required      
documentation 
A URI to the original document from which the contents of the <content>element has been extracted.                    
documentation 
CHANGE FROM 1.0: Replaced original with uri to define concretedatatype and to introduce a more descriptive name. URIs permit abroader range of identifiers than simple filenames (eg database ornetwork resources).  Finally, using URIs solves problems withoperating system dependent pathnames.                    
source-language  xs:language  required      
documentation 
The language for the <source> elements in the given <content>.                    
mime-type  xlf:mimeType  required      
documentation 
The MIME type of the data as defined in RFC 1341.                
documentation 
CHANGE FROM 1.0: This replaces the form attribute on<internal-file>                
md5-checksum  xs:hexBinary        
documentation 
The MD5 checksum of the binary data.                
documentation 
CHANGE FROM 1.0: This replaces the crc attribute on<internal-file> and <external-file>                
content-creation-tool  xs:string        
documentation 
The tool that created the original content.                    
documentation 
CHANGE FROM 1.0: Changed tool attribute to content-creation-tool.                    
content-creation-tool-version  xs:string        
documentation 
The version of the tool that created the original content.                    
content-creation-date  xs:date        
documentation 
The date the original content was created.                    
documentation 
CHANGE FROM 1.0: Changed date attribute to content-creation-date.                    
category  xs:string        
documentation 
This gives domain information on the subject of what is beingtranslated.                    
target-language  xs:language        
documentation 
The language for the <target> elements in the given <content>                    
product-name  xs:string        
documentation 
The name of the product which uses this document.                    
documentation 
OPEN ISSUE: Define "uses"                    
product-version  xs:string        
documentation 
The version of the product which uses this document.                    
build-num  xs:string        
documentation 
The build number of version of the product or application thelocalizable material is for.                    
annotation
documentation 
Content header            
documentation 
The <header> element contains data relating to the <xliff> element.            
documentation 
OPEN ISSUE: Instead of having the uri, mime-type, source andtarget-language attributes we could define an original-documentelement of type bilingualReferenceContainerType. This would appear inthe header and would support inlined data as well as linked externalreferences.            

element html-content
diagram
namespace urn:oasis:names:tc:xliff:1.1
attributes
Name  Type  Use  Default  Fixed  Annotation
mime-type  xlf:mimeType      text/html  
language  xs:language        
annotation
documentation 
Inline XHTML container.            

element instructions
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:referenceContainerType
children xlf:contact xlf:abstract-container
used by
group referenceElements
attributes
Name  Type  Use  Default  Fixed  Annotation
language  xs:language        
priority  xs:integer    1    
documentation 
A priority between 1 and 10, 1 being the highest priority.                            
annotation
documentation 
The <instruction> element is used to add localisation-relatedinstructions.            
documentation 
The content of <instructions> may include instructions fromdevelopers about how to handle the <source>.            

element it
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:codeContainerType
children xlf:sub
used by
group textContent
attributes
Name  Type  Use  Default  Fixed  Annotation
md5-checksum  xs:hexBinary        
documentation 
The MD5 checksum of the format code.              
documentation 
CHANGE FROM 1.0: This replaces the crc attribute on <bpt>,<ept>, <it>, <ph>.              
tag-position  xs:NMTOKEN  required      
documentation 
Indicates whether an isolated tag <it> is a beginning or and endingtag.                            
documentation 
CHANGE FROM 1.0: renamed attribute: pos -> tag-position                            
documentation 
CHANGE FROM 1.0: Changed values to begin/end for consistency withpaired mark up element names.                            
id  xs:NMTOKEN  required      
documentation 
The id attribute is used as a unique identifier for the given element.                
documentation 
OPEN ISSUE: Are there rules about these that we need to capture,either in the schema or in documentation?  It's important that "diff"tools not get thrown off because one tool decides that it will changeall of the IDs produced by one vendor into a convention that it likesbetter.                
ref  xs:NMTOKEN        
documentation 
The ref attribute is used to link different elements that may berelated. For example, a reference to its definition, or paragraphsbelonging to the same group, etc.                
content-type  xs:NMTOKEN        
documentation 
The content-type attribute specifies the content and the type ofresource or style of the data of a markup element.                
annotation
documentation 
An isolated tag.            
documentation 
The <it> element is used to delimit a beginning/ending sequence ofnative codes that does not have its corresponding ending/beginningwithin the segment. When possible, the content-type allows you to specifywhat kind of attribute the placeholder represents. A list of preferredvalues for the content-type attribute is available.            

element link
diagram
namespace urn:oasis:names:tc:xliff:1.1
attributes
Name  Type  Use  Default  Fixed  Annotation
href  xs:anyURI  required      
documentation 
The location of the file or the URL for a <link> element.                    
mime-type  xlf:mimeType  required      
documentation 
The MIME type of the data as defined in RFC 1341.                
documentation 
CHANGE FROM 1.0: This replaces the form attribute on<internal-file>                
md5-checksum  xs:hexBinary        
documentation 
The MD5 checksum of the binary data.                
documentation 
CHANGE FROM 1.0: This replaces the crc attribute on<internal-file> and <external-file>                
annotation
documentation 
Pointer to external (outside of this XML document) reference data.            

element mrk
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:textContainerType
children xlf:g xlf:bpt xlf:ept xlf:ph xlf:it xlf:mrk xlf:x xlf:bx xlf:ex
used by
group textContent
attributes
Name  Type  Use  Default  Fixed  Annotation
marker-type  xs:NMTOKEN  required      
documentation 
The marker-type attribute specifies what an <mrk> element isdefining within the content of a <source> or <target> element.                            
id  xs:NMTOKEN        
documentation 
The id attribute is used as a unique identifier for the given element.                
comment  xs:string        
documentation 
An alpha-numeric comment in a tag.                            
annotation
documentation 
An inline marker.            
documentation 
The <mrk> element delimits a section of text that has specialmeaning, such as a terminological unit, a proper name, an item thatmust not be modified, etc. It can be used for various processingtasks. For example, to indicate to a Machine Translation tool propernames that must not be translated; for terminology verification, tomark suspect expressions after a grammar checking. The <mrk>element is usually not generated by the extraction tool and it is notpart of the tags used to merge the XLIFF document back into its original format. A list of preferred values for the mtype attributeis available.            
documentation 
OPEN ISSUE: Perhaps the <mrk> element should be dropped.  The 1.0spec says that it's not really used by XLIFF tools, so this should bepushed out so that another namespace (and another standard) can defineit more rigorously.            

element ph
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:codeContainerType
children xlf:sub
used by
group textContent
attributes
Name  Type  Use  Default  Fixed  Annotation
md5-checksum  xs:hexBinary        
documentation 
The MD5 checksum of the format code.              
documentation 
CHANGE FROM 1.0: This replaces the crc attribute on <bpt>,<ept>, <it>, <ph>.              
id  xs:NMTOKEN  required      
documentation 
The id attribute is used as a unique identifier for the given element.                
documentation 
OPEN ISSUE: Are there rules about these that we need to capture,either in the schema or in documentation?  It's important that "diff"tools not get thrown off because one tool decides that it will changeall of the IDs produced by one vendor into a convention that it likesbetter.                
content-type  xs:NMTOKEN        
documentation 
The content-type attribute specifies the content and the type ofresource or style of the data of a placeholder element.                
tag-association  xs:NMTOKEN        
documentation 
Indicates the association of a <ph> element with the text prior orafter.                            
documentation 
CHANGE FROM 1.0: renamed attribute: assoc -> tag-association                            
annotation
documentation 
A placeholder.            
documentation 
The <ph> element is used to delimit a sequence of nativestand-alone codes in the segment. When possible, the content-type allows youto specify what kind of attribute the placeholder represents. A listof preferred values for the content-type attribute is available.            

element resource-context
diagram
namespace urn:oasis:names:tc:xliff:1.1
children xlf:coord
used by
complexType annotatedElementType
attributes
Name  Type  Use  Default  Fixed  Annotation
type  xs:NMTOKEN        
documentation 
Resource type - Indicates the type of the container element.                    
documentation 
The values for the restype attribute are as follows:- button = Button in UI.- caption = Title in UI, caption in documentation, alternate text,  etc.- checkbox = Check box in UI.- cell = Text in a table cell.- dialog = Dialog box in UI.- file = Filename, path.- fn = Footnote.- footer = Footer text.- font = Font name.- frame = Frame or window, or any generic group of components.- header = Header text.- heading = Title or header-type segment.- keywords = List of keywords, enumeration within a paragraph, etc.- label = Static text, label in UI, etc.- listitem = Paragraph in a list, entry in a list box, etc.- menu = Menu.- menuitem = Entry in a UI menu.- message = Prompt, error or warning message.- radio = Radio button in UI.- shortcut = Windows accelerators, shortcuts in resource or property  files.- string = Generic text from source code, string table, etc.- var = Variable.                    
name  xs:NMTOKEN        
documentation 
Resource name - Resource name or identifier of a item.                    
documentation 
For example: the key in the key/value pair in a Java properties file,the ID of a string in a Windows string table, the index value of anentry in a database table, etc.                    
help-id  xs:NMTOKEN        
documentation 
Help ID - The help-id attribute stores the help identifier of an item.                    
documentation 
For example, in Windows resources it corresponds to the Help IDparameter of a control.                    
menu  xs:string        
documentation 
Menu - The menu attribute stores the menu property of an item.                    
menu-option  xs:string        
documentation 
Menu option - The menu-option attribute stores the option data of acontrol.                    
menu-name  xs:string        
documentation 
Menu name - The menu-name attribute stores the menu name of a control.                    
annotation
documentation 
Context related to Windows resource data.            
documentation 
OPEN ISSUE: Should these Windows specific attributes be taken out ofthe core XLIFF schema and be defined as an extension in a separatenamespace?            

element size-constraints
diagram
namespace urn:oasis:names:tc:xliff:1.1
children xlf:font
used by
element trans-unit
attributes
Name  Type  Use  Default  Fixed  Annotation
size-unit  xs:string        
documentation 
Unit of size - The size-unit attribute specifies the units of measureused in the maxheight, minheight, maxwidth, and minwidth attributes.                    
documentation 
The recommended values for the size-unit attribute are as follows:- pixel = Pixel.- byte = 8-bit byte.- char = Unicode character.                    
documentation 
OPEN ISSUE: use schema type system rather than size-unit which hasproblems - can't apply to more than one of min/max width. Also can'tspecify multiple constraints on same dimension - eg maxwidth = 500pixels and maxwidth = 40 characters. If we do decide to retain thisattribute we need to enumerate and close the value list.                                            
maxwidth  xs:positiveInteger        
documentation 
Maximum width - The maximum width for the <target> of a<trans-unit>. This could be interpreted as lines, pixels, or anyother relevant unit. The unit is determined by the size-unitattribute, which defaults to pixel.                    
minwidth  xs:positiveInteger        
documentation 
Minimum width - The minimum width for the <target> of a<trans-unit>. This could be interpreted as lines, pixels, or anyother relevant unit. The unit is determined by the size-unitattribute, which defaults to pixel.                    
maxheight  xs:positiveInteger        
documentation 
Maximum height - The maximum height for the <target> of a<trans-unit>. This could be interpreted as lines, pixels, or anyother relevant unit. The unit is determined by the size-unitattribute, which defaults to pixel.                    
minheight  xs:positiveInteger        
documentation 
Minimum height - The minimum height for the <target> of a<trans-unit>. This could be interpreted as lines, pixels, or anyother relevant unit. The unit is determined by the size-unitattribute, which defaults to pixel.                    
maxbytes  xs:positiveInteger        
documentation 
Maximum bytes - The maximum number of bytes for the <target> of a<trans-unit>.  The verification of whether the relevant textrespects this requirement must be done using the encoding andline-break type of the final target environment.                    
minbytes  xs:positiveInteger        
documentation 
Minimum bytes - The minimum number of bytes for the <target> of a<trans-unit>.  The verification of whether the relevant textrespects this requirement must be done using the encoding andline-break type of the final target environment.                    
annotation
documentation 
Size constraints.            
documentation 
OPEN ISSUE: Should these attributes be taken out of the core XLIFFschema and be defined as an extension in a separate namespace?            

element skeleton
diagram
namespace urn:oasis:names:tc:xliff:1.1
type xlf:genericContainerType
children xlf:abstract-container
used by
element header
annotation
documentation 
The <skeleton> element contains the skeleton or the location of theskeleton.            

element source
diagram
namespace urn:oasis:names:tc:xliff:1.1
children xlf:g xlf:bpt xlf:ept xlf:ph xlf:it xlf:mrk xlf:x xlf:bx xlf:ex
used by
elements alt-trans trans-unit
attributes
Name  Type  Use  Default  Fixed  Annotation
language  xs:language        
annotation
documentation 
A source text segment.            
documentation 
The <source> element is used to delimit a unit of text that couldbe a paragraph, a title, a menu item, a caption, etc.            

element style-guide
diagram
namespace urn:oasis:names:tc:xliff:1.1
type xlf:bilingualReferenceContainerType
children xlf:contact xlf:abstract-container
used by
group referenceElements
attributes
Name  Type  Use  Default  Fixed  Annotation
language  xs:language        
source-language  xs:language        
target-language  xs:language        
annotation
documentation 
The <style-guide> element contains the style guide or the locationof the style guide.            

element sub
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:textContainerType
children xlf:g xlf:bpt xlf:ept xlf:ph xlf:it xlf:mrk xlf:x xlf:bx xlf:ex
used by
group codeContent
attributes
Name  Type  Use  Default  Fixed  Annotation
mime-type  xlf:mimeType        
documentation 
A text/* MIME type as defined in RFC 1341.                
documentation 
CHANGE FROM 1.0: This replaces the datatype attribute.                
content-type  xs:NMTOKEN        
documentation 
The content-type attribute specifies the content and the type ofresource or style of the data of a markup element.                
annotation
documentation 
Some sub-flow text.            
documentation 
The <sub> element is used to delimit sub-flow text inside asequence of native code, for example: the definition of a footnote orthe text of a title attribute in a HTML <a> element. When possible,the content-type allows you to specify what kind of attribute the placeholderrepresents. Lists of preferred values for the content-type and datatypeattributes are available.            

element target
diagram
namespace urn:oasis:names:tc:xliff:1.1
children xlf:g xlf:bpt xlf:ept xlf:ph xlf:it xlf:mrk xlf:x xlf:bx xlf:ex
used by
elements alt-trans trans-unit
attributes
Name  Type  Use  Default  Fixed  Annotation
language  xs:language        
state  xs:NMTOKEN        
documentation 
The status of a particular translation in a <target> or<bin-target> element.                
documentation 
The values for the state attribute are as follows:- needs-translation = The item needs to be translated.- needs-review = The item needs to be reviewed.- needs-resizing = The item needs to be resized or reformatted.                
annotation
documentation 
A target text segment.            
documentation 
The <target> element is used to delimit a unit of text. A paragraphin XLIFF does not necessarily correspond to a "paragraph" in aword-processor. It's simply a unit of text that could be a paragraph,a title, a menu item, a caption, etc. A list of preferred values forthe restype attribute is available.            

element text-content
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xs:string
attributes
Name  Type  Use  Default  Fixed  Annotation
mime-type  xlf:mimeType      text/plain  
language  xs:language        
annotation
documentation 
Inline plain text container.            

element text-resource-context
diagram
namespace urn:oasis:names:tc:xliff:1.1
children xlf:font
attributes
Name  Type  Use  Default  Fixed  Annotation
css-style  xs:string        
documentation 
The css-style attribute allows any valid CSS style statement to bespecified.                    
style  xs:NMTOKEN        
documentation 
The resource style of a control. For example, in Windows resources itcorresponds to the STYLE statement.                    
exstyle  xs:NMTOKEN        
documentation 
The exstyle attribute stores the extended style of a control. Forexample, in Windows resources it corresponds to the EXSTYLE statement.                    
annotation
documentation 
Context related to Windows resource text.            
documentation 
OPEN ISSUE: Should these Windows specific attributes be taken out ofthe core XLIFF schema and be defined as an extension in a separatenamespace?            

element trans-unit
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:annotatedElementType
children xlf:comment xlf:context xlf:resource-context xlf:size-constraints xlf:source xlf:target xlf:alt-trans
used by
elements bin-unit group
attributes
Name  Type  Use  Default  Fixed  Annotation
id  xs:NMTOKEN  required      
documentation 
The id attribute is used as a unique identifier for the given element.                
documentation 
OPEN ISSUE: Are there rules about these that we need to capture,either in the schema or in documentation?  It's important that "diff"tools not get thrown off because one tool decides that it will changeall of the IDs produced by one vendor into a convention that it likesbetter.                
approved  xs:boolean    false    
documentation 
Indicates whether a translation is final.                
translate  xs:boolean    true    
documentation 
Indicates whether or not the text referred to should be translated.                
reformat  xs:boolean    true    
documentation 
Indicates whether the target can be formatted (size, font, etc.)                
mime-type  xlf:mimeType        
documentation 
A text/* MIME type as defined in RFC 1341.                
documentation 
CHANGE FROM 1.0: This replaces the datatype attribute.                
charclass  xs:string        
documentation 
This indicates that a translation is restricted to a subset ofcharacters (e.g. ASCII only, Katakana only, uppercase only, etc.).                            
documentation 
OPEN ISSUE: Enumerate and close possible values.                            
annotation
documentation 
A translation unit (source/target text).            
documentation 
The <trans-unit> elements contains a <source>, <target> andassociated elements. Lists of recommended values for the datatype,restype, and size-unit attributes are available.            
documentation 
All child elements of <trans-unit> pertain to their sibling<source> element.            

element translation-memory
diagram
namespace urn:oasis:names:tc:xliff:1.1
type xlf:bilingualReferenceContainerType
children xlf:contact xlf:abstract-container
used by
group referenceElements
attributes
Name  Type  Use  Default  Fixed  Annotation
language  xs:language        
source-language  xs:language        
target-language  xs:language        
annotation
documentation 
The <translation-memory> element contains the translation memory orthe location of the translation memory.            

element x
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:emptyContainerType
used by
group textContent
attributes
Name  Type  Use  Default  Fixed  Annotation
id  xs:NMTOKEN  required      
documentation 
The id attribute is used as a unique identifier for the given element.                
documentation 
OPEN ISSUE: Are there rules about these that we need to capture,either in the schema or in documentation?  It's important that "diff"tools not get thrown off because one tool decides that it will changeall of the IDs produced by one vendor into a convention that it likesbetter.                
content-type  xs:NMTOKEN        
documentation 
The content-type attribute specifies the content and the type ofresource or style of the data of a placeholder element.                
clonable  xs:boolean    true    
documentation 
This indicates that a copy of the given inline element can be made andplaced in the <target>.                
annotation
documentation 
A generic placeholder.            
documentation 
The <x/> element is used to replace any code of the originaldocument. When possible, the content-type allows you to specify what kind ofattribute the placeholder represents. A list of preferred values forthe content-type attribute is available.            
documentation 
OPEN ISSUE: What's difference between the <ph> and <x> elements?            

element xliff
diagram
namespace urn:oasis:names:tc:xliff:1.1
children xlf:header xlf:group
attributes
Name  Type  Use  Default  Fixed  Annotation
version  xs:string      1.1  
documentation 
The XLIFF version number.                    
language  xs:language        
annotation
documentation 
A single piece of XLIFF extracted content.             
documentation 
See the XLIFF envelope specification for recommendations on how tosend multiple pieces of related content.            

group codeContent
diagram
namespace urn:oasis:names:tc:xliff:1.1
children xlf:sub
used by
complexType codeContainerType
annotation
documentation 
The elements that can appear within inline element which contain code.            

group referenceElements
diagram
namespace urn:oasis:names:tc:xliff:1.1
children xlf:instructions xlf:comment xlf:style-guide xlf:glossary xlf:translation-memory xlf:abstract-reference
used by
element header
annotation
documentation 
Standard reference elements.            

group textContent
diagram
namespace urn:oasis:names:tc:xliff:1.1
children xlf:g xlf:bpt xlf:ept xlf:ph xlf:it xlf:mrk xlf:x xlf:bx xlf:ex
used by
elements source target
complexType textContainerType
annotation
documentation 
The elements that can appear either within the <source> or <target>elements, or within inline element which contains text.            
documentation 
They enclose or replace any formatting or control codes thatis not text, but resides within the text unit.            

complexType annotatedElementType
diagram
namespace urn:oasis:names:tc:xliff:1.1
children xlf:comment xlf:context xlf:resource-context
used by
elements alt-trans bin-unit group trans-unit
annotation
documentation 
Elements which allow the standard note and context elements.            
documentation 
CHANGE FROM 1.0: In the 1.0 DTD notes (<instructions> or<comment>) were allowed in this content model. Now only<comment> are allowed and all <instructions> must now appear inthe <header>.            

complexType bilingualReferenceContainerType
diagram
namespace urn:oasis:names:tc:xliff:1.1
type extension of xlf:referenceContainerType
children xlf:contact xlf:abstract-container
used by
elements glossary style-guide translation-memory
attributes
Name  Type  Use  Default  Fixed  Annotation
language  xs:language        
source-language  xs:language        
target-language  xs:language        
annotation
documentation 
A type for an element containing internal or externalbilingual reference data.            

complexType codeContainerType
diagram
namespace urn:oasis:names:tc:xliff:1.1
children xlf:sub
used by
elements bpt ept it ph
attributes
Name  Type  Use  Default  Fixed  Annotation
md5-checksum  xs:hexBinary        
documentation 
The MD5 checksum of the format code.              
documentation 
CHANGE FROM 1.0: This replaces the crc attribute on <bpt>,<ept>, <it>, <ph>.              
annotation
documentation 
In-line elements which enclose code.         

complexType emptyContainerType
diagram
namespace urn:oasis:names:tc:xliff:1.1
used by
elements bx ex x
attributes
Name  Type  Use  Default  Fixed  Annotation
annotation
documentation 
In-line elements with no content.        

complexType genericContainerType
diagram
namespace urn:oasis:names:tc:xliff:1.1
children xlf:abstract-container
used by
elements bin-source bin-target skeleton
annotation
documentation 
A type for an element containing internal or external data.            

complexType referenceContainerType
diagram
namespace urn:oasis:names:tc:xliff:1.1
children xlf:contact xlf:abstract-container
used by
elements abstract-reference comment instructions
complexType bilingualReferenceContainerType
attributes
Name  Type  Use  Default  Fixed  Annotation
language  xs:language        
annotation
documentation 
A type for an element containing internal or externalreference data.            

complexType textContainerType
diagram
namespace urn:oasis:names:tc:xliff:1.1
children xlf:g xlf:bpt xlf:ept xlf:ph xlf:it xlf:mrk xlf:x xlf:bx xlf:ex
used by
elements g mrk sub
attributes
Name  Type  Use  Default  Fixed  Annotation
annotation
documentation 
In-line elements which enclose text.         

simpleType mimeType
namespace urn:oasis:names:tc:xliff:1.1
type restriction of xs:token
used by
attributes html-content/@mime-type text-content/@mime-type mimeTypeAttributes/@mime-type
attributeGroup textMimeTypeAttributes
facets
pattern (text|image|audio|video|application|multipart)/([a-z0-9\-])+
annotation
documentation 
A simple type representing MIME types as defined in RFC 1341.            

attributeGroup inlineClonableAttribute
namespace urn:oasis:names:tc:xliff:1.1
used by
elements bx g x
attributes
Name  Type  Use  Default  Fixed  Annotation
clonable  xs:boolean    true    
documentation 
This indicates that a copy of the given inline element can be made andplaced in the <target>.                

attributeGroup inlineMarkupAttributes
namespace urn:oasis:names:tc:xliff:1.1
used by
elements bpt bx g it sub
attributes
Name  Type  Use  Default  Fixed  Annotation
content-type  xs:NMTOKEN        
documentation 
The content-type attribute specifies the content and the type ofresource or style of the data of a markup element.                
annotation
documentation 
Attributes applicable to inline markup elements.           

attributeGroup inlinePlaceholderAttributes
namespace urn:oasis:names:tc:xliff:1.1
used by
elements ph x
attributes
Name  Type  Use  Default  Fixed  Annotation
content-type  xs:NMTOKEN        
documentation 
The content-type attribute specifies the content and the type ofresource or style of the data of a placeholder element.                
annotation
documentation 
Attributes applicable to inline placeholder elements.           

attributeGroup languagePairAttributes
namespace urn:oasis:names:tc:xliff:1.1
used by
complexType bilingualReferenceContainerType
attributes
Name  Type  Use  Default  Fixed  Annotation
source-language  xs:language        
target-language  xs:language        
annotation
documentation 
Provides source and target language attributes.            

attributeGroup mimeTypeAttributes
namespace urn:oasis:names:tc:xliff:1.1
used by
elements base64-data header link
attributes
Name  Type  Use  Default  Fixed  Annotation
mime-type  xlf:mimeType  required      
documentation 
The MIME type of the data as defined in RFC 1341.                
documentation 
CHANGE FROM 1.0: This replaces the form attribute on<internal-file>                
md5-checksum  xs:hexBinary        
documentation 
The MD5 checksum of the binary data.                
documentation 
CHANGE FROM 1.0: This replaces the crc attribute on<internal-file> and <external-file>                
annotation
documentation 
Attributes for elements with a MIME type.            
documentation 
OPEN ISSUE: Do we want a mime-type version?            

attributeGroup optionalIdAttribute
namespace urn:oasis:names:tc:xliff:1.1
used by
elements group mrk
attributes
Name  Type  Use  Default  Fixed  Annotation
id  xs:NMTOKEN        
documentation 
The id attribute is used as a unique identifier for the given element.                

attributeGroup optionalRefAttribute
namespace urn:oasis:names:tc:xliff:1.1
used by
elements bx ex it
attributes
Name  Type  Use  Default  Fixed  Annotation
ref  xs:NMTOKEN        
documentation 
The ref attribute is used to link different elements that may berelated. For example, a reference to its definition, or paragraphsbelonging to the same group, etc.                

attributeGroup requiredIdAttribute
namespace urn:oasis:names:tc:xliff:1.1
used by
elements bin-unit bpt bx ept ex g it ph trans-unit x
attributes
Name  Type  Use  Default  Fixed  Annotation
id  xs:NMTOKEN  required      
documentation 
The id attribute is used as a unique identifier for the given element.                
documentation 
OPEN ISSUE: Are there rules about these that we need to capture,either in the schema or in documentation?  It's important that "diff"tools not get thrown off because one tool decides that it will changeall of the IDs produced by one vendor into a convention that it likesbetter.                

attributeGroup requiredRefAttribute
namespace urn:oasis:names:tc:xliff:1.1
used by
elements bpt ept
attributes
Name  Type  Use  Default  Fixed  Annotation
ref  xs:NMTOKEN  required      
documentation 
The ref attribute is used to link different elements that must berelated. For example, a begin to an end markup tag.                

attributeGroup targetAttributes
namespace urn:oasis:names:tc:xliff:1.1
used by
elements bin-target target
attributes
Name  Type  Use  Default  Fixed  Annotation
state  xs:NMTOKEN        
documentation 
The status of a particular translation in a <target> or<bin-target> element.                
documentation 
The values for the state attribute are as follows:- needs-translation = The item needs to be translated.- needs-review = The item needs to be reviewed.- needs-resizing = The item needs to be resized or reformatted.                
annotation
documentation 
Attributes applicable to a target element (<target> and<bin-target>).            

attributeGroup textMimeTypeAttributes
namespace urn:oasis:names:tc:xliff:1.1
used by
elements alt-trans group sub trans-unit
attributes
Name  Type  Use  Default  Fixed  Annotation
mime-type  xlf:mimeType        
documentation 
A text/* MIME type as defined in RFC 1341.                
documentation 
CHANGE FROM 1.0: This replaces the datatype attribute.                
annotation
documentation 
Attributes for text elements with text/* MIME type.            

attributeGroup transUnitAttributes
namespace urn:oasis:names:tc:xliff:1.1
used by
elements bin-unit trans-unit
attributes
Name  Type  Use  Default  Fixed  Annotation
approved  xs:boolean    false    
documentation 
Indicates whether a translation is final.                
translate  xs:boolean    true    
documentation 
Indicates whether or not the text referred to should be translated.                
reformat  xs:boolean    true    
documentation 
Indicates whether the target can be formatted (size, font, etc.)                
annotation
documentation 
Attributes applicable to a translation unit element (<trans-unit>and <bin-unit>).            

attributeGroup specialAttrs
namespace http://www.w3.org/XML/1998/namespace
attributes
Name  Type  Use  Default  Fixed  Annotation
xml:base  xs:anyURI        
xml:lang  xs:language        
xml:space  xs:NCName    preserve    


XML Schema documentation generated with
XML Spy Schema Editor www.xmlspy.com