196,825 research outputs found

    Criojo: A Pivot Language for Service-Oriented Computing - The Introspective Chemical Abstract Machine

    Get PDF
    Interoperability remains a significant challenge in service-oriented computing. After proposing a pivot architecture to solve three interoperability problems, namely adaptation, integration and coordination problems between clients and servers, we explore the theoretical foundations for this architecture. A pivot architecture requires a universal language for orchestrating services and a universal language for interfacing resources. Since there is no evidence today that Web Services technologies can provide this basis, we propose a new language called Criojo and essentially show that it can be considered as a pivot language. We formalize the language Criojo and its operational semantics, by resorting to a chemical abstract machine, and give an account of formal translations into Criojo: in a distributed context, we deal with idiomatic languages for four major programming paradigms: imperative programming, logic programming, functional programming and concurrent programming

    A Survey Paper on Service Oriented Architecture Approach and Modern Web Services

    Get PDF
    Service-Oriented Architecture is an architectural design pattern based on distinct pieces of software providing application functionality as services to other applications via a protocol. It is a collection of micro-services which are self-contained and provides unit functionality. The architectural style has the following essential core features which are inter-operability, service abstraction, service discovery, service autonomy, service statelessness re-usability, loose coupling. Service-oriented architectures are not a new thing. The first service-oriented architecture for many people in the past was with the use DCOM (uses RPC – Remote Procedural Calls) and CORBA (uses IIOP protocol) but because of the lack of standards and also with the advent of modern web development (Web 2.0) and the use of mobile phones and their penetration service oriented architecture is being implemented as Web Services (uses mainly HTTP/HTTPS) protocol. Most common implementations of Web Services can be done as SOAP (Simple Object Access Protocol)-based which essentially is a HTTP/HTTPS POST with an XML payload in it. SOAP based web services expose service interface using WSDL (Web Service Description Language) and there is a pre-defined contract via XSD (XML Schema Definition) between the service being exposed and the client side that consumes this service. The other most popular lightweight implementation of web services is using RESTful (Representational State Transfer) architecture where the payload is in JSON (Java Script Object Notation) / XML and uses RESTful style of communication to access resources on the server. So any application written in any language for example C# or C++ or C or Groovy or Java that can make a HTTP call should be able to access the services and since the data is in XML/JSON they can make a sense of data and this way we can re-use services and be inter-operable. The goal of our survey is to delve deeper into SOA principles, key constituents and how Web Services - implementation of SOA has taken this into such a wide spread usage and created a phenomena and various technologies that can be used to develop/consume web services and also about the protocols being used and some common use cases in building re-usable and scalable application architectures using web services

    Performance evaluation of a distributed integrative architecture for robotics

    Get PDF
    The eld of robotics employs a vast amount of coupled sub-systems. These need to interact cooperatively and concurrently in order to yield the desired results. Some hybrid algorithms also require intensive cooperative interactions internally. The architecture proposed lends it- self amenable to problem domains that require rigorous calculations that are usually impeded by the capacity of a single machine, and incompatibility issues between software computing elements. Implementations are abstracted away from the physical hardware for ease of de- velopment and competition in simulation leagues. Monolithic developments are complex, and the desire for decoupled architectures arises. Decoupling also lowers the threshold for using distributed and parallel resources. The ability to re-use and re-combine components on de- mand, therefore is essential, while maintaining the necessary degree of interaction. For this reason we propose to build software components on top of a Service Oriented Architecture (SOA) using Web Services. An additional bene t is platform independence regarding both the operating system and the implementation language. The robot soccer platform as well as the associated simulation leagues are the target domain for the development. Furthermore are machine vision and remote process control related portions of the architecture currently in development and testing for industrial environments. We provide numerical data based on the Python frameworks ZSI and SOAPpy undermining the suitability of this approach for the eld of robotics. Response times of signi cantly less than 50 ms even for fully interpreted, dynamic languages provides hard information showing the feasibility of Web Services based SOAs even in time critical robotic applications

    Protocols and Structures for Inference: A RESTful API for Machine Learning

    Full text link
    Diversity in machine learning APIs (in both software toolkits and web services), works against realising machine learning’s full potential, making it difficult to draw on individual algorithms from different products or to compose multiple algorithms to solve complex tasks. This paper introduces the Protocols and Structures for Inference (PSI) service architecture and specification, which presents inferential entities—relations, attributes, learners and predictors—as RESTful web resources that are accessible via a common but flexible and extensible interface. Resources describe the data they ingest or emit using a variant of the JSON schema language, and the API has mechanisms to support non-JSON data and future extension of service features

    SSWAP: A Simple Semantic Web Architecture and Protocol for semantic web services

    Get PDF
    <p>Abstract</p> <p>Background</p> <p>SSWAP (<b>S</b>imple <b>S</b>emantic <b>W</b>eb <b>A</b>rchitecture and <b>P</b>rotocol; pronounced "swap") is an architecture, protocol, and platform for using reasoning to semantically integrate heterogeneous disparate data and services on the web. SSWAP was developed as a hybrid semantic web services technology to overcome limitations found in both pure web service technologies and pure semantic web technologies.</p> <p>Results</p> <p>There are currently over 2400 resources published in SSWAP. Approximately two dozen are custom-written services for QTL (Quantitative Trait Loci) and mapping data for legumes and grasses (grains). The remaining are wrappers to Nucleic Acids Research Database and Web Server entries. As an architecture, SSWAP establishes how clients (users of data, services, and ontologies), providers (suppliers of data, services, and ontologies), and discovery servers (semantic search engines) interact to allow for the description, querying, discovery, invocation, and response of semantic web services. As a protocol, SSWAP provides the vocabulary and semantics to allow clients, providers, and discovery servers to engage in semantic web services. The protocol is based on the W3C-sanctioned first-order description logic language OWL DL. As an open source platform, a discovery server running at <url>http://sswap.info</url> (as in to "swap info") uses the description logic reasoner Pellet to integrate semantic resources. The platform hosts an interactive guide to the protocol at <url>http://sswap.info/protocol.jsp</url>, developer tools at <url>http://sswap.info/developer.jsp</url>, and a portal to third-party ontologies at <url>http://sswapmeet.sswap.info</url> (a "swap meet").</p> <p>Conclusion</p> <p>SSWAP addresses the three basic requirements of a semantic web services architecture (<it>i.e</it>., a common syntax, shared semantic, and semantic discovery) while addressing three technology limitations common in distributed service systems: <it>i.e</it>., <it>i</it>) the fatal mutability of traditional interfaces, <it>ii</it>) the rigidity and fragility of static subsumption hierarchies, and <it>iii</it>) the confounding of content, structure, and presentation. SSWAP is novel by establishing the concept of a canonical yet mutable OWL DL graph that allows data and service providers to describe their resources, to allow discovery servers to offer semantically rich search engines, to allow clients to discover and invoke those resources, and to allow providers to respond with semantically tagged data. SSWAP allows for a mix-and-match of terms from both new and legacy third-party ontologies in these graphs.</p

    Multi-Paradigm Reasoning for Access to Heterogeneous GIS

    Get PDF
    Accessing and querying geographical data in a uniform way has become easier in recent years. Emerging standards like WFS turn the web into a geospatial web services enabled place. Mediation architectures like VirGIS overcome syntactical and semantical heterogeneity between several distributed sources. On mobile devices, however, this kind of solution is not suitable, due to limitations, mostly regarding bandwidth, computation power, and available storage space. The aim of this paper is to present a solution for providing powerful reasoning mechanisms accessible from mobile applications and involving data from several heterogeneous sources. By adapting contents to time and location, mobile web information systems can not only increase the value and suitability of the service itself, but can substantially reduce the amount of data delivered to users. Because many problems pertain to infrastructures and transportation in general and to way finding in particular, one cornerstone of the architecture is higher level reasoning on graph networks with the Multi-Paradigm Location Language MPLL. A mediation architecture is used as a “graph provider” in order to transfer the load of computation to the best suited component – graph construction and transformation for example being heavy on resources. Reasoning in general can be conducted either near the “source” or near the end user, depending on the specific use case. The concepts underlying the proposal described in this paper are illustrated by a typical and concrete scenario for web applications

    Workflow support for simulation of service oriented B-to-C transaction

    Get PDF
    Computation technologies and computer tools offer varied resources for the implementation of applications of electronic commerce (e-commerce). The current organizational models are based on nets of associations that are integrated to achieve business objectives. Therefore, the effectiveness of the commercial operation doesn't only depend on an appropriate configuration of technologies but also on efficiency in the business services. Service-Oriented Architecture (SOA) is an architectural style for distributed computation that considers the creation and administration of business services. With Web Services the services can be published in the Web and accessed by applications independently from language and technology. In this work a workflow support for the modeling and simulation of applications of e-commerce based on services and technologies Web Services is proposed. Tools are applied of processes modeling, with their integration in TIBCO that result in the modeling of a process business to consumer (b-to-c), their simulation and the evaluation of metrics of performanceI Workshop InnovaciĂłn en Sistemas de Software (WISS)Red de Universidades con Carreras en InformĂĄtica (RedUNCI

    Challenges for the Multilingual Web of Data

    Get PDF
    The Web has witnessed an enormous growth in the amount of semantic information published in recent years. This growth has been stimulated to a large extent by the emergence of Linked Data. Although this brings us a big step closer to the vision of a Semantic Web, it also raises new issues such as the need for dealing with information expressed in different natural languages. Indeed, although the Web of Data can contain any kind of information in any language, it still lacks explicit mechanisms to automatically reconcile such information when it is expressed in ifferent languages. This leads to situations in which data expressed in a certain language is not easily accessible to speakers of other languages. The Web of Data shows the potential for being extended to a truly multilingual web as vocabularies and data can be published in a language-independent fashion, while associated language-dependent (linguistic) information supporting the access across languages can be stored separately. In this sense, the multilingual Web of Data can be realized in our view as a layer of services and resources on top of the existing Linked Data infrastructure adding i) linguistic information for data and vocabularies in different languages, ii) mappings between data with labels in different languages, and iii) services to dynamically access and traverse Linked Data across different languages. In this article we present this vision of a multilingual Web of Data. We discuss challenges that need to be addressed to make this vision come true and discuss the role that techniques such as ontology localization, ontology mapping, and cross-lingual ontology-based information access and presentation will play in achieving this. Further, we propose an initial architecture and describe a roadmap that can provide a basis for the implementation of this vision

    How to Present Web-Based Legal Information: Towards Library Web 2.0

    Get PDF
    The World Wide Web has rapidly evolved from a technological into a social medium. Web 2.0 has become a metaphor for the distributed and decentralized collaboration networks on a global scale. With the recent trends of new media development, the sources available have reached a critical mass resulting in an unprecedented information overload. The urgent challenge to all information professionals, in this case law librarians, is no longer availability and direct provision of resources, but rather the filtering and highlighting. As an example of the utilization of Web 2.0 values, the Cornell Law Library (CLL) recently re-launched its website. The site highlights the wealth of resources and services available at this premier research library while, at all times, taking into consideration the information needs and information-seeking behaviors of our users and the worldwide legal research community. Library jargon was removed wherever possible to make the navigational language natural to non-librarians, which led to the creation of a new standard in interface design and information architecture for the site
    • 

    corecore