DOCSLIB.ORG

Understanding

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Understanding Implementing UBL Mark Crawford UBL Vice Chair XML 2003 9 December 2003 Why Are We Talking About UBL • UBL fulfils the promise of XML for business by defining a standard cross-industry vocabulary • UBL is the ebXML missing link • UBL plus ebXML enables the next generation of eBusiness exchanges – Cheaper, easier, Internet-ready – Extends benefits of EDI to small businesses – Fits existing legal and trade concepts – Allows re-use of data • UBL can provide the XML payload for a wide variety of other web-based business frameworks Overview 1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability 4 Making UBL Happen 5 UBL Phase 2 6 Summary The promise of XML for e-business • Plug ‘n’ play electronic commerce – Spontaneous trade – No custom programming • Ubiquity on the Internet – Dirt-cheap tools – Complete platform independence – Enable true global market availability • Enable universal interoperability – Abandon existing EDI systems – Handle both "publication" document types and "transactional" documents Goals for Successful eBusiness Services • Web-enable existing fax- and paper-based business practices • Allow businesses to upgrade at their own pace • Preserve the existing investment in electronic business exchanges • Integrate small and medium-size businesses into existing electronic data exchange-based supply chains The standardization of XML business documents is the easiest way to accomplish these goals. XML For Interoperability??? • anyML • anyML Diff erenc infor es in matio nal co ntent Diff eren tags ces & m in ean ings D iff ere nc p es os in itio ns Different information elements Can’t We Just Do It? OpenTag Markup W3C Specifications Documentation Metadata - PICS Document Definition Markup Language (DDML) T ext Encoding Initiative (T EI) MIX - Mediation of Information Using XML WEBDAV (IETF 'Extensions for Distributed Authoring and Versioning on the Web') Channel Definition Format, CDF (Based on XML) CDIF XML-Based Transfer Format DAV Searching and Locating (DASL) RDF Rich Site Summary (RSS) Synchronized Multimedia Integration Language (SMIL) Graphic Communications Association - GCA 'Paper' DT D Open Content Syndication (OCS) Precision Graphics Markup Language (PGML) DocBook XML DT D W3C Document Object Model (DOM), Level 1 Specification Vector Markup Language (VML) Tutorial Markup Language (T ML) Web Collections using XML WebBroker: Distributed Object Communication on the Web International Development Markup Language (IDML) Meta Content Framework Using XML (MCF) Web Interface Definition Language (WIDL) Call Processing Language (CPL) XML-Data XML/EDI - Electronic Data Interchange Call Policy Markup Language (CPML) Namespaces in XML XML/EDI Repository Working Group VoiceXML Forum (Voice Extensible Markup Language Forum) Resource Description Framework (RDF) European XML/EDI Pilot Project VoxML Markup Language Australia New Zealand Land Information Council (ANZLIC) - Metadata EEMA EDI/EC Work Group - XML/EDI Telephony Markup Language (T ML) Alexandria Digital Library Project ANSI ASC X12/XML and DISA SABLE: A Standard for T ext-to-Speech Synthesis Markup AT LA Serials Project (AT LAS) Information and Content Exchange (ICE) Java Speech Markup Language (JSML) XML Metadata Interchange Format (XMI)-Object Management Group (OMG) CommerceNet Industry Initiative SpeechML OMG Common Warehouse Metadata Interchange (CWMI) Specification eCo Interoperability Framework Specification TalkML Object Management Group XML/Value RFP BizT alk Framework XML and VRML (Virtual Reality Modeling Language) - X3D MDC Open Information Model (OIM) eCo Framework Project and Working Group XML for Workflow Management [NIST ] Educom Instructional Management Systems Project (IMS) Commerce XML (cXML) SWAP - Simple Workflow Access Protocol Metadata Specification RosettaNet XML-Based Process Management Standard: Wf-XML Structured Graph Format (SGF) Open Catalog Protocol (OCP) Theological Markup Language (T hML) Legal XML Working Group and UELP vCard Electronic Business Card LitML: A Liturgical Markup Language XML Court Interface (XCI) iCalendar XML DT D XML-F ('XML for FAX') Georgia State University Electronic Court Filing Project XML Encoded Form Values Extensible Forms Description Language (XFDL) Web Standards Project (WSP) Capability Card: An Attribute Certificate in XML XML Forms Architecture (XFA) HT ML T hreading - Use of HT ML in Email T elecommunications Interchange Markup (TIM, TCIF/IPI) Broadcast Hypertext Markup Language (BHT ML) Open Software Description Format (OSD) aecXML Working Group - Architecture, Engineering and Construction IEEE LTSC XML Ad Hoc Group XLF (Extensible Log Format) Initiative Product Data Markup Language (PDML) IEEE Standard DTD Apache XML Project Product Definition Exchange (PDX) Open Settlement Protocol (OSP) - ET SI/T IPHON WAP Wireless Markup Language Specification Electronic Component Information Exchange (ECIX) and Directory Services Markup Language (DSML) HT T P Distribution and Replication Protocol (DRP) Pinnacles Component Information Standard (PCIS) WDDX - Web Distributed Data Exchange Chemical Markup Language ECIX QuickData Specifications Business Rules Markup Language (BRML) Molecular Dynamics [Markup] Language (MoDL) ECIX Component Information Dictionary Standard (CIDS) Common Business Library (CBL) Bioinformatic Sequence Markup Language (BSML) ECIX Timing Diagram Markup Language (TDML) Open Applications Group - OAGIS BIOpolymer Markup Language (BIOML) Encoded Archival Description (EAD) Schema for Object-oriented XML (SOX) Virtual Hyperglossary (VHG) UML eXchange Format (UXF) XMLT P.Org - XML Transfer Protocol Weather Observation Definition Format (OMF) XML Data Binding Specification The XML Bookmark Exchange Language (XBEL) Open Financial Exchange (OFX/OFE) T ranslation Memory eXchange (T MX) Simple Object Definition Language (SODL) and XMOP Service Interactive Financial Exchange (IFX) P3P Syntax Specification Simple Object Access Protocol (SOAP) FinXML - 'T he Digital Language for Capital Markets' Scripting News in XML XML and Music Extensible Financial Reporting Markup Language (XFRML) InterX.org Initiative Clinical T rial Data Model Open T rading Protocol (OT P) NuDoc T echnology Human Resource Management Markup Language (HRMML) Financial Products Markup Language (FpML) Coins: Tightly Coupled JavaBeans and XML Elements HR-XML Consortium Mortgage Bankers Association of America XML Workgroup DMT F Common Information Model (CIM) XML-HR Initiative - Human Resources Digital Property Rights Language (DPRL) Universal Plug and Play Forum ECMData - Electronic Component Manufacturer Data Sheet Inventory Specification XML Digital Signature (Signed XML - IET F/W3C) Process Interchange Format XML (PIF-XML) Bean Markup Language (BML) Digital Receipt Infrastructure Initiative Ontology and Conceptual Knowledge Markup Languages The Koala Bean Markup Language (KBML) Digest Values for DOM (DOMHASH) XOL - XML-Based Ontology Exchange Language Jigsaw XML Format (JXML) Signed Document Markup Language (SDML) Procedural Markup Language (PML) Chinese XML Now! FIXML - A Markup Language for the FIX Application Message Layer QAML - T he Q&A Markup Language MOS-X (Media Object Server - XML) Bank Internet Payment System (BIPS) LACIT O Projet Archivage de données linguistiques FLBC (Formal Language for Business Communication) and KQML smartX ['SmartCard'] Markup Language (SML) sonores et textuelles [Linguistic Data Archiving Project] ISO 12083 XML DTDs Real Estate T ransaction Markup Language (RETML) Astronomical Markup Language Extensible User Interface Language (XUL) OpenMLS - Real Estate DT D Design Astronomical Instrument Markup Language (AIML) User Interface Markup Language (UIML) ACORD - XML for the Insurance Industry GedML: [GEDCOM] Genealogical Data in XML Process Specification Language (PSL) and XML Customer Profile Exchange (CPEX) Working Group Newspaper Association of America (NAA) - Standard for XML DTD for Phone Books Customer Support Consortium Classified Advertising Data 5.5 Using XML for RFCs XML for the Automotive Industry - SAE J2008 News Industry Text Format (NIT F) Schools Interoperability Framework (SIF) XML.ORG - T he XML Industry Portal XMLNews: XMLNews-Story and XMLNews-Meta Guideline XML (gXML) X-ACT - XML Active Content Technologies Council NewsML and IPT C2000 Extensible Protocol Electronic Business XML Initiative (ebXML) Notes Flat File Format (NFF) XML Belief Network File Format (Bayesian Networks) Portal Markup Language (PML) Java Help API Predictive Model Markup Language (PMML) EDGARspace Portal Cold Fusion Markup Language (CFML) The Data Documentation Initiative (DDI) DII Common Operating Environment (COE) XML Registry Document Content Description for XML (DCD) XML and CORBA Open eBook Initiative XSchema Mathematical Markup Language OpenMath Standard The Role of a Hub Format Why UBL? • Leverages knowledge from existing EDI and XML B2B systems • Applies across all industry sectors and domains of electronic trade (80/20 rule) • Fully leverages XML • Provides the ebXML missing link: – XML Payload +ebXML CCTS +modelling methodology • Non-proprietary and committed to freedom from royalties • On track to become international standard for trade through ISO TC154 Overview 1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability
Load more

Recommended publications
  • Using the UML for Architectural Description?
    Using the UML for Architectural Description? Rich Hilliard Integrated Systems and Internet Solutions, Inc. Concord, MA USA [email protected] Abstract. There is much interest in using the Unified Modeling Lan- guage (UML) for architectural description { those techniques by which architects sketch, capture, model, document and analyze architectural knowledge and decisions about software-intensive systems. IEEE P1471, the Recommended Practice for Architectural Description, represents an emerging consensus for specifying the content of an architectural descrip- tion for a software-intensive system. Like the UML, IEEE P1471 does not prescribe a particular architectural method or life cycle, but may be used within a variety of such processes. In this paper, I provide an overview of IEEE P1471, describe its conceptual framework, and investigate the issues of applying the UML to meet the requirements of IEEE P1471. Keywords: IEEE P1471, architectural description, multiple views, view- points, Unified Modeling Language 1 Introduction The Unified Modeling Language (UML) is rapidly maturing into the de facto standard for modeling of software-intensive systems. Standardized by the Object Management Group (OMG) in November 1997, it is being adopted by many organizations, and being supported by numerous tool vendors. At present, there is much interest in using the UML for architectural descrip- tion: the techniques by which architects sketch, capture, model, document and analyze architectural knowledge and decisions about software-intensive systems. Such techniques enable architects to record what they are doing, modify or ma- nipulate candidate architectures, reuse portions of existing architectures, and communicate architectural information to others. These descriptions may the be used to analyze and reason about the architecture { possibly with automated support.
    [Show full text]
  • OMG Systems Modeling Language (OMG Sysml™) Tutorial 25 June 2007
    OMG Systems Modeling Language (OMG SysML™) Tutorial 25 June 2007 Sanford Friedenthal Alan Moore Rick Steiner (emails included in references at end) Copyright © 2006, 2007 by Object Management Group. Published and used by INCOSE and affiliated societies with permission. Status • Specification status – Adopted by OMG in May ’06 – Finalization Task Force Report in March ’07 – Available Specification v1.0 expected June ‘07 – Revision task force chartered for SysML v1.1 in March ‘07 • This tutorial is based on the OMG SysML adopted specification (ad-06-03-01) and changes proposed by the Finalization Task Force (ptc/07-03-03) • This tutorial, the specifications, papers, and vendor info can be found on the OMG SysML Website at http://www.omgsysml.org/ 7/26/2007 Copyright © 2006,2007 by Object Management Group. 2 Objectives & Intended Audience At the end of this tutorial, you should have an awareness of: • Benefits of model driven approaches for systems engineering • SysML diagrams and language concepts • How to apply SysML as part of a model based SE process • Basic considerations for transitioning to SysML This course is not intended to make you a systems modeler! You must use the language. Intended Audience: • Practicing Systems Engineers interested in system modeling • Software Engineers who want to better understand how to integrate software and system models • Familiarity with UML is not required, but it helps 7/26/2007 Copyright © 2006,2007 by Object Management Group. 3 Topics • Motivation & Background • Diagram Overview and Language Concepts • SysML Modeling as Part of SE Process – Structured Analysis – Distiller Example – OOSEM – Enhanced Security System Example • SysML in a Standards Framework • Transitioning to SysML • Summary 7/26/2007 Copyright © 2006,2007 by Object Management Group.
    [Show full text]
  • 73 Metadata Interchange in Service Based Architecture
    UDC:681.324 Review paper METADATA INTERCHANGE IN SERVICE BASED ARCHITECTURE Alma Butkovi Tomac Nagravision Kudelski group, Cheseaux / Lausanne [email protected] Dražen Tomac Cambridge Technology Partners, Genève [email protected] Abstract: Metadata is important factor for understanding, controlling and planning in complex information systems both from technical and business perspective. However its usage is often limited due to opposing or non-existent standards. The article discusses current state of meta model standards and shows new possibilities for meta data interchange based on XML as de facto standard for data interchange and increasing acceptance of web services architecture. Keywords: metadata, web services, XMI, CWM. 1. INTRODUCTION Term “meta” comes from old Greek work representing after, next, with; Latin word denoting something transcendental or beyond nature. Applying the prefix meta denotes more comprehensive or transcendent then the base itself. Meta data transcends the data in a way that it describes or references more than individual data instance: it provides domain, format, context of the data, data source, business related rule etc. Most common short definitions on metadata say: Meta data is data about data. This definition does not describe meta data in its whole scope. To quote [4]:” Meta data is all physical data (contained in software and other media) and knowledge (contained in employees and various media) from inside and outside an organization, including information about the physical data, technical and business processes, rules and constraints of the data, and structures of the data used by a corporation.” 2. METADATA SIGNIFICANCE Although metadata significance is widely recognized and important in information systems, it gains on its importance for data warehouse projects, business intelligence and semantic web.
    [Show full text]
  • Pivotpoint-Sparx Partnership Promotes Model-Based Systems
    PivotPoint-Sparx Partnership Promotes Model-Based Systems Engineering with SysML PivotPoint Technology and Sparx Systems today announced a technology partnership that will combine their complementary strengths in SysML training and tools for systems engineers. PivotPoint announced that its “SysML Distilled™ with Enterprise Architect™” workshop is immediately available, and will use Sparx’s new MDG Technology for SysML™ product. Fallbrook, California (PRWEB) - October 9, 2006 -- PivotPoint Technology and Sparx Systems today announced a technology partnership to promote model-based systems engineering with the Systems Modeling Language (SysML). SysML is the new domain-specific modeling language for systems engineering applications that was adopted by the Object Management Group as OMG SysML™ in July 2006, and is attracting users among systems engineers worldwide. Under the agreement, PivotPoint will be Sparx’s primary partner for training and consulting services that use Sparx’s new SysML product (MDG Technology for SysML™), which was released last week. PivotPoint showed its readiness to partner by announcing the immediate availability of a new “SysML Distilled™ with Enterprise Architect™” workshop, which combines both SysML language and tool training. SysML extends the Unified Modeling Language (UML), the industry standard for specifying software-intensive systems, so that it can also specify hardware, processes, personnel, and facilities. Systems engineers who want to follow a model-based systems engineering process gain at least two important advantages in using SysML. First, SysML is a smaller language than UML 2.0 since it has fewer diagrams and constructs, so it is easier for engineers to learn and apply. Second, SysML adds to the semantic expressiveness of UML with two new diagrams for defining requirements and parametric constraints, which systems engineers need to fully specify complex systems.
    [Show full text]
  • 03-01-06 BPDM RFP.Pdf
    Business Process Definition Metamodel RFP Object Management Group First Needham Place 250 First Avenue, Suite 100 Needham, MA 02494 Telephone: +1-781-444-0404 Facsimile: +1-781-444-0320 Business Process Definition Metamodel Request For Proposal OMG Document: bei/2003-01-06 Letters of Intent due: June 16, 2003 Submissions due: August 18, 2003 Objective of this RFP This Request For Proposals solicits submissions that specify a business process definition metamodel, which is platform independent with respect to specific business process definition languages. This metamodel will define an abstract language for specification of executable business processes that execute within an enterprise (with or without human involvement); and may collaborate between otherwise- independent business processes executing in different business units or enterprises. The specification developed in response to this RFP is expected to achieve the following: • A common metamodel to unify the diverse business process definition graphical and textual notations that exist in the industry • A metamodel that complements existing UML metamodels so that business processes specifications can be part of complete system specifications to assure consistency and completeness bei/2003-01-06, January 31, 2003 1 Business Process Definition Metamodel RFP • The ability to integrate process models for workflow management processes, automated business processes, and collaborations between business units. • Support for the specification of choreography, describing the collaboration
    [Show full text]
  • Designing Universal Chemical Markup (UCM) Through the Reusable Methodology Based on Analyzing Existing Related Formats
    Designing Universal Chemical Markup (UCM) through the reusable methodology based on analyzing existing related formats Background: In order to design concepts for a new general-purpose chemical format we analyzed the strengths and weaknesses of current formats for common chemical data. While the new format is discussed more in the next article, here we describe our software s t tools and two stage analysis procedure that supplied the necessary information for the n i r development. The chemical formats analyzed in both stages were: CDX, CDXML, CML, P CTfile and XDfile. In addition the following formats were included in the first stage only: e r P CIF, InChI, NCBI ASN.1, NCBI XML, PDB, PDBx/mmCIF, PDBML, SMILES, SLN and Mol2. Results: A two stage analysis process devised for both XML (Extensible Markup Language) and non-XML formats enabled us to verify if and how potential advantages of XML are utilized in the widely used general-purpose chemical formats. In the first stage we accumulated information about analyzed formats and selected the formats with the most general-purpose chemical functionality for the second stage. During the second stage our set of software quality requirements was used to assess the benefits and issues of selected formats. Additionally, the detailed analysis of XML formats structure in the second stage helped us to identify concepts in those formats. Using these concepts we came up with the concise structure for a new chemical format, which is designed to provide precise built-in validation capabilities and aims to avoid the potential issues of analyzed formats.
    [Show full text]
  • Linking Nwchem and Avogadro with the Syntax and Semantics of Chemical Markup Language Wibe a De Jong1*†, Andrew M Walker2† and Marcus D Hanwell3†
    de Jong et al. Journal of Cheminformatics 2013, 5:25 http://www.jcheminf.com/content/5/1/25 RESEARCH ARTICLE Open Access From data to analysis: linking NWChem and Avogadro with the syntax and semantics of Chemical Markup Language Wibe A de Jong1*†, Andrew M Walker2† and Marcus D Hanwell3† Abstract Background: Multidisciplinary integrated research requires the ability to couple the diverse sets of data obtained from a range of complex experiments and computer simulations. Integrating data requires semantically rich information. In this paper an end-to-end use of semantically rich data in computational chemistry is demonstrated utilizing the Chemical Markup Language (CML) framework. Semantically rich data is generated by the NWChem computational chemistry software with the FoX library and utilized by the Avogadro molecular editor for analysis and visualization. Results: The NWChem computational chemistry software has been modified and coupled to the FoX library to write CML compliant XML data files. The FoX library was expanded to represent the lexical input files and molecular orbitals used by the computational chemistry software. Draft dictionary entries and a format for molecular orbitals within CML CompChem were developed. The Avogadro application was extended to read in CML data, and display molecular geometry and electronic structure in the GUI allowing for an end-to-end solution where Avogadro can create input structures, generate input files, NWChem can run the calculation and Avogadro can then read in and analyse the CML output produced. The developments outlined in this paper will be made available in future releases of NWChem, FoX, and Avogadro. Conclusions: The production of CML compliant XML files for computational chemistry software such as NWChem can be accomplished relatively easily using the FoX library.
    [Show full text]
  • ABBREVIATIONS EBU Technical Review
    ABBREVIATIONS EBU Technical Review AbbreviationsLast updated: January 2012 720i 720 lines, interlaced scan ACATS Advisory Committee on Advanced Television 720p/50 High-definition progressively-scanned TV format Systems (USA) of 1280 x 720 pixels at 50 frames per second ACELP (MPEG-4) A Code-Excited Linear Prediction 1080i/25 High-definition interlaced TV format of ACK ACKnowledgement 1920 x 1080 pixels at 25 frames per second, i.e. ACLR Adjacent Channel Leakage Ratio 50 fields (half frames) every second ACM Adaptive Coding and Modulation 1080p/25 High-definition progressively-scanned TV format ACS Adjacent Channel Selectivity of 1920 x 1080 pixels at 25 frames per second ACT Association of Commercial Television in 1080p/50 High-definition progressively-scanned TV format Europe of 1920 x 1080 pixels at 50 frames per second http://www.acte.be 1080p/60 High-definition progressively-scanned TV format ACTS Advanced Communications Technologies and of 1920 x 1080 pixels at 60 frames per second Services AD Analogue-to-Digital AD Anno Domini (after the birth of Jesus of Nazareth) 21CN BT’s 21st Century Network AD Approved Document 2k COFDM transmission mode with around 2000 AD Audio Description carriers ADC Analogue-to-Digital Converter 3DTV 3-Dimension Television ADIP ADress In Pre-groove 3G 3rd Generation mobile communications ADM (ATM) Add/Drop Multiplexer 4G 4th Generation mobile communications ADPCM Adaptive Differential Pulse Code Modulation 3GPP 3rd Generation Partnership Project ADR Automatic Dialogue Replacement 3GPP2 3rd Generation Partnership
    [Show full text]
  • XML for Java Developers G22.3033-002 Course Roadmap
    XML for Java Developers G22.3033-002 Session 1 - Main Theme Markup Language Technologies (Part I) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Course Roadmap Consider the Spectrum of Applications Architectures Distributed vs. Decentralized Apps + Thick vs. Thin Clients J2EE for eCommerce vs. J2EE/Web Services, JXTA, etc. Learn Specific XML/Java “Patterns” Used for Data/Content Presentation, Data Exchange, and Application Configuration Cover XML/Java Technologies According to their Use in the Various Phases of the Application Development Lifecycle (i.e., Discovery, Design, Development, Deployment, Administration) e.g., Modeling, Configuration Management, Processing, Rendering, Querying, Secure Messaging, etc. Develop XML Applications as Assemblies of Reusable XML- Based Services (Applications of XML + Java Applications) 2 1 Agenda XML Generics Course Logistics, Structure and Objectives History of Meta-Markup Languages XML Applications: Markup Languages XML Information Modeling Applications XML-Based Architectures XML and Java XML Development Tools Summary Class Project Readings Assignment #1a 3 Part I Introduction 4 2 XML Generics XML means eXtensible Markup Language XML expresses the structure of information (i.e., document content) separately from its presentation XSL style sheets are used to convert documents to a presentation format that can be processed by a target presentation device (e.g., HTML in the case of legacy browsers) Need a
    [Show full text]
  • Business Meeting of the Openmath Society 2018
    Business Meeting of the OpenMath Society 2018 Michael Kohlhase (President) Openmath Society http://openmath.org August 13. 2018, Hagenberg Kohlhase: Business Meeting of the OpenMath Society 2018 1 13. 8. 18, Hagenberg OpenMath 2018 Business Meeting (as required by Statutes) 1. Election of Chair of the meeting 2. Election of Secretary and two Minute Checkers (James is in Rio) 3. Annual Report 4. New Members? 5. Adoption of Balance Sheet and discharge of the Executive Committee 6. GDPR/Privacy issues for the Minutes 7. Election of the Executive Committee 8. Adoption of the second revision of the OM2 Standard 9. New OpenMath web site 10. OpenMath in JSON 11. OpenMath3 12. OMCD (management) Issues 13. Any Other Business (please come forward) Kohlhase: Business Meeting of the OpenMath Society 2018 2 13. 8. 18, Hagenberg Annual Report on Activities (2017-2018) I Last Open Business meeting, July 2017 in Edinburgh (internal ones in Spring to keep charter happy) I OM Repositories: Moved all digital assets to http://github.com/OpenMath I OM Web Site: deployed a new web site based on GH Pages (see below) I OM CD Submission Process: based on GitHub now, I OM Standard moved to separate repository, build process renovated, automated by travis. I OM2 Standard: thorough editing, more error fixing (OM binding) I OM3 Standard Effort: not started due to OM2e2 work Kohlhase: Business Meeting of the OpenMath Society 2018 3 13. 8. 18, Hagenberg New Members? I Anybody who has attended 3 OM Workshops or worked on OM for 6 months can become a member (will be generous) I please suggest new members (self-nominations encouraged) I New members proposed by OM Executive Committee I ???? Kohlhase: Business Meeting of the OpenMath Society 2018 4 13.
    [Show full text]
  • Wireless Application Protocol WAP
    Wireless Application Protocol WAP F. Ricci 2008/2009 Content Web and mobility Problems of HTML in the mobile context Wap 1.x Motivations Features Architecture Examples of WML (Wireless Markup Language) pages Wap 2.0 XHTML MP Examples Differences with Wap 1.x Examples World Wide Web and mobility Protocol (HTTP, Hypertext Transfer Protocol) and language (HTML, Hypertext Markup Language) of the Web have not been designed for mobile applications and mobile devices, thus creating many problems! Typical transfer sizes HTTP request: 100-350 byte responses avg. <10 kbyte, header 160 byte, GIF 4.1kByte, JPEG 12.8 kbyte, HTML 5.6 kbyte but also many large files that cannot be ignored The Web is not a file system Web pages are not simple files to download static and dynamic content, interaction with servers via forms, content transformation, push technologies etc. many hyperlinks, automatic loading and reloading, redirecting a single click might have big consequences! HTML and mobile devices HTML designed for computers with “high” performance, color high-resolution display, mouse, hard disk typically, web pages optimized for design, not for communication Mobile devices often only small, low-resolution displays, very limited input interfaces (small touch-pads, soft-keyboards) Additional “features” animated GIF, Java AWT, Frames, ActiveX Controls, Shockwave, movie clips, audio, ... many web pages assume true color, multimedia support, high-resolution and many plug-ins Web pages ignore the heterogeneity of end-systems!
    [Show full text]
  • A Logic-Based Service for Verifying Use Case Models
    COMPUTATION TOOLS 2017 : The Eighth International Conference on Computational Logics, Algebras, Programming, Tools, and Benchmarking A Logic-based Service for Verifying Use Case Models Fernando Bautista, Carlos Cares Computer Science and Informatics Department, University of La Frontera (UFRO) Temuco, Chile Email: [email protected], [email protected] Abstract—Use cases are a modeling means to specify the required modular and scalable solution in order to initially implement use of software systems. As part of UML (Unified Modeling some types of verifications and then another group of them Language), it has become the de facto standard for functional under an incremental development. specifications, mainly in object-oriented design and development. In order to check these models, we propose a theoretical solution In this paper, we present a first Prolog prototype, as proof by adapting a general quality of models framework (SEQUAL), of concept, of a tool that can aid the quality assessment of and, following our approach, a rule-based solution that includes a use case diagram. Moreover, we have implemented it as a both expert-based and definition-based rules. In order to promote Web service in order to illustrate that logic-based solutions can a distributed set of quality assessment services, a Web service has also be part of key quality assessment process in cloud-based been developed. It works on XMI (XML Metadata Interchange) software development environment. files which are parsed and verified by Prolog clauses. In order to check use case models and their application, Keywords–Rule-based quality; UseCase verification; Logic- based services; XMI; Prolog.
    [Show full text]