Submissions:Xsd:sequence embedding

From Odp

(Difference between revisions)
Jump to: navigation, search
Line 6: Line 6:
{{Reengineering OP Proposal NOR Template
{{Reengineering OP Proposal NOR Template
|Description=*for a description of XSD see: http://en.wikipedia.org/wiki/XML_Schema_(W3C)
|Description=*for a description of XSD see: http://en.wikipedia.org/wiki/XML_Schema_(W3C)
-
The pattern c overs the cases where an xsd:element is embedded into an xsd:sequence, which is in its turn embedded by an xsd:element.
+
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 graphical representation only illustrates the XSD case.
-
The DTD case is exemplified by TMX ()
+
*The DTD case is exemplified by TMX ()
The following structure from TMX illustrates the same pattern conversion
The following structure from TMX illustrates the same pattern conversion
-
   <!ELEMENT tu    \(tuv+\) >
+
   <!ELEMENT tu    (tuv+) >
 +
This describes that a translation unit (tu) consists of one or more translation unit variants (tuv).
|Graphical Representation=1.JPG
|Graphical Representation=1.JPG
}}
}}

Revision as of 22:07, 14 August 2009


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have informations about the evaluation process of this proposal

Current revision ID: 5498

General information

Name structural 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 exemplified by TMX ()

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).

Graphical Representation

Diagram

Image:1.JPG


Ontology

Description xx
Graphical Representation

Diagram

Image:Xsd-embedding2.JPG


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

Image:Xsd-step3.png


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.
Graphical Representation

Diagram

Image: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


Ontology example

Description The xsd:sequence embedding pattern as the resulting ontology pattern.
Graphical Representation

Diagram

Image:xsd-step5.JPG

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

Image:Xsd-embedding-6.png


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
Review article Posted on About revision (current is 5498)
MathieuDAquin about Xsd:sequence embedding 24550838 September 2009 56285,628
EnricoDaga about Xsd:sequence embedding 24550838 September 2009 57235,723
BorisVillazón-Terrazas about Xsd:sequence embedding 24550838 September 2009 57235,723

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

Other info at evaluation tab

Retrieved from "http://ontologydesignpatterns.org/wiki/Submissions:Xsd:sequence_embedding"
Personal tools
Quality Committee
Content OP publishers