DOCSLIB.ORG

TU07 XML at The

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
TU07 XML at The ApacheCon 2004 November 2004 XML at the ASF Ted Leung [email protected] Copyright © Sauria Associates, LLC 2004 1 ApacheCon 2004 November 2004 Overview xml.apache.org ws.apache.org Xerces XML-RPC Xalan Axis FOP WSIF Batik JaxMe Xindice cocoon.apache.org Forrest XML-Security Cocoon XML-Commons Lenya XMLBeans Copyright © Sauria Associates, LLC ApacheCon 2004 2 There are three major XML focused projects at the ASF. Originally there was one project, xml.apache.org. Earlier this year, the Cocoon and web services projects were formed. Xml.apache.org contains a number of projects that are general purpose XML tools. Most of these tools are based on specifications from the World Wide Web Consortium. This includes XML itself, XSLT, XSL Formatting object, Scalable Vector Graphics, and XML Signature and XML Encryption The web services project, ws.apache.org contains projects that cluster around standards for dealing with Web Services, including SOAP and XML-RPC The Cocoon project is oriented around the Cocoon Web publishing framework which is basd on XML, XSLT, and a number of other XML related technologies. I’m not going to be able to give you any deep technical details regarding all of these projects. Instead, I’m going to try to describe what these projects are, what standards they implement, and talk about situations where you might use them. Unless I say otherwise, I’m going to be covering the Java projects. There are a few projects which have C/C++ versions and I’ll mention that where applicable. Copyright © Sauria Associates, LLC 2004 2 ApacheCon 2004 November 2004 Xerces-J <?xml version="1.0" encoding="UTF-8"?> <books xmlns="http://sauria.com/schemas/apache-xml-book/books" xmlns:tns="http://sauria.com/schemas/apache-xml-book/books" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation= "http://sauria.com/schemas/apache-xml-book/books http://www.sauria.com/schemas/apache-xml-book/books.xsd" version="1.0"> <book> <title>Effective Java</title> <author>Joshua Bloch</author> <isbn>yyy-yyyyyyyyyy</isbn> <month>August</month> <year>2001</year> <publisher>Addison-Wesley</publisher> <address>New York, New York</address> </book> </books> Copyright © Sauria Associates, LLC ApacheCon 2004 3 Xerces-J is an XML parser written in Java. There is also a C++ version Xerces-C, and a Perl wrapper for the C Version called Xerces-P The job of an XML parser is to break an XML document up into its constituent parts: Elements Attributes Character data The parser also verifies that the document obeys the rules of XML: Well-formedness Validity (optional) Namespace rules The parts are exposed to an application via an API of some sort. XML Parsing is the fundamental building block for just about every XML based application and technology Copyright © Sauria Associates, LLC 2004 3 ApacheCon 2004 November 2004 Xerces-J Provide API’s to the parts SAX DOM XNI XNI-based pull Validation DTDs XML Schema Support Relax NG support via Andy Clark’s Neko Tools for XNI When would I use it? Everywhere Copyright © Sauria Associates, LLC ApacheCon 2004 4 Xerces provides 4 APIs for accessing the parts of an XML document SAX – defacto standard - event callback based – produces “event streams” DOM – W3C standard – tree oriented object model – produces a DOM tree XNI – Xerces Native Interface – event callback based XNI-based pull – CyberNeko – allows inversion of control There are three major standards for validating XML documents. Xerces has built in support for 2 and added support for the third. Xerces has built in support for XML DTD’s and the W3C XML Schema Via Andy Clark’s CyberNeko Tools for XNI, Xerces has support for OASIS’s Relax NG XML parsing provides the foundation layer for most XML applications. If you are using XML the question isn’t so much when would I use an XML parser, the question is, will I know that I am using an XML parser. Some of the projects that I’ll discuss in this talk use an XML parser as part of their implementation Copyright © Sauria Associates, LLC 2004 4 ApacheCon 2004 November 2004 Xalan-J What does it do? XSLT Processor Converts one kind of XML into another Uses a stylesheet (XML document) Stylesheet describes tree transformation Declarative programming model Based on pattern matching Copyright © Sauria Associates, LLC ApacheCon 2004 5 Xalan-J is an XSLT processor. As with Xerces, there is also a C++ version. XSLT is the XSL Transformations language. It is a declarative language for describing how to transform a source XML document into another XML document. The transformations are specified via an XML document called an XSLT stylesheet XSLT views every XML document as a tree of nodes, similar to the DOM model. Transformations on documents correspond to transformations of the input tree Copyright © Sauria Associates, LLC 2004 5 ApacheCon 2004 November 2004 Xalan-J <?xml version="1.0"?> <html> <books> <head> <book> <META http-equiv="Content-Type" <title>Effective Java</title> content="text/html; charset=UTF-8"> <author>Joshua Bloch</author> <title>Book Inventory</title> <isbn>yyy-yyyyyyyyyy</isbn> </head> <month>August</month> <body> <year>2001</year> <em>Effective Java</em> <publisher>Addison- <br> Wesley</publisher> <b>Joshua Bloch</b> <address>New York, New <br> York</address> yyy-yyyyyyyyyy<br> </book> August, </books> 2001<br> Addison-Wesley<br> New York, New York<br> <p></p> </body> </html> Copyright © Sauria Associates, LLC ApacheCon 2004 6 Here’s a simple example of the way that XSLT can be used to transform XML into another XML dialect. Conveniently, HTML can also be viewed as an XML vocabulary, so we can use XSLT to convert XML data into HTML In this diagram, the arrows show how various parts of the XML document get transformed into the HTML document. Copyright © Sauria Associates, LLC 2004 6 ApacheCon 2004 November 2004 Xalan-J <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:books="http://sauria.com/schemas/apache-xml-book/books" exclude-result-prefixes="books"> <xsl:output method="html" version="4.0" encoding="UTF-8" indent="yes" omit-xml-declaration="yes"/> <xsl:template match="books:books"> <html> <head><title>Book Inventory</title></head> <body> <xsl:apply-templates/> </body> </html> </xsl:template> <xsl:template match="books:book"> <xsl:apply-templates/> <p /> </xsl:template> <xsl:template match="books:title"> <em><xsl:value-of select="."/></em><br /> </xsl:template> … Copyright © Sauria Associates, LLC ApacheCon 2004 7 This is a portion of the XSLT stylesheet that produced the HTML document in the previous slide The important thing to look at here is the <xsl:template> elements, which show how the pattern matching model of XSLT functions. The template matches, some nodes are inserted into the result tree. More templates can be tried if <xsl:apply-templates/> appears in the template body Copyright © Sauria Associates, LLC 2004 7 ApacheCon 2004 November 2004 Xalan-J TrAX API is part of JAXP XSLTC Compiler Extensions EXSLT Xalan specific When would I use it? Convert XML to HTML Convert XML to XML WML Vocabulary translation Copyright © Sauria Associates, LLC ApacheCon 2004 8 JAXP provides an API for dealing with an XSLT processor This API is called TrAX, which stands for Transformation API for XML. In JDK 1.4 and above, the reference implementation for TrAX is provided by Xalan Xalan provides two XSLT processing engines. The default engine interprets XSLT stylesheets as it transforms a document. The XSLTC engine compiles XSLT stylesheets into Java programs called translets. The translets are then executed to transform the document This approach has large performance benefits in scenarios where the documents being transformed use a fixed grammar or set of grammars. Xalan allows two forms of extensions: It supports the EXSLT XSLT extension library found at http://www.exslt.org Xalan also includes is own mechanism for defining XSLT extensions. This allows you to define extension elements (in XSLT stylesheets) and extension functions (which can be used in XPath expressions). I’ve already show an example of using XSLT to convert XML to HTML. You can build entire web sites this way, and use XSLT to generate the right kind of output format – HTML, XHTML, WML and so on. If you are doing publishing, this kind of single input multiple output should be very appealing. There are also lots of applications where you need to take XML data that uses a grammar and convert it into another grammar. XSLT can be very useful in these situations as well. Copyright © Sauria Associates, LLC 2004 8 ApacheCon 2004 November 2004 FOP What does it do? XSL Processor Convert XML with XSL elements into non XML formats Copyright © Sauria Associates, LLC ApacheCon 2004 9 FOP is an XSL Formatting Object processor XSL Formatting Objects is a W3C Recommendation that uses XML markup to describe how to render a document. The usual rendering is a non-XML format. The XSL specification contains lots of constructs for specifying precise layout and page control. Copyright © Sauria Associates, LLC 2004 9 ApacheCon 2004 November 2004 FOP – XSL Input <?xml version="1.0" encoding="UTF-8"?> <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"> <fo:layout-master-set> <fo:simple-page-master margin-right="0.5in" margin-left="0.5in" margin-bottom="0.5in" margin-top="0.5in" page-width="8.5in" page-height="11in" master-name="book-page"> <fo:region-body margin="1in"/> </fo:simple-page-master> </fo:layout-master-set> <fo:page-sequence master-reference="book-page">
Load more

Recommended publications
  • XML Signature/Encryption — the Basis of Web Services Security
    Special Issue on Security for Network Society Falsification Prevention and Protection Technologies and Products XML Signature/Encryption — the Basis of Web Services Security By Koji MIYAUCHI* XML is spreading quickly as a format for electronic documents and messages. As a consequence, ABSTRACT greater importance is being placed on the XML security technology. Against this background research and development efforts into XML security are being energetically pursued. This paper discusses the W3C XML Signature and XML Encryption specifications, which represent the fundamental technology of XML security, as well as other related technologies originally developed by NEC. KEYWORDS XML security, XML signature, XML encryption, Distributed signature, Web services security 1. INTRODUCTION 2. XML SIGNATURE XML is an extendible markup language, the speci- 2.1 Overview fication of which has been established by the W3C XML Signature is an electronic signature technol- (WWW Consortium). It is spreading quickly because ogy that is optimized for XML data. The practical of its flexibility and its platform-independent technol- benefits of this technology include Partial Signature, ogy, which freely allows authors to decide on docu- which allows an electronic signature to be written on ment structures. Various XML-based standard for- specific tags contained in XML data, and Multiple mats have been developed including: ebXML and Signature, which enables multiple electronic signa- RosettaNet, which are standard specifications for e- tures to be written. The use of XML Signature can commerce transactions, TravelXML, which is an EDI solve security problems, including falsification, spoof- (Electronic Data Interchange) standard for travel ing, and repudiation. agencies, and NewsML, which is a standard specifica- tion for new distribution formats.
    [Show full text]
  • SDL Livecontent S1000D Delivery Server Installation and Upgrade Manual
    SDL LiveContent S1000D Delivery Server Installation and Upgrade Manual SDL LiveContent S1000D 5.6 January 2018 Legal notice Copyright and trademark information relating to this product release. Copyright © 2009–2018 SDL Group. SDL Group means SDL PLC. and its subsidiaries and affiliates. All intellectual property rights contained herein are the sole and exclusive rights of SDL Group. All references to SDL or SDL Group shall mean SDL PLC. and its subsidiaries and affiliates details of which can be obtained upon written request. All rights reserved. Unless explicitly stated otherwise, all intellectual property rights including those in copyright in the content of this website and documentation are owned by or controlled for these purposes by SDL Group. Except as otherwise expressly permitted hereunder or in accordance with copyright legislation, the content of this site, and/or the documentation may not be copied, reproduced, republished, downloaded, posted, broadcast or transmitted in any way without the express written permission of SDL. LiveContent S1000D is a registered trademark of SDL Group. All other trademarks are the property of their respective owners. The names of other companies and products mentioned herein may be the trademarks of their respective owners. Unless stated to the contrary, no association with any other company or product is intended or should be inferred. This product may include open source or similar third-party software, details of which can be found by clicking the following link: “Acknowledgments ” on page 15. Although SDL Group takes all reasonable measures to provide accurate and comprehensive information about the product, this information is provided as-is and all warranties, conditions or other terms concerning the documentation whether express or implied by statute, common law or otherwise (including those relating to satisfactory quality and fitness for purposes) are excluded to the extent permitted by law.
    [Show full text]
  • Open Source Used in Cisco Unity Connection 11.5 SU 1
    Open Source Used In Cisco Unity Connection 11.5 SU 1 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-132949842 Open Source Used In Cisco Unity Connection 11.5 SU 1 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-132949842 Contents 1.1 ace 5.3.5 1.1.1 Available under license 1.2 Apache Commons Beanutils 1.6 1.2.1 Notifications 1.2.2 Available under license 1.3 Apache Derby 10.8.1.2 1.3.1 Available under license 1.4 Apache Mina 2.0.0-RC1 1.4.1 Available under license 1.5 Apache Standards Taglibs 1.1.2 1.5.1 Available under license 1.6 Apache STRUTS 1.2.4. 1.6.1 Available under license 1.7 Apache Struts 1.2.9 1.7.1 Available under license 1.8 Apache Xerces 2.6.2. 1.8.1 Notifications 1.8.2 Available under license 1.9 axis2 1.3 1.9.1 Available under license 1.10 axis2/cddl 1.3 1.10.1 Available under license 1.11 axis2/cpl 1.3 1.11.1 Available under license 1.12 BeanUtils(duplicate) 1.6.1 1.12.1 Notifications Open Source Used In Cisco Unity Connection
    [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]
  • Roller: an Open Source Javatm Ee Blogging Platform
    ROLLER: AN OPEN SOURCE JAVATM EE BLOGGING PLATFORM • Dave Johnson – Staff Engineer S/W – Sun Microsystems, Inc. Agenda • Roller history • Roller features • Roller community • Roller internals: backend • Roller internals: frontend • Customizing Roller • Roller futures Roller started as an EJB example... • Homeport – a home page / portal (2001) ... became an O'Reilly article • Ditched EJBs and HAHTsite IDE (2002) • Used all open source tools instead and thus... ... and escaped into the wild I am allowing others to use my installation of Roller for their weblogging. Hopefully this will provide a means for enhancing the Roller user base as well as provide a nice environment for communication and expression. Anthony Eden August 8, 2002 ... to find a new home at Apache • Apache Roller (incubating) – Incubation period: June 2005 - ??? Agenda • Roller history • Roller features • Roller community • Roller internals: backend • Roller internals: frontend • Customizing Roller • Roller futures Roller features: standard blog stuff • Individual and group blogs • Hierarchical categories • Comments, trackbacks and referrers • File-upload and Podcasting support • User editable page templates • RSS and Atom feeds • Blog client support (Blogger/MetaWeblog API) • Built-in search engine Multiple blogs per user Multiple users per blog Blog client support • XML-RPC based Blogger and MetaWeblog API • Lots of blog clients work with Roller, for example: ecto http://ecto.kung-foo.tv For Mac OSX and Windows Roller 3.0: What's new • Big new release, 3 months in dev
    [Show full text]
  • Return of Organization Exempt from Income
    OMB No. 1545-0047 Return of Organization Exempt From Income Tax Form 990 Under section 501(c), 527, or 4947(a)(1) of the Internal Revenue Code (except black lung benefit trust or private foundation) Open to Public Department of the Treasury Internal Revenue Service The organization may have to use a copy of this return to satisfy state reporting requirements. Inspection A For the 2011 calendar year, or tax year beginning 5/1/2011 , and ending 4/30/2012 B Check if applicable: C Name of organization The Apache Software Foundation D Employer identification number Address change Doing Business As 47-0825376 Name change Number and street (or P.O. box if mail is not delivered to street address) Room/suite E Telephone number Initial return 1901 Munsey Drive (909) 374-9776 Terminated City or town, state or country, and ZIP + 4 Amended return Forest Hill MD 21050-2747 G Gross receipts $ 554,439 Application pending F Name and address of principal officer: H(a) Is this a group return for affiliates? Yes X No Jim Jagielski 1901 Munsey Drive, Forest Hill, MD 21050-2747 H(b) Are all affiliates included? Yes No I Tax-exempt status: X 501(c)(3) 501(c) ( ) (insert no.) 4947(a)(1) or 527 If "No," attach a list. (see instructions) J Website: http://www.apache.org/ H(c) Group exemption number K Form of organization: X Corporation Trust Association Other L Year of formation: 1999 M State of legal domicile: MD Part I Summary 1 Briefly describe the organization's mission or most significant activities: to provide open source software to the public that we sponsor free of charge 2 Check this box if the organization discontinued its operations or disposed of more than 25% of its net assets.
    [Show full text]
  • Introduction to XML
    Introduction to XML CS 317/387 Agenda – Introduction to XML 1. What is it? 2. What’s it good for? 3. How does it work? 4. The infrastructure of XML 5. Using XML on the Web 6. Implementation issues & costs 2 1. What is it? Discussion points: First principles: OHCO Example: A simple XML fragment Compare/contrast: SGML, HTML, XHTML A different XML for every community Terminology 3 1 Ordered hierarchies of content objects Premise: A text is the sum of its component parts A <Book> could be defined as containing: <FrontMatter>, <Chapter>s, <BackMatter> <FrontMatter> could contain: <BookTitle> <Author>s <PubInfo> A <Chapter> could contain: <ChapterTitle> <Paragraph>s A <Paragraph> could contain: <Sentence>s or <Table>s or <Figure>s … Components chosen should reflect anticipated use 4 Ordered hierarchies of content objects OHCO is a useful, albeit imperfect, model Exposes an object’s intellectual structure Supports reuse & abstraction of components Better than a bit-mapped page image Better than a model of text as a stream of characters plus formatting instructions Data management system for document-like objects Does not allow overlapping content objects Incomplete; requires infrastructure 5 Content objects in a book Book FrontMatter BookTitle Author(s) PubInfo Chapter(s) ChapterTitle Paragraph(s) BackMatter References Index 6 2 Content objects in a catalog card Card CallNumber MainEntry TitleStatement TitleProper StatementOfResponsibility Imprint SummaryNote AddedEntrySubject(s) Added EntryPersonalName(s) 7 Semistructured Data Another data model, based on trees. Motivation: flexible representation of data. Often, data comes from multiple sources with differences in notation, meaning, etc. Motivation: sharing of documents among systems and databases.
    [Show full text]
  • Web API Protocol and Security Analysis Web
    EXAMENSARBETE INOM DATATEKNIK, GRUNDNIVÅ, 15 HP STOCKHOLM, SVERIGE 2017 Web API protocol and security analysis Web API protokoll- och säkerhetsanalys CRISTIAN ARAYA MANJINDER SINGH KTH SKOLAN FÖR TEKNIK OCH HÄLSA Web API protocol and security analysis Web API protokoll- och säkerhetsanalys Cristian Araya and Manjinder Singh Degree project in Computer science First level, 15hp Supervisor from KTH: Reine Bergström Examiner: Ibrahim Orhan TRITA-STH 2017:34 KTH The School of Technology and Health 141 52 Flemingsberg, Sweden Abstract There is problem that every company has its own customer portal. This problem can be solved by creating a platform that gathers all customers’ portals in one place. For such platform, it is required a web API protocol that is fast, secure and has capacity for many users. Consequently, a survey of various web API protocols has been made by testing their performance and security. The task was to find out which web API protocol offered high security as well as high performance in terms of response time both at low and high load. This included an investigation of previous work to find out if certain protocols could be ruled out. During the work, the platform’s backend was also developed, which needed to implement chosen web API protocols that would later be tested. The performed tests measured the APIs’ connection time and their response time with and without load. The results were analyzed and showed that the protocols had both pros and cons. Finally, a protocol was chosen that was suitable for the platform because it offered high security and fast connection.
    [Show full text]
  • Reading the Runes for Java Runtimes the Latest IBM Java Sdks
    Java Technology Centre Reading the runes for Java runtimes The latest IBM Java SDKs ... and beyond Tim Ellison [email protected] © 2009 IBM Corporation Java Technology Centre Goals . IBM and Java . Explore the changing landscape of hardware and software influences . Discuss the impact to Java runtime technology due to these changes . Show how IBM is leading the way with these changes 2 Mar 9, 2009 © 2009 IBM Corporation Java Technology Centre IBM and Java . Java is critically important to IBM – Provides fundamental infrastructure to IBM software portfolio – Delivers standard development environment – Enables cost effective multi platform support – Delivered to Independent Software Vendors supporting IBM server platforms . IBM is investing strategically in virtual machine technology – Since Java 5.0, a single Java platform technology supports ME, SE and EE – Technology base on which to delivery improved performance, reliability and serviceability • Some IBM owned code (Virtual machine, JIT compiler, ...) • Some open source code (Apache XML parser, Apache Core libraries, Zlib, ...) • Some Sun licensed code (class libraries, tools, ...) . Looking to engender accelerated and open innovation in runtime technologies – Support for Eclipse, Apache (Harmony, XML, Derby, Geronimo, Tuscany) – Broad participation of relevant standards bodies such as JCP and OSGi 3 Mar 9, 2009 © 2009 IBM Corporation Java Technology Centre IBM Java – 2009 key initiatives . Consumability – Deliver value without complexity. – Ensure that problems with our products can be addressed quickly, allowing customers to keep focus on their own business issues. – Deliver a consistent model for solving customer problems. “Scaling Up” - Emerging hardware and applications – Provide a Java implementation that can scale to the most demanding application needs.
    [Show full text]
  • Xerox® Igen™ 150 Press 3 Party Software License Disclosure
    Xerox® iGen™ 150 Press 3rd Party Software License Disclosure October 2013 The following software packages are copyrighted for use in this product according to the license stated. Full terms and conditions of all 3rd party software licenses are available from the About screen under the Help menu on the Press Interface or by accessing the Support & Drivers page located on the http://www.xerox.com website. Adobe Icons and Web Logos, license: Adobe Icons and Web Logos License Apache log4j 1.2.8, Apache log4j 1.2.9, Apache Web Services XML-RPC 1.2.b1, Apache Lucene Java 1.3, Apache Tomcat 4.1.27, license: Apache License 1.1 Apache Axis 1.x 1.4, Apache Jakarta Commons HttpClient 3.0.alpha1, Apache Jakarta Commons Logging 1.0.4, Apache Jakarta Lucene 1.9.1, Apache XML Security Java 1.3.0, saxpath 1.0 FCS, Skin Look And Feel (skinlf) 1.2.8, Spring Framework Utilities 0.7, Apache Web Services Axis 1.2rc3, Apache Xerces Java XML Parser 2.7.1, Apache XML Xalan-Java 2.7.0, Jetty - Java HTTP Servlet Server 4.0.D0, Lucene Snowball, Streaming API for XML (StAX) - JSR-173 20040819, license: Apache License 2.0 Perl 5.8.5, Perl 5.10.0, AppConfig-1.66, Archive-Tar-1.58, Compress::Zlib-2.020, Expect.pm- 1.21, File-NCopy-0.36, File-NFSLock-1.20, Filesys-Df-0.92, Filesys-DiskFree-0.06, HTML- Parser-3.69, HTML-Tagset-3.20, HTML-Template-2.9, IO-Stty-0.02, IO-Tty-1.08, IO-Zlib- 1.09, libxml-perl-0.08, Net-Netmask-1.9015, Net-Telnet-3.03, perl-5.8.3, perlindex-1.605, Pod- Escapes-1.04, Pod-POM-0.25, Pod-Simple-3.13, Proc-ProcessTable-0.45, Socket6-0.23, Stat-
    [Show full text]
  • Oracle Revenue Management and Billing Installation Guide
    Oracle® Revenue Management and Billing Version 2.8.0.0.0 Installation Guide Revision 16.2 F17820-01 June, 2019 Oracle Revenue Management and Billing Installation Guide Oracle Revenue Management and Billing Installation Guide F17820-01 Copyright Notice Copyright © 2019, Oracle and/or its affiliates. All rights reserved. Trademark Notice Oracle, Java, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure, and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or de-compilation of this software, unless required by law for interoperability, is prohibited. Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error- free. If you find any errors, please report them to us in writing. Restricted Rights Notice If this software or related documentation is delivered to the U.S.
    [Show full text]
  • Open Source and Third Party Documentation
    Open Source and Third Party Documentation Verint.com Twitter.com/verint Facebook.com/verint Blog.verint.com Content Introduction.....................2 Licenses..........................3 Page 1 Open Source Attribution Certain components of this Software or software contained in this Product (collectively, "Software") may be covered by so-called "free or open source" software licenses ("Open Source Components"), which includes any software licenses approved as open source licenses by the Open Source Initiative or any similar licenses, including without limitation any license that, as a condition of distribution of the Open Source Components licensed, requires that the distributor make the Open Source Components available in source code format. A license in each Open Source Component is provided to you in accordance with the specific license terms specified in their respective license terms. EXCEPT WITH REGARD TO ANY WARRANTIES OR OTHER RIGHTS AND OBLIGATIONS EXPRESSLY PROVIDED DIRECTLY TO YOU FROM VERINT, ALL OPEN SOURCE COMPONENTS ARE PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. Any third party technology that may be appropriate or necessary for use with the Verint Product is licensed to you only for use with the Verint Product under the terms of the third party license agreement specified in the Documentation, the Software or as provided online at http://verint.com/thirdpartylicense. You may not take any action that would separate the third party technology from the Verint Product. Unless otherwise permitted under the terms of the third party license agreement, you agree to only use the third party technology in conjunction with the Verint Product.
    [Show full text]