US20130086061A1 - Implementing service oriented architecture industry model repository using semantic web technologies - Google Patents
Implementing service oriented architecture industry model repository using semantic web technologies Download PDFInfo
- Publication number
- US20130086061A1 US20130086061A1 US13/533,007 US201213533007A US2013086061A1 US 20130086061 A1 US20130086061 A1 US 20130086061A1 US 201213533007 A US201213533007 A US 201213533007A US 2013086061 A1 US2013086061 A1 US 2013086061A1
- Authority
- US
- United States
- Prior art keywords
- services
- assets
- topic
- repository
- computer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000005516 engineering process Methods 0.000 title description 9
- 230000015654 memory Effects 0.000 claims description 26
- 238000004891 communication Methods 0.000 claims description 24
- 238000000034 method Methods 0.000 claims description 23
- 238000004590 computer program Methods 0.000 claims description 11
- 238000013499 data model Methods 0.000 claims description 2
- 238000013461 design Methods 0.000 claims description 2
- 230000008520 organization Effects 0.000 claims 2
- 230000001419 dependent effect Effects 0.000 claims 1
- 238000012545 processing Methods 0.000 description 34
- 230000002085 persistent effect Effects 0.000 description 18
- 238000010586 diagram Methods 0.000 description 17
- 230000006870 function Effects 0.000 description 9
- 230000003287 optical effect Effects 0.000 description 5
- 241000207961 Sesamum Species 0.000 description 4
- 235000003434 Sesamum indicum Nutrition 0.000 description 4
- 239000004744 fabric Substances 0.000 description 4
- 238000007726 management method Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 230000000155 isotopic effect Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 239000000463 material Substances 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 238000013550 semantic technology Methods 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000012800 visualization Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 230000000644 propagated effect Effects 0.000 description 1
- 210000003813 thumb Anatomy 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
-
- G06F17/30002—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Definitions
- 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.
- SOA service oriented architecture
- IMR industry model repository
- 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).
- ISO 13250-1 topic map related ISO/IEC standards
- RDMS relational database management system
- individual semantic technologies such as web ontology language (OWL), resource description framework (RDF), and SPARQL protocol and RDF query language (SPARQL).
- 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.
- TMCL Topic Map Constraint Language
- TQL Topic Map Query Language
- RDBMS Relational Database Management System
- SQL structured query language
- a method for implementing topic map meta models of a service oriented architecture (SOA) industry model repository (IMR) 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.
- FIG. 1 is a computer network in which illustrative embodiments may be implemented.
- FIG. 2 is a data processing system in which illustrative embodiments may be implemented.
- 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.
- IMR industry model repository
- FIG. 4 shows an overview of a service oriented architecture (SOA) industry model repository (IMR) meta-model with OWL/RDF maps.
- SOA service oriented architecture
- IMR industry model repository
- FIG. 5 shows an example of an OWL-DL representation of a topic map.
- 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.
- 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.
- 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.
- 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.
- 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.
- server 4 and server 6 connect to network 2 along with storage unit 8 .
- clients 10 , 12 , and 14 connect to network 2 .
- Clients 10 , 12 , and 14 may be, for example, personal computers or network computers.
- 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.
- 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.
- 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 .
- 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.
- TCP/IP Transmission Control Protocol/Internet Protocol
- 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.
- 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.
- 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.
- 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 .
- communications fabric 22 provides communications between processor unit 24 , memory 26 , persistent storage 28 , communications unit 30 , input/output (I/O) unit 32 , and display 34 .
- 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.
- 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.
- persistent storage 28 may contain one or more components or devices.
- 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.
- a removable hard drive may be used for persistent storage 28 .
- Communications unit 30 in these examples, provides for communications with other data processing systems or devices.
- 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.
- Input/output unit 32 allows for input and output of data with other devices that may be connected to data processing system 20 .
- 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.
- 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 .
- 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 .
- program code computer usable program code, or computer readable program code
- 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 .
- 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.
- 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 .
- 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.
- 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 .
- 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 .
- 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 .
- 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.
- 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.
- a storage device may be comprised of an organic semiconductor.
- 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.
- 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.
- 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.
- a communications unit may include one or more devices used to transmit and receive data, such as a modem or a network adapter.
- 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 .
- 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 .
- 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.
- 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 .
- 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 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.
- the IMR users 108 may include but are not limited to repository administrator, model manager, system architect, and business analyst.
- 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.
- 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 .
- RAM model assets
- wiki document models
- 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.
- 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.
- 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.
- 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 .
- RDF resource description framework
- 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.
- 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:
- 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 .
- 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.
- a handle to the RDF repository 350 is obtained.
- uniform resource identifiers for each topic of the topic map 210 are created 352 .
- a connection to the repository is obtained 354 .
- 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 .
- the topic occurrence RDF statements or RDF triples 360 to be sent to the repository.
- an occurrence of the topic in the topic map is read 362 .
- a topic occurrence RDF statement or RDF triple is created 364 .
- 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.
- 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.
- 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.
- the semantic web RDF repository allows for 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.
- the standards based query language of SPARQL Protocol and RDF Query Language 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.
- 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.
- inference technology such as semantic web based query languages, such as SPARQL to provide answers to queries across the asset-requirements topic maps.
- SPARQL semantic web based query languages
- semantic web technologies of the World Wide Web Consortium 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.
- 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.
- 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.
- a 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.
- 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.
- 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).
- LAN local area network
- WAN wide area network
- Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.
- 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.
- 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.
- 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).
- 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.
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.
Description
- Pursuant to 35 USC §120, this application is a continuation application of U.S. patent application Ser. No. 12/640,697 filed Dec. 17, 2009 (pending).
- 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.
- 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).
- 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.
- 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.
- Each individual semantic technology implementation provides its own set of advantages and disadvantages.
- 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.
-
FIG. 1 is a computer network in which illustrative embodiments may be implemented. -
FIG. 2 is a data processing system in which illustrative embodiments may be implemented. -
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. -
FIG. 4 shows an overview of a service oriented architecture (SOA) industry model repository (IMR) meta-model with OWL/RDF maps. -
FIG. 5 shows an example of an OWL-DL representation of a topic map. -
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. -
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. -
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. - 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 thatFIGS. 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. -
FIG. 1 depicts a pictorial representation of a network of data processing systems in which illustrative embodiments may be implemented. Networkdata processing system 1 is a network of computers in which the illustrative embodiments may be implemented. Networkdata processing system 1 containsnetwork 2, which is the medium used to provide communication links between various devices and computers connected together within networkdata processing system 1.Network 2 may include connections, such as wire, wireless communication links, or fiber optic cables. - In the depicted example,
server 4 andserver 6 connect tonetwork 2 along withstorage unit 8. In addition,clients network 2.Clients server 4 provides information, such as boot files, operating system images, and applications toclients Clients data processing system 1 may include additional servers, clients, and other devices not shown. - 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 onserver 4 and downloaded toclient 10 overnetwork 2 for use onclient 10. - In the depicted example, network
data processing system 1 is the Internet withnetwork 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, networkdata 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. - 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 asserver 4 orclient 10 inFIG. 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 includescommunications fabric 22, which provides communications betweenprocessor unit 24,memory 26,persistent storage 28,communications unit 30, input/output (I/O)unit 32, anddisplay 34. -
Processor unit 24 serves to execute instructions for software that may be loaded intomemory 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. -
Memory 26 andpersistent storage 28 are examples ofstorage 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 bypersistent storage 28 also may be removable. For example, a removable hard drive may be used forpersistent storage 28. -
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. - Input/
output unit 32 allows for input and output of data with other devices that may be connected todata 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. - Instructions for the operating system, applications, and/or programs may be located in
storage devices 36, which are in communication withprocessor unit 24 throughcommunications fabric 22. In these illustrative examples the instructions are in a functional form onpersistent storage 28. These instructions may be loaded intomemory 26 for running byprocessor unit 24. The processes of the different embodiments may be performed byprocessor unit 24 using computer implemented instructions, which may be located in a memory, such asmemory 26. - 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 asmemory 26 orpersistent storage 28. -
Program code 38 is located in a functional form on computerreadable media 40 that is selectively removable and may be loaded onto or transferred todata processing system 20 for running byprocessor unit 24.Program code 38 and computerreadable media 40 formcomputer program product 42 in these examples. In one example, computerreadable 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 ofpersistent storage 28 for transfer onto a storage device, such as a hard drive that is part ofpersistent storage 28. In a tangible form, computerreadable 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 todata processing system 20. The tangible form of computerreadable media 40 is also referred to as computerrecordable storage media 44. In some instances, computerreadable media 40 may not be removable. - Alternatively,
program code 38 may be transferred todata processing system 20 from computerreadable media 40 through a communications link tocommunications 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 computerreadable signal media 46. - In some illustrative embodiments,
program code 38 may be downloaded over a network topersistent storage 28 from another device or data processing system for use withindata 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 todata processing system 20. The data processing system providingprogram code 38 may be a server computer, a client computer, or some other device capable of storing and transmittingprogram code 38. - 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 fordata processing system 20. Other components shown inFIG. 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. - 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 computerreadable media 40 are examples of storage devices in a tangible form. - 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 incommunications fabric 22. -
FIG. 3 shows theIMR architecture system 100 which may be part of the networkdata processing system 1 shown inFIG. 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 andtopic map interface 104 andsemantic web implementation 105 which represent and implement the IMR meta models using semantics provided by the OWL language. TheSOA 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. - The
IMR architecture system 100 includes federatedphysical 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 inFIG. 3 . - Applications and
services 106 are provided toIMR users 108 through the network 109 (e.g. intranet or Internet) usinginterfaces 107. The interfaces used by theIMR users 108 include reports generation and tools supporting multi-formats and visualization tools supporting complex views. The applications andservices 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 inFIG. 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. Theinterfaces 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. - The
IMR users 108 may include but are not limited to repository administrator, model manager, system architect, and business analyst. -
FIG. 4 shows a service oriented architecture (SOA) industry model repository (IMR)component 102 in greater detail. TheSOA IMR component 102 includes aMeta Model Service 202 associated with the physical asset repository. Within themeta 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 mapmeta model 210 with data specific to a particular topic or industry vertical. The topic mapmeta model 210 is associated with the physical asset repositories which may include but are not limited torepository 204 of model assets (RAM) 212,requirement models 214, and document models (wiki) 216. - The internal
meta model service 202 of theSOA IMR component 102 is the SOA IMR meta-model service using ISO Standard topicmap 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 mapsmeta models model service interface 202 allow users to programmatically access, manage, and maintain these meta models. - 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.
- The SOA IMR
meta model service 202 maps or implements the ISO topicmap 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 topicmap 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. -
FIG. 5 shows an example of a topic map. Thetopic map 400 may be converted to an OWL-DL representation. ‘Abandon’ 401 shown inFIG. 5 is an index item in the ISO topic mapmeta model 210. Converting thetopic map 400 ofFIG. 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 thetopic map 400 shown inFIG. 5 was converted to an OWL-DL representation, the following would be assigned: -
- Abandon 401 is a topic
-
Requirements Model 402 is a topic - Atomic Data Element 403 is a topic
- Claim recovery—Abandoned 404 is a topic
- Has 411 is an association type
-
Found 412 is an association type
Then, the ‘abandon’topic 401 is searched for in other parts of thesemantic web repository 218. The search results may yield as follows: - Topic Abandon found in topic Claim recovery—Abandoned
- Once the topics, occurrences and attributes are assigned, they are converted to RDF triples and persisted in an RDF repository.
-
FIG. 6 is a UML class diagram that shows a Java implementation of the SOA IMR meta data management interface. TheTopicMapService 340 is an interface is implemented by theTopicMapServiceBindingImpl 342. TheTopicMapServiceBindingImpl 342 uses aCacheManagerSingleton 344 to add and remove an item from cache and aController 346 to create or get Associations, Occurrence, Topics, TopicMap and set Associations and Topics. TheController 346 usesTopicMapRDFDAO 348 to provide the conversion of the SOA IMR topic mapmeta model 210 to an OWL-DL representation 218. - The
TopicMapRDFDAO 348 converts a topic of atopic map 210 into RDF triples and then the RDF triples are persisted in an RDF repository. Referring toFIG. 7 , in a first step a handle to theRDF repository 350 is obtained. Then, uniform resource identifiers for each topic of thetopic 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 thetopic map 210 are created 356 and the topic RDF statements RDF triples are added to therepository 358. - 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 therepository 366.Decision point 368 shows that if there are additional occurrences of the topic on thetopic map 210, the steps of creating a topic occurrence RDF statement or RDF triple 364 and adding a topic occurrence RDF statement to therepository 366 are repeated until no more occurrences of the topic on thetopic map 210 occur. - 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.
-
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. - 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.
- 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.
- 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.
- 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.
- 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.
- 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).
- 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.
- 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.
- 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.
- 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. - 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.
- 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.
Claims (20)
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.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/533,007 US20130086061A1 (en) | 2009-12-17 | 2012-06-26 | Implementing service oriented architecture industry model repository using semantic web technologies |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/640,697 US8244768B2 (en) | 2009-12-17 | 2009-12-17 | Implementing service oriented architecture industry model repository using semantic web technologies |
US13/533,007 US20130086061A1 (en) | 2009-12-17 | 2012-06-26 | Implementing service oriented architecture industry model repository using semantic web technologies |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/640,697 Continuation US8244768B2 (en) | 2009-12-17 | 2009-12-17 | Implementing service oriented architecture industry model repository using semantic web technologies |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130086061A1 true US20130086061A1 (en) | 2013-04-04 |
Family
ID=44152528
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/640,697 Expired - Fee Related US8244768B2 (en) | 2009-12-17 | 2009-12-17 | Implementing service oriented architecture industry model repository using semantic web technologies |
US13/533,007 Abandoned US20130086061A1 (en) | 2009-12-17 | 2012-06-26 | Implementing service oriented architecture industry model repository using semantic web technologies |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/640,697 Expired - Fee Related US8244768B2 (en) | 2009-12-17 | 2009-12-17 | Implementing service oriented architecture industry model repository using semantic web technologies |
Country Status (1)
Country | Link |
---|---|
US (2) | US8244768B2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130173523A1 (en) * | 2011-12-29 | 2013-07-04 | Spribo, Llc. | Method and system for contextual knowledge society network |
US9026412B2 (en) | 2009-12-17 | 2015-05-05 | International Business Machines Corporation | Managing and maintaining scope in a service oriented architecture industry model repository |
US20180366013A1 (en) * | 2014-08-28 | 2018-12-20 | Ideaphora India Private Limited | System and method for providing an interactive visual learning environment for creation, presentation, sharing, organizing and analysis of knowledge on subject matter |
US11551567B2 (en) * | 2014-08-28 | 2023-01-10 | Ideaphora India Private Limited | System and method for providing an interactive visual learning environment for creation, presentation, sharing, organizing and analysis of knowledge on subject matter |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9721216B2 (en) * | 2007-11-26 | 2017-08-01 | International Business Machines Corporation | Solution that automatically recommends design assets when making architectural design decisions for information services |
US8341155B2 (en) * | 2008-02-20 | 2012-12-25 | International Business Machines Corporation | Asset advisory intelligence engine for managing reusable software assets |
US8607190B2 (en) * | 2009-10-23 | 2013-12-10 | International Business Machines Corporation | Automation of software application engineering using machine learning and reasoning |
US8645904B2 (en) * | 2009-10-26 | 2014-02-04 | International Business Machines Corporation | Cross repository impact analysis using topic maps |
US9704130B2 (en) * | 2009-10-26 | 2017-07-11 | International Business Machines Corporation | Standard based mapping of industry vertical model to legacy environments |
US8726236B2 (en) * | 2009-10-26 | 2014-05-13 | International Business Machines Corporation | Determining context specific content |
US8775462B2 (en) * | 2009-12-17 | 2014-07-08 | International Business Machines Corporation | Service oriented architecture industry model repository meta-model component with a standard based index |
US8566358B2 (en) * | 2009-12-17 | 2013-10-22 | International Business Machines Corporation | Framework to populate and maintain a service oriented architecture industry model repository |
US8631071B2 (en) | 2009-12-17 | 2014-01-14 | International Business Machines Corporation | Recognition of and support for multiple versions of an enterprise canonical message model |
US8244768B2 (en) | 2009-12-17 | 2012-08-14 | International Business Machines Corporation | Implementing service oriented architecture industry model repository using semantic web technologies |
US9111004B2 (en) | 2009-12-17 | 2015-08-18 | International Business Machines Corporation | Temporal scope translation of meta-models using semantic web technologies |
US20120278353A1 (en) * | 2011-04-28 | 2012-11-01 | International Business Machines | Searching with topic maps of a model for canonical model based integration |
US8666951B2 (en) * | 2012-01-20 | 2014-03-04 | International Business Machines Corporation | Managing multiple versions of enterprise meta-models using semantic based indexing |
IN2013CH05997A (en) * | 2013-12-20 | 2015-06-26 | Infosys Ltd | |
US9026652B1 (en) * | 2014-07-09 | 2015-05-05 | Fmr Llc | Web service asset management and web service information storage |
CN106156238B (en) * | 2015-04-27 | 2019-09-03 | 科大讯飞股份有限公司 | Ontology information querying method and system |
CN105955999B (en) * | 2016-04-20 | 2019-04-23 | 华中科技大学 | A kind of ThetaJoin inquiry processing method of extensive RDF graph |
CN106021420A (en) * | 2016-05-13 | 2016-10-12 | 乐视控股(北京)有限公司 | Method and device for optimizing table structure |
CN106874426B (en) * | 2017-01-23 | 2019-12-31 | 福州大学 | RDF (resource description framework) streaming data keyword real-time searching method based on Storm |
CN110659350B (en) * | 2019-09-24 | 2023-03-21 | 吉林大学 | Semantic search system and search method based on domain ontology |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6789252B1 (en) * | 1999-04-15 | 2004-09-07 | Miles D. Burke | Building business objects and business software applications using dynamic object definitions of ingrediential objects |
US20060206883A1 (en) * | 2004-07-13 | 2006-09-14 | The Mitre Corporation | Semantic system for integrating software components |
US20060271563A1 (en) * | 2001-05-15 | 2006-11-30 | Metatomix, Inc. | Appliance for enterprise information integration and enterprise resource interoperability platform and methods |
US20080126397A1 (en) * | 2006-07-03 | 2008-05-29 | Oracle International Corporation | RDF Object Type and Reification in the Database |
US20090018996A1 (en) * | 2007-01-26 | 2009-01-15 | Herbert Dennis Hunt | Cross-category view of a dataset using an analytic platform |
US20090063522A1 (en) * | 2007-08-17 | 2009-03-05 | Oracle International Corporation | System and method for managing ontologies as service metadata assets in a metadata repository |
US20090150981A1 (en) * | 2007-12-06 | 2009-06-11 | Alexander Phillip Amies | Managing user access entitlements to information technology resources |
US20100174693A1 (en) * | 2009-01-08 | 2010-07-08 | Fluid Operations Gmbh | Collaborative workbench for managing data from heterogeneous sources |
US20110035391A1 (en) * | 2009-08-06 | 2011-02-10 | Sap Ag | Uniform Data Model and API for Representation and Processing of Semantic Data |
Family Cites Families (55)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US1260565A (en) * | 1917-08-29 | 1918-03-26 | James E Marshall | Inclinometer. |
US6366930B1 (en) * | 1996-04-12 | 2002-04-02 | Computer Associates Think, Inc. | Intelligent data inventory & asset management systems method and apparatus |
US6799174B2 (en) * | 1997-09-08 | 2004-09-28 | Science Applications International Corporation | Retrieving, organizing, and utilizing networked data using databases |
US7783468B2 (en) * | 1998-05-13 | 2010-08-24 | Accretive Technologies, Inc. | Automated system and method for service and cost architecture modeling of enterprise systems |
US6539396B1 (en) * | 1999-08-31 | 2003-03-25 | Accenture Llp | Multi-object identifier system and method for information service pattern environment |
US6256773B1 (en) * | 1999-08-31 | 2001-07-03 | Accenture Llp | System, method and article of manufacture for configuration management in a development architecture framework |
US7099859B2 (en) * | 2000-01-20 | 2006-08-29 | International Business Machines Corporation | System and method for integrating off-line ratings of businesses with search engines |
US7080064B2 (en) * | 2000-01-20 | 2006-07-18 | International Business Machines Corporation | System and method for integrating on-line user ratings of businesses with search engines |
JP2001290937A (en) * | 2000-04-07 | 2001-10-19 | Fujitsu Ltd | Asset management system |
EP1360611A2 (en) * | 2000-12-12 | 2003-11-12 | Time Warner Entertainment Company, L.P. | Digital asset data type definitions |
US6925457B2 (en) * | 2001-07-27 | 2005-08-02 | Metatomix, Inc. | Methods and apparatus for querying a relational data store using schema-less queries |
US20030009740A1 (en) * | 2001-06-11 | 2003-01-09 | Esoftbank (Beijing) Software Systems Co., Ltd. | Dual & parallel software development model |
US7103871B1 (en) * | 2002-04-04 | 2006-09-05 | Bellsouth Intellectual Property Corp. | Method for rapid application life cycle change requests |
US7483879B2 (en) * | 2003-01-17 | 2009-01-27 | International Business Machines Corporation | System and method for accessing non-compatible content repositories |
US7631314B2 (en) * | 2003-08-26 | 2009-12-08 | International Business Machines Corporation | Method and system for dynamically associating type information and creating and processing meta-data in a service oriented architecture |
US7693973B2 (en) * | 2003-08-28 | 2010-04-06 | International Business Machines Corporation | Pluggable state meta-data processors based on meta information modeling in a service oriented architecture |
US7483973B2 (en) * | 2003-08-28 | 2009-01-27 | International Business Machines Corporation | Gateway for service oriented state |
US8180845B2 (en) * | 2003-12-17 | 2012-05-15 | Sap Ag | Remote debugging of software |
US20060047810A1 (en) * | 2004-09-02 | 2006-03-02 | Kyle Herzog | Asset management system and method |
US7487512B2 (en) * | 2004-09-30 | 2009-02-03 | Sap Ag | Publish-subscribe event notifications |
US20060112122A1 (en) * | 2004-11-23 | 2006-05-25 | International Business Machines Corporation | Method, system, and storage medium for implementing business process modules |
US7805382B2 (en) * | 2005-04-11 | 2010-09-28 | Mkt10, Inc. | Match-based employment system and method |
US20060236307A1 (en) * | 2005-04-15 | 2006-10-19 | Debruin David | System and method for transformation of wireless application definition to simplified form |
US20070022410A1 (en) * | 2005-07-22 | 2007-01-25 | Ban Linda B | Method and system for using a component business model to transform warranty claims processing in the automotive industry |
US20070073663A1 (en) * | 2005-09-26 | 2007-03-29 | Bea Systems, Inc. | System and method for providing full-text searching of managed content |
US7831535B2 (en) * | 2005-11-02 | 2010-11-09 | Manyworlds, Inc. | Adaptive knowledge lifecycle management aligned with assessed financial value based on organizing structure of knowledge assets |
US7856446B2 (en) * | 2005-12-27 | 2010-12-21 | Baynote, Inc. | Method and apparatus for determining usefulness of a digital asset |
CN100558038C (en) | 2006-03-31 | 2009-11-04 | 国际商业机器公司 | Service logger and related system and method |
US20070239768A1 (en) * | 2006-04-10 | 2007-10-11 | Graphwise Llc | System and method for creating a dynamic database for use in graphical representations of tabular data |
US7526501B2 (en) * | 2006-05-09 | 2009-04-28 | Microsoft Corporation | State transition logic for a persistent object graph |
US7516155B2 (en) * | 2006-05-16 | 2009-04-07 | International Business Machines Corporation | method to validate consistency of component business model maps |
US7979840B2 (en) * | 2006-10-31 | 2011-07-12 | International Business Machines Corporation | Method and apparatus for service-oriented architecture process decomposition and service modeling |
US8930890B2 (en) * | 2006-12-05 | 2015-01-06 | International Business Machines Corporation | Software model skinning |
US7606795B2 (en) * | 2007-02-08 | 2009-10-20 | International Business Machines Corporation | System and method for verifying the integrity and completeness of records |
KR101307711B1 (en) * | 2007-05-16 | 2013-09-11 | 인터내셔널 비지네스 머신즈 코포레이션 | A consistent method system and computer program for developing software asset based solutions |
US8122426B2 (en) * | 2007-08-29 | 2012-02-21 | International Business Machines Corporation | Governance framework for architecture design in a service oriented enterprise |
US9811849B2 (en) * | 2007-09-28 | 2017-11-07 | Great-Circle Technologies, Inc. | Contextual execution of automated workflows |
US8577837B2 (en) * | 2007-10-30 | 2013-11-05 | Sap Ag | Method and system for generic extraction of business object data |
US8230387B2 (en) * | 2007-10-31 | 2012-07-24 | International Business Machines Corporation | System and method to organize assets in a repository |
US20090182750A1 (en) * | 2007-11-13 | 2009-07-16 | Oracle International Corporation | System and method for flash folder access to service metadata in a metadata repository |
US9721216B2 (en) * | 2007-11-26 | 2017-08-01 | International Business Machines Corporation | Solution that automatically recommends design assets when making architectural design decisions for information services |
US8250521B2 (en) * | 2007-12-14 | 2012-08-21 | International Business Machines Corporation | Method and apparatus for the design and development of service-oriented architecture (SOA) solutions |
US9589250B2 (en) * | 2008-01-11 | 2017-03-07 | Oracle International Corporation | System and method for asset registration workflows utilizing an eventing infrastructure in a metadata repository |
US8589338B2 (en) * | 2008-01-24 | 2013-11-19 | Oracle International Corporation | Service-oriented architecture (SOA) management of data repository |
US8627339B2 (en) * | 2008-01-24 | 2014-01-07 | International Business Machines Corporation | Service-oriented architecture component processing model |
US8401022B2 (en) * | 2008-02-08 | 2013-03-19 | Oracle International Corporation | Pragmatic approaches to IMS |
US9646274B2 (en) * | 2008-02-11 | 2017-05-09 | Oracle International Corporation | System and method for accessing business process instances through mobile devices |
US20090210390A1 (en) * | 2008-02-20 | 2009-08-20 | International Business Machines Corporation | Asset adviser intelligence engine for managing reusable software assets |
US9171096B2 (en) * | 2008-10-24 | 2015-10-27 | Oracle International Corporation | System and method for harvesting metadata into a service metadata repository |
KR100993288B1 (en) * | 2008-12-15 | 2010-11-09 | 한국과학기술정보연구원 | System and Method for Efficient Reasoning Using View in DBMS-based RDF Triple Store |
US8566358B2 (en) * | 2009-12-17 | 2013-10-22 | International Business Machines Corporation | Framework to populate and maintain a service oriented architecture industry model repository |
US8631071B2 (en) * | 2009-12-17 | 2014-01-14 | International Business Machines Corporation | Recognition of and support for multiple versions of an enterprise canonical message model |
US8244768B2 (en) | 2009-12-17 | 2012-08-14 | International Business Machines Corporation | Implementing service oriented architecture industry model repository using semantic web technologies |
US9111004B2 (en) * | 2009-12-17 | 2015-08-18 | International Business Machines Corporation | Temporal scope translation of meta-models using semantic web technologies |
US9026412B2 (en) * | 2009-12-17 | 2015-05-05 | International Business Machines Corporation | Managing and maintaining scope in a service oriented architecture industry model repository |
-
2009
- 2009-12-17 US US12/640,697 patent/US8244768B2/en not_active Expired - Fee Related
-
2012
- 2012-06-26 US US13/533,007 patent/US20130086061A1/en not_active Abandoned
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6789252B1 (en) * | 1999-04-15 | 2004-09-07 | Miles D. Burke | Building business objects and business software applications using dynamic object definitions of ingrediential objects |
US20060271563A1 (en) * | 2001-05-15 | 2006-11-30 | Metatomix, Inc. | Appliance for enterprise information integration and enterprise resource interoperability platform and methods |
US20060206883A1 (en) * | 2004-07-13 | 2006-09-14 | The Mitre Corporation | Semantic system for integrating software components |
US20080126397A1 (en) * | 2006-07-03 | 2008-05-29 | Oracle International Corporation | RDF Object Type and Reification in the Database |
US20090018996A1 (en) * | 2007-01-26 | 2009-01-15 | Herbert Dennis Hunt | Cross-category view of a dataset using an analytic platform |
US20090063522A1 (en) * | 2007-08-17 | 2009-03-05 | Oracle International Corporation | System and method for managing ontologies as service metadata assets in a metadata repository |
US20090150981A1 (en) * | 2007-12-06 | 2009-06-11 | Alexander Phillip Amies | Managing user access entitlements to information technology resources |
US20100174693A1 (en) * | 2009-01-08 | 2010-07-08 | Fluid Operations Gmbh | Collaborative workbench for managing data from heterogeneous sources |
US20110035391A1 (en) * | 2009-08-06 | 2011-02-10 | Sap Ag | Uniform Data Model and API for Representation and Processing of Semantic Data |
Non-Patent Citations (1)
Title |
---|
Heather Kreger, "Navigating the SOA Open Standards Landscape Around Architecture" * |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9026412B2 (en) | 2009-12-17 | 2015-05-05 | International Business Machines Corporation | Managing and maintaining scope in a service oriented architecture industry model repository |
US20130173523A1 (en) * | 2011-12-29 | 2013-07-04 | Spribo, Llc. | Method and system for contextual knowledge society network |
US20180366013A1 (en) * | 2014-08-28 | 2018-12-20 | Ideaphora India Private Limited | System and method for providing an interactive visual learning environment for creation, presentation, sharing, organizing and analysis of knowledge on subject matter |
US11551567B2 (en) * | 2014-08-28 | 2023-01-10 | Ideaphora India Private Limited | System and method for providing an interactive visual learning environment for creation, presentation, sharing, organizing and analysis of knowledge on subject matter |
Also Published As
Publication number | Publication date |
---|---|
US8244768B2 (en) | 2012-08-14 |
US20110153608A1 (en) | 2011-06-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8244768B2 (en) | Implementing service oriented architecture industry model repository using semantic web technologies | |
US9111004B2 (en) | Temporal scope translation of meta-models using semantic web technologies | |
US8775462B2 (en) | Service oriented architecture industry model repository meta-model component with a standard based index | |
US8631071B2 (en) | Recognition of and support for multiple versions of an enterprise canonical message model | |
US9026412B2 (en) | Managing and maintaining scope in a service oriented architecture industry model repository | |
US20180232265A1 (en) | System and method for detecting, collecting, analyzing, and communicating event-related information | |
US20190287006A1 (en) | Integrated monitoring and communications system using knowledge graph based explanatory equipment management | |
US8566358B2 (en) | Framework to populate and maintain a service oriented architecture industry model repository | |
US20150227839A1 (en) | Systems and methods for semantic inference and reasoning | |
WO2016033493A1 (en) | Dynamic ontology schema generation and asset management for standards for exchanging data | |
Nath et al. | SETL: A programmable semantic extract-transform-load framework for semantic data warehouses | |
Pedrinaci et al. | Semantic Web Services. | |
US20120030240A1 (en) | Enterprise content management federation and integration system | |
US9800644B2 (en) | Service oriented query and service query language framework | |
US20150127688A1 (en) | Facilitating discovery and re-use of information constructs | |
Buchmann et al. | Enriching linked data with semantics from domain-specific diagrammatic models | |
Pfaff et al. | A web-based system architecture for ontology-based data integration in the domain of IT benchmarking | |
Castellanos et al. | A framework for alignment of data and processes architectures applied in a government institution | |
Sargolzaei Javan et al. | SmartData 4.0: a formal description framework for big data | |
Dau | Semantic technologies for enterprises | |
Mezaour et al. | Building enterprise ready applications using linked open data | |
Yue | Semantic web-based intelligent geospatial web services | |
Powell et al. | A semantic registry for digital library collections and services | |
Indrayasaa et al. | Ontology-based Approach: A Smartphone Knowledge Representation | |
Slimani | Semantic description of web services |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |