Scalable vector graphics
TL;DR: This article introduces the scalable vector graphics (SVG) standard by highlighting two main SVG themes: graphics capabilities and dynamism.
Abstract: This article introduces the scalable vector graphics (SVG) standard by highlighting two main SVG themes: graphics capabilities and dynamism. SVG can satisfy needs for distributed, lightweight, graphics-centered applications. Its integration with other XML technologies make it an ideal fit for ever-expanding XML workflows.
Citations
More filters
TL;DR: BioModels Database has become a recognised reference resource for systems biology and is being used by the community in a variety of ways; for example, it is used to benchmark different simulation systems, and to study the clustering of models based upon their annotations.
Abstract: Background
Quantitative models of biochemical and cellular systems are used to answer a variety of questions in the biological sciences. The number of published quantitative models is growing steadily thanks to increasing interest in the use of models as well as the development of improved software systems and the availability of better, cheaper computer hardware. To maximise the benefits of this growing body of models, the field needs centralised model repositories that will encourage, facilitate and promote model dissemination and reuse. Ideally, the models stored in these repositories should be extensively tested and encoded in community-supported and standardised formats. In addition, the models and their components should be cross-referenced with other resources in order to allow their unambiguous identification.
587 citations
16 Jun 2009
TL;DR: This model tries to fulfill the promise of the HTML5 specification, which references X3D for declarative 3D scenes but does not define a specific integration mode, and proposes an implementation framework that should work with multiple browser frontends and different X2D runtime backends.
Abstract: We present a model that allows to directly integrate X3D nodes into HTML5 DOM content. This model tries to fulfill the promise of the HTML5 specification, which references X3D for declarative 3D scenes but does not define a specific integration mode. The goal of this model is to ease the integration of X3D in modern web applications by directly mapping and synchronizing live DOM elements to a X3D scene model. This is a very similar approach to the current SVG integration model for 2D graphics.Furthermore, we propose a framework that includes a new X3D Profile for the DOM integration. This profile should make implementation simple, but in addition we show that the current X3D runtime model still scales well. A detailed discussion includes DOM integration issues like events, namespaces and scripting. We finally propose an implementation framework that should work with multiple browser frontends (e.g. Firefox and WebKit) and different X3D runtime backends.We hope to connect the technologies and the X3D/ W3C communities with this proposal and outline a model, how an integration without plugins could work. Moreover, we hope to inspire further work, which could lead to a native X3D implementation in browsers similar to the SVG implementations today.
303 citations
TL;DR: The article emphasizes the demonstration of the expressive power of the notation and how it can support the description of various aspects of user interfaces, namely interaction techniques, interactive components, and the behavioral part of interactive applications such as the dialog and the functional core.
Abstract: The design of real-life complex systems calls for advanced software engineering models, methods, and tools in order to meet critical requirements such as reliability, dependability, safety, or resilience that will avoid putting the company, the mission, or even human life at stake. When such systems encompass a substantial interactive component, the same level of confidence is required towards the human-computer interface. Conventional empirical or semiformal techniques, although very fruitful, do not provide sufficient insight on the reliability of the human-system cooperation, and offer no easy way to, for example, quantitatively and qualitatively compare two design options with respect to that reliability. The aim of this article is to present a user interface description language (called ICOs) for the engineering and development of usable and reliable user interfaces. The CASE tool supporting the ICOs notation (called Petshop) is a Petri nets-based-tool for the design, specification, prototyping, and validation of interactive software. In that environment models (built with the formal description technique ICOs) of the interactive application can be interactively modified and executed. This is used to support prototyping phases (when the models and the interactive application evolve significantly to meet late user requirements, for instance) as well as the operation phase (after the system is deployed). The use of ICOs and PetShop is presented on several large-scale systems such as a multimodal ground segment application for satellite control, an air traffic control interactive application, and an application for new generation of interactive cockpits in large civil aircraft such as Airbus A380 or Boeing 787. The article emphasizes the demonstration of the expressive power of the notation and how it can support the description of various aspects of user interfaces, namely interaction techniques (both WIMP and post-WIMP), interactive components (such as widgets), and the behavioral part of interactive applications such as the dialog and the functional core. It also demonstrates that PetShop provides dedicated support for prototyping activities of behavioral aspects at the various levels of the architecture of interactive systems. While the focus is on past work done on various large-scale applications, the article also highlights why and how ICOs and Petshop are able to address challenges raised by next-generation user interfaces.
166 citations
TL;DR: An XML-based interchange format for event-driven process chains (EPC) that is called EPC markup language (EPML), which builds on EPC syntax related work and is tailored to be a serialization format for EPC modelling tools.
Abstract: This article presents an XML-based interchange format for event-driven process chains (EPC) that is called EPC markup language (EPML). EPML builds on EPC syntax related work and is tailored to be a serialization format for EPC modelling tools. Design principles inspired by other standardization efforts and XML design guidelines have governed the specification of EPML. After giving an overview of EPML concepts we present examples to illustrate its features including flat and hierarchical EPCs, business views, graphical information, and syntactical correctness.
151 citations
TL;DR: The first survey of the state of the art in the field of real-time 3D graphics rendering in the browser is presented, which briefly summarise the approaches for remote rendering of3D graphics, before surveying complementary research on data compression methods, and notable application fields.
142 citations
References
More filters
Book•
01 Nov 2000
TL;DR: This specification defines the features and syntax for Scalable Vector Graphics (SVG) Version 1.1, a modularized language for describing two-dimensional vector and mixed vector/raster graphics in XML.
Abstract: This specification defines the features and syntax for Scalable Vector Graphics (SVG) Version 1.1, a modularized language for describing two-dimensional vector and mixed vector/raster graphics in XML. Status of this document This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C. This document is the 15 November 2002 Proposed Recommendation of the SVG 1.1 specification. SVG 1.1 serves two purposes: to provide a modularization of SVG based on SVG 1.0 and to include the errata found so far in SVG 1.0. The SVG Working Group believes SVG 1.1 has been widely reviewed by the community, developers and other W3C groups. The list of changes made in this version of the document is available. W3C Advisory Committee representatives are invited to send formal review comments to the W3C Team until 20 December 2002 at w3t-svg@w3.org. After the review the Director will announce the document's disposition. This announcement should not be expected sooner than 21 days after the end of the review. Public comments are also welcome. Please send them to www-svg@w3.org: the public email list for issues related to vector graphics on the Web. This list is archived and senders must agree to have their message publicly archived from their first posting. To subscribe send an email to www-svg-request@w3.org with the word subscribe in the subject line. The W3C SVG Working Group have released a test suite for SVG 1.1 along with an implementation report. The latest information regarding patent disclosures related to this document is available on the Web. As of this publication, the SVG Working Group are not aware of any royaltybearing patents they believe to be essential to SVG. This document has been produced by the W3C SVG Working Group as part of the Graphics Activity within the W3C Document Formats Domain. The goals of the W3C SVG Working Group are discussed in the W3C SVG Charter (W3C Members only). The W3C SVG Working Group has maintained a public Web page, http://www.w3.org/Graphics/SVG/, which contains further background information. The authors of this document are the SVG Working Group participants. Publication of this document does not imply endorsement by the W3C membership. A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR/. W3C publications may be updated, replaced, or obsoleted by other documents at any time.
382 citations