Edit Reengineering OP Proposal Form: Submissions:Xsd:sequence embedding

From Odp

You have to log in to edit pages.

Re-engineering OP Proposal
Example
About
Reviews taken into account
Additional Information
Submitted to event

General Information

Nameinfo.pngThis field is associated with the property Name This property indicates a name for the entity it is associated with. The value of this property is of type String. :
Probleminfo.pngDescription in natural language of the re-engineering problem addressed by the pattern :	This pattern addresses the re-engineering of certain embedded structures within XSD and DTD representations into a meronymic pattern.

Non-Ontological Resource

Descriptioninfo.pngDescription in natural language of the non-ontological resource. :	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 Representationinfo.pngThis field has to be assigned with the name of the file (including its extension) that graphically represents the non-ontological resource. The image file must be uploaded on the wiki before through the Upload file function that can be accessed through the menu on the left. :

Ontology

Descriptioninfo.pngDescription in natural language of the output after applying the pattern. :	The ontology comprising the pattern representing the relevant XSD or DTD fragment.
Graphical Representationinfo.pngThis field has to be assigned with the name of the file (including its extension) that graphically represents the ontology. The image file must be uploaded on the wiki before through the Upload file function that can be accessed through the menu on the left. :

Solution

Descriptioninfo.pngDescription in natural language of the general process, using a sequence of activities. :	The re-engineering process 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 Representationinfo.pngThis field has to be assigned with the name of the file (including its extension) that graphically represents the sequence of activities. The image file must be uploaded on the wiki before through the Upload file function that can be accessed through the menu on the left. :

Scenario

Descriptioninfo.pngDescription in natural language of an example of the re-engineering problem. :	The application scenario is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF and TMX standards for translation memory.

Non-Ontological Resource

Descriptioninfo.pngDescription in natural language of an example of the non-ontological resource. :	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. A more detailed description of TMX can be found in NeOn deliverable D2.4.3: Multilingual and Localization Support for Ontologies (www.neon-project.org).
Graphical Representationinfo.pngThis field has to be assigned with the name of the file (including its extension) that graphically represents the non-ontological resource. The image file must be uploaded on the wiki before through the Upload file function that can be accessed through the menu on the left. :
Web Referenceinfo.pngLink to a website which holds the non-ontological resource. :

Ontology

Descriptioninfo.pngDescription in natural language of an example of the non-ontological resource. :	The xsd:sequence embedding pattern as the resulting ontology pattern.
Graphical Representationinfo.pngThis field has to be assigned with the name of the file (including its extension) that graphically represents the ontology generated. The image file must be uploaded on the wiki before through the Upload file function that can be accessed through the menu on the left. :
Web reference info.pngLink to a website which holds the ontology generated. :

Solution

Descriptioninfo.pngDescription in natural language of the process applied to the non-ontological resource example, using the sequence of activities described in the pattern :	The ontological pattern re-engineered from the XLIFF fragment.
Graphical Representationinfo.pngThis field has to be assigned with the name of the file (including its extension) that graphically represents the sequence of activities. The image file must be uploaded on the wiki before through the Upload file function that can be accessed through the menu on the left. :

Summary:

This is a minor edit Watch this page

Cancel

Submitted byinfo.pngThis field can be assigned with multiple separated by comma. It is associated with the property submittedBy. This property indicates the ODP user who submitted either a Proposed Content OP, a Content OP, a Modeling Issue, or a Feedback. The value of this property are of type ODPUser. :
Authorinfo.pngThe author of the pattern :
Also known Asinfo.pngThis field can be assigned with multiple values separated by commas. It is associated with the property With this property you can indicate alternative names (if any) for the Ontology Design Pattern. The values of this property are of type String. :
Known usesinfo.pngThis field can be assigned with multiple values separated by commas. It is associated with the property KnownUse This property indicates existing ontologies where the Content OP is used as a building block. Note that such ontologies are different from the ontologies where the Content OP is extracted from (see the ExtractedFrom property). The value of this property is of type URL. This property is a subproperty of Property:PatternUsage. :
Related toinfo.pngThis field can be assigned with multiple values separated by commas. It is associated with the property This property is of type Page. :
Other Referencesinfo.pngLEGACY: DO NOT USE. Migrate existing references to new format. This field can be assigned with multiple values separated by commas. It is associated with the property Property:Reference :

Edit Reengineering OP Proposal Form: Submissions:Xsd:sequence embedding

From Odp

Views

Personal tools

Navigation

Contribute

Help

Catalogues

Quality Committee

Content OP publishers

Editorial Board

Administrator

WOP

Search

Toolbox