This case study is a follow-up to the Business Case on interconnecting business registers using the Core Business Vocabulary. It explains how organizations can be described in RDF using the Core Business Vocabulary and the Organization Ontology. To do this, it provides an example of a real organization, PricewaterhouseCoopers Enterprise Advisory a legal entity registered in the Belgian company register, which is then described in RDF using these specifications.
Retail Banking - an ontological example by Lauren MadarLauren Madar
How can Ontology benefit large organizations? Ontologies facilitate knowledge discovery and transfer across different domains, and here's a case for the retail banking industry, from the Fall 2014 class taught by Barry Smith, PhD at the University at Buffalo.
Challenges for the Future of Retail BankingDesignit
Digital transformation in retail banking is a thriving and complex phenomenon. We at Designit try to make sense of it by identifying leading trends in three deeply interdependent categories: new enabling technologies, new customer expectations, and new strategic trends. The future holds uncertainty and promise, but some immediate actions are patently necessary for banks that want to stay relevant in an increasingly dynamic scenario.
Implementation of Ontology Based Business Registries to Support e-CommerceGihan Wikramanayake
Manjith Gunatilaka, G N Wikramanayake, D D Karunaratna (2004) "Implementation of Ontology Based Business Registries to Support e-Commerce" In:6th International Information Technology Conference, Edited by:V.K. Samaranayake et al. pp. 222-231. Infotel Lanka Society, Colombo, Sri Lanka: IITC Nov 29-Dec 1, ISBN: 955-8974-01-3
Welcome to the new Enterprise Architecture Professional Journal! We serve practicing and aspiring enterprise architects, as well as those who apply the holistic perspective of enterprise architecture to other disciplines. EAPJ informs their daily work and benefits their careers with content that is focused, concise, authoritative, practical and accessible. In this column, we preview all articles and recommend introductory reading each piece that assumes specialized knowledge.
This issue focuses on how EA can empower organizations to achieve their goals. EA and quality expert Mike Novak compares the TOGAF® framework for enterprise architecture with the Baldrige approach to organizational performance assessment and improvement, and shows how organizations could benefit from integrating the two paradigms. This is a great article for all those who have wondered about the relationship between EA and quality practices, or would like to learn more about either paradigm. The article assumes a bit of familiarity with the TOGAF standard, so novices should consult one of the references at the end of this article.
This issue also features an interview with Mike Callahan, a senior partner in AgileLayer, a business architecture methodology, software and consulting provider. Mike Callahan introduces us to his area of expertise, and explains how business architects practice many of the approaches Mike Novak describes in his TOGAF/Baldrige article.
I’d like to thank our expert reviewers for this issue, Jeff Hensgen and Chris McCurdy. EAPJ needs additional seasoned professionals like them willing to willing to help develop and select the best articles.
This issue focuses on how EA can empower organizations to achieve their goals. EA and quality expert Mike Novak compares the TOGAF®1 framework for enterprise architecture with the Baldrige approach to organizational performance assessment and improvement, and shows how organizations could benefit from integrating the two paradigms. This is a great article for all those who have wondered about the relationship between EA and quality practices, or would like to learn more about either paradigm. The article assumes a bit of familiarity with the TOGAF standard, so novices should consult one of the references at the bottom of this page. This issue also features an interview with Mike Callahan, a senior partner in AgileLayer, a business architecture methodology, software and consulting provider. Mike Callahan introduces us to his area of expertise, and explains how business architects practice many of the methods Mike Novak describes in his TOGAF/Baldrige article.
Improving B2B Transactions by Exploiting Business RegistriesGihan Wikramanayake
Manjith Gunatilaka, G N Wikramanayake, D D Karunaratna (2004) "Improving B2B Transactions by Exploiting Business Registries" In:23rd National Information Technology Conference, pp. 103-109. Computer Society of Sri Lanka, Colombo: CSSL Jul 8-9, ISBN: 955-9155-12-1
A FRAMEWORK FOR BUILDING A MULTILINGUAL INDUSTRIAL ONTOLOGY: METHODOLOGY AND ...IJwest
As Web 3.0 is blooming, ontologies augment semantic Web with semi–structured knowledge. Industrial
ontologies can help in improving online commercial communication and marketing. In addition,
conceptualizing the enterprise knowledge can improve information retrieval for industrial applications.
Having ontologies combine multiple languages can help in delivering the knowledge to a broad sector of
Internet users. In addition, multi-lingual ontologies can also help in commercial transactions. This
research paper provides a framework model for building industrial multilingual ontologies which include
Corpus Determination, Filtering, Analysis, Ontology Building, and Ontology Evaluation. It also addresses
factors to be considered when modeling multilingual ontologies. A case study for building a bilingual
English-Arabic ontology for smart phones is presented. The ontology was illustrated using an ontology
editor and visualization tool. The built ontology consists of 67 classes and 18 instances presented in both
Arabic and English. In addition, applications for using the ontology are presented. Future research
directions for the built industrial ontology are presented.
Retail Banking - an ontological example by Lauren MadarLauren Madar
How can Ontology benefit large organizations? Ontologies facilitate knowledge discovery and transfer across different domains, and here's a case for the retail banking industry, from the Fall 2014 class taught by Barry Smith, PhD at the University at Buffalo.
Challenges for the Future of Retail BankingDesignit
Digital transformation in retail banking is a thriving and complex phenomenon. We at Designit try to make sense of it by identifying leading trends in three deeply interdependent categories: new enabling technologies, new customer expectations, and new strategic trends. The future holds uncertainty and promise, but some immediate actions are patently necessary for banks that want to stay relevant in an increasingly dynamic scenario.
Implementation of Ontology Based Business Registries to Support e-CommerceGihan Wikramanayake
Manjith Gunatilaka, G N Wikramanayake, D D Karunaratna (2004) "Implementation of Ontology Based Business Registries to Support e-Commerce" In:6th International Information Technology Conference, Edited by:V.K. Samaranayake et al. pp. 222-231. Infotel Lanka Society, Colombo, Sri Lanka: IITC Nov 29-Dec 1, ISBN: 955-8974-01-3
Welcome to the new Enterprise Architecture Professional Journal! We serve practicing and aspiring enterprise architects, as well as those who apply the holistic perspective of enterprise architecture to other disciplines. EAPJ informs their daily work and benefits their careers with content that is focused, concise, authoritative, practical and accessible. In this column, we preview all articles and recommend introductory reading each piece that assumes specialized knowledge.
This issue focuses on how EA can empower organizations to achieve their goals. EA and quality expert Mike Novak compares the TOGAF® framework for enterprise architecture with the Baldrige approach to organizational performance assessment and improvement, and shows how organizations could benefit from integrating the two paradigms. This is a great article for all those who have wondered about the relationship between EA and quality practices, or would like to learn more about either paradigm. The article assumes a bit of familiarity with the TOGAF standard, so novices should consult one of the references at the end of this article.
This issue also features an interview with Mike Callahan, a senior partner in AgileLayer, a business architecture methodology, software and consulting provider. Mike Callahan introduces us to his area of expertise, and explains how business architects practice many of the approaches Mike Novak describes in his TOGAF/Baldrige article.
I’d like to thank our expert reviewers for this issue, Jeff Hensgen and Chris McCurdy. EAPJ needs additional seasoned professionals like them willing to willing to help develop and select the best articles.
This issue focuses on how EA can empower organizations to achieve their goals. EA and quality expert Mike Novak compares the TOGAF®1 framework for enterprise architecture with the Baldrige approach to organizational performance assessment and improvement, and shows how organizations could benefit from integrating the two paradigms. This is a great article for all those who have wondered about the relationship between EA and quality practices, or would like to learn more about either paradigm. The article assumes a bit of familiarity with the TOGAF standard, so novices should consult one of the references at the bottom of this page. This issue also features an interview with Mike Callahan, a senior partner in AgileLayer, a business architecture methodology, software and consulting provider. Mike Callahan introduces us to his area of expertise, and explains how business architects practice many of the methods Mike Novak describes in his TOGAF/Baldrige article.
Improving B2B Transactions by Exploiting Business RegistriesGihan Wikramanayake
Manjith Gunatilaka, G N Wikramanayake, D D Karunaratna (2004) "Improving B2B Transactions by Exploiting Business Registries" In:23rd National Information Technology Conference, pp. 103-109. Computer Society of Sri Lanka, Colombo: CSSL Jul 8-9, ISBN: 955-9155-12-1
A FRAMEWORK FOR BUILDING A MULTILINGUAL INDUSTRIAL ONTOLOGY: METHODOLOGY AND ...IJwest
As Web 3.0 is blooming, ontologies augment semantic Web with semi–structured knowledge. Industrial
ontologies can help in improving online commercial communication and marketing. In addition,
conceptualizing the enterprise knowledge can improve information retrieval for industrial applications.
Having ontologies combine multiple languages can help in delivering the knowledge to a broad sector of
Internet users. In addition, multi-lingual ontologies can also help in commercial transactions. This
research paper provides a framework model for building industrial multilingual ontologies which include
Corpus Determination, Filtering, Analysis, Ontology Building, and Ontology Evaluation. It also addresses
factors to be considered when modeling multilingual ontologies. A case study for building a bilingual
English-Arabic ontology for smart phones is presented. The ontology was illustrated using an ontology
editor and visualization tool. The built ontology consists of 67 classes and 18 instances presented in both
Arabic and English. In addition, applications for using the ontology are presented. Future research
directions for the built industrial ontology are presented.
A FRAMEWORK FOR BUILDING A MULTILINGUAL INDUSTRIAL ONTOLOGY: METHODOLOGY AND...dannyijwest
As Web 3.0 is blooming, ontologies augment semantic Web with semi–structured knowledge. Industrial
ontologies can help in improving online commercial communication and marketing. In addition,
conceptualizing the enterprise knowledge can improve information retrieval for industrial applications.
Having ontologies combine multiple languages can help in delivering the knowledge to a broad sector of
Internet users. In addition, multi-lingual ontologies can also help in commercial transactions. This research
paper provides a framework model for building industrial multilingual ontologies which include Corpus
Determination, Filtering, Analysis, Ontology Building, and Ontology Evaluation
The document discusses ontologies, including:
1) It defines ontologies as formal specifications of concepts and relationships that can exist for an agent or community. Ontologies allow knowledge to be shared and reused.
2) Ontologies can be used to facilitate knowledge management, enable learning about a domain, and enable intelligent search and query expansion.
3) The document provides guidance on developing ontologies, including researching the domain, using existing resources, defining classes and properties, and choosing an ontology language.
A Survey of Ontology-based Information Extraction for Social Media Content An...ijcnes
The amount of information generated in the Web has grown enormously over the years. This information is significant to individuals, businesses and organizations. If analyzed, understood and utilized, it will provide a valuable insight to its stakeholders. However, many of these information are semi-structured or unstructured which makes it difficult to draw in-depth understanding of the implications behind those information. This is where Ontology-based Information Extraction (OBIE) and social media content analysis come into play. OBIE has now become a popular way to extract information coming from machine-readable sources. This paper presents a survey of OBIE, Ontology languages and tools and the process to build an ontology model and framework. The author made a comparison of two ontology building frameworks and identified which framework is complete.
This document discusses whether business process integration is feasible through the use of enterprise application integration (EAI) technology. It first provides background on business process integration and past approaches using ERP systems. It then explains that EAI offers a more flexible way to integrate business processes and systems without needing to change existing business processes or software. The document presents a case study that explores how a company implemented an EAI solution and whether it enabled the integration of business processes. The case study findings suggest that EAI technology can integrate business processes when combined with ERP systems in a more flexible manner.
The document discusses challenges that multi-site organizations face in connecting corporate policies and manuals to location-specific documents. It proposes using a Manual Reference Matrix to systematically reference site-specific supporting documents from the corporate quality manual. The Manual Reference Matrix lists each location and links to their individual matrix. This allows the corporate manual to maintain common requirements while accommodating differences in scope, exclusions or documents between locations. It also discusses controlling the matrix template to ensure consistency across locations.
An Ontology-Based Information Extraction Approach For R Sum SRichard Hogue
This document discusses developing an ontology-driven information extraction system called the Ontology-based Résumé Parser (ORP) to extract information like experiences, qualifications, education, and personal details from millions of résumés in English and Turkish. The system uses various domain ontologies within its Ontology Knowledgebase to semantically parse résumés and match concepts. It aims to assist with expert finding and skills aggregation by analyzing data semantically rather than just syntactically matching keywords. The Résumé Ontology is described in detail to represent information typically included in résumés through semantic annotations.
Putting Controlled Vocabulary To Work I Davis 2008Ian Davis
The document discusses strategies for developing and implementing controlled vocabularies. It addresses the challenges of uncontrolled vs. controlled vocabularies and outlines a multi-step strategy for creation, maintenance, and integration across systems. Key points include stating the business case, gaining organizational buy-in, determining standards and scope, and leveraging semantic relationships between terms to improve search capabilities.
ESWC2008 Identity OpenLink - On The Evolution of Termsrumito
The document discusses the evolution of terms and language for describing data on the semantic web. It argues that creating a perfectly uniform language from scratch has generally failed, and that natural languages and terminology evolve most successfully through distributed community practice and reuse of existing terms. The semantic web aims to leverage existing semantic hubs and allow for diversity and heterogeneity of descriptions while making context and relationships between terms explicit.
Keystone Summer School 2015: Mauro Dragoni, Ontologies For Information RetrievalMauro Dragoni
The presentation provides an overview of what an ontology is and how it can be used for representing information and for retrieving data with a particular focus on the linguistic resources available for supporting this kind of task. Overview of semantic-based retrieval approaches by highlighting the pro and cons of using semantic approaches with respect to classic ones. Use cases are presented and discussed
Proposal of an Ontology Applied to Technical Debt on PL/SQL DevelopmentJorge Barreto
The document proposes an ontology for technical debt in PL/SQL development. It discusses relevant concepts like ontologies, technical debt, and PL/SQL. An initial model is developed in Protégé with five types of technical debt - documentation, requirements, tests, design, and code. The model could be expanded to include more debt types and relationships. The ontology provides a standardized vocabulary to describe technical debt for PL/SQL developers.
This document provides an overview of Oracle Corporation and its business. It discusses that Oracle is the world's largest enterprise software company that develops and markets database management systems and enterprise software. It also discusses Oracle's acquisition strategy and organization into software and services businesses. The software business is divided into new software licenses and software license updates/support, while the services business is divided into consulting, On Demand, and education. It provides details on Oracle's flagship database product and middleware products.
Metadata for Terminology / KOS ResourcesMarcia Zeng
1. Why do we need metadata for terminology resources? 2. What do we need to know about a terminology resource? 3. Is there a standardized set of metadata elements for terminology resources?-- a presentation at the "New Dimensions in Knowledge Organization Systems", a Joint NKOS/ CENDI Workshop, World Bank, Washington, DC. September 11, 2008 http://nkos.slis.kent.edu/2008workshop/NKOS-CENDI2008.htm
The Truth about Content: Learning from the Past in order to Succeed in the Fu...Scott Abel
This presentation will throw a spotlight onto the single most common,
and most serious, reason why Content Management projects fail. In a
nutshell, too many projects become so focused on the technology they
want to deploy that they forget about what matters most - the content
and the people who use it. Real-life case studies will be used to
illustrate this problem. The optimism of the audience will be rebuilt
by introducing a proven solution to this issue with this being a call
to move the focus of CM project towards Content Oriented Architectures.
The most common mistake found in content management projects is rather
surprising. The reason most CM projects falter is that the project
team, and frequently its stakeholders, become unduly enamored with
some piece of technology and assume, or hope, that one or two
applications will erase all of the challenges surrounding the
creation, management, reuse and delivery of content. When a particular
collection of applications fail to deliver on the expectations, the
usual response is to insert even more applications. With each new
application that is introduced, a number of connectors and patches are
also added so that one tool can work with the others that are already
in place. This continues until, with seeming inevitability, these
projects crumble under the weight of growing system complexity. These
projects fail, in short, because, in becoming fixated on technology,
they essentially forget about their content.
This presentation will use a number of project cases studies, some
older and some exceedingly current, to illustrate the downward path
that most CM projects follow. While this might sound ominous, this
journey will actually arrive at a hopeful conclusion. If CM projects
place content at the center of their solution designs, adopting in
effect a Content Oriented Architecture (COA), it becomes possible for
projects to use technology, even exploit it, in ways that emphasize
helping authors, publishers and content users. Under this model, the
quality and usefulness of the content assets becomes the overriding
focus and where automation is introduced it is to either further
improve the quality of the content or to reduce the cost and effort
needed to achieve the desired results. Examples of successful projects
will be used to prove that Content Oriented Architectures are not
really new and that they do deliver results that endure over time.
Presentation made in the context of the FAO AIMS Webinar titled “Knowledge Organization Systems (KOS): Management of Classification Systems in the case of Organic.Edunet” (http://aims.fao.org/community/blogs/new-webinaraims-knowledge-organization-systems-kos-management-classification-systems)
21/2/2014
The objective of this webinar is to provide a brief overview of the Knowledge Organization Systems (KOS) and the tools used for managing them. The presentation will focus on the management of the multilingual Organic.Edunet ontology as a case study. In this context it will present aspects such as the collaborative work, multilinguality needs and update of the concepts using an online KOS management tool (MoKi).
Semantic Rules Representation in Controlled Natural Language in FluentEditorCognitum
Abstract. The purpose of this paper is to present a way of representation of semantic rules (SWRL) in controlled natural language (English) in order to facilitate understanding the rules by humans interacting with a machine. The rule representation is implemented in FluentEditor – ontology editor with controlled natural language (CNL). The representation can be used in a lot of domains where people interact with machines and use specialized interfaces to define knowledge in a system (semantic knowledge base), e.g. representing medical knowledge and guidelines, procedures in crisis management or in management of any coordination processes. Such knowledge bases are able to support decision making in any discipline provided there is a knowledge stored in a proper semantic way.
The document discusses the need for an SOA registry repository to manage growing complexity in SOA deployments. As services become more complex, with multiple related artifacts, informal management is insufficient. A registry repository acts as a central point of control and system of record to govern the service lifecycle according to organizational policies. It functions similar to a library, containing artifacts and metadata to describe them, and enables management of information across the full lifecycle from a single source of reference. The registry repository is positioned as an increasingly important component for handling challenges that arise in large scale SOA ecosystems.
Semantic Web: Technolgies and Applications for Real-WorldAmit Sheth
Amit Sheth and Susie Stephens, "Semantic Web: Technolgies and Applications for Real-World," Tutorial at 2007 World Wide Web Conference, Banff, Canada.
Tutorial discusses technologies and deployed real-world applications through 2007.
Tutorial description at: http://www2007.org/tutorial-T11.php
This presentation has some helpful advice for Department of Defense (DoD) Communities of Interest (COI) when they are creating ontologies: 1) start with simple lists... them move forward.
More Related Content
Similar to How to describe registered organisations using the Registered Organization vocabulary and the Organization Ontology
A FRAMEWORK FOR BUILDING A MULTILINGUAL INDUSTRIAL ONTOLOGY: METHODOLOGY AND...dannyijwest
As Web 3.0 is blooming, ontologies augment semantic Web with semi–structured knowledge. Industrial
ontologies can help in improving online commercial communication and marketing. In addition,
conceptualizing the enterprise knowledge can improve information retrieval for industrial applications.
Having ontologies combine multiple languages can help in delivering the knowledge to a broad sector of
Internet users. In addition, multi-lingual ontologies can also help in commercial transactions. This research
paper provides a framework model for building industrial multilingual ontologies which include Corpus
Determination, Filtering, Analysis, Ontology Building, and Ontology Evaluation
The document discusses ontologies, including:
1) It defines ontologies as formal specifications of concepts and relationships that can exist for an agent or community. Ontologies allow knowledge to be shared and reused.
2) Ontologies can be used to facilitate knowledge management, enable learning about a domain, and enable intelligent search and query expansion.
3) The document provides guidance on developing ontologies, including researching the domain, using existing resources, defining classes and properties, and choosing an ontology language.
A Survey of Ontology-based Information Extraction for Social Media Content An...ijcnes
The amount of information generated in the Web has grown enormously over the years. This information is significant to individuals, businesses and organizations. If analyzed, understood and utilized, it will provide a valuable insight to its stakeholders. However, many of these information are semi-structured or unstructured which makes it difficult to draw in-depth understanding of the implications behind those information. This is where Ontology-based Information Extraction (OBIE) and social media content analysis come into play. OBIE has now become a popular way to extract information coming from machine-readable sources. This paper presents a survey of OBIE, Ontology languages and tools and the process to build an ontology model and framework. The author made a comparison of two ontology building frameworks and identified which framework is complete.
This document discusses whether business process integration is feasible through the use of enterprise application integration (EAI) technology. It first provides background on business process integration and past approaches using ERP systems. It then explains that EAI offers a more flexible way to integrate business processes and systems without needing to change existing business processes or software. The document presents a case study that explores how a company implemented an EAI solution and whether it enabled the integration of business processes. The case study findings suggest that EAI technology can integrate business processes when combined with ERP systems in a more flexible manner.
The document discusses challenges that multi-site organizations face in connecting corporate policies and manuals to location-specific documents. It proposes using a Manual Reference Matrix to systematically reference site-specific supporting documents from the corporate quality manual. The Manual Reference Matrix lists each location and links to their individual matrix. This allows the corporate manual to maintain common requirements while accommodating differences in scope, exclusions or documents between locations. It also discusses controlling the matrix template to ensure consistency across locations.
An Ontology-Based Information Extraction Approach For R Sum SRichard Hogue
This document discusses developing an ontology-driven information extraction system called the Ontology-based Résumé Parser (ORP) to extract information like experiences, qualifications, education, and personal details from millions of résumés in English and Turkish. The system uses various domain ontologies within its Ontology Knowledgebase to semantically parse résumés and match concepts. It aims to assist with expert finding and skills aggregation by analyzing data semantically rather than just syntactically matching keywords. The Résumé Ontology is described in detail to represent information typically included in résumés through semantic annotations.
Putting Controlled Vocabulary To Work I Davis 2008Ian Davis
The document discusses strategies for developing and implementing controlled vocabularies. It addresses the challenges of uncontrolled vs. controlled vocabularies and outlines a multi-step strategy for creation, maintenance, and integration across systems. Key points include stating the business case, gaining organizational buy-in, determining standards and scope, and leveraging semantic relationships between terms to improve search capabilities.
ESWC2008 Identity OpenLink - On The Evolution of Termsrumito
The document discusses the evolution of terms and language for describing data on the semantic web. It argues that creating a perfectly uniform language from scratch has generally failed, and that natural languages and terminology evolve most successfully through distributed community practice and reuse of existing terms. The semantic web aims to leverage existing semantic hubs and allow for diversity and heterogeneity of descriptions while making context and relationships between terms explicit.
Keystone Summer School 2015: Mauro Dragoni, Ontologies For Information RetrievalMauro Dragoni
The presentation provides an overview of what an ontology is and how it can be used for representing information and for retrieving data with a particular focus on the linguistic resources available for supporting this kind of task. Overview of semantic-based retrieval approaches by highlighting the pro and cons of using semantic approaches with respect to classic ones. Use cases are presented and discussed
Proposal of an Ontology Applied to Technical Debt on PL/SQL DevelopmentJorge Barreto
The document proposes an ontology for technical debt in PL/SQL development. It discusses relevant concepts like ontologies, technical debt, and PL/SQL. An initial model is developed in Protégé with five types of technical debt - documentation, requirements, tests, design, and code. The model could be expanded to include more debt types and relationships. The ontology provides a standardized vocabulary to describe technical debt for PL/SQL developers.
This document provides an overview of Oracle Corporation and its business. It discusses that Oracle is the world's largest enterprise software company that develops and markets database management systems and enterprise software. It also discusses Oracle's acquisition strategy and organization into software and services businesses. The software business is divided into new software licenses and software license updates/support, while the services business is divided into consulting, On Demand, and education. It provides details on Oracle's flagship database product and middleware products.
Metadata for Terminology / KOS ResourcesMarcia Zeng
1. Why do we need metadata for terminology resources? 2. What do we need to know about a terminology resource? 3. Is there a standardized set of metadata elements for terminology resources?-- a presentation at the "New Dimensions in Knowledge Organization Systems", a Joint NKOS/ CENDI Workshop, World Bank, Washington, DC. September 11, 2008 http://nkos.slis.kent.edu/2008workshop/NKOS-CENDI2008.htm
The Truth about Content: Learning from the Past in order to Succeed in the Fu...Scott Abel
This presentation will throw a spotlight onto the single most common,
and most serious, reason why Content Management projects fail. In a
nutshell, too many projects become so focused on the technology they
want to deploy that they forget about what matters most - the content
and the people who use it. Real-life case studies will be used to
illustrate this problem. The optimism of the audience will be rebuilt
by introducing a proven solution to this issue with this being a call
to move the focus of CM project towards Content Oriented Architectures.
The most common mistake found in content management projects is rather
surprising. The reason most CM projects falter is that the project
team, and frequently its stakeholders, become unduly enamored with
some piece of technology and assume, or hope, that one or two
applications will erase all of the challenges surrounding the
creation, management, reuse and delivery of content. When a particular
collection of applications fail to deliver on the expectations, the
usual response is to insert even more applications. With each new
application that is introduced, a number of connectors and patches are
also added so that one tool can work with the others that are already
in place. This continues until, with seeming inevitability, these
projects crumble under the weight of growing system complexity. These
projects fail, in short, because, in becoming fixated on technology,
they essentially forget about their content.
This presentation will use a number of project cases studies, some
older and some exceedingly current, to illustrate the downward path
that most CM projects follow. While this might sound ominous, this
journey will actually arrive at a hopeful conclusion. If CM projects
place content at the center of their solution designs, adopting in
effect a Content Oriented Architecture (COA), it becomes possible for
projects to use technology, even exploit it, in ways that emphasize
helping authors, publishers and content users. Under this model, the
quality and usefulness of the content assets becomes the overriding
focus and where automation is introduced it is to either further
improve the quality of the content or to reduce the cost and effort
needed to achieve the desired results. Examples of successful projects
will be used to prove that Content Oriented Architectures are not
really new and that they do deliver results that endure over time.
Presentation made in the context of the FAO AIMS Webinar titled “Knowledge Organization Systems (KOS): Management of Classification Systems in the case of Organic.Edunet” (http://aims.fao.org/community/blogs/new-webinaraims-knowledge-organization-systems-kos-management-classification-systems)
21/2/2014
The objective of this webinar is to provide a brief overview of the Knowledge Organization Systems (KOS) and the tools used for managing them. The presentation will focus on the management of the multilingual Organic.Edunet ontology as a case study. In this context it will present aspects such as the collaborative work, multilinguality needs and update of the concepts using an online KOS management tool (MoKi).
Semantic Rules Representation in Controlled Natural Language in FluentEditorCognitum
Abstract. The purpose of this paper is to present a way of representation of semantic rules (SWRL) in controlled natural language (English) in order to facilitate understanding the rules by humans interacting with a machine. The rule representation is implemented in FluentEditor – ontology editor with controlled natural language (CNL). The representation can be used in a lot of domains where people interact with machines and use specialized interfaces to define knowledge in a system (semantic knowledge base), e.g. representing medical knowledge and guidelines, procedures in crisis management or in management of any coordination processes. Such knowledge bases are able to support decision making in any discipline provided there is a knowledge stored in a proper semantic way.
The document discusses the need for an SOA registry repository to manage growing complexity in SOA deployments. As services become more complex, with multiple related artifacts, informal management is insufficient. A registry repository acts as a central point of control and system of record to govern the service lifecycle according to organizational policies. It functions similar to a library, containing artifacts and metadata to describe them, and enables management of information across the full lifecycle from a single source of reference. The registry repository is positioned as an increasingly important component for handling challenges that arise in large scale SOA ecosystems.
Semantic Web: Technolgies and Applications for Real-WorldAmit Sheth
Amit Sheth and Susie Stephens, "Semantic Web: Technolgies and Applications for Real-World," Tutorial at 2007 World Wide Web Conference, Banff, Canada.
Tutorial discusses technologies and deployed real-world applications through 2007.
Tutorial description at: http://www2007.org/tutorial-T11.php
This presentation has some helpful advice for Department of Defense (DoD) Communities of Interest (COI) when they are creating ontologies: 1) start with simple lists... them move forward.
Similar to How to describe registered organisations using the Registered Organization vocabulary and the Organization Ontology (20)
How to describe registered organisations using the Registered Organization vocabulary and the Organization Ontology
1. EUROPEAN
JOINING UP GOVERNMENTS COMMISSION
November, 2012
Case Study
How to describe Organizations in RDF
using the Core Business Vocabulary
and the Organization Ontology?
2. Case study: How to describe organizations in RDF using the
Core Business Vocabulary and the Organization Ontology?
Why using both Example: Description Example: Description of the
Introduction Vocabularies Pilot in Greece References
Vocabularies? of the legal entity organizational structure
Introduction
This case study is a follow-up to the Business Case on interconnecting “The Core Business Vocabulary
business registers using the Core Business Vocabulary [1]. This document
explains how organizations can be described in RDF using the Core can be combined with the more
Business Vocabulary and the Organization Ontology. To do this, it general Organization Ontology.
provides an example of a real organization, PricewaterhouseCoopers
Enterprise Advisory a legal entity registered in the Belgian company The Core Business Vocabulary
register, which is then described in RDF using these specifications.
can be used for describing
A Core Vocabulary is a simplified, reusable, and extensible data model Registered Legal Organizations
that captures the fundamental characteristics of a data entity in a
context-neutral fashion. Core Vocabularies can be used in (RegORG), the Organization
interoperability agreements for enabling information systems, developed Ontology (ORG) to describe the
independently, to exchange information, thus making it possible for
information to travel across borders and domains. several parts of an organization.”
The first three Core Vocabularies [2] developed by the Interoperability
Solutions for European Public Administrations (ISA) of the European
Commission [3] (the Core Person, Core Location and Core Business) have
been undertaken by the Government Linked Data Working Group (GLD
WG) of W3C [3].
The Core Vocabularies can be used in conjunction with other ontologies
and vocabularies. For example, the Core Business Vocabulary can be
combined with the more general Organization Ontology. Whereas the
Core Business Vocabulary should be used for describing Registered Legal [1] https://joinup.ec.europa.eu/community/core_vocabularies/description
[2] https://joinup.ec.europa.eu/community/core_vocabularies/description
Organizations (RegORG)* [5], the Organization Ontology (ORG) [6] [3] http://ec.europa.eu/isa/
should be used to describe the several parts of an organization. [4] http://www.w3.org/2011/gld/
[5] http://dvcs.w3.org/hg/gld/raw-file/default/legal/index.html
[6] http://www.w3.org/TR/vocab-org/
*In order to better align the Core Business Vocabulary with the Organization Ontology, the
GLD WG has recently renamed it to 'Registered Organization Vocabulary’ (RegORG).
3. Case study: How to describe organizations in RDF using the
Core Business Vocabulary and the Organization Ontology?
Why using both Example: Description Example: Description of the
Introduction Vocabularies Pilot in Greece References
Vocabularies? of the legal entity organizational structure
What is the Core Business
Vocabulary? “The Core Business Vocabulary is
The Core Business Vocabulary is a vocabulary for describing
a simplified, reusable and
organizations that have gained legal entity status through a formal extensible data model to describe
registration process, typically in a national or regional register. This data
model captures the fundamental characteristics of a legal entity, e.g. its organizations that have gained
legal name, its registered activities and address. This same attributes can
be used to describe private and governmental organizations.
legal entity status through a
formal registration process.”
The Core Business Vocabulary was first developed by the ISA Programme
in cooperation with DG MARKT of the European Commission . This
Directorate General is responsible for the EC legislative proposal on
interconnecting National Business Registers. The Core Business
Vocabulary Working Group was chaired by Piotr Madziar from DG Both Vocabularies
MARKT/F2. Other members of the Working Group where affiliated with
XBRL Europe, opencorporates.com, the European Business Register and abide by the Linked
the European Banking Authority EBA.
Data principles
What is the ORG Ontology? They promote the use of common identifiers for
organizations in the form of URIs.
The ORG Ontology is designed to enable publication of information on
organizations and organizational structures including governmental
organizations. It is intended to provide a generic, reusable core ontology They can be easily combined with other Linked Data
that can be extended or specialized for use in particular situations. The vocabularies.
ORG Ontology has been used by the UK Government for describing
public organizations. They can easily be extended with new classes and
attributes to fulfil new domain requirements.
4. Case study: How to describe organizations in RDF using the
Core Business Vocabulary and the Organization Ontology?
Why using both Example: Description Example: Description of the
Introduction Vocabularies Pilot in Greece References
Vocabularies? of the legal entity organizational structure
Why using both Vocabularies?
(A) Extract from a business register
The Core Business Vocabulary enables anyone to describe the essential
elements of a registered organization. These data fields are typically shown in
the official extracts of business registers (A):
• the legal name of the organization
• the registered number of the organization
• the legal address of the organization
• the activities for which the organization is registered for
• the type of organization
Each organization is identified by a unique URI, which
is aligned with the new directive 2012/17/EU [7]*.
The ORG Ontology is more generic and makes it possible to describe
organizational structures using RDF. These are typically described in (B) Organizational Chart
organizational charts (B) :
• the organization’s purpose
• the organizational decomposition of an organization
• the people who are members of the organization at each one of its levels
*According to the new directive 2012/17/EU: "Member States shall ensure that companies have a unique
identifier allowing them to be unequivocally identified in communication between registers through the
system of interconnection of central, commercial and companies registers established in accordance with
Article 4a(2) ("the system of interconnection of registers"). That unique identifier shall comprise, at least,
elements making it possible to identify the Member State of the register, the domestic register of origin and
the company number in that register and, where appropriate, features to avoid identification errors."
[7] http://eur-lex.europa.eu/smartapi/cgi/sga_doc?smartapi!celexplus!prod!CELEXnumdoc&lg=EN&numdoc=32012L0017
5. Case study: How to describe organizations in RDF using the
Core Business Vocabulary and the Organization Ontology?
Why using both Example: Description Example: Description of the
Introduction Vocabularies Pilot in Greece References
Vocabularies? of the legal entity organizational structure
Description of the legal entity Legal name
<rov:RegisteredOrganization
rdf:about=“http://kbopub.economie.fgov.be/kbopub/toonondernemingps.html?ondernemi
PricewaterhouseCoopers Enterprise Advisory is a registered n
gsnummer=415622333”>
legal entity in the Belgian company register (Kruispuntbank <rov:legalName>PricewaterhouseCoopers Enterprise Advisory</rov:legalName>
</rov:RegisteredOrganization>
van Ondernemingen – Banque-Carrefour des Entreprises). This
example shows how the company can be described in RDF
Registered number
using the Core Business Vocabulary. The data was extracted
<rov:registration>
from the Belgian company register. <adms:Identifier rdf:about="http://example.com/Reg415622333">
<skos:notation>0415.622.333</skos:notation>
<adms:schemeAgency>Belgian Base Register for Companies</adms:schemeAgency>
</adms:Identifier>
</rov:registration>
Belgian Company Register
Legal address
Registered number
Legal name <rov:registeredAddress>
<locn:Address rdf:about="http://example.com/ra415622333">
<locn:postCode>1932 Zaventem</locn:postCode>
<locn:fullAddress>Belgium, Woluwedal 18</locn:fullAddress>
Legal address
</locn:Address>
</rov:registeredAddress>
Type
Type
<rov:companyType>
<skos:Concept rdf:about="http://example.com/Cooperatievevennootshap">
Activities <rdfs:label>Cooperatieve vennootshap</rdfs:label>
</skos:Concept>
</rov:companyType>
Activities for which the company is registered for
Extract of PricewaterhouseCoopers Enterprise Advisory data <skos:Concept rdf:about="http://example.com/ca7022">
registered as legal entity in the Belgian company register <rdfs:label>Business and other management consultancy activities</rdfs:label>
</skos:Concept>
<skos:Concept rdf:about="http://example.com/ca74142">
<rdfs:label>Other business and management consultancy activities</rdfs:label>
</skos:Concept>
6. Case study: How to describe organizations in RDF using the
Core Business Vocabulary and the Organization Ontology?
Why using both Example: Description Example: Description of the
Introduction Vocabularies Pilot in Greece References
Vocabularies? of the legal entity organizational structure
Description of the
organizational structure
Organizational decomposition
PricewaterhouseCoopers Enterprise Advisory is divided into
<org:Organization rdf:ID="Consulting">
‘Consulting’ and ‘Deals’ practices. Each practice is composed <rdfs:label rdf:datatype=http://www.w3.org/2001/XMLSchema#string
of different units. This example provides a description of the >Consulting</rdfs:label>
<org:hasSubOrganization>
organizational structure (and other additional information) <org:Organization rdf:ID="Finance_and_Treasury"/>
of PricewaterhouseCoopers Enterprise Advisory in RDF </org:hasSubOrganization>
<org:hasSubOrganization>
using the ORG Ontology. <org:Organization rdf:ID="Technology_Consulting"/>
</org:hasSubOrganization>
<org:hasSubOrganization>
PricewaterhouseCoopers Enterprise Advisory <org:Organization rdf:ID="Strategy_and_Operations"/>
</org:hasSubOrganization>
Purpose
<org:purpose>
Deals Consulting
<rdfs:Resource rdf:ID="For_profit"/>
</org:purpose>
Transaction Services Finance and Treasury Members
<org:hasMember rdf:resource="http://JoaoFrade.org/foaf.rdf#me"/>
Valuation Services Strategy and Operations
Strategic Investment
Technology Consulting
Decisions
Capital Markets
Accounting Advisory
Services organizational structure of
PricewaterhouseCoopers
Government Enterprise Advisory
Infrastructure Public and
Corporate Finance
7. Case study: How to describe organizations in RDF using the
Core Business Vocabulary and the Organization Ontology?
Why using both Example: Description Example: Description of the
Introduction Vocabularies Pilot in Greece References
Vocabularies? of the legal entity organizational structure
Piloting the Core Business
Vocabulary in Greece
The International Hellenic University has used the Core Business
Vocabulary for publishing some 28000 companies registered in the Greek
Tax Authorities business registry as linked data* [8,9].
The pilot deals only with non-confidential data, e.g. name, company type
and activity, and address.
Lessons Learnt
Well-structured, dereferencable URIs were designed in order to assign to
each legal entity a unique Web identifier. Currently, all legal entities are The Core Business Vocabulary can be used for
assigned URIs of the following structure http://linkeddata.ihu.edu.gr representing basic company data. Case-specific
/resource/company/{afm}, where afm is the unique identifier of a legal peculiarities call for additional modelling effort. The
entity maintained by the tax authorities. flexibility of RDF minimises this effort.
The example of the pilot can be used by other countries that decide to An authoritative source, e.g. a company register, should
publish their company data as linked open data. be responsible for assigning and maintaining good
URIs for companies.
To browse the data served by the pilot, you may visit
http://linkeddata.ihu.edu.gr:8080/rdf-browser/
Reference data, such as taxonomies of company types,
For the time being the main part of the website is only available in
statuses and activities, has to published as linked open
Greek but the procedure applied is described in English. data so that people avoid re-inventing the wheel.
Publishing multi-lingual linked open data entails a
* Linked data is a promising method of publishing structured, machine-readable data on the Web so that it number of technical challenges.
can be inter-connected, thus enriching its meaning and crow-sourcing improvements in quality. In this
case, core business information has been linked to the location of companies with the goal to enable
reuse in third party services and applications where core business data may be required. [8] http://ec.europa.eu/isa/news/2012/opendata_greece_en.htm
[9] https://joinup.ec.europa.eu/asset/core_business/news/core-business-
and-core-location-vocabularies-piloted-greece
8. Case study: How to describe organizations in RDF using the
Core Business Vocabulary and the Organization Ontology?
Why using both Example: Description Example: Description of the
Introduction Vocabularies Pilot in Greece References
Vocabularies? of the legal entity organizational structure
Contact us Visit our initiatives
https://joinup.ec.europa.eu/contact
SOFTWARE
FORGES
References COM M UNITY
An organization ontology (ORG)
http://www.w3.org/TR/vocab-org/ ADM S.
Registered Organization Vocabulary (RegOrg)
http://dvcs.w3.org/hg/gld/raw-file/default/legal/index.html
SW
Business Case: Interconnecting business registers with the
Core Business Vocabulary CORE
https://joinup.ec.europa.eu/asset/core_business/document/in PUBLIC
terconnecting-business-registers-core-business-vocabulary SERVICE
VOCABULARY
Get involved
Disclaimer
The views expressed in this document are purely those of the writer and may not, in any circumstances, be
Follow @SEMICeu on Twitter
interpreted as stating an official position of the European Commission.
The European Commission does not guarantee the accuracy of the information included in this study, nor
does it accept any responsibility for any use thereof. Join SEMIC group on LinkedIn
Reference herein to any specific products, specifications, process, or service by trade name, trademark,
manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or
favouring by the European Commission.
All care has been taken by the author to ensure that s/he has obtained, where necessary, permission to use Join SEMIC community on Joinup
any parts of manuscripts including illustrations, maps, and graphs, on which intellectual property rights
already exist from the titular holder(s) of such rights or from her/his or their legal representative.
This Business Case was prepared for the ISA programme by PwC EU Services EESV