Submissions:Xsd:sequence embedding

From Odp

Revision as of 18:12, 14 August 2009 by WimPeters (Talk | contribs)
Jump to: navigation, search


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

General information

Name xsd:sequence embedding
Problem This pattern addresses the re-engineering of an of xsd:element embedded into an xsd:sequence, which is in its turn embedded by an xsd:element.

The ontological result is a meronymic structure.


Non-Ontological Resource

Description xx
Graphical Representation

Diagram (this article has no graphical representation)


Ontology

Description xx
Graphical Representation

Diagram (this article has no graphical representation)


Process

Description xx
Graphical Representation

Diagram (this article has no graphical representation)


Scenario example

Description The application scenarion 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 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 i. “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 (this article has no graphical representation)

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

Diagram (this article has no graphical representation)

Web Reference http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl.owl


Process example

Description The pattern tailored to the XLIFF fragment.
Graphical Representation

Diagram (this article has no graphical representation)


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 5481)
MathieuDAquin about Xsd:sequence embedding 24550838 September 2009 56285,628
BorisVillazón-Terrazas about Xsd:sequence embedding 24550838 September 2009 57235,723
EnricoDaga about Xsd:sequence embedding 24550838 September 2009 57235,723

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

Other info at evaluation tab

Personal tools
Quality Committee
Content OP publishers