Showing 9 pages using this property.
V | |
|---|---|
| View Inheritance + | The wikipage input value "Object Oriented:
Ontology:
|
| Vocabulary Alignment Pattern: Conjoint Instances of an external Class + | Some subquery has no valid condition. + |
| Vocabulary Alignment Pattern: Conjoint Instances of an external Class + | The wikipage input value "The patterns "Subclass of an external Class" and "Sub property of an external Property" allow the extension of external classes or properties. Instances, however, can not be easily instances of the external vocabularies. But the use of instances of the external classes, is an essential aim of vocabulary alignments. So it should be possible, to use instances of the classes foaf:Agent or its subclass foaf:Person describe an instance of a class own:Person in the own ontology. The concepts foaf:Person and own:Person are not equivalent, but there is an intersection of instances. The set of intersection is even larger if the domain and range of properties of the own class are sub properties of properties of the external vocabulary. As used herein, the description logic models a equivalence between class B and class D, for such instances of both classes, defined on an object property like p1. The external class is from the perspective of their own domain typically in the range of an defined object property. Therefore, this pattern is used on an inverse object property." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Vocabulary Alignment Pattern: Sub property of an external Property + | Some subquery has no valid condition. + |
| Vocabulary Alignment Pattern: Subclass of an external Class + | Some subquery has no valid condition. + |
| Vocabulary Alignment Pattern: Subclass of an external Class + | The wikipage input value "The pattern "Subclass of a external Class" is used, in the SIOC vocabulary to align the classes sioc:UserAccount and foaf:OnlineAccount. Instances of a so inferred class are a subset of the instances of the class of the external vocabulary." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
W | |
| WinstonPartWhole + | Some subquery has no valid condition. + |
X | |
| Xsd:sequence embedding + | Some subquery has no valid condition. + |
| Xsd:sequence embedding + | The wikipage input value "*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 wikipage input value "The re-engineering process involves a number of steps:
The wikipage input value "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.
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)." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
'Ontology Design Patterns'