A semantic grid is an approach to grid computing in which information, computing resources and services are described using the semantic data model . In this model, the data and metadata are expressed through facts (small sentences), becoming directly understandable for humans. This makes it easier for resources to be discovered and combined automatically to create virtual organizations (VOs). The descriptions constitute metadata and are typically represented using the technologies of the Semantic Web , such as the Resource Description Framework (RDF).
7-527: Like the Semantic Web, the semantic grid can be defined as "an extension of the current grid in which information and services are given well-defined meaning, better enabling computers and people to work in cooperation." This notion of the semantic grid was first articulated in the context of e-Science , observing that such an approach is necessary to achieve a high degree of easy-to-use and seamless automation, enabling flexible collaborations and computations on
14-529: A global scale. The use of semantic web and other knowledge technologies in grid applications are sometimes described as the knowledge grid. Semantic grid extends this by also applying these technologies within the grid middleware . Some semantic grid activities are coordinated through the Semantic Grid Research Group of the Global Grid Forum . This World Wide Web –related article
21-460: Is a stub . You can help Misplaced Pages by expanding it . Middleware Middleware is a type of computer software program that provides services to software applications beyond those available from the operating system . It can be described as "software glue". Middleware makes it easier for software developers to implement communication and input/output, so they can focus on the specific purpose of their application. It gained popularity in
28-474: Is somewhat standardized through the Service Availability Forum and is commonly used in complex, embedded systems within the telecom, defence, and aerospace industries. Many categories of middleware have been defined, based on the field in which it is used or the application module it serves. A recent bibliography identified the main categories of middleware as follows: The term middleware
35-844: The operating system and applications on each side of a distributed computing system in a network." Services that can be regarded as middleware include enterprise application integration , data integration , message oriented middleware (MOM), object request brokers (ORBs), and the enterprise service bus (ESB). Database access services are often characterised as middleware. Some of them are language specific implementations and support heterogeneous features and other related communication features. Examples of database-oriented middleware include ODBC , JDBC , and transaction processing monitors. Distributed computing system middleware can loosely be divided into two categories—those that provide human-time services (such as web request servicing) and those that perform in machine-time. This latter middleware
42-415: The 1980s as a solution to the problem of how to link newer applications to older legacy systems, although the term had been in use since 1968. The term is most commonly used for software that enables communication and management of data in distributed applications . An IETF workshop in 2000 defined middleware as "those services found above the transport (i.e. over TCP/IP) layer set of services but below
49-434: The application environment" (i.e. below application-level APIs ). In this more specific sense middleware can be described as the hyphen ("-") in client-server , or the -to- in peer-to-peer . Middleware includes web servers , application servers , content management systems , and similar tools that support application development and delivery. ObjectWeb defines middleware as: "The software layer that lies between
#258741