MétaCan
Menu
Retour à la cohorte
Enregistrement W2532734653 · doi:10.1109/spca.2006.297458

Agent-Based Service-Oriented Computing and Applications

2006· article· en· W2532734653 sur OpenAlexaff
Weiming Shen, Hamada Ghenniwa, Yinsheng Li

Notice bibliographique

Revuenon disponible
Typearticle
Langueen
DomaineComputer Science
ThématiqueService-Oriented Architecture and Web Services
Établissements canadiensNational Research Council CanadaWestern University
Organismes subventionnairesnon disponible
Mots-clésComputer scienceServices computingWeb serviceWS-I Basic ProfileService-oriented architectureWS-PolicyWorld Wide WebInteroperabilitySOAPWeb modelingSoftware engineeringWeb developmentWeb application securityWeb intelligence

Résumé

récupéré en direct d'OpenAlex

Summary form only given. Service-oriented computing (SOC) is considered as a new computing paradigm after the object-oriented computing paradigm. It utilizes services as fundamental elements for applications/solutions. Services are autonomous platform-independent computational elements that can be described, published, discovered, orchestrated and programmed using XML for the purpose of developing massively distributed interoperable applications. Web services technology is part of the SOC paradigm and can be considered as an implementation of the SOC model. Web services are featured with application, platform and provider independence. They provide an appropriate approach for building open large-scale application environments. In such environments, services are not treated as isolated and one-time affairs but rather as elements of an interactive, dynamic and collaborative architecture. Service collaboration within or across environments is modelled in terms of supported transactions or processes that are subject to norms or protocols specified for certain business domains. Services are thereby orchestrated vertically within one environment, or horizontally across multiple environments. As a result, an individual environment streamlines services in terms of internal transactions while restrains its function scope to be highly specific to the targeted user group. Multiple environments collaborate in order to extend their business chains. Web services have been supported by major IT vendors through their commercial platforms such as Microsoft's .NET and SUN's J2EE. Web services have had quick evolution and broad acceptance. However, there are still a number of issues that limit the wide applications of Web services in industry. Current Web services technologies lack semantic description, generic service model, dynamic composition, and flexible cooperation strategies. Software agents have been proved to handle sophisticated interaction patterns. Agent-orientation is an appropriate design paradigm to enable automatic and dynamic collaborations, especially for e-Business systems with complex and distributed transactions. In services realization, software agents are very essential for the provision of a focused and cohesive set of active capabilities. Therefore, we envision a combination of agent and Web services technologies and strongly believe that we are on the right track towards an evolution of current SOC paradigm. Software agents can be one of the essential evolvements of Web services in that they are functional entities, instead of simple interaction delegations or communication proxies. The idea is to exploit agents' capabilities of proactive interactions to enhance Web services' behaviours. With such a computing paradigm, software components, each representing both a service and an agent, cooperatively or competitively interact to provide unified services in a specified environment, such as brokering, pricing and negotiation in an e-marketplace, as well as cross-enterprise environments, such as integration and cooperation in a virtual enterprise. We envision a Web service-based environment as a collection of economically motivated agent-based Web services. Software agents are implemented as services with different functionalities and roles. In fact, the dynamic agent-based behaviour model plus the Web service-based interoperable protocols can generate a flexible, reconfigurable and coordinated approach to perform business process management both across enterprises and within an enterprise. We have developed an agent-based service-oriented system architecture for manufacturing enterprise collaboration. In this system, each enterprise provides a number of Web services registered in a UDDI repository. The Web services are implemented by the AWS (agent-based Web services) technology with a built-in agent core. So, enterprises are equipped with negotiation ability with upper mediating agents. Moreover, upper mediating agents are also implemented as a network of AWSs on the Internet. The unification of software agents and Web services can be proposed at both the design level and the implementation level. At the design level, we encapsulate Web services into agent models so that each agent represents a service in its action and relation to the environment. In this sense, we treat a Web service as a semi-autonomous agent. On the other hand, Web services technologies are used to implement the external behaviours of software agents. Therefore, agents can be used to build high-level models with flexible interaction patterns, while Web services are more suitable for solving interoperability problems among heterogeneous applications across enterprises. At the implementation level, UDDI, WSDL and SOAP provide such capacities as discovery, deployment and communication, while specifications such as BPEL4WS provide service composition and process enactment. A software prototype system has been implemented for inter-enterprise manufacturing resource sharing. It demonstrates how the proposed agent-based service-oriented integration architecture can be used to establish a collaborative environment that provides dynamic resource scheduling services

Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.

Comment cette classification a été obtenuedéplier

Prédiction distillée sur la base complète

Imitation des enseignants

Ni prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.

score de la tête « metaresearch » (Codex)0,000
score de la tête « metaresearch » (Gemma)0,000
Version: codex-gemma-dda1882f352aStatut de validation: machine_predicted_unvalidated
Catégories candidatesaucune
Catégories consensuellesaucune
DomaineSignal candidat: aucune · Signal consensuel: aucune
Devis d'étudeSignal candidat: Théorique ou conceptuel · Signal consensuel: aucune
GenreSignal candidat: Méthodes · Signal consensuel: aucune
Score de désaccord entre enseignants0,880
Score d'incertitude au seuil0,594

Scores Codex et Gemma par catégorie

CatégorieCodexGemma
Métarecherche0,0000,000
Méta-épidémiologie (sens strict)0,0000,000
Méta-épidémiologie (sens large)0,0000,000
Bibliométrie0,0000,001
Études des sciences et des technologies0,0000,000
Communication savante0,0000,000
Science ouverte0,0010,000
Intégrité de la recherche0,0000,000
Charge utile insuffisante (le modèle a refusé de juger)0,0000,000

Scores machine (provisoires)

Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.

Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.

Tête enseignante Opus0,006
Tête enseignante GPT0,221
Écart entre enseignants0,215 · la distance entre les deux têtes enseignantes sur ce seul travail
Statut de validationscore_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découle

Classification

machine, non validée

Prédiction automatique; un appel candidat d’une seule tête enseignante, pas un consensus.

Les modèles n’ont appliqué aucune catégorie : rien dans la taxonomie ne correspondait à ce travail.
Devis d'étudeThéorique ou conceptuel
Domainenon disponible
GenreMéthodes

Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».

En bref

Citations8
Publié2006
Routes d'admission1
Résumé présentoui

Explorer davantage

Même sujetService-Oriented Architecture and Web ServicesTravaux en français237 207