<?xml version="1.0" encoding="ISO-8859-1"?><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<front>
<journal-meta>
<journal-id>0123-3432</journal-id>
<journal-title><![CDATA[Íkala, Revista de Lenguaje y Cultura]]></journal-title>
<abbrev-journal-title><![CDATA[Íkala]]></abbrev-journal-title>
<issn>0123-3432</issn>
<publisher>
<publisher-name><![CDATA[Escuela de Idiomas, Universidad de Antioquia]]></publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id>S0123-34322010000200006</article-id>
<title-group>
<article-title xml:lang="en"><![CDATA[Standards-based Content Resources: A Prerequisite for Content Integration and Content Interoperability]]></article-title>
<article-title xml:lang="es"><![CDATA[Recursos de contenido basados en estándares: un prerrequisito para la integración de contenido e interoperabilidad de contenido]]></article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name>
<surname><![CDATA[Galinski]]></surname>
<given-names><![CDATA[Christian]]></given-names>
</name>
<xref ref-type="aff" rid="A01"/>
</contrib>
</contrib-group>
<aff id="A01">
<institution><![CDATA[,International Information Centre for Terminology (Infoterm)  ]]></institution>
<addr-line><![CDATA[Vienna ]]></addr-line>
<country>Austria</country>
</aff>
<pub-date pub-type="pub">
<day>00</day>
<month>05</month>
<year>2010</year>
</pub-date>
<pub-date pub-type="epub">
<day>00</day>
<month>05</month>
<year>2010</year>
</pub-date>
<volume>15</volume>
<numero>25</numero>
<fpage>143</fpage>
<lpage>157</lpage>
<copyright-statement/>
<copyright-year/>
<self-uri xlink:href="http://www.scielo.org.co/scielo.php?script=sci_arttext&amp;pid=S0123-34322010000200006&amp;lng=en&amp;nrm=iso"></self-uri><self-uri xlink:href="http://www.scielo.org.co/scielo.php?script=sci_abstract&amp;pid=S0123-34322010000200006&amp;lng=en&amp;nrm=iso"></self-uri><self-uri xlink:href="http://www.scielo.org.co/scielo.php?script=sci_pdf&amp;pid=S0123-34322010000200006&amp;lng=en&amp;nrm=iso"></self-uri><abstract abstract-type="short" xml:lang="en"><p><![CDATA[Objective: to show how standards-based approaches for content standardization, content management, content related services and tools as well as the respective certification systems not only guarantee reliable content integration and content interoperability, but also are of particular benefit to people with special needs in eAccessibility/eInclusion. Method: document MoU/MG/05 N0221 ''Semantic Interoperability and the need for a coherent policy for a framework of distributed, possibly federated repositories for all kinds of content items on a world-wide scale''2, which was adopted in 2005, was a first step towards the formulation of global interoperability requirements for structured content. These requirements -based on advanced terminological principles- were taken up in EU-projects such as IN-SAFETY (INfrastructure and SAFETY) and OASIS (Open architecture for Accessible Services Integration and Standardization). Results: Content integration and content interoperability are key concepts in connection with the emergence of state-of-the-art distributed and federated databases/repositories of structured content. Given the fact that linguistic content items are increasingly combined with or embedded in non-linguistic content items (and vice versa), a systemic and generic approach to data modelling and content management has become the order of the day. Fulfilling the requirements of capability for multilinguality and multimodality, based on open standards makes software and database design fit for eAccessibility/eInclusion from the outset. It also makes structured content capable for global content integration and content interoperability, because it enhances its potential for being re-used and re-purposed in totally different eApplications. Such content as well as the methods, tools and services applied can be subject to new kinds of certification schemes which also should be based on standards. Conclusions: Content must be totally reliable in some applications, e.g. in eAccessibility/ eInclusion. New methods and tools for certification, verification and validation are largely facilitated by standards-based data-models and standardized content, which will have an impact on future ICT-related standards in general. While thus increasing the reliability of data, risk of all sorts and liability will be reduced.]]></p></abstract>
<abstract abstract-type="short" xml:lang="es"><p><![CDATA[Objetivo: demostrar que tanto los enfoques basados en estándares para la normalización y la gestión de contenidos y para los servicios y las herramientas relacionados con los contenidos, como sus respectivos sistemas de certificación, no sólo garantizan la integración y la interoperabilidad con-fiables de contenidos, sino que, además, benefician en particular a las personas con necesidades especiales en e-Accesibilidad / e-Inclusión. Método: el documento ''Semantic Interoperability and the need for a coherent policy for a framework of distributed, possibly federated repositories for all kinds of content items on a world-wide scale'', que se adoptó en 2005, fue un primer paso en la formulación de requisitos globales de interoperabilidad para contenidos estructurados. Dichos requisitos -fundamentados en principios terminológicos- se han adoptado en proyectos de la Unión Europea como IN-SAFETY (Infrastructure and Safety) y OASIS (Open architecture for Accessible Services Integration and Standardization). Resultados: La integración y la interoperabilidad de contenidos son conceptos clave en relación con la aparición de bases de datos / repositorios de contenidos estructurados. Dado que los ítems de contenido lingüístico se combinan o se insertan cada vez más en ítems de contenido no lingüístico (y viceversa), un enfoque sistémico y genérico de modelación de datos y gestión de contenidos está a la orden del día. Dicho sistema cumple los requisitos para el multilingüismo y está basado en normas abiertas, de manera que, desde el principio, adapta el software y el diseno de bases de datos a la e-Accesibilidad / e-Inclusión. Además, hace el contenido estructurado adaptable a la integración e interoperabilidad de contenidos, ya que refuerza su potencial para ser reutilizado y redirigido en e-aplicaciones totalmente distintas. Este contenido, al igual que los métodos, las herramientas y los servicios que se emplean, pueden ser sometidos a nuevos tipos de esquemas de certificación que estén basados en estándares. Conclusión: el contenido debe ser totalmente confiable en algunas aplicaciones como e-Accesibilidad / e-Inclusión. Nuevos modelos y herramientas para la certificación, la verificación y la validación son provistos por los modelos de datos basados en estándares y en contenidos normalizados, que influenciarán las futuras normas de ICT (Integration and Content Interoperability) en general. Además de aumentar la confiabilidad de los datos, disminuyen los riesgos de todo tipo y la responsabilidad.]]></p></abstract>
<abstract abstract-type="short" xml:lang="fr"><p><![CDATA[Objectif: démontrer qu'aussi bien les approches basées sur des standards pour la normalisation et la gestion de contenus, pour les services et les outils en rapport avec les contenus, que leurs systemes de certification respectifs, ne garantissent pas seulement la fiabilité de l'intégration et de l'interopérabilité de contenus, mais, de plus, bénéficient notamment aux personnes qui ont des nécessités spéciales en e-Accessibilité/e-Inclusion. Méthode: le document MoU/MG/05 N0221 ''Semantic Interoperability and the need for a coherent policy for a framework of distributed, possibly federated repositories for all kinds of content items on a world-wide scale'' , adopté en 2005, représente un premier pas dans la formulation de conditions requises globales d'interopérabilité pour des contenus structurés. Ces conditions requises - basées sur des principes terminologiques - ont été adoptées dans des projets de l'UE comme IN-SAFETY (INfrastructure and SAFETY) et OASIS (Open architecture for Accessible Services Integration and Standardization). Résultats: l'intégration et l'interopérabilité de contenus sont des concepts clefs en ce qui concerne l'apparition de bases de données/réservoir de contenus structurés. Etant donné que les items de contenu linguistique se combinent et s'inserent toujours davantage a l'intérieur des items de contenu non linguistique (et viceversa), une approche systémique et générique de modélation de données et de gestion de contenus est a l'ordre du jour. Le systeme en question remplit les conditions requises pour le multilinguisme et se base sur des normes ouvertes, en sorte que depuis le début, il adapte le software et le design de bases de données a e-Accessibilité/e-Inclusion. De plus, il rend le contenu structuré adaptable a l'intégration et a l'interopérabilité de contenus, renforçant son potentiel afin d'etre réutilisé et redirigé en e-applications bien distinctes. Ce contenu, les méthodes, les outils et les services que l'on emploie peuvent etre soumis a de nouveaux types de schémas de certification fondés sur des standards. Conclusion: le contenu doit etre totalement fiable dans quelques applications comme e-Accessibilité/e-Inclusion. De nouveaux modeles et des outils pour la certification, la vérification et la validation sont fournis par les modeles de données basées sur des standards et sur des contenus normalisés, lesquels influenceront les futures normes de CT en général. En plus d'augmenter la fiabilité des données, ils diminuent tout type de risques, ainsi que la responsabilité légale.]]></p></abstract>
<kwd-group>
<kwd lng="en"><![CDATA[international standards]]></kwd>
<kwd lng="en"><![CDATA[content repositories]]></kwd>
<kwd lng="en"><![CDATA[standardized structured content]]></kwd>
<kwd lng="en"><![CDATA[standardized data models]]></kwd>
<kwd lng="en"><![CDATA[content integration and interoperability]]></kwd>
<kwd lng="en"><![CDATA[verification]]></kwd>
<kwd lng="en"><![CDATA[validation]]></kwd>
<kwd lng="en"><![CDATA[certification]]></kwd>
<kwd lng="en"><![CDATA[eAccessibility]]></kwd>
<kwd lng="en"><![CDATA[eInclusion]]></kwd>
<kwd lng="es"><![CDATA[normas internacionales]]></kwd>
<kwd lng="es"><![CDATA[repositorios de contenidos]]></kwd>
<kwd lng="es"><![CDATA[contenido estructurado normalizado]]></kwd>
<kwd lng="es"><![CDATA[modelos de datos estructurados]]></kwd>
<kwd lng="es"><![CDATA[integración e interoperabilidad de contenidos]]></kwd>
<kwd lng="es"><![CDATA[verificación]]></kwd>
<kwd lng="es"><![CDATA[validación]]></kwd>
<kwd lng="es"><![CDATA[certificación]]></kwd>
<kwd lng="es"><![CDATA[e-Accessibilidad]]></kwd>
<kwd lng="es"><![CDATA[e-Inclusión]]></kwd>
<kwd lng="fr"><![CDATA[normes internationales]]></kwd>
<kwd lng="fr"><![CDATA[réservoirs de contenus]]></kwd>
<kwd lng="fr"><![CDATA[contenu structuré normalisé]]></kwd>
<kwd lng="fr"><![CDATA[modele de données structurées]]></kwd>
<kwd lng="fr"><![CDATA[intégration et interopérabilité de contenus]]></kwd>
<kwd lng="fr"><![CDATA[vérification]]></kwd>
<kwd lng="fr"><![CDATA[validation]]></kwd>
<kwd lng="fr"><![CDATA[certification]]></kwd>
<kwd lng="fr"><![CDATA[e-Accessibilité]]></kwd>
<kwd lng="fr"><![CDATA[e-Inclusion]]></kwd>
</kwd-group>
</article-meta>
</front><body><![CDATA[ <p align="right"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>ART&Iacute;CULOS DE INVESTIGACI&Oacute;N</b></font></p>     <p>&nbsp;</p>     <p align="center"><font size="4" face="Verdana, Arial, Helvetica, sans-serif"><b>Standards-based Content Resources: A Prerequisite for Content Integration and Content Interoperability*<a name="en1"></a><sup><a href="#n1">1</a></sup> </b></font></p>     <p align="center">&nbsp;</p>     <p align="center"><font size="3" face="Verdana, Arial, Helvetica, sans-serif"><b>Recursos  de contenido basados en est&aacute;ndares: un prerrequisito para la integraci&oacute;n de  contenido e interoperabilidad de contenido</b></font></p>     <p>&nbsp;</p>     <p>&nbsp;</p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>Christian Galinski** </b>    <br> Dr.   Christian Galinski. International Information Centre for Terminology   (Infoterm), Vienna (Austria) www.infoterm.info. E-mail: <a href="mailto:infocgalinski@infoterm.org">infocgalinski@infoterm.org</a> </font></p>     <p>&nbsp;</p> <hr size=1 noshade>     ]]></body>
<body><![CDATA[<p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>ABSTRACT</b></font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>Objective: </b>to show how standards-based approaches for content standardization, content management, content related services and tools as well as the respective certification systems not only guarantee reliable content integration and content interoperability, but also are of particular benefit to people with special needs in eAccessibility/eInclusion.    <br>   <b>Method: </b>document MoU/MG/05 N0221   ''Semantic Interoperability and the need for a coherent policy for a   framework of distributed, possibly federated repositories for all kinds   of content items on a world-wide scale''<a name="en2"></a><a href="#n2"><sup>2</sup></a>, which was adopted in 2005, was a first step towards the formulation of global interoperability requirements for structured   content. These requirements -based on advanced terminological   principles- were taken up in EU-projects such as IN-SAFETY   (INfrastructure and SAFETY) and OASIS (Open architecture for Accessible   Services Integration and Standardization).    <br>   <b>Results: </b>Content   integration and content interoperability are key concepts in connection   with the emergence of state-of-the-art distributed and federated databases/repositories of structured content. Given the fact that linguistic content items are increasingly   combined with or embedded in non-linguistic content items (and vice   versa), a systemic and generic approach to data modelling and content   management has become the order of the day. Fulfilling   the requirements of capability for multilinguality and multimodality,   based on open standards makes software and database design fit for   eAccessibility/eInclusion from the outset. It also makes structured   content capable for global content integration and content   interoperability, because it enhances its potential for being re-used   and re-purposed in totally different eApplications. Such content as well as the methods, tools and services applied can be subject to new kinds of certification schemes which also should be based on standards.    <br> <b>Conclusions: </b>Content must be totally reliable in some applications, e.g. in eAccessibility/ eInclusion. New methods and tools for certification, verification and validation   are largely facilitated by standards-based data-models and standardized   content, which will have an impact on future ICT-related standards in   general. While thus increasing the reliability of data, risk of all   sorts and liability will be reduced. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>Keywords: </b>international   standards, content repositories, standardized structured content,   standardized data models, content integration and interoperability,   verification, validation, certification, eAccessibility, eInclusion </font></p> <hr size=1 noshade>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>RESUMEN</b></font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>Objetivo: </b>demostrar que tanto los enfoques basados en est&aacute;ndares para la normalizaci&oacute;n y la gesti&oacute;n de   contenidos y para los servicios y las herramientas relacionados con los   contenidos, como sus respectivos sistemas de certificaci&oacute;n, no s&oacute;lo   garantizan la integraci&oacute;n y la interoperabilidad con-fiables de   contenidos, sino que, adem&aacute;s, benefician en particular a las personas   con necesidades especiales   en e-Accesibilidad / e-Inclusi&oacute;n.    <br>   M&eacute;todo: el documento ''Semantic   Interoperability and the need for a coherent policy for a framework of   distributed, possibly federated repositories for all kinds of content items on a world-wide scale'', que se adopt&oacute; en 2005, fue un primer paso en la formulaci&oacute;n de   requisitos globales de interoperabilidad para contenidos estructurados.   Dichos requisitos -fundamentados en principios terminol&oacute;gicos- se han   adoptado en proyectos de la Uni&oacute;n Europea como IN-SAFETY <i>(Infrastructure and Safety) </i>y OASIS <i>(Open architecture for Accessible Services Integration and Standardization)</i>.    <br>   <b>Resultados: </b>La integraci&oacute;n y la interoperabilidad de contenidos son   conceptos clave en relaci&oacute;n con la aparici&oacute;n de bases de datos /   repositorios de contenidos estructurados. Dado que los &iacute;tems de   contenido ling&uuml;&iacute;stico se combinan o se insertan cada vez m&aacute;s en &iacute;tems de   contenido no ling&uuml;&iacute;stico (y viceversa), un enfoque sist&eacute;mico y gen&eacute;rico   de modelaci&oacute;n de datos y gesti&oacute;n de contenidos est&aacute; a la orden del d&iacute;a.   Dicho sistema cumple los requisitos para el multiling&uuml;ismo y est&aacute;   basado en normas abiertas, de manera que, desde el principio, adapta el <i>software </i>y el diseno de bases de datos a la e-Accesibilidad / e-Inclusi&oacute;n. Adem&aacute;s, hace el contenido estructurado   adaptable a la integraci&oacute;n e interoperabilidad de contenidos, ya que   refuerza su potencial para ser reutilizado y redirigido en   e-aplicaciones totalmente distintas. Este contenido, al igual que los   m&eacute;todos, las herramientas y los servicios que se emplean, pueden ser   sometidos a nuevos tipos de esquemas de certificaci&oacute;n que est&eacute;n basados   en est&aacute;ndares.    ]]></body>
<body><![CDATA[<br> <b>Conclusi&oacute;n: </b>el contenido debe ser totalmente   confiable en algunas aplicaciones como e-Accesibilidad / e-Inclusi&oacute;n.   Nuevos modelos y herramientas para la certificaci&oacute;n, la verificaci&oacute;n y   la validaci&oacute;n son provistos por los modelos de datos basados en   est&aacute;ndares y en contenidos normalizados, que influenciar&aacute;n las futuras   normas de ICT <i>(Integration and Content Interoperability) </i>en general. Adem&aacute;s de aumentar la confiabilidad de los datos, disminuyen los riesgos de todo tipo y la responsabilidad. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>Palabras clave: </b>normas internacionales, repositorios de contenidos, contenido estructurado normalizado,   modelos de datos estructurados, integraci&oacute;n e interoperabilidad de   contenidos, verificaci&oacute;n, validaci&oacute;n, certificaci&oacute;n, e-Accessibilidad,   e-Inclusi&oacute;n </font></p> <hr size=1 noshade>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>R&Eacute;SUM&Eacute;</b></font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>Objectif: </b>d&eacute;montrer   qu'aussi bien les approches bas&eacute;es sur des standards pour la   normalisation et la gestion de contenus, pour les services et les outils   en rapport avec les contenus, que leurs systemes   de certification respectifs, ne garantissent pas seulement la fiabilit&eacute;   de l'int&eacute;gration et de l'interop&eacute;rabilit&eacute; de contenus, mais, de plus,   b&eacute;n&eacute;ficient notamment aux personnes qui ont des n&eacute;cessit&eacute;s sp&eacute;ciales en   e-Accessibilit&eacute;/e-Inclusion.    <br>   <b>M&eacute;thode: </b>le document MoU/MG/05 N0221    ''Semantic Interoperability and the need for a coherent policy for a framework of distributed, possibly federated repositories for all kinds of content items on a world-wide scale''   , adopt&eacute; en 2005, repr&eacute;sente   un premier pas dans la formulation de conditions requises globales   d'interop&eacute;rabilit&eacute; pour des contenus structur&eacute;s. Ces conditions requises   - bas&eacute;es sur des principes terminologiques - ont &eacute;t&eacute; adopt&eacute;es dans des   projets de l'UE comme IN-SAFETY (INfrastructure and SAFETY) et OASIS <i>(Open architecture for Accessible Services Integration and Standardization).    <br> </i><b>R&eacute;sultats: </b>l'int&eacute;gration et l'interop&eacute;rabilit&eacute; de contenus sont des concepts clefs en ce qui concerne l'apparition de bases de donn&eacute;es/r&eacute;servoir de contenus structur&eacute;s. Etant donn&eacute; que les items de contenu linguistique se combinent   et s'inserent toujours davantage a l'int&eacute;rieur des items de contenu non   linguistique (et viceversa), une approche syst&eacute;mique et g&eacute;n&eacute;rique de   mod&eacute;lation de donn&eacute;es et de gestion de contenus est a l'ordre du jour.   Le systeme en question remplit les conditions requises pour le   multilinguisme et se base sur des normes ouvertes, en sorte que depuis   le d&eacute;but, il adapte le software et le design de   bases de donn&eacute;es a e-Accessibilit&eacute;/e-Inclusion. De plus, il rend le   contenu structur&eacute; adaptable a l'int&eacute;gration et a l'interop&eacute;rabilit&eacute; de   contenus, renfor&ccedil;ant son potentiel afin d'etre r&eacute;utilis&eacute; et redirig&eacute; en e-applications bien distinctes. Ce contenu, les m&eacute;thodes, les outils et les services que l'on emploie peuvent etre soumis a de nouveaux types de sch&eacute;mas de certification fond&eacute;s sur des standards. <b>Conclusion: </b>le   contenu doit etre totalement fiable dans quelques applications comme   e-Accessibilit&eacute;/e-Inclusion. De nouveaux modeles et des outils pour la   certification, la v&eacute;rification et la validation sont fournis par les modeles de donn&eacute;es bas&eacute;es sur des standards et sur des contenus normalis&eacute;s,   lesquels influenceront les futures normes de CT en g&eacute;n&eacute;ral. En plus   d'augmenter la fiabilit&eacute; des donn&eacute;es, ils diminuent tout type de   risques, ainsi que la responsabilit&eacute; l&eacute;gale. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>Mots-cl&eacute;s: </b>normes internationales, r&eacute;servoirs de contenus, contenu structur&eacute; normalis&eacute;, modele de donn&eacute;es structur&eacute;es, int&eacute;gration et interop&eacute;rabilit&eacute; de contenus, v&eacute;rification, validation, certification, e-Accessibilit&eacute;, e-Inclusion </font></p> <hr size=1 noshade>     <p>&nbsp;</p>     <p>&nbsp;</p>     <p><font size="3" face="Verdana, Arial, Helvetica, sans-serif"><b>1. CONTENT IN EACCESSIBILITY/EINCLUSION SYSTEMS </b></font></p>     ]]></body>
<body><![CDATA[<p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Particularly   in the field of eAccessibility/eInclusion the use and re-use of all   kinds of content across different technical platforms is a must. On the   other hand, strongly heterogeneous content today in reality is more the   rule than the exception. Therefore, the consortium of the OASIS Project   has conceived a complementary project to formulate a standard which   makes ontologies in the field of ambient assisted living (AAL)   interoperable. As a matter of fact, many data in   eAccessibility/eInclusion are the same as or similar to those in   eHealth, for medical devices and in medical informatics. Although the   project is focused on AAL, the planned approach of the proposed project   is highly generic so that content interoperability aspects of the   related fields will be covered. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">While   in the past the development focus was on tools (i.e. devices, computer   hardware and software), it is increasingly recognized today that   ''communication'' ultimately is the most important issue, namely: </font></p> <ul>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">communication between impaired people (directly or through ICT devices),</font></li>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">communication between impaired people and the tools they use,</font></li>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">communication between the tools.   </font></li>     </ul>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">This   is why standardization of content-related aspects is gaining   importance. Therefore, metadata, data models, messages, protocols,   conversion of all sorts, multilinguality (incl. cultural diversity),   multimodality, design for all (DfA) among others have become the   objective of standardization efforts in industry, by specialized   organizations, in public institutions as can be gathered from the ISTSB   Report (2000). </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Ongoing   efforts, which are still little coordinated thus leading to a plethora   of competing ''standards'' (which are often even contradicting each   other), would - if not better coordinated - lead to a situation, where tools lose usefulness for   those who most urgently need them: people with special needs.   Therefore, recent efforts are focused on aspects related to content and   communication of ambient assisted living (AAL), which is widely covering   content aspects of eInclusion/eAccessibility, while not neglecting   endeavours undertaken in related domains, such as eHealth. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The   OASIS project coincides with a new megatrend in standardization, which   in the past 60 years had largely shifted from hardware and software in   the traditional sense towards methodology standardization. For a number   of years, however, the number of standards for services and content is   growing exponentially. People with special needs are among those who   will benefit most from this development. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">eBusiness   is leading the field with the standardization of structured content (in   ISO: ''database standards'') and the standardization of the methodology   related to such content. In the field of eBusiness it has been   recognized that only standardization approaches to structured content   and its related services and tools can bring about the intended   efficiencies and guarantees for reliability and other benefits. </font></p>     ]]></body>
<body><![CDATA[<p>&nbsp;</p>     <p><font size="3" face="Verdana, Arial, Helvetica, sans-serif"><b>2. DEFINITIONS </b></font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">This contribution focuses on <b><i>structured content </i></b>at the level of lexical semantics, such as: </font></p> <ul>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Lexicographical data;</font></li>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Terminology and similar kinds of language resources, such as: </font></li>       <ul type="circle">             <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">nomenclatures, taxonomies, typologies etc., </font></li>             <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">glossaries, vocabularies etc., </font></li>             <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">terminological phraseology, morphology, </font></li>             <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">graphical symbols and other non-linguistic representations, </font></li>             <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">properties, characteristics, attributes, etc., </font></li>             ]]></body>
<body><![CDATA[<li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">proper names, addresses and other items of all kinds of directories; </font></li>           </ul>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Thesauri, classification schemes, keywords and other kinds of documentation languages;</font></li>           <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Encyclopaedic (knowledge) entries, covering among others:                  </font>         <ul type="circle">               <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">knowledge-enriched terminology entries, </font></li>             <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">(explained) proper names and other kinds of data closely related to names; </font></li>             </ul>       </li>      <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Ontologies,   topic maps and other kinds of knowledge-structuring systems, which in   reality -more often than not- are contradictory, not coherent, not   possible to integrate, not reliable, and full of deficits, if needed in   applications which support people with special needs. This situation is   becoming unacceptable, especially in our aging societies, where more and   more people suffer from multiple impairments.</font></li>     </ul>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The above-mentioned kinds   of structured content in the form of <b><i>language resources</i></b>,   which are increasingly supplemented by non-verbal representations -   here multimodality comes into the picture-, are not the only kinds of   structured content which are necessary for efficient communication.   Further kinds may be needed, such as:</font></p> <ul>    ]]></body>
<body><![CDATA[<li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Information on services, covering among others:</font></li>     <ul type="circle">           <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">(product) classification and nomenclatures, catalogue data, properties etc. for services, </font></li>           <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">conditions of rendering the respective service, </font></li>           <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">qualification services, for instance, to train skills or improve human qualifications, </font></li>         </ul>     <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Directory information, such as:</font></li>   <ul type="circle">           <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">address and contact information of institutions/organizations/persons, </font></li>           <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">time-related information: opening hours, availability etc., </font></li>       </ul>     <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">GPS-related information, such as:</font></li>   <ul type="circle">           ]]></body>
<body><![CDATA[<li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">position/location, </font></li>           <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">guiding/steering information (incl. information on obstacles etc.). </font></li>       </ul>     </ul>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>2.2 Content Management Related Concepts </b></font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">In   order to manage these different types of structured information (today   mostly web-based and in distributed form) - so that the best suited   ''stakeholder'' for a given kind of content can ensure the maintenance,   updating and versioning as well as quality assurance of the content in a   most efficient way -, a number of additional elements are needed with   respect to content interoperability, such as: </font></p> <ul>     <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b><i>Metadata </i></b>(or data categories, as they are more precisely called in the field of terminology) and the respective <b><i>metadata registries</i></b>; </font></li>     <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b><i>Identification systems</i></b> for individual pieces of information. </font></li>     </ul>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">ISO/IEC-JTC   1/SC 32/WG 2 ''MetaData'' is the Working Group that formulates the   methodology standards on metadata and metadata registries (especially   the ISO/IEC 11179 MDR series). Within the framework of the MoU/MG there   are recommendations to harmonize a multitude of ID-systems for content   items, which are a great barrier to the efficient exchange of structured   content in a systematic way, including checking processes, like   certification and validation etc. In product data management for   eBusiness the trend goes in the direction of using ISO 29002-5 as an   open, non-proprietary standard as basis for applying an ID-system at the   highest level of content granularity. </font></p>     ]]></body>
<body><![CDATA[<p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">For   the sake of completeness it should be mentioned that the above-cited   approaches are increasingly applied also for the preparation and re-use   of textual and other unstructured content, e.g. in technical   communication, automatic and computer-assisted translation, etc. No   wonder that eInclusion/eAccessibility aspects are also discovered and   developed here. &#91;CEN CWA 15778:2008&#93; </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">In   this connection, interoperability needs to be seen through the eyes of   content - not only through the glasses of content management   systems.Then it can be recognized that content interoperability goes   beyond the concept of semantic interoperability, as it is generally   seen. <b><i>Content interoperability </i></b>is the capability of content items/ entities (i.e. structured content at the level of lexical semantics) to be: </font></p> <ul>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">integrated into or combined with other (types of) content items/entities; </font></li>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">extensively re-used for other purposes (also sub-items/entities to be re-usable); </font></li>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">searchable, retrievable, recombinable from different points-of-view. </font></li>     </ul>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>2.3 Standardization Related Concepts </b></font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Why   is standardization so important in this connection? Only international   standards guarantee the most efficient use and re-use of structured   content across language boundaries and system platforms. This efficient   use and reuse can only take place if two fundamental principles of content management methodology are realized: <b><i>single sourcing </i></b>and <b><i>resource-sharing</i></b>.   The above remarks lead to some reflection on the nature of   standardization and the benefits of standardization for communication in   eInclusion/eAccessibility. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b><i>Standardization </i></b>is an activity for establishing, with regard to <i>actual or potential problems</i>, provisions for <i>common and repeated use</i>, aimed at the <i>achievement of the optimum degree of order in a given context</i>.   In particular, the activity consists of the processes of formulating,   issuing and implementing standards. Important benefits of   standardization are the improvement of the <i>suitability of products, processes and services for their intended purposes</i>, <i>prevention of barriers to trade </i>and <i>facilitation of technological cooperation</i>.   (ISO/IEC Guide 2: 2004) Standardization endeavours are governed by   highly systemic approaches. In particular, methodology standards aim at   generic solutions, which are also applicable in other eApplications. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The preparation of standards is based on <b><i>consensus</i></b>, which is a <i>general agreement</i>, characterized by the <i>absence of sustained opposition to substantial issues </i>by any important part of the <i>concerned interests </i>and by a <i>process that involves seeking to take into account the views of all parties </i>(namely industry, research, public administration, consumers) concerned and to <i>reconcile any conflicting arguments</i>.   (ISO/IEC Guide 2:2004) Therefore, standards published by standards   organizations are called ''open standards'' in contrast to ''industry   standards'', which usually are proprietary. Huge efforts are undertaken   to harmonize existing open standards at national, regional and   international levels so that they do not contradict each other.   Naturally this is less the case with industry standards. </font></p>     ]]></body>
<body><![CDATA[<p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>2.4 Certification Related Concepts </b></font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b><i>Certification </i></b>is defined as a <i>procedure </i>by which a <i>third party </i>gives <i>written assurance </i>that a <i>product</i>, <i>process </i>or <i>service </i>conforms to <i>specified requirements. </i>&#91;ISO   14050:2006&#93; No doubt services can be certified. Certification involves a   number of documented processes, at the end of which there is a   documented assessment result. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The   fact that data structures and content should be standards-compliant   and, if they are, can be certified, is a relatively new conception. This   standards compliance needs to be assessed according to <i>validation/verification criteria, </i>defined   as policy, procedure or requirement used as a reference against which   evidence is compared. In this connection, two closely related <i>systematic, independent and documented processes</i> are of relevance: </font></p> <ul>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b><i>Verification </i></b>uses <i>objective evidence </i>that (<i>specified) requirements </i>which   define an intended use or application have been met for the sake of the   evaluation of assertions against agreed verification criteria. Whenever   specified requirements have been met, a verified status is achieved. </font></li>     <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b><i>Validation </i></b>uses <i>objective evidence </i>to confirm that (<i>specified) requirements </i>which   define an intended use or application have been met. Whenever all   requirements have been met, a validated status is achieved. </font></li>     </ul>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">There are many ways to <i>verify </i>that   requirements have been met, such as doing tests, performing   demonstrations, carrying out alternative calculations, comparing a new   design specification with a proven design specification, or inspecting   documents before one issues them. The process of <i>validation </i>can   be carried out under realistic use conditions or within a simulated use   environment. See: <a href="http://www.praxiom.com/iso-definition.htm#Quality" target="_blank">http://www.praxiom.com/iso-definition.htm#Quality</a> </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The   concepts emerged after many years of discussion of standards-based   quality management systems and their requirements. In this connection <b><i>quality </i></b>has been explained in many sources as the <i>totality of features and characteristics of a product or service </i>that bear on its <i>ability to satisfy stated or implied needs</i>.   The quality of data and data-related services and tools has only   recently entered the radar of quality assessment and certification   approaches. Needless to say that the potential for quality of data and   related services and tools is higher than if they are not   standards-based. In any case, the need for reliability of some data in   eInclusion/eAccessibility applications has to be much higher than that   in many other content repositories. The use of standards-based   approaches here reduces risks and thus liability in cases of mishaps or   accidents. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b><i>Quality </i></b>of something as defined by international standards is a relative concept which: </font></p>  <ul>     <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">can be determined by comparing a set of inherent characteristics with a set of requirements; <i>If   those inherent characteristics meet all requirements, high or excellent   quality is achieved. If those characteristics do not meet all   requirements, a low or poor level of quality is achieved. </i></font></li>     ]]></body>
<body><![CDATA[<li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">therefore,   is a question of degree; As a result, the central quality question is:   How well does this set of inherent characteristics comply with this set   of requirements? In short, the quality of something depends on a set of   inherent characteristics and a set of requirements and how well the   former complies with the latter. </font></li>     </ul>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">By   linking quality to requirements, ISO 9000 argues that the quality of   something   cannot be established in a vacuum.Quality is always relative to a set of requirements.   See <a href="http://www.praxiom.com/iso-definition.htm#Quality" target="_blank">http://www.praxiom.com/iso-definition.htm#Quality</a></font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The assessment of quality management systems and services takes place by means of an <b><i>audit</i></b>, which is a <i>systematic, independent and documented process </i>for obtaining <i>audit evidence </i>and evaluating it objectively to determine the extent to which the <i>audit criteria </i>are fulfilled. <b><i>Audit criteria </i></b>are a set of policies, procedures or requirements used as a reference against which <i>audit evidence </i>is compared. One distinguishes between <b><i>internal audits </i></b>(sometimes called <i>firstparty audits</i>) and <b><i>external audits </i></b>(including those generally termed <i>second-and third-party audits</i>).   &#91;ISO 19011&#93; Third-party audits are conducted by external, independent   auditing organizations, such as those providing registration or <i>certification</i> of conformity to the requirements of ISO 9001 or ISO 14001. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">While   quality assessment and certification through audits is relatively well   developed in industry and services, the verification and validation of   structured content and related services and tools is still in its   infancy. Factual and physical properties based data can comparatively   easily be validated. Other properties, e.g.   those relating to ''soft'' criteria, such as functions, can probably only   be validated, if validation is against a limited number of pre-defined   values. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>2.5 Special Case: Skills Certification in the ICT Field </b></font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">eCertification   (or ICT certification) in Europe can be considered as the set of   processes by which an individual gains a credential in a particular ICT   skill or,   more generally, in a range of skills. Such credentials are usually   granted by recognized bodies, themselves often but not always accredited   by some governmental or official organization. In order to attain the   qualification, that individual must achieve a declared standard, judged   by a formal assessment process. The whole scheme is governed by quality   assurance processes, covering both the development and maintenance of   the skills standard, and the assessment procedures. See: CWA 00000: 2009   ''ICT Certification in Europe'' (in print) </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">CWA 00000: 2009 refers to the following definitions of eCertification: </font></p>     <blockquote>       <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">(1)   ''Certification   often means the awarding of a certificate, or other testimonial, that   formally recognizes and records success in the assessment of Knowledge,   Skills and/or Competencies, as the final step in the completion of a   Qualification. However, it is also used, in particular in relation to   ICT Practitioner occupations, to mean the Qualification as a whole. It   is important to be aware of these two (''narrow'' and ''broad'') meanings of   Certification.'' &#91;Dixon and Beier in CWA 15515: 2006&#93;</font></p>       ]]></body>
<body><![CDATA[<p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">(2)    ''Certification   is the process of formally validating knowledge, knowhow and/or skills   and competencies acquired by an individual, following a standard   assessment procedure. Certificates or diplomas are issued by accredited   awarding bodies''. &#91;Tissot: 2004 in CWA 00000: 2009&#93;</font></p>       <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">(3)    ''In   general, ICT professional certifications are seen as a credential - the   result of an objective assessment procedure run by an approved third   party, in which an individual meets the performance specifications   delineated in job profiles whichare recognisedby industrystakeholders.''   &#91;CEPIS: 2007;Cedefop:2006&#93;. </font></p> </blockquote> <ul>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">There are three ISO standards related to eCertification, namely: </font></li>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">ISO/IEC 17024:2003 ''Conformity Assessment - General requirements for bodies operating certification of persons'' </font></li>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">ISO/IEC TR 19759:2005 ''Software Engineering - Guide to the Software Engineering Body of Knowledge (SWEBOK)'' </font></li>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">ISO/IEC 24773:2008 ''Certification of software engineering professionals </font></li>     </ul>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">These   standards seem to have relatively little effect on the proliferation of   qualification and certification schemes on the market. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">While   it can be recognized that certification provides value in both the   labour and product segments of the ICT market, the report &#91;CEPIS: 2007&#93;   describes over 600 often overlapping qualifications from over 60   providers as a ''certification jungle'', causing confusion to prospective   users. The rapid growth in these industry qualifications has been driven   by the market over recent years, indeed the market barely existed 15   years ago. They usually relate to a more specific set of skills,   including for specific products, and are generally more practical in   their approach than traditional academic qualifications. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">As   these market certifications contrast and co-exist with the historic   universitybased education system, leading to the phrase ''parallel   universe'', there remains resistance, even hostility, in some academic   quarters in some countries, to these certification schemes.They are seen   as developing skills not education, and product ability not underlying   theory, little more than marketing aids to the commercial interests of   thevendors.On the other hand, their globalapplication contrasts with the   national or even self-accreditation of most university degrees.   &#91;CWA00000: 2009&#93; </font></p>     ]]></body>
<body><![CDATA[<p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Concerning   the skills and qualifications necessary for being familiar with the   issues involved in content interoperability available training and   studies are not sufficient - even if certified. </font></p>     <p>&nbsp;</p>     <p><font size="3" face="Verdana, Arial, Helvetica, sans-serif"><b>3. IMPLEMENTATION CASE: THE EU-PROJECT OASIS </b></font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">OASIS   (Open architecture for Accessible Services Integration and   Standardization), an ongoing European large-scale Integrated Project   within the 7th Framework Programme, started in January 2008 for a period   of four years. OASIS aims at an open and innovative reference   architecture, based upon ontologies and semantic services, which will   allow plug and play and costeffective interconnection of existing and   new services in all domains required for the independent and autonomous   living of the elderly and their Quality of Life enhancement (for this   and the following see Bekiaris and Bateman, 2009). </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Achieving   practical interoperability has to be one component of a general   strategy for enabling information from different parts of a single   organization or from different organizations to be bound together, to   act as a multiplier for   application opportunities. Moreover, in some domains, the requirements   of appropriate interoperability are even more important. In the   provision and support of environments and services for the ageing   population, the consequences of poor quality decisions, increased   maintenance costs, and inflexible integration, brought about by   inappropriate inferences and inconsistent knowledge, can lead directly   to risky situations. For the user affected this is not only   unacceptable, but may even be life-threatening. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The   OASIS development will provide an open source complementary solution to   the direction now being pursued in the SemanticWeb approach to ontology   design: whereas in the Semantic Web re-usability is pursued across open   ontologies, the OASIS solution will show how re-usability can be   achieved following the tried and tested results of decades of practical   experience in software engineering. Crucially, the open Semantic Web   approach entails that small local modules may have global side-effects   (for example, by changing class membership); in contrast, the OASIS   hyper-ontology will demonstrate how interoperability can be achieved   within strict modularity. Side effects in software design are a source   of major system instability, development and maintenance costs -   avoiding them for ontology design will therefore be a major innovative   contribution of considerable benefit. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The above-mentioned DfA Report comprises a review of standards in the field according to: </font></p> <ul>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Level 1: general requirements for technical aids, </font></li>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Level 2: particular requirements for families of technical aids, </font></li>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Level 3: Specific requirements for types of technical aids, </font></li>     ]]></body>
<body><![CDATA[</ul>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">referring   to standards at international, regional and national levels. The aspect   most underrepresented here is communication and content to enable   communication, as well as the respective standards. The OASIS Project   aims to fill this gap by developing a Common Ontological Framework,   which will also be introduced into standardization. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Needless   to mention that the open source Common Ontological Framework of the   OASIS Project will follow the MoU/MG recommendation of 2005, which states as basic requirements for the development of fundamental methodology standards concerning content interoperability: </font></p>  <ul>     <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Multilinguality and cultural diversity, </font></li>     <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Multimodality, </font></li>     <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Accessibility (covering also eInclusion), </font></li>     <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Multi-channel   presentations, which have to be considered at the earliest stage of   software design before implementation &#91;Bekiaris and Bateman, 2009&#93;.</font></li>     </ul>     <p>&nbsp;</p>     <p><font size="3" face="Verdana, Arial, Helvetica, sans-serif"><b>4. SUMMARY AND OUTLOOK </b></font></p>     ]]></body>
<body><![CDATA[<p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Content   integration - whether in the form of virtual or real data integration -   and content interoperability must be based among others on: </font></p> <ul>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Consistent methodology standards for datamodels and data modelling; </font></li>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Coordinated standardization of several kinds of structured content; </font></li>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Standardized identification systems for individual pieces of information; </font></li>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Standardized transfer protocols and interchange formats; in order to be efficient and reliable. </font></li>     </ul>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">At   present, standardization in eBusiness is leading the field with highly   generic methodology standards and the implementation of content   repositories with standardized structured content. The EU-Project OASIS   attempts to combine the results of a number of past projects with best   practices in the field of structured content preparation and maintenance   as well as with respect to content integration. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">In   certain cases there is a definite need for certification, validation or   verification of data. The respective standardization efforts are still   in their infancy. Some kinds of certification, validation or   verification can possibly be done through web services. These and other   kinds of certification should </font></p> <ul>       <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">particularly benefit small content and service providers; </font></li>     <li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">be affordable; </font></li>     ]]></body>
<body><![CDATA[<li><font size="2" face="Verdana, Arial, Helvetica, sans-serif">fit the kind of service, the technical state-of-the-art at the service providers' side and the expectations of the clients.</font></li>     </ul>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Coordination   and harmonization efforts supported by the EU Commission have a   positive effect on the development of technical, organizational and   content interoperability standards as well as standards-based content   repositories, which will benefit people with special needs. </font></p>     <p>&nbsp;</p>     <p><font size="3" face="Verdana, Arial, Helvetica, sans-serif"><b>REFERENCES </b></font></p>     <!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">1. Bekiaris,   E. D. &amp; Bateman, J.A. (2009). Content Interoperability   Standardization. The open Reference Architecture of the OASIS Project   with its open source Common Ontological Framework and related tools. China Standardization, Special edition 2009. Beijing 2009, pp. 41-44. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000158&pid=S0123-3432201000020000600001&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">2. CEPIS   (ed.). Survey of Certification Schemes for ICT Professionals across   Europe towards Harmonisation (HARMONISE).   <a href="http://www.cepis-harmonise.org" target="_blank">http://www.cepis-harmonise.org</a>, September 2007, Project of CEPIS Council   of European Professional Informatics Societies, final report. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000159&pid=S0123-3432201000020000600002&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">3. Cedefop   (ed.). ICT Skills Certification in Europe. Cedefop Dossier series 13.   Luxembourg: Office for Official Publications of the European   Communities, 2006. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000160&pid=S0123-3432201000020000600003&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">4. ICTSB   (ed.). Design for All. ICTSB Project Team Final Report (2000)   <a href="http://www.ictsb.org/Activities/Design_for_All/Documents/ICTSB Main Report .pdf" target="_blank">http://www.ictsb.org/Activities/Design_for_All/Documents/ICTSB%20Main%20Report%20.pdf</a>. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000161&pid=S0123-3432201000020000600004&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">5. MoU/MG:2004   Semantic Interoperability and the need for a coherent policy for a   framework of distributed, possibly federated repositories for all kinds   of content items on a worldwide scale (MoU/MG/05 N0221 adopted in 2005). </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000162&pid=S0123-3432201000020000600005&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">6. MoU/MG:2004 Statement on eBusiness Standards and Cultural Diversity (MoU/MG/05 N0222 adopted in 2006). </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000163&pid=S0123-3432201000020000600006&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">7. ISO/IEC Guide 2:2004. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000164&pid=S0123-3432201000020000600007&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">8. ISO 8000 (series). Data quality. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000165&pid=S0123-3432201000020000600008&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">9. ISO 9000:2005. Quality management systems - Fundamentals and vocabulary. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000166&pid=S0123-3432201000020000600009&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">10. ISO 9001:2000. Quality management systems - Requirements. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000167&pid=S0123-3432201000020000600010&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">11. ISO/IEC 11179 (series). Information technology - Metadata registries (MDR). </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000168&pid=S0123-3432201000020000600011&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">12. ISO 14001:2004. Environmental management systems - Requirements with guidance for use. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000169&pid=S0123-3432201000020000600012&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">13. ISO 14050:2009.Environmental management - Vocabulary. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000170&pid=S0123-3432201000020000600013&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">14. ISO/IEC 17024:2003. ''Conformity Assessment - General requirements for bodies operating certification of persons''. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000171&pid=S0123-3432201000020000600014&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">15. ISO 19011:2002. Guidelines for quality and/or environmental management systems auditing. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000172&pid=S0123-3432201000020000600015&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">16. ISO/IEC TR 19759:2005. ''Software Engineering - Guide to the Software Engineering Body of Knowledge (SWEBOK)''. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000173&pid=S0123-3432201000020000600016&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">17. ISO/IEC TR 20943 (series). Information technology - Procedures for achieving metadata registry content consistency. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000174&pid=S0123-3432201000020000600017&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">18. ISO/IEC 24773:2008. Certification of software engineering professionals - Comparison framework. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000175&pid=S0123-3432201000020000600018&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">19. ISO/TS   29002-5:2009. Industrial automation systems and integration - Exchange   of characteristic data - Part 5: Identification scheme. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000176&pid=S0123-3432201000020000600019&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">20. CEN   CWA 15778:2008. Document Processing for Accessibility. CEN Workshop   Document Processing for Accessibility. WS/DPA: Brussels, 2008. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000177&pid=S0123-3432201000020000600020&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">21. CEN   CWA 15515:2006. European ICT Skills Meta-Framework - State-of-the-art   review, clarification of the realities, and recommendations for next   steps. CEN Workshop ICT-Skills (IT profiles and curricula). WS/ICT:   Brussels, 2006. </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000178&pid=S0123-3432201000020000600021&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">22. CWA   00000: 2009. ICT Certification in Europe. CEN Workshop ICT-Skills (IT   profiles and curricula). WS/ICT: Brussels, 2009 (in print). </font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000179&pid=S0123-3432201000020000600022&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><p>&nbsp;</p>     <p>&nbsp;</p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Recibido: 20-03-10    ]]></body>
<body><![CDATA[<br>   Aceptado: 20-04-10 </font></p>     <p>&nbsp;</p>     <p>&nbsp;</p>     <p><font size="3" face="Verdana, Arial, Helvetica, sans-serif"><b>NOTES</b></font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><a name="n1"></a><a href="#en1">1</a> This contribution was   partially funded by the EC FP7 project OASIS - Open architecture for   Accessible Services Integration and Standardization, Grant Agreement   No. 215754.</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">  <a name="n2"></a><a href="#en2">2</a>   <a href="http://isotc.iso.org/livelink/livelink/fetch/2000/2489/Ittf_Home/MoU-MG/Moumg221.pdf" target="_blank">http://isotc.iso.org/livelink/livelink/fetch/2000/2489/Ittf_Home/MoU-MG/Moumg221.pdf</a> </font></p>      ]]></body><back>
<ref-list>
<ref id="B1">
<label>1</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Bekiaris]]></surname>
<given-names><![CDATA[E. D.]]></given-names>
</name>
<name>
<surname><![CDATA[Bateman]]></surname>
<given-names><![CDATA[J.A.]]></given-names>
</name>
</person-group>
<article-title xml:lang="en"><![CDATA[Content Interoperability Standardization. The open Reference Architecture of the OASIS Project with its open source Common Ontological Framework and related tools]]></article-title>
<source><![CDATA[China Standardization, Special edition]]></source>
<year>2009</year>
<month>20</month>
<day>09</day>
<page-range>41-44</page-range><publisher-loc><![CDATA[Beijing ]]></publisher-loc>
</nlm-citation>
</ref>
<ref id="B2">
<label>2</label><nlm-citation citation-type="">
<collab>CEPIS</collab>
<source><![CDATA[Survey of Certification Schemes for ICT Professionals across Europe towards Harmonisation (HARMONISE)]]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B3">
<label>3</label><nlm-citation citation-type="book">
<collab>Cedefop</collab>
<source><![CDATA[ICT Skills Certification in Europe. Cedefop Dossier series 13]]></source>
<year>2006</year>
<publisher-loc><![CDATA[Luxembourg ]]></publisher-loc>
<publisher-name><![CDATA[Office for Official Publications of the European Communities]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B4">
<label>4</label><nlm-citation citation-type="">
<collab>ICTSB</collab>
<source><![CDATA[Design for All. ICTSB Project Team Final Report]]></source>
<year>2000</year>
</nlm-citation>
</ref>
<ref id="B5">
<label>5</label><nlm-citation citation-type="">
<source><![CDATA[Semantic Interoperability and the need for a coherent policy for a framework of distributed, possibly federated repositories for all kinds of content items on a worldwide scale]]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B6">
<label>6</label><nlm-citation citation-type="">
<source><![CDATA[Statement on eBusiness Standards and Cultural Diversity]]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B7">
<label>7</label><nlm-citation citation-type="">
<source><![CDATA[]]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B8">
<label>8</label><nlm-citation citation-type="">
<source><![CDATA[]]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B9">
<label>9</label><nlm-citation citation-type="">
<source><![CDATA[Quality management systems - Fundamentals and vocabulary]]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B10">
<label>10</label><nlm-citation citation-type="">
<source><![CDATA[Quality management systems - Requirements]]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B11">
<label>11</label><nlm-citation citation-type="">
<source><![CDATA[Information technology - Metadata registries (MDR)]]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B12">
<label>12</label><nlm-citation citation-type="">
<source><![CDATA[Environmental management systems - Requirements with guidance for use]]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B13">
<label>13</label><nlm-citation citation-type="">
<source><![CDATA[Environmental management - Vocabulary]]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B14">
<label>14</label><nlm-citation citation-type="">
<source><![CDATA[''Conformity Assessment - General requirements for bodies operating certification of persons'']]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B15">
<label>15</label><nlm-citation citation-type="">
<source><![CDATA[Guidelines for quality and/or environmental management systems auditing]]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B16">
<label>16</label><nlm-citation citation-type="">
<source><![CDATA[''Software Engineering - Guide to the Software Engineering Body of Knowledge (SWEBOK)'']]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B17">
<label>17</label><nlm-citation citation-type="">
<source><![CDATA[Information technology - Procedures for achieving metadata registry content consistency]]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B18">
<label>18</label><nlm-citation citation-type="">
<source><![CDATA[Certification of software engineering professionals - Comparison framework]]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B19">
<label>19</label><nlm-citation citation-type="">
<source><![CDATA[Industrial automation systems and integration - Exchange of characteristic data - Part 5: Identification scheme]]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B20">
<label>20</label><nlm-citation citation-type="">
<source><![CDATA[Document Processing for Accessibility. CEN Workshop Document Processing for Accessibility]]></source>
<year>2008</year>
<publisher-loc><![CDATA[Brussels ]]></publisher-loc>
</nlm-citation>
</ref>
<ref id="B21">
<label>21</label><nlm-citation citation-type="">
<source><![CDATA[European ICT Skills Meta-Framework - State-of-the-art review, clarification of the realities, and recommendations for next steps. CEN Workshop ICT-Skills (IT profiles and curricula)]]></source>
<year>2006</year>
<publisher-loc><![CDATA[Brussels ]]></publisher-loc>
</nlm-citation>
</ref>
<ref id="B22">
<label>22</label><nlm-citation citation-type="">
<source><![CDATA[ICT Certification in Europe. CEN Workshop ICT-Skills (IT profiles and curricula)]]></source>
<year>2009</year>
<publisher-loc><![CDATA[Brussels ]]></publisher-loc>
</nlm-citation>
</ref>
</ref-list>
</back>
</article>
