'Ontology Design Patterns' - User contributions [en]

Reviews:WimPeters about Enlarge Class Definition for Resolving Disjointness due to Subsomption

2009-09-09T14:18:44Z

WimPeters: New page: {{Content OP Proposal Review Template |CreationDate=2009/9/9 |SubmittedBy=WimPeters |ContentOPUnderReview=Enlarge Class Definition for Resolving Disjointness due to Subsomption |RevisionID...

{{Content OP Proposal Review Template
|CreationDate=2009/9/9
|SubmittedBy=WimPeters
|ContentOPUnderReview=Enlarge Class Definition for Resolving Disjointness due to Subsomption
|RevisionID=5731
|Score=0 - needs major revision
|ReviewSummary=This pattern proposal deserves discussion, in combination with the pattern proposal "Define Hybrid Class Resolving Disjointness due to Subsomption", which is a solution variant to the same problem proposed by the same authors.

I am not sure about the logical consequences of including definitions from a desired superclass for the hyponymic relation between the subclass enriched with this superclass definition and its orginal superclass.
|ReviewConfidence=medium
|ReviewProblems=The problems and discussion points associated with this pattern are the same as those mentioned for the "Define Hybrid Class Resolving Disjointness due to Subsomption" pattern.

The additional problem I see with this particular pattern is that, once the definition from the disjoint superclass has been added, the subclass relation between the enriched subclass and its original superclass may be compromised.
|ReviewRelevance=high for best practise.
|ReviewBestPractice=none that I know of.
|ReviewReusability=very reusable if approved.
|ReviewRelations=related to the "Define Hybrid Class Resolving Disjointness due to Subsomption" pattern.
|ReviewUnderstandability=good, although a very clear definition of what "definition" means is crucial for a proper understanding.
|ReviewClearProblem=description is clear.
|ReviewClearRelevance=Consequences are unclear.
|ReviewFigures=clear enough.
The enriched definition is not graphically linked to the class it originates from.
|ReviewMissing=there is no owl ontology, nor a scenario description
}}

Reviews:WimPeters about Define Hybrid Class Resolving Disjointness due to Subsomption

2009-09-09T11:56:57Z

WimPeters: New page: {{Content OP Proposal Review Template |CreationDate=2009/9/9 |SubmittedBy=WimPeters |ContentOPUnderReview=Define Hybrid Class Resolving Disjointness due to Subsomption |RevisionID=5753 |Sc...

{{Content OP Proposal Review Template
|CreationDate=2009/9/9
|SubmittedBy=WimPeters
|ContentOPUnderReview=Define Hybrid Class Resolving Disjointness due to Subsomption
|RevisionID=5753
|Score=1 - needs minor revision
|ReviewSummary=This pattern proposal deserves discussion, in combination with the pattern proposal "Enlarge Class Definition for Resolving Disjointness due to Subsomption", which is a solution variant to the same problem proposed by the same authors.

|ReviewConfidence=medium, having mainly worked with lightweight ontologies.
|ReviewProblems=Once a subclass is to be defined as a subclass of two disjoint superclasses, this pattern offers a work-around after a more fundamental question has been answered with "yes": Are the two superclasses still to be considered as disjoint?
This is a non-trivial decision, which is borne out by lower than expected levels of agreement between experts (see http://www.eswc2007.org/pdf/eswc07-voelker1.pdf).
In description logics two classes are considered as disjoint iff their taxonomic overlap, i.e. the set of common individuals, must be empty in all possible worlds.
As soon as there exists an instance in the extensions of two disjoint superclasses, the engieer is confronted with the following choices:
1. the disjointness axiom should be deleted, which will negatively affect consistency checking and the automatic evaluation of individuals in a knowledge base with regards to a given ontology (again see (http://www.eswc2007.org/pdf/eswc07-voelker1.pdf))

2. the proposed pattern should be used. This pattern allows to maintain the original disjoint superclasses while indirectly allowing an instance to be in the extension of both. This goes against the principle of disjointness, but may be convenient in the case where the ontology is imported from another URI.

The pattern defines a hybrid class as a union of the definitions of the disjoint classes. The proposers should indicate more precisely what these definitions consist of. Do they consist of all properties and restrictions?
Is this equivalent to creating a class AnimalOrPlant, or AnimalAndPlant? Is there a difference between the two?

Maybe a third option to be taken into account in the discussion is the introduction of degrees of disjointness.
|ReviewRelevance=high, especially if this pattern is judged as best practise. This type of
|ReviewBestPractice=I am not aware of best practise for the solution of this problem.
|ReviewReusability=very reusable
|ReviewRelations=related pattern proposal:
"Enlarge Class Definition for Resolving Disjointness due to Subsomption"
|ReviewUnderstandability=good
|ReviewClearRelevance=It is not clear to me what the union of concept definitions entails.
|ReviewFigures=Figure is clear. It does not illustrate any relations between DisjointClass 1 and DisjointClass2 on the one hand, and HypbridClass on the other, although the latter is a union of the definitions of the former.
|ReviewMissing=There is no owl version of the pattern. Also, there is no scenario description.
}}

Submissions:ConceptTerms

2009-09-08T11:18:50Z

WimPeters: Review has been created. Annotation 'assigned' has been removed.

{{Content_OP_Proposal_toolbar}}
{{Include Image
|ImageName=ConceptTermsPattern.jpg
}}
{{Content OP Proposal Template
|SubmittedBy=Pierre-YvesVandenbussche
|Name=ConceptTerms
|Intent=This CP allows designers to represent language complexity for concept description (preferred term, synonyms, translation relation,etc.).
|Domain=Linguistic, Vocabulary,
|CompetencyQuestion=How to distinguish a preferred term or label from synonyms in order to name a concept?, How to enable cross language searching?, How to allow adding properties on term?
|ContentODPDescription=A concept is named in a particular language by a preferred term and a set of simple non preferred terms. Those terms artifacts specialize the term entity which owns common properties for terms such as: language, source information (when creating vocabulary from corpora). This list of properties may be extended depending on vocabulary specific needs.
|ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl
|Consequences=Compare to labels on a concept class, this solution has a higher data load.
|Scenario=Used for terminology representation. For example, a preferred term "car" in english could be translated in "voiture" in french and linked to the same concept. Here translation relation is possible thanks to the term entity.
|ReengineeredFrom=BS8723-5 model: http://schemas.bs8723.org/
}}
{{Element list header}}

{{Scenarios about me}}
{{Reviews about me}}
{{Submission to event
|Event=WOP2009
}}

[[Category:Review assigned]]

Reviews:WimPeters about ConceptTerms

2009-09-08T11:18:49Z

WimPeters: New page: {{Content OP Proposal Review Template |CreationDate=2009/9/8 |SubmittedBy=WimPeters |ContentOPUnderReview=ConceptTerms |RevisionID=5626 |Score=1 - needs minor revision |ReviewSummary=Overa...

{{Content OP Proposal Review Template
|CreationDate=2009/9/8
|SubmittedBy=WimPeters
|ContentOPUnderReview=ConceptTerms
|RevisionID=5626
|Score=1 - needs minor revision
|ReviewSummary=Overall, this pattern constitutes a good candidate, because it is based on an existing standard. This indicates the need for the incorporation of more standard representations for this particular modeling issue in ODP. Only then a proper discussion of this pattern is possible. Until then, the fact that it bases itself on a standard warrants acceptance.

|ReviewConfidence=My confidence is high for modeling the relation between linguistic/terminological knowledge and ontology classes.
|ReviewProblems=The pattern has been used in various scenarios, and is from that perspective interesting to discuss.

The model, which has been re-engineered directly from a terminological standard model, is too simple to express many linguistic notions that contribute to the quality of information extraction.
It is very important to acknowledge that the pattern fits into a range of proposed standard formats for the expression of concept labels in terms of preference and constitution, such as SKOS, TBX, TMF, LMF, LIR and LingInfo.
It is only after the inclusionof these patterns that it is possible to have a proper discussion of the merits of this pattern on the basis of a comprehensive comparison.

|ReviewRelevance=high for users adhering to the BS8723-2 standard. Insufficient for users who need to model more comples linguistic knowledge.
|ReviewBestPractice=The pattern does represent a best practise, since it is based on a standard.
There are may alternative solutions, which need to be modeled as alternatives, and linked to this pattern in order to maximize coverage and usage.
|ReviewReusability=very re-usable, because of its modular nature.
|ReviewRelations=other standards and best practises need to be proposed as alternatives.
|ReviewClearProblem=the description of the problem is
|ReviewClearRelevance=these are clearly stated.
|ReviewFigures=Not sll relatons are named in the diagram, more specifically the relations involving terms.
|ReviewMissing=A scenario should be added, in which ideally all classes come into play, in order to show why this particular constellation of simple/compound (non)prefered terms is necessary versus a more straightforward list of components model from LMF (see http://gate.ac.uk/gate-extras/neon/ontologies/Lmf-component-module.owl and http://ontoware.org/frs/download.php/606/lmf.owl

The authors should be more specific about the way in which the re-engineering of this particular BS8723-2 fragment is incomplete.
It omits the Equivalence relation between SimpleNonPreferredTerm and PreferredTerm. Also, the CompoundEquivalence relation between PreferredTerm and CompoundNonPreferredTerm is lacking. The model is available from http://schemas.bs8723.org/Model.aspx.
}}

Submissions:Xsd:sequence embedding

2009-08-15T08:16:01Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|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=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=The ontology comprising the pattern representing the relevant XSD or DTD fragment.
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|Description=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 Representation=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=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.
}}
{{Reengineering OP Proposal NOR Example Template
|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.
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 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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as the resulting ontology pattern.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The ontological pattern re-engineered from the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-15T08:14:56Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|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=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=The ontology comprising the pattern representing the relevant XSD or DTD fragment.
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|Description=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 Representation=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=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.
}}
{{Reengineering OP Proposal NOR Example Template
|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.
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 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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as the resulting ontology pattern.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The ontological pattern re-engineered from the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-15T08:12:47Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|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=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|Description=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 Representation=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=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 transaltion memory.
}}
{{Reengineering OP Proposal NOR Example Template
|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.
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 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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as the resulting ontology pattern.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The ontological pattern re-engineered from the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
|Other References=
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-15T08:06:44Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|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=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|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=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenario is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as the resulting ontology pattern.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-15T08:03:11Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|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 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 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
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|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=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenario is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as the resulting ontology pattern.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T22:08:09Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|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=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|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=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenario is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as the resulting ontology pattern.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T22:07:44Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|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=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|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=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenario is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as the resulting ontology pattern.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T22:05:56Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|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 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+\) >
|Graphical Representation=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|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=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenario is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as the resulting ontology pattern.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T22:03:52Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|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 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 (note|prop)*, tuv+) >
This describes that a translation unit (tu) consists of one or more translation unit variants (tuv).
|Graphical Representation=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|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=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenario is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as the resulting ontology pattern.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T22:01:45Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.

}}
{{Reengineering OP Proposal NOR Template
|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 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 ((note|prop)*, tuv+) >

|Graphical Representation=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|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=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenarion is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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 “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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as the resulting ontology pattern.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T18:50:41Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|Description=for a description of XSD see: http://en.wikipedia.org/wiki/XML_Schema_(W3C)
|Graphical Representation=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|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=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenarion is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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 “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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as the resulting ontology pattern.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T18:47:06Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|Description=xx
|Graphical Representation=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|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=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenarion is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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 “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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as the resulting ontology pattern.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Feedback:Modifying a proposed reengineering pattern

2009-08-14T18:44:59Z

WimPeters: please ignore this feedback

{{TitleDescription Template
|Title=modifying a proposed reengineering proposal
|Description=I have created a partial reengineering proposal, which i saved. I then found out that I can not modify it anymore.
The amount of information that needs to be entered in one go is too large, and makes the proposal process very cumbersome.
Intermediate saves and editing options of saved versions should be enabled, whcih would allow an incremental creation of a proposal.
}}
{{Feedback Template
|Author=WimPeters,
|Priority=High
|Status=To be done
}}
{{Answer Template
|Answer=Please ignore my complaint about the lack of incremental editing facilities, I have found out now that this is working perfectly. Appology, spoke too soon.
}}

Submissions:Xsd:sequence embedding

2009-08-14T18:41:24Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|Description=xx
|Graphical Representation=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|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=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenarion is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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 “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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as ontology.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T18:40:31Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|Description=xx
|Graphical Representation=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|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=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenarion is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as ontology.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T18:39:26Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|Description=xx
|Graphical Representation=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|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=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenarion is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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.

http://www.ontologydesignpatterns.org/ont/dul/DUL.owl1. TransUnit: contains (a set of) translational equivalences
http://www.ontologydesignpatterns.org/ont/dul/DUL.owl2. 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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as ontology.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T18:37:22Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|Description=xx
|Graphical Representation=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|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=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenarion is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as ontology.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T18:30:18Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|Description=xx
|Graphical Representation=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|Description=xx
|Graphical Representation=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenarion is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as ontology.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T18:25:55Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|Description=xx
|Graphical Representation=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|Description=xx
|Graphical Representation=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenarion is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as ontology.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T18:25:01Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|Description=xx
|Graphical Representation=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|Description=xx
|Graphical Representation=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenarion is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as ontology.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=Xsd-embedding-step6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T18:23:17Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|Description=xx
|Graphical Representation=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|Description=xx
|Graphical Representation=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenarion is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as ontology.
|Graphical Representation=xsd-step5.JPG
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=xsd-embedding-step6.png
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T18:22:25Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|Description=xx
|Graphical Representation=1.JPG
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.JPG
}}
{{Reengineering OP Proposal Process Template
|Description=xx
|Graphical Representation=Xsd-step3.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenarion is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=xsd-step4.jpg
|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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as ontology.
|Graphical Representation=xsd-step5.jpg
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=xsd-embedding-step6.jpg
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T18:20:06Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|Description=xx
|Graphical Representation=1.jpg
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=Xsd-embedding2.jpg
}}
{{Reengineering OP Proposal Process Template
|Description=xx
|Graphical Representation=Xsd-step3.jpg
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenarion is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=xsd-step4.jpg
|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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as ontology.
|Graphical Representation=xsd-step5.jpg
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=xsd-embedding-step6.jpg
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Xsd:sequence embedding

2009-08-14T18:12:44Z

WimPeters:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|Description=xx
|Graphical Representation=1.jpg
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=xsd-embedding2.jpg
}}
{{Reengineering OP Proposal Process Template
|Description=xx
|Graphical Representation=xsd-step3.jpg
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenarion is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=xsd-step4.jpg
|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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as ontology.
|Graphical Representation=xsd-step5.jpg
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=xsd-embedding-step6.jpg
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

Feedback:Modifying a proposed reengineering pattern

2009-08-14T18:08:07Z

WimPeters: Please allow intermediate saves and edits of pattern proposals.

Submissions:Xsd:sequence embedding

2009-08-14T17:58:09Z

WimPeters: an ontology pattern covering xsd:sequence embedding in XLIFF

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|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.
}}
{{Reengineering OP Proposal NOR Template
|Description=xx
|Graphical Representation=1.jpg
}}
{{Reengineering OP Proposal Ontology Template
|Description=xx
|Graphical Representation=xsd-step2.jpg
}}
{{Reengineering OP Proposal Process Template
|Description=xx
|Graphical Representation=xsd-step3.jpg
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=The application scenarion is in the area of the modelling of lexical translational equivalence according to the format of the XLIFF standard.
}}
{{Reengineering OP Proposal NOR Example Template
|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=xsd-step4.jpg
|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
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The xsd:sequence embedding pattern as ontology.
|Graphical Representation=xsd-step5.jpg
|Web Reference=http://gate.ac.uk/gate-extras/neon/ontologies/xsd-embedding.owl.owl
}}
{{Reengineering OP Proposal Process Example Template
|Description=The pattern tailored to the XLIFF fragment.
|Graphical Representation=xsd-embedding-step6.jpg
}}
{{Reengineering OP Proposal Additional Information Template
|Author=Wim Peters
}}

{{Scenarios about me}}
{{Reviews about me}}

File:Xsd-embedding-6.png

2009-08-14T17:37:54Z

WimPeters:

File:Xsd-step5.JPG

2009-08-14T17:37:12Z

WimPeters:

File:Xsd-step4.png

2009-08-14T17:36:40Z

WimPeters:

File:Xsd-step3.png

2009-08-14T17:36:04Z

WimPeters:

File:Xsd-embedding2.JPG

2009-08-14T17:34:02Z

WimPeters: graphical representation of the resulting ontological pattern

graphical representation of the resulting ontological pattern

File:1.JPG

2009-08-14T17:30:15Z

WimPeters: uploaded a new version of "Image:1.JPG": this picture illustrates the embedding of xsd:element into an xsd:sequence, which is in its turn embedded by an xsd:element

thisi picture illustrates the embedding of xsd:element into an xsd:sequence, which is in its turn embedded by an xsd:element

File:1.JPG

2009-08-14T17:28:55Z

WimPeters: thisi picture illustrates the embedding of xsd:element into an xsd:sequence, which is in its turn embedded by an xsd:element

thisi picture illustrates the embedding of xsd:element into an xsd:sequence, which is in its turn embedded by an xsd:element

Submissions:Metonymy-species-commodity

2008-06-18T14:04:52Z

WimPeters:

{{Content_OP_Proposal_toolbar}}
{{Include Image
|ImageName=met1.jpg
}}
{{Content OP Proposal Template
|SubmittedBy=User:WimPeters
|Name=FAO-metonymy-species-commodity
|AlsoKnownAs=fish-species-exploited-as-commodity
|Intent=To establish a link between species exploitation and consumer goods.

This pattern has been observed in WordNet, where words share the following metonymic or regular polysemic patterns: animal-food, animal-commodity and life form-consumer goods. This is why the pattern has been named "metonymy".
Regular polysemy is a metonymic phenomenon in that it describes the substitution of one word sense by another related sense. It establishes a semantic relation between two concepts that are associated with the
same word. Regular polysemy is regular in that it captures conventionalized
and therefore recurrent processes of sense extension, which have been captured in lexical resources such as dictionaries and thesauri.
|Domain=Fisheries
|CompetencyQuestion=For which commodity is the species used when caught?
|ReusableOWLBuildingBlock=http://gate.ac.uk/gate-extras/neon/ontologies/metonymy1_FAO.owl
|Consequences=the link between species and consumer product will allow the blacklisting of product manufactured from endangered stocks.
|Scenario=Yellowfin tuna is provided as fresh or chilled food commodity
|HasComponent=Submissions:Biological Entities
|RelatedCP=Submissions:Biological Entities
}}
{{Element list header}}
This pattern has been observed in WordNet, where words share the following regular polysemic patterns animal-food, animal-commodity and life form-consumer goods.
{{Scenarios about me}}
{{Reviews about me}}

Submissions:Metonymy-species-commodity

2008-06-18T14:02:35Z

WimPeters:

{{Content_OP_Proposal_toolbar}}
{{Include Image
|ImageName=met1.jpg
}}
{{Content OP Proposal Template
|SubmittedBy=User:WimPeters
|Name=FAO-metonymy-species-commodity
|AlsoKnownAs=fish-species-exploited-as-commodity
|Intent=To establish a link between species exploitation and consumer goods.

This pattern has been observed in WordNet, where words share the following regular polysemic patterns: animal-food, animal-commodity and life form-consumer goods.
regular polysemy is a metonymic phenomenon in that it describes the substitution of one word sense by another related sense. It establishes a semantic relation between two concepts that are associated with the
same word. Regular polysemy is regular in that it captures conventionalized
and therefore recurrent processes of sense extension, which have been captured in lexical resources such as dictionaries and thesauri.
|Domain=Fisheries
|CompetencyQuestion=For which commodity is the species used when caught?
|ReusableOWLBuildingBlock=http://gate.ac.uk/gate-extras/neon/ontologies/metonymy1_FAO.owl
|Consequences=the link between species and consumer product will allow the blacklisting of product manufactured from endangered stocks.
|Scenario=Yellowfin tuna is provided as fresh or chilled food commodity
|HasComponent=Submissions:Biological Entities
|RelatedCP=Submissions:Biological Entities
}}
{{Element list header}}
This pattern has been observed in WordNet, where words share the following regular polysemic patterns animal-food, animal-commodity and life form-consumer goods.
{{Scenarios about me}}
{{Reviews about me}}

Feedback:Free text on pattern submision page

2008-06-18T13:48:40Z

WimPeters: text should be displayed

{{TitleDescription Template
|Title=display of free text on pattern submission page
|Description=sugegstion to display all relevant information entered on the form.
}}
{{Feedback Template
|Author=User:WimPeters
|Priority=Medium
|Status=To be done
}}
The text entered in the free text box should be displayed when the pattern wiki page is accessed. I just entered a short motivation for the "metonymy" pattern I created, and this text box seemed the best place to put it. Please tell me if there is a more appropriate place for free text explanation.

Submissions:Metonymy-species-commodity

2008-06-18T13:38:44Z

WimPeters: New page: {{Content_OP_Proposal_toolbar}} {{Include Image |ImageName=met1.jpg }} {{Content OP Proposal Template |SubmittedBy=User:WimPeters |Name=FAO-metonymy-species-commodity |AlsoKnownAs=fish-spe...

File:Met1.jpg

2008-06-18T12:22:33Z

WimPeters: description of a species-commodity metonymic relation for FAO concepts

description of a species-commodity metonymic relation for FAO concepts

Reviews:WimPeters about Classification

2008-06-12T14:03:57Z

WimPeters: New page: {{Content OP Proposal Review Template |CreationDate=12/06/2008 |SubmittedBy=WimPeters |ContentOPUnderReview=Classification |RevisionID=2375 |ReviewText=The Concepts class in not clearly de...

{{Content OP Proposal Review Template
|CreationDate=12/06/2008
|SubmittedBy=WimPeters
|ContentOPUnderReview=Classification
|RevisionID=2375
|ReviewText=The Concepts class in not clearly defined. From the pattern I assume that this "socially" predicates the Entity class in some way. Please provide more explantion.
}}