U.S. patent application number 13/533007 was filed with the patent office on 2013-04-04 for implementing service oriented architecture industry model repository using semantic web technologies.
This patent application is currently assigned to INTERNATIONAL BUSINESS MACHINES CORPORATION. The applicant listed for this patent is Eoin Lane, Magda Mahmoud Mourad, Harry Thomas Pendergrass, Mei Yang Selvage. Invention is credited to Eoin Lane, Magda Mahmoud Mourad, Harry Thomas Pendergrass, Mei Yang Selvage.
Application Number | 20130086061 13/533007 |
Document ID | / |
Family ID | 44152528 |
Filed Date | 2013-04-04 |
United States Patent
Application |
20130086061 |
Kind Code |
A1 |
Lane; Eoin ; et al. |
April 4, 2013 |
IMPLEMENTING SERVICE ORIENTED ARCHITECTURE INDUSTRY MODEL
REPOSITORY USING SEMANTIC WEB TECHNOLOGIES
Abstract
A plurality of topic maps are stored in one or more storage
devices. Each of the topic maps represents information using
topics, associations, and occurrences. Each of the topic maps
provides meta data for assets stored in an asset repository. A
computer provides one or more services over a network. At least one
of the one or more services enables functionality of one or more
user interfaces. The one or more services provide semantic search
functionality for the assets of the asset repository. The semantic
search functionality utilizes the topics, associations, and
occurrences of one or more of the topic maps to find one of more of
the assets of the asset repository that satisfies conditions input
via one of the one or more user interfaces.
Inventors: |
Lane; Eoin; (Littleton,
MA) ; Selvage; Mei Yang; (Pocatello, ID) ;
Mourad; Magda Mahmoud; (Yorktown Heights, NY) ;
Pendergrass; Harry Thomas; (Aloha, OR) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Lane; Eoin
Selvage; Mei Yang
Mourad; Magda Mahmoud
Pendergrass; Harry Thomas |
Littleton
Pocatello
Yorktown Heights
Aloha |
MA
ID
NY
OR |
US
US
US
US |
|
|
Assignee: |
INTERNATIONAL BUSINESS MACHINES
CORPORATION
ARMONK
NY
|
Family ID: |
44152528 |
Appl. No.: |
13/533007 |
Filed: |
June 26, 2012 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
12640697 |
Dec 17, 2009 |
8244768 |
|
|
13533007 |
|
|
|
|
Current U.S.
Class: |
707/736 |
Current CPC
Class: |
G06F 16/23 20190101;
G06Q 10/10 20130101; G06F 16/958 20190101 |
Class at
Publication: |
707/736 |
International
Class: |
G06F 17/30 20060101
G06F017/30 |
Claims
1. A method comprising: storing a plurality of topic maps in one or
more storage devices, wherein each of the topic maps represents
information using topics, associations, and occurrences, wherein
each of the topic maps provides meta data for assets stored in an
asset repository; and a computer providing one or more services
over a network, at least one of the one or more services enabling
functionality of one or more user interfaces, wherein the one or
more services provide semantic search functionality for the assets
of the asset repository, said semantic search functionality
utilizing the topics, associations, and occurrences of one or more
of the topic maps to find one of more of the assets of the asset
repository that satisfies conditions input via one of the one or
more user interfaces.
2. The method of claim 1, further comprising: the computer creating
uniform resource identifiers for the topics of at least one of the
topic maps; and the computer creating topic resource description
framework triples for each topic of at least one of the topic
maps.
3. The method of claim 1, further comprising: the computer creating
topic occurrence resource description framework triples for each
occurrence of an element or index item in at least one of the topic
maps.
4. The method of claim 1, wherein each of the topics, associations,
and occurrences are data structures for a related type of
information of the topic maps.
5. The method of claim 1, wherein the represented information of
the topic maps is necessary for enabling search functionalities
dependent upon hypergraph relationships between topics that are
represented by data structures of the topic maps of the
associations.
6. The method of claim 1, wherein each of the topic maps conform to
International Organization for Standardization (ISO)/International
Electrotechnical Commission (IEC) standard 13250-1 or a standard
based upon or derivative from ISO/IEC standard 13250-1.
7. The method of claim 1, wherein each of the plurality of topic
maps comprises data for a particular topic or industry
vertical.
8. The method of claim 1, wherein each of the plurality of topic
maps comprises data for a different industry vertical of a company
owning the assets of the asset repository.
9. The method of claim 1, wherein each of the plurality of topic
maps comprises data for a different topic for an industry to which
the assets of the asset repository relate, each different topic
representing a conceptual space of meaning.
10. The method of claim 1, further comprising: the computer
utilizing a meta model search service implemented within an
abstraction layer of a system architecture where the topic maps are
stored to interface with the asset repository, which asset
repository is maintained in a separate layer of abstraction of the
system architecture.
11. The method of claim 1, further comprising: the computer
converting topics of stored topic maps into Resource Description
Framework (RDF) triples, which RDF triples are persisted in an RDF
repository, wherein the one or more services utilize the RDF
triples for the semantic Web search functionality.
12. The method of claim 1, wherein the assets of the asset
repository comprise at least three of: industry models, business
models, unified modeling language (UML) design applications, data
models, business services, service components, and technical
services for a specific organization.
13. The method of claim 1, wherein the asset repository comprises a
plurality of different types of repositories, each storing a subset
of the assets.
14. The method of claim 1, further comprising: the computer
implementing the one or more services in an application and
services layer of abstraction of a system architecture; the
computer implementing the one or more services in a service
oriented architecture (SOA) industry model repository (IMR)
component layer of abstraction of the system architecture; and the
computer implementing the asset repository in a federated physical
assets layer of abstraction of the system architecture, wherein
communications between the application and services layer and the
federated physical assets layer must occur through the service
oriented architecture (SOA) industry model repository (IMR)
component layer.
15. The method of claim 1, wherein the one or more services are Web
services, wherein the assets are distributed across a plurality of
different physical storage devices, which storage devices store the
assets in a heterogeneous manner, wherein said assets are federated
into a single logical repository referred to as the asset
repository.
16. A computer system comprising: one or more processors, one or
more computer-readable memories and one or more computer-readable
tangible storage devices; program instructions, stored on at least
one of the one or more storage devices for execution by at least
one of the one or more processors via at least one of the one or
more memories, to store a plurality of topic maps in one or more
storage devices, wherein each of the topic maps represents
information using topics, associations, and occurrences, wherein
each of the topic maps provides meta data for assets stored in an
asset repository; and program instructions, stored on at least one
of the one or more storage devices for execution by at least one of
the one or more processors via at least one of the one or more
memories, to provide one or more services over a network, at least
one of the one or more services enabling functionality of one or
more user interfaces, wherein the one or more services provide
semantic search functionality for the assets of the asset
repository, said semantic search functionality utilizing the
topics, associations, and occurrences of one or more of the topic
maps to find one of more of the assets of the asset repository that
satisfies conditions input via one of the one or more user
interfaces.
17. The computer system of claim 16, further comprising: program
instructions, stored on at least one of the one or more storage
devices for execution by at least one of the one or more processors
via at least one of the one or more memories, to implement the one
or more services in an application and services layer of
abstraction of a system architecture; program instructions, stored
on at least one of the one or more storage devices for execution by
at least one of the one or more processors via at least one of the
one or more memories, to implement the one or more services in a
service oriented architecture (SOA) industry model repository (IMR)
component layer of abstraction of the system architecture; and
program instructions, stored on at least one of the one or more
storage devices for execution by at least one of the one or more
processors via at least one of the one or more memories, to
implement the asset repository in a federated physical assets layer
of abstraction of the system architecture, wherein communications
between the application and services layer and the federated
physical assets layer must occur through the service oriented
architecture (SOA) industry model repository (IMR) component
layer.
18. The computer system of claim 16, wherein the one or more
services are Web services, wherein the assets are distributed
across a plurality of different physical storage devices, which
store the assets in a heterogeneous manner, wherein said assets are
federated into a single logical repository referred to as the asset
repository.
19. A computer program product comprising: one or more
computer-readable tangible storage devices; program instructions,
stored on at least one of the one or more storage devices, to store
a plurality of topic maps in one or more storage devices, wherein
each of the topic maps represents information using topics,
associations, and occurrences, wherein each of the topic maps
provides meta data for assets stored in an asset repository; and
program instructions, stored on at least one of the one or more
storage devices, to provide one or more services over a network, at
least one of the one or more services enabling functionality of one
or more user interfaces, wherein the one or more services provide
semantic search functionality for the assets of the asset
repository, said semantic search functionality utilizing the
topics, associations, and occurrences of one or more of the topic
maps to find one of more of the assets of the asset repository that
satisfies conditions input via one of the one or more user
interfaces.
20. The computer program product of claim 19, further comprising:
program instructions, stored on at least one of the one or more
storage devices, to implement the one or more services in an
application and services layer of abstraction of a system
architecture; program instructions, stored on at least one of the
one or more storage devices, to implement the one or more services
in a service oriented architecture (SOA) industry model repository
(IMR) component layer of abstraction of the system architecture;
and program instructions, stored on at least one of the one or more
storage devices, to implement the asset repository in a federated
physical assets layer of abstraction of the system architecture,
wherein communications between the application and services layer
and the federated physical assets layer must occur through the
service oriented architecture (SOA) industry model repository (IMR)
component layer.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] Pursuant to 35 USC .sctn.120, this application is a
continuation application of U.S. patent application Ser. No.
12/640,697 filed Dec. 17, 2009 (pending).
BACKGROUND OF THE INVENTION
[0002] The present invention relates to meta models and more
specifically to implementing service oriented architecture (SOA)
industry model repository (IMR) meta models using semantic web
technologies.
[0003] A service oriented architecture (SOA) meta model based on
topic maps can be built using a number of technologies such as
implementing topic maps using topic map related ISO/IEC standards
(ISO 13250-1), defining the meta model in a relational database
management system (RDMS), and individual semantic technologies such
as web ontology language (OWL), resource description framework
(RDF), and SPARQL protocol and RDF query language (SPARQL).
[0004] Topic map related ISO standards are implemented using Topic
Map Constraint Language (TMCL) and Topic Map Query Language (TMQL)
and come with their own programming model.
[0005] In defining the topic map meta model in a database
management system, for example Relational Database Management
System (RDBMS), the industry models are shredded into the desired
granularity. RDBMS is relied upon for persistence and constraints
and uses structured query language (SQL) as the query language,
however this approach is limited by its lack of scalability and
inference logic.
[0006] Each individual semantic technology implementation provides
its own set of advantages and disadvantages.
SUMMARY OF THE INVENTION
[0007] According to one embodiment, of the present invention, a
method for implementing topic map meta models of a service oriented
architecture (SOA) industry model repository (IMR) is provided
comprising a meta model service associated with a physical asset
repository. The meta model service includes at least one topic map
meta model with data specific to a particular topic or industry
vertical included within an information model repository common
meta-meta model, and the information model repository common
meta-meta model included within a meta-meta-meta model with a topic
map based index. The method comprises assigning topics, occurrences
and attributes to the at least one topic map meta model with data
specific to a particular topic or industry vertical; converting
topics of the at least one topic map meta model with data specific
to a particular topic or industry vertical into resource
description framework triples; and persisting the resource
description framework triples into a resource description framework
repository.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
[0008] FIG. 1 is a computer network in which illustrative
embodiments may be implemented.
[0009] FIG. 2 is a data processing system in which illustrative
embodiments may be implemented.
[0010] FIG. 3 shows an overview of an industry model repository
(IMR) solution architecture system including a service oriented
architecture (SOA) industry model repository (IMR) component.
[0011] FIG. 4 shows an overview of a service oriented architecture
(SOA) industry model repository (IMR) meta-model with OWL/RDF
maps.
[0012] FIG. 5 shows an example of an OWL-DL representation of a
topic map.
[0013] FIG. 6 shows a UML class diagram of the TopicMap RDF data
access object converting the SOA IMR topic map meta model to an
OWL-DL representation.
[0014] FIG. 7 shows a flowchart for taking a topic and all of the
location of the RDF server and particular repository to be used for
persisting the resulting RDF.
[0015] FIG. 8 shows a sequence diagram showing how a topic map
would be automatically converted to an OWL-DL representation and
stored in an RDF repository.
DETAILED DESCRIPTION OF THE INVENTION
[0016] With reference now to the figures, and in particular, with
reference to FIGS. 1 and 2, exemplary diagrams of data processing
environments are provided in which illustrative embodiments may be
implemented. It should be appreciated that FIGS. 1 and 2 are only
exemplary and are not intended to assert or imply any limitation
with regard to the environments in which different embodiments may
be implemented. Many modifications to the depicted environments may
be made.
[0017] FIG. 1 depicts a pictorial representation of a network of
data processing systems in which illustrative embodiments may be
implemented. Network data processing system 1 is a network of
computers in which the illustrative embodiments may be implemented.
Network data processing system 1 contains network 2, which is the
medium used to provide communication links between various devices
and computers connected together within network data processing
system 1. Network 2 may include connections, such as wire, wireless
communication links, or fiber optic cables.
[0018] In the depicted example, server 4 and server 6 connect to
network 2 along with storage unit 8. In addition, clients 10, 12,
and 14 connect to network 2. Clients 10, 12, and 14 may be, for
example, personal computers or network computers. In the depicted
example, server 4 provides information, such as boot files,
operating system images, and applications to clients 10, 12, and
14. Clients 10, 12, and 14 are clients to server 4 in this example.
Network data processing system 1 may include additional servers,
clients, and other devices not shown.
[0019] Program code located in network data processing system 1 may
be stored on a computer recordable storage medium and downloaded to
a data processing system or other device for use. For example,
program code may be stored on a computer recordable storage medium
on server 4 and downloaded to client 10 over network 2 for use on
client 10.
[0020] In the depicted example, network data processing system 1 is
the Internet with network 2 representing a worldwide collection of
networks and gateways that use the Transmission Control
Protocol/Internet Protocol (TCP/IP) suite of protocols to
communicate with one another. At the heart of the Internet is a
backbone of high-speed data communication lines between major nodes
or host computers, consisting of thousands of commercial,
governmental, educational and other computer systems that route
data and messages. Of course, network data processing system 1 also
may be implemented as a number of different types of networks, such
as, for example, an intranet, a local area network (LAN), or a wide
area network (WAN). FIG. 1 is intended as an example, and not as an
architectural limitation, for the different illustrative
embodiments.
[0021] With reference now to FIG. 2, a block diagram of a data
processing system is shown in which illustrative embodiments may be
implemented. Data processing system 20 is an example of a computer,
such as server 4 or client 10 in FIG. 1, in which computer usable
program code or instructions implementing the processes may be
located for the illustrative embodiments. In this illustrative
example, data processing system 20 includes communications fabric
22, which provides communications between processor unit 24, memory
26, persistent storage 28, communications unit 30, input/output
(I/O) unit 32, and display 34.
[0022] Processor unit 24 serves to execute instructions for
software that may be loaded into memory 26. Processor unit 24 may
be a set of one or more processors, or may be a multi-processor
core, depending on the particular implementation. Further,
processor unit 24 may be implemented using one or more
heterogeneous processor systems in which a main processor is
present with secondary processors on a single chip. As another
illustrative example, processor unit 24 may be a symmetric
multi-processor system containing multiple processors of the same
type.
[0023] Memory 26 and persistent storage 28 are examples of storage
devices 36. A storage device is any piece of hardware that is
capable of storing information, such as, for example, without
limitation, data, program code in functional form, and/or other
suitable information either on a temporary basis and/or a permanent
basis. Memory 26, in these examples, may be, for example, a random
access memory or any other suitable volatile or non-volatile
storage device. Persistent storage 28 may take various forms
depending on the particular implementation. For example, persistent
storage 28 may contain one or more components or devices. For
example, persistent storage 28 may be a hard drive, a flash memory,
a rewritable optical disk, a rewritable magnetic tape, or some
combination of the above. The media used by persistent storage 28
also may be removable. For example, a removable hard drive may be
used for persistent storage 28.
[0024] Communications unit 30, in these examples, provides for
communications with other data processing systems or devices. In
these examples, communications unit 30 is a network interface card.
Communications unit 30 may provide communications through the use
of either or both physical and wireless communication links.
[0025] Input/output unit 32 allows for input and output of data
with other devices that may be connected to data processing system
20. For example, input/output unit 32 may provide a connection for
user input through a keyboard, a mouse, and/or some other suitable
input device. Further, input/output unit 32 may send output to a
printer. Display 34 provides a mechanism to display information to
a user.
[0026] Instructions for the operating system, applications, and/or
programs may be located in storage devices 36, which are in
communication with processor unit 24 through communications fabric
22. In these illustrative examples the instructions are in a
functional form on persistent storage 28. These instructions may be
loaded into memory 26 for running by processor unit 24. The
processes of the different embodiments may be performed by
processor unit 24 using computer implemented instructions, which
may be located in a memory, such as memory 26.
[0027] These instructions are referred to as program code, computer
usable program code, or computer readable program code, that may be
read and run by a processor in processor unit 24. The program code
in the different embodiments may be embodied on different physical
or tangible computer readable media, such as memory 26 or
persistent storage 28.
[0028] Program code 38 is located in a functional form on computer
readable media 40 that is selectively removable and may be loaded
onto or transferred to data processing system 20 for running by
processor unit 24. Program code 38 and computer readable media 40
form computer program product 42 in these examples. In one example,
computer readable media 40 may be in a tangible form, such as, for
example, an optical or magnetic disc that is inserted or placed
into a drive or other device that is part of persistent storage 28
for transfer onto a storage device, such as a hard drive that is
part of persistent storage 28. In a tangible form, computer
readable media 40 also may take the form of a persistent storage,
such as a hard drive, a thumb drive, or a flash memory that is
connected to data processing system 20. The tangible form of
computer readable media 40 is also referred to as computer
recordable storage media 44. In some instances, computer readable
media 40 may not be removable.
[0029] Alternatively, program code 38 may be transferred to data
processing system 20 from computer readable media 40 through a
communications link to communications unit 30 and/or through a
connection to input/output unit 32. The communications link and/or
the connection may be physical or wireless in the illustrative
examples. The computer readable media also may take the form of
non-tangible media, such as communication links or wireless
transmissions containing the program code. The non-tangible media
can be referred to as a computer readable signal media 46.
[0030] In some illustrative embodiments, program code 38 may be
downloaded over a network to persistent storage 28 from another
device or data processing system for use within data processing
system 20. For instance, program code stored in a computer readable
storage medium in a server data processing system may be downloaded
over a network from the server to data processing system 20. The
data processing system providing program code 38 may be a server
computer, a client computer, or some other device capable of
storing and transmitting program code 38.
[0031] The different components illustrated for data processing
system 20 are not meant to provide architectural limitations to the
manner in which different embodiments may be implemented. The
different illustrative embodiments may be implemented in a data
processing system including components in addition to, or in place
of, those illustrated for data processing system 20. Other
components shown in FIG. 2 can be varied from the illustrative
examples shown. The different embodiments may be implemented using
any hardware device or system capable of executing program code. As
one example, the data processing system may include organic
components integrated with inorganic components and/or may be
comprised entirely of organic components excluding a human being.
For example, a storage device may be comprised of an organic
semiconductor.
[0032] As another example, a storage device in data processing
system 20 is any hardware apparatus that may store data. Memory 26,
persistent storage 28 and computer readable media 40 are examples
of storage devices in a tangible form.
[0033] In another example, a bus system may be used to implement
communications fabric 22 and may be comprised of one or more buses,
such as a system bus or an input/output bus. Of course, the bus
system may be implemented using any suitable type of architecture
that provides for a transfer of data between different components
or devices attached to the bus system. Additionally, a
communications unit may include one or more devices used to
transmit and receive data, such as a modem or a network adapter.
Further, a memory may be, for example, memory 26 or a cache such as
found in an interface and memory controller hub that may be present
in communications fabric 22.
[0034] FIG. 3 shows the IMR architecture system 100 which may be
part of the network data processing system 1 shown in FIG. 1 and
includes a service oriented architecture (SOA) industry model
repository (IMR) component 102. The SOA-IMR component 102 provides
tools to facilitate the consumption and reuse of the model assets
through topic map IMR meta model creation and topic map interface
104 and semantic web implementation 105 which represent and
implement the IMR meta models using semantics provided by the OWL
language. The SOA IMR component 102 is discussed in further detail
in an application entitled, "SERVICE ORIENTED ARCHITECTURE INDUSTRY
MODEL REPOSITORY META-MODEL WITH A STANDARD BASED INDEX" filed
concurrently with the present application. This application is
hereby incorporated by reference. Block 105 is described in greater
detail below.
[0035] The IMR architecture system 100 includes federated physical
model assets 103 that are stored in different types of repositories
depending on the model driven framework tools and products that are
being deployed by the system. The federated physical assets may
include framework, industry models, business models, unified
modeling language (UML) design applications, data models, business
services, service components, and technical services. The federated
physical assets are not limited to the assets shown in FIG. 3.
[0036] Applications and services 106 are provided to IMR users 108
through the network 109 (e.g. intranet or Internet) using
interfaces 107. The interfaces used by the IMR users 108 include
reports generation and tools supporting multi-formats and
visualization tools supporting complex views. The applications and
services 106 may include registration and profile management;
creating and customizing repository meta model, importing
customized and disparate model/data into the repository,
examining/decomposing complex diagrams and structures, structure,
link, and trace change disparate model/assets; advanced search and
query, navigate/browse data assets; select and download
model/assets, customize/add models/assets submit for repository
upload; and impact analysis. The application and services are not
limited to the assets shown in FIG. 3. The applications and
services are described in greater detail in applications entitled
"FRAMEWORK TO POPULATE AND MAINTAIN A SERVICE ORIENTED ARCHITECTURE
INDUSTRY MODEL", "MANAGING AND MAINTAINING SCOPE IN A SERVICE
ORIENTED ARCHITECTURE INDUSTRY MODEL REPOSITORY", and "RECOGNITION
OF AND SUPPORT FOR MULTIPLE VERSIONS OF AN ENTERPRISE CANONICAL
MESSAGE MODEL" filed concurrently with the present application.
These applications are hereby incorporated by reference. The
interfaces 107 are further described in greater detail in an
application entitled, "SERVICE ORIENTED ARCHITECTURE INDUSTRY MODEL
REPOSITORY META-MODEL WITH A STANDARD BASED INDEX" filed
concurrently and hereby incorporated by reference.
[0037] The IMR users 108 may include but are not limited to
repository administrator, model manager, system architect, and
business analyst.
[0038] FIG. 4 shows a service oriented architecture (SOA) industry
model repository (IMR) component 102 in greater detail. The SOA IMR
component 102 includes a Meta Model Service 202 associated with the
physical asset repository. Within the meta model service 202 is a
meta-meta-meta model 206 with a topic map based index, an
information model repository (IMR) common meta-meta model 208 and
at least one topic map meta model 210 with data specific to a
particular topic or industry vertical. The topic map meta model 210
is associated with the physical asset repositories which may
include but are not limited to repository 204 of model assets (RAM)
212, requirement models 214, and document models (wiki) 216.
[0039] The internal meta model service 202 of the SOA IMR component
102 is the SOA IMR meta-model service using ISO Standard topic map
meta models 210. Topic Maps map both web and real-world information
resources, by reifying real-world resources as "subjects" and
creating "topic" constructs to capture their characteristics and
relationships with other topics and subjects. By using the topic
maps meta models 206, 208, and 210 as the repository internal meta
model, a common meta model service interface 202 allow users to
programmatically access, manage, and maintain these meta
models.
[0040] Topic Maps are an ISO/IEC standard (ISO 13250-1) for mapping
both web and real-world information resources, by reifying
real-world resources as "subjects", and creating "topic" constructs
to capture their characteristics and relationships with other
topics and subjects.
[0041] The SOA IMR meta model service 202 maps or implements the
ISO topic map meta models 210 to a web ontology language (OWL)
representation of the topic map. The industry model repository
(IMR) provides the context for the implementation of the ISO topic
map meta models 210 to the OWL representation of the topic maps.
The OWL representation of the topic map is stored in a resource
description framework (RDF) semantic web repository 218. An example
of a semantic web repository is a Sesame RDF Server which is an
open source framework for querying and analyzing RDF data. The
repository preferably allows for versioning and merging of
asset-requirement topic maps and therefore allows topic maps to be
built up by different domain experts to be organized in conceptual
spaces according to meaning.
[0042] FIG. 5 shows an example of a topic map. The topic map 400
may be converted to an OWL-DL representation. `Abandon` 401 shown
in FIG. 5 is an index item in the ISO topic map meta model 210.
Converting the topic map 400 of FIG. 5 to an OWL-DL representation
would include assigning topics, occurrences and attributes to the
elements and index items in the topic map. For example if the
`Abandon` portion 401 of the topic map 400 shown in FIG. 5 was
converted to an OWL-DL representation, the following would be
assigned: [0043] Abandon 401 is a topic [0044] Requirements Model
402 is a topic [0045] Atomic Data Element 403 is a topic [0046]
Claim recovery--Abandoned 404 is a topic [0047] Has 411 is an
association type [0048] Found 412 is an association type Then, the
`abandon` topic 401 is searched for in other parts of the semantic
web repository 218. The search results may yield as follows: [0049]
Topic Abandon found in topic Claim recovery--Abandoned
[0050] Once the topics, occurrences and attributes are assigned,
they are converted to RDF triples and persisted in an RDF
repository.
[0051] FIG. 6 is a UML class diagram that shows a Java
implementation of the SOA IMR meta data management interface. The
TopicMapService 340 is an interface is implemented by the
TopicMapServiceBindingImpl 342. The TopicMapServiceBindingImpl 342
uses a CacheManagerSingleton 344 to add and remove an item from
cache and a Controller 346 to create or get Associations,
Occurrence, Topics, TopicMap and set Associations and Topics. The
Controller 346 uses TopicMapRDFDAO 348 to provide the conversion of
the SOA IMR topic map meta model 210 to an OWL-DL representation
218.
[0052] The TopicMapRDFDAO 348 converts a topic of a topic map 210
into RDF triples and then the RDF triples are persisted in an RDF
repository. Referring to FIG. 7, in a first step a handle to the
RDF repository 350 is obtained. Then, uniform resource identifiers
for each topic of the topic map 210 are created 352. In the next
step, a connection to the repository is obtained 354. Next, topic
RDF statements or RDF triples based on the topic map 210 are
created 356 and the topic RDF statements RDF triples are added to
the repository 358.
[0053] In the next step, create the topic occurrence RDF statements
or RDF triples 360 to be sent to the repository. To create a topic
occurrence RDF statement or RDF triple 360, an occurrence of the
topic in the topic map is read 362. Next, a topic occurrence RDF
statement or RDF triple is created 364. Then the topic occurrence
RDF statement or RDF triple is added to the repository 366.
Decision point 368 shows that if there are additional occurrences
of the topic on the topic map 210, the steps of creating a topic
occurrence RDF statement or RDF triple 364 and adding a topic
occurrence RDF statement to the repository 366 are repeated until
no more occurrences of the topic on the topic map 210 occur.
[0054] When no occurrences remain (as indicated by decision point
368), the method of taking in a topic and all of the locations of
the topic on the RDF server and the particular repository to be
used for persisting the resulting RDF ends 370. All of the
locations of the topic on the RDF server and the particular
repository to be used for persisting the resulting RDF triples are
accounted for. Therefore, different repositories may be used for
different industry models.
[0055] FIG. 8 is a sequence diagram that shows how a topic map
would be automatically converted to an OWL-DL representation and
stored in a semantic web RDF repository, such as a Sesame RDF
server. The Sesame RDF server is an open source framework for
querying and analyzing RDF data.
[0056] The semantic web RDF repository allows for versioning and
merging of asset-requirement topic maps. With versioning and
merging of asset-requirement topic maps, topic maps may be built by
different domain experts and organized in conceptual spaces
according to meaning. For example, a domain expert could build up
an asset--requirements topic map in the SOA information service
space and another domain expert could build an assets-requirements
topic map in the integration services space and both maps could
then be easily merged together to provide multiple views on the
topic map based on the role of who is using them. A user would only
need to see the relevant subset of the asset-requirement topic map
to help understand what particular assets are relevant to his
requirements. An asset requirements domain expert would only see
the relevant services topic map for his domain. An
asset-requirements topic map admin would be able to see and
navigate the entire map, create new association type of new topic
types.
[0057] By providing an implementation for converting the SOA IMR
topic map meta model to a semantic representation, the standards
based query language of SPARQL Protocol and RDF Query Language
(SPARQL) may be used to query the SOA IMR topic map meta model.
SPARQL allows for very fast querying, will scale to millions of
data items. Another advantage is that the requirement maps are
maintained and information is kept up to date. By using a standards
based query language, search and query requirement maps to
understand the suitable industry model assets or combinations of
assets to be used for a particular set of requirements. Querying of
relevant information about a particular model asset can be carried
out using the standard based query language, such as where the
particular model asset can be found and what assets the particular
model asset can be used in conjunction with new information such as
associations between using assets can be uncovered using inference
technology such as semantic web based query languages, such as
SPARQL to provide answers to queries across the asset-requirements
topic maps. The selection of an RDF based repository like Sesame
provides support for the kind of querying to determine all of the
assets that can be used to satisfy a particular requirement, even
though some assets do not have explicit relationships with the
requirement.
[0058] By using semantic web technologies of the World Wide Web
Consortium (W3C), such as OWL and RDF, a user has the OWL
capabilities and tools for expressing constraints, doing constraint
checking and automated reasoning/inference, and for querying and
visualization of ontology. In addition using semantic web
technologies for converting the SOA IMR topic map meta model to an
OWL-DL representation also has many additional benefits. Using
semantic web technology allows the complex model-model, model
requirement, and requirement-requirement associations both abstract
and instance data to be expressed mathematically in the form of
triples (subject, predicate) which may be continuously checked for
consistency to ensure the integrity of the data. Automatic tools
can be used for consistency checking. Additional constraints can
also be introduced depending on the particular industry model.
Since the semantic web technologies are mathematically based,
inference of the data can be performed to identify new
associations. By using standard XML based technologies of the World
Wide Web Consortium (W3C) such as OWL and RDF, a variety of tools
such as security can be leveraged. Controlled access to the topic
maps, maps or subsection of the maps is supported using the family
of XML security based standards.
[0059] The terminology used herein is for the purpose of describing
particular embodiments only and is not intended to be limiting of
the invention. As used herein, the singular forms "a", "an" and
"the" are intended to include the plural forms as well, unless the
context clearly indicates otherwise. It will be further understood
that the terms "comprises" and/or "comprising," when used in this
specification, specify the presence of stated features, integers,
steps, operations, elements, and/or components, but do not preclude
the presence or addition of one or more other features, integers,
steps, operations, elements, components, and/or groups thereof.
[0060] Any suitable computer usable or computer readable medium may
be utilized. The computer-usable or computer-readable medium may
be, for example but not limited to, an electronic, magnetic,
optical, electromagnetic, infrared, or semiconductor system,
apparatus, device, or propagation medium. More specific examples (a
non-exhaustive list) of the computer-readable medium would include
the following: an electrical connection having one or more wires, a
portable computer diskette, a hard disk, a random access memory
(RAM), a read-only memory (ROM), an erasable programmable read-only
memory (EPROM or Flash memory), an optical fiber, a portable
compact disc read-only memory (CD-ROM), an optical storage device,
a transmission media such as those supporting the Internet or an
intranet, or a magnetic storage device. Note that the
computer-usable or computer-readable medium could even be paper or
another suitable medium upon which the program is printed, as the
program can be electronically captured, via, for instance, optical
scanning of the paper or other medium, then compiled, interpreted,
or otherwise processed in a suitable manner, if necessary, and then
stored in a computer memory. In the context of this document, a
computer-usable or computer-readable medium may be any medium that
can contain, store, communicate, propagate, or transport the
program for use by or in connection with the instruction execution
system, apparatus, or device. The computer-usable medium may
include a propagated data signal with the computer-usable program
code embodied therewith, either in baseband or as part of a carrier
wave. The computer usable program code may be transmitted using any
appropriate medium, including but not limited to the Internet,
wireline, optical fiber cable, RF, etc.
[0061] Computer program code for carrying out operations of one or
more embodiments of the present invention may be written in an
object oriented programming language such as Java, Smalltalk, C++
or the like. However, the computer program code for carrying out
operations of one or more embodiments of the present invention may
also be written in conventional procedural programming languages,
such as the "C" programming language or similar programming
languages. The program code may execute entirely on the user's
computer, partly on the user's computer, as a stand-alone software
package, partly on the user's computer and partly on a remote
computer or entirely on the remote computer or server. In the
latter scenario, the remote computer may be connected to the user's
computer through a local area network (LAN) or a wide area network
(WAN), or the connection may be made to an external computer (for
example, through the Internet using an Internet Service
Provider).
[0062] The present invention is described below with reference to
flowchart illustrations and/or block diagrams of methods, apparatus
(systems) and computer program products according to embodiments of
the invention. It will be understood that each block of the
flowchart illustrations and/or block diagrams, and combinations of
blocks in the flowchart illustrations and/or block diagrams, can be
implemented by computer program instructions. These computer
program instructions may be provided to a processor of a general
purpose computer, special purpose computer, or other programmable
data processing apparatus to produce a machine, such that the
instructions, which execute via the processor of the computer or
other programmable data processing apparatus, create means for
implementing the functions/acts specified in the flowchart and/or
block diagram block or blocks.
[0063] These computer program instructions may also be stored in a
computer-readable memory that can direct a computer or other
programmable data processing apparatus to function in a particular
manner, such that the instructions stored in the computer-readable
memory produce an article of manufacture including instruction
means which implement the function/act specified in the flowchart
and/or block diagram block or blocks.
[0064] The computer program instructions may also be loaded onto a
computer or other programmable data processing apparatus to cause a
series of operational steps to be performed on the computer or
other programmable apparatus to produce a computer implemented
process such that the instructions which execute on the computer or
other programmable apparatus provide steps for implementing the
functions/acts specified in the flowchart and/or block diagram
block or blocks.
[0065] The flowchart and block diagrams in the Figures illustrate
the architecture, functionality, and operation of possible
implementations of systems, methods and computer program products
according to various embodiments of the present invention for
example as shown in FIGS. 1-4 and 6-8. In this regard, each block
in the flowchart or block diagrams may represent a module, segment,
or portion of code, which comprises one or more executable
instructions for implementing the specified logical function(s). It
should also be noted that, in some alternative implementations, the
functions noted in the block may occur out of the order noted in
the figures. For example, two blocks shown in succession may, in
fact, be executed substantially concurrently, or the blocks may
sometimes be executed in the reverse order, depending upon the
functionality involved. It will also be noted that each block of
the block diagrams and/or flowchart illustration, and combinations
of blocks in the block diagrams and/or flowchart illustration, can
be implemented by special purpose hardware-based systems that
perform the specified functions or acts, or combinations of special
purpose hardware and computer instructions.
[0066] The corresponding structures, materials, acts, and
equivalents of all means or step plus function elements in the
claims below are intended to include any structure, material, or
act for performing the function in combination with other claimed
elements as specifically claimed. The description of the present
invention has been presented for purposes of illustration and
description, but is not intended to be exhaustive or limited to the
invention in the form disclosed. Many modifications and variations
will be apparent to those of ordinary skill in the art without
departing from the scope and spirit of the invention. The
embodiment was chosen and described in order to best explain the
principles of the invention and the practical application, and to
enable others of ordinary skill in the art to understand the
invention for various embodiments with various modifications as are
suited to the particular use contemplated.
[0067] Having thus described the invention of the present
application in detail and by reference to embodiments thereof, it
will be apparent that modifications and variations are possible
without departing from the scope of the invention defined in the
appended claims.
* * * * *