Revision as of 08:06, 15 August 2009

Warning!

This is an old revision. Go to current revision

Last modified date is: 2009-08-15

General information

Name	Structural XML/DTD embedding to ontological meronymy
Problem	This pattern addresses the re-engineering of certain embedded structures within XSD and DTD representations into a meronymic pattern.

Non-Ontological Resource

Description

*For a description of XSD see: http://en.wikipedia.org/wiki/XML_Schema_(W3C)

The pattern covers the cases where an xsd:element is embedded into an xsd:sequence, which is in its turn embedded by an xsd:element.

The graphical representation only illustrates the XSD case.
The DTD case is described in the example section.

Graphical Representation

Diagram

Ontology

Description	xx
Graphical Representation	Diagram

Process

Description	The re-enginneering proess involves a number of steps: The creation of embedding class and embedded class(es) The creation of an instance of the hasPart object property from the DOLCE Ultra Light ontology (http://www.ontologydesignpatterns.org/ont/dul/DUL.owl) with embedding class as domain and embedded class(es) as range.
Graphical Representation	Diagram

Scenario example

Description	The application scenario is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.

Example of a Non-Ontological Resource

Description

*XLIFF

The purpose of the OASIS XLIFF standard (http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html) is to define and promote, through extensible XML vocabularies, the adoption of a specification for the interchange of localizable software and document based objects and related metadata. XLIFF should be able to mark-up and capture localization information and interoperate with different processes and phases without loss of information. It should fulfill specific requirements of being tool-neutral. It should support the localization related aspects of internationalization and entire localization process. It also needs to support common software and content data formats. This should also provide an extensibility mechanism to allow the development of tools compatible with an implementer’s proprietary data formats and workflow requirements.

1. TransUnit: contains (a set of) translational equivalences
2. Source: the source of the translation pair
3. SegSource: the translatable text, divided into segments
4. Mrk: Each segment is marked by means of the <Mrk> element with attribute “mType” set to the value "seg".
5. Target: the target of the translation pair
6. Alt-Trans: possible translations as Target instances
7. Equiv-trans: Indicates if the target language translation is a direct equivalent of the source text.

DTD embedding is exemplified (but not illustrated on this page) by Translation Memory eXchange standard (TMX) (http://www.lisa.org/Translation-Memory-e.34.0.html). TMX is the vendor-neutral open XML standard for the exchange of Translation Memory data created by Computer Aided Translation and localization tools. The purpose of TMX is to allow easier exchange of translation memory data between tools and/or translation vendors with little or no loss of critical data during the process. In existence since 1998, TMX is a certifiable standard format. TMX is developed and maintained by OSCAR (Open Standards for Container/Content Allowing Re-use), a LISA (Localization Industry Standards Association) Special Interest Group.

The following structure from TMX illustrates the same pattern conversion

  <!ELEMENT tu     (tuv+) >

This describes that a translation unit (tu) consists of one or more translation unit variants (tuv). A translationUnit contains the data for a given translation unit. A TranslationUnitVariant specifies text in a given language

Graphical Representation

Diagram

Web Reference

http://schemas.liquid-technologies.com/Oasis/XLIFF/1.2/default.html?url=http://schemas.liquid-technologies.com/Oasis/XLIFF/1.2/xliff-core-1_2-strict_xsd.html

Ontology example

Description	The xsd:sequence embedding pattern as the resulting ontology pattern.
Graphical Representation	Diagram
Web Reference	http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl

Process example

Description	The pattern tailored to the XLIFF fragment.
Graphical Representation	Diagram

About

SubmittedBy
Author	Wim Peters
Also known as
Known uses
Related to
Other References

Scenarios

Scenarios about Xsd:sequence embedding

No scenario is added to this Content OP.

Reviews

Reviews about Xsd:sequence embedding

There is no review about this proposal.

Some subquery has no valid condition.

This revision (revision ID 5501) takes in account the reviews: none

Other info at evaluation tab

@@ Line 8: / Line 8: @@
 The pattern covers the cases where an xsd:element is embedded into an xsd:sequence, which is in its turn embedded by an xsd:element.
 *The graphical representation only illustrates the XSD case.
-*The DTD case is exemplified by the Translation Memory eXchange standard (TMX) (http://www.lisa.org/Translation-Memory-e.34.0.html). TMX is the vendor-neutral open XML standard for the exchange of Translation Memory data created by Computer Aided Translation and localization tools. The purpose of TMX is to allow easier exchange of translation memory data between tools and/or translation vendors with little or no loss of critical data during the process. In existence since 1998, TMX is a certifiable standard format. TMX is developed and maintained by OSCAR (Open Standards for Container/Content Allowing Re-use), a LISA  (Localization Industry Standards Association) Special Interest Group.
+*The DTD case is described in the example section.
-The following structure from TMX illustrates the same pattern conversion
-   <!ELEMENT tu     (tuv+) >
-This describes that a translation unit (tu) consists of one or more translation unit variants (tuv).
-A translationUnit contains the data for a given translation unit.
-A TranslationUnitVariant specifies text in a given language
 |Graphical Representation=1.JPG
 }}
@@ Line 42: / Line 36: @@
 *6.	Alt-Trans: 	possible translations as Target instances
 *7.	Equiv-trans: 	Indicates if the target language translation is a direct equivalent of the source text.
+*DTD embedding is exemplified (but not illustrated on this page) by Translation Memory eXchange standard (TMX) (http://www.lisa.org/Translation-Memory-e.34.0.html). TMX is the vendor-neutral open XML standard for the exchange of Translation Memory data created by Computer Aided Translation and localization tools. The purpose of TMX is to allow easier exchange of translation memory data between tools and/or translation vendors with little or no loss of critical data during the process. In existence since 1998, TMX is a certifiable standard format. TMX is developed and maintained by OSCAR (Open Standards for Container/Content Allowing Re-use), a LISA  (Localization Industry Standards Association) Special Interest Group.
+The following structure from TMX illustrates the same pattern conversion
+   <!ELEMENT tu     (tuv+) >
+This describes that a translation unit (tu) consists of one or more translation unit variants (tuv).
+A translationUnit contains the data for a given translation unit.
+A TranslationUnitVariant specifies text in a given language
 |Graphical Representation=xsd-step4.png
 |Web Reference=http://schemas.liquid-technologies.com/Oasis/XLIFF/1.2/default.html?url=http://schemas.liquid-technologies.com/Oasis/XLIFF/1.2/xliff-core-1_2-strict_xsd.html

Difference between revisions of "Submissions:Xsd:sequence embedding"