DOCSLIB.ORG

Assembler Service and DDX Reference

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Assembler Service and DDX Reference bbc Assembler Service and DDX Reference Adobe Experience Manager 6.2 Forms June 2016 Legal Notices For more information, see http://help.adobe.com/en_US/legalnotices/index.html.s Contents 1 About This Help .........................................................................................................................12 Additional information...............................................................................................................................................................12 Part I: DDX User Document 2 Introducing Document Description XML.................................................................................14 DDX document structure ..........................................................................................................................................................14 DDX building blocks....................................................................................................................................................................14 DDX principles...............................................................................................................................................................................15 Result elements ......................................................................................................................................................................16 Source elements.....................................................................................................................................................................18 Filter elements ........................................................................................................................................................................19 Profile elements......................................................................................................................................................................20 Grouping PDF sources..........................................................................................................................................................21 Grouping XDP sources and content................................................................................................................................22 Input and output..........................................................................................................................................................................22 Using input and output maps ...........................................................................................................................................22 Using External Data URLs for source and result values............................................................................................23 Using External Data URLs for string values .........................................................................................................................24 Scope of elements that affect PDF or XDP properties ....................................................................................................24 Scope of PDF page properties...........................................................................................................................................24 Scope of XDPContent...........................................................................................................................................................25 Specifying length .........................................................................................................................................................................26 Dynamic document assembly.................................................................................................................................................26 Optional source documents ..............................................................................................................................................26 Lists of documents.................................................................................................................................................................26 Automatic Conversion of source documents to PDF documents..............................................................................27 3 Assembling PDF Documents.....................................................................................................29 Specifying source documents .................................................................................................................................................29 About base documents .......................................................................................................................................................29 Page ranges..............................................................................................................................................................................30 Other source attributes........................................................................................................................................................31 Specifying multiple input streams.........................................................................................................................................31 List defined by a source that specifies a name in the input map .........................................................................32 List defined by a source that specifies URL...................................................................................................................32 List defined by the matchSource and select attributes acting on source.........................................................33 Saving PDF documents..............................................................................................................................................................34 4 Modifying Acrobat and XML Forms .........................................................................................36 Flattening forms ...........................................................................................................................................................................36 Restrictions on documents containing forms....................................................................................................................37 Acrobat forms..........................................................................................................................................................................37 XFA-based forms....................................................................................................................................................................38 5 Creating and Modifying Acrobat and XML (XFA) Forms ........................................................39 Assemble a simple XDP document........................................................................................................................................39 3 Adobe Experience Manager Forms Contents Assembler Service and DDX Reference 4 Dynamically insert forms or form fragments into an XFA form ..................................................................................40 Resolve references .......................................................................................................................................................................41 Package an XDP document as PDF........................................................................................................................................42 PDF documents from single XFA-based forms ...........................................................................................................43 Assemble XFA-based forms with other documents..................................................................................................43 PDF documents from Acrobat forms..............................................................................................................................45 Package a PDF document as XDP...........................................................................................................................................45 6 Assembling PDF Packages and Portfolios ...............................................................................46 Understanding PDF packages ................................................................................................................................................46 About PDF package and portfolio properties....................................................................................................................47 PDF Package property: package files and package specifications.......................................................................47 PDF Portfolio properties......................................................................................................................................................48 Folders........................................................................................................................................................................................50 Navigation welcome page and navigation heading.................................................................................................50 Creating a PDF Portfolio.............................................................................................................................................................51 Creating
Load more

Recommended publications
  • Specification for JSON Abstract Data Notation Version
    Standards Track Work Product Specification for JSON Abstract Data Notation (JADN) Version 1.0 Committee Specification 01 17 August 2021 This stage: https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.md (Authoritative) https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.html https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.pdf Previous stage: https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.md (Authoritative) https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.html https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.pdf Latest stage: https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.md (Authoritative) https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.html https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.pdf Technical Committee: OASIS Open Command and Control (OpenC2) TC Chair: Duncan Sparrell ([email protected]), sFractal Consulting LLC Editor: David Kemp ([email protected]), National Security Agency Additional artifacts: This prose specification is one component of a Work Product that also includes: JSON schema for JADN documents: https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/schemas/jadn-v1.0.json JADN schema for JADN documents: https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/schemas/jadn-v1.0.jadn Abstract: JSON Abstract Data Notation (JADN) is a UML-based information modeling language that defines data structure independently of data format.
    [Show full text]
  • Understanding JSON Schema Release 2020-12
    Understanding JSON Schema Release 2020-12 Michael Droettboom, et al Space Telescope Science Institute Sep 14, 2021 Contents 1 Conventions used in this book3 1.1 Language-specific notes.........................................3 1.2 Draft-specific notes............................................4 1.3 Examples.................................................4 2 What is a schema? 7 3 The basics 11 3.1 Hello, World!............................................... 11 3.2 The type keyword............................................ 12 3.3 Declaring a JSON Schema........................................ 13 3.4 Declaring a unique identifier....................................... 13 4 JSON Schema Reference 15 4.1 Type-specific keywords......................................... 15 4.2 string................................................... 17 4.2.1 Length.............................................. 19 4.2.2 Regular Expressions...................................... 19 4.2.3 Format.............................................. 20 4.3 Regular Expressions........................................... 22 4.3.1 Example............................................. 23 4.4 Numeric types.............................................. 23 4.4.1 integer.............................................. 24 4.4.2 number............................................. 25 4.4.3 Multiples............................................ 26 4.4.4 Range.............................................. 26 4.5 object................................................... 29 4.5.1 Properties...........................................
    [Show full text]
  • Efficient Sorting of Search Results by String Attributes
    Efficient sorting of search results by string attributes Nicholas Sherlock Andrew Trotman Department of Computer Science Department of Computer Science University of Otago University of Otago Otago 9054 New Zealand Otago 9054 New Zealand [email protected] [email protected] Abstract It is sometimes required to order search In addition, the search engine must allocate memory results using textual document attributes such as to an index structure which allows it to efficiently re- titles. This is problematic for performance because trieve those post titles by document index, which, using of the memory required to store these long text a simplistic scheme with 4 bytes required per docu- strings at indexing and search time. We create a ment offset, would require an additional 50 megabytes method for compressing strings which may be used of storage. for approximate ordering of search results on textual For search terms which occur in many documents, attributes. We create a metric for analyzing its most of the memory allocated to storing text fields like performance. We then use this metric to show that, post titles must be examined during result list sorting. for document collections containing tens of millions of As 550 megabytes is vastly larger than the cache mem- documents, we can sort document titles using 64-bits ory available inside the CPU, sorting the list of docu- of storage per title to within 100 positions of error per ments by post title requires the CPU to load that data document. from main memory, which adds substantial latency to query processing and competes for memory bandwidth Keywords Information Retrieval, Web Documents, with other processes running on the same system.
    [Show full text]
  • [MS-LISTSWS]: Lists Web Service Protocol
    [MS-LISTSWS]: Lists Web Service Protocol Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected].
    [Show full text]
  • V10.5.0 (2013-07)
    ETSI TS 126 234 V10.5.0 (2013-07) Technical Specification Universal Mobile Telecommunications System (UMTS); LTE; Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols and codecs (3GPP TS 26.234 version 10.5.0 Release 10) 3GPP TS 26.234 version 10.5.0 Release 10 1 ETSI TS 126 234 V10.5.0 (2013-07) Reference RTS/TSGS-0426234va50 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission.
    [Show full text]
  • FIDO Technical Glossary
    Client to Authenticator Protocol (CTAP) Implementation Draft, February 27, 2018 This version: https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-client-to-authenticator-protocol-v2.0-id- 20180227.html Previous Versions: https://fidoalliance.org/specs/fido-v2.0-ps-20170927/ Issue Tracking: GitHub Editors: Christiaan Brand (Google) Alexei Czeskis (Google) Jakob Ehrensvärd (Yubico) Michael B. Jones (Microsoft) Akshay Kumar (Microsoft) Rolf Lindemann (Nok Nok Labs) Adam Powers (FIDO Alliance) Johan Verrept (VASCO Data Security) Former Editors: Matthieu Antoine (Gemalto) Vijay Bharadwaj (Microsoft) Mirko J. Ploch (SurePassID) Contributors: Jeff Hodges (PayPal) Copyright © 2018 FIDO Alliance. All Rights Reserved. Abstract This specification describes an application layer protocol for communication between a roaming authenticator and another client/platform, as well as bindings of this application protocol to a variety of transport protocols using different physical media. The application layer protocol defines requirements for such transport protocols. Each transport binding defines the details of how such transport layer connections should be set up, in a manner that meets the requirements of the application layer protocol. Table of Contents 1 Introduction 1.1 Relationship to Other Specifications 2 Conformance 3 Protocol Structure 4 Protocol Overview 5 Authenticator API 5.1 authenticatorMakeCredential (0x01) 5.2 authenticatorGetAssertion (0x02) 5.3 authenticatorGetNextAssertion (0x08) 5.3.1 Client Logic 5.4 authenticatorGetInfo (0x04)
    [Show full text]
  • Acrobat Application Security Guide (All Versions)
    Acrobat Application Security Guide (all versions) Acrobat® Family of Products © 2012 Adobe Systems Incorporated. All rights reserved. Adobe Application Security Guide for the Adobe® Acrobat Family of Products. If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected under copyright law even if it is not distributed with software that includes an end user license agreement. The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this guide. Please remember that existing artwork or images that you may want to include in your project may be protected under copyright law. The unauthorized incorporation of such material into your new work could be a violation of the rights of the copyright owner. Please be sure to obtain any permission required from the copyright owner. Any references to company names in sample templates are for demonstration purposes only and are not intended to refer to any actual organization.
    [Show full text]
  • Best Practices for Model-Driven Development with Adobe® Livecycle® ES2 Guides Guiding People Through the Data Capture Experience
    Adobe LiveCycle ES2 Technical Guide Best Practices for Model-Driven Development with Adobe® LiveCycle® ES2 Guides Guiding people through the data capture experience. Introduction Background Guides in Adobe LiveCycle ES2 are Flash Player compatible wizard-like panels that help guide people through a data capture experience. Guides can dynamically change and adapt based on input data to ensure that only relevant questions are asked and accurate data is captured. These rich and engaging experiences help reduce transaction abandonment rates that are prevalent with more complex data collection interfaces. In LiveCycle ES2, Guides use the concept of model-driven development, which is the next level of abstraction in writing software applications. This abstraction offers improved productivity and makes applications that are higher in quality and easier to create, compared to lower-level development techniques. Model-driven development separates the data structures and constraint logic from the user interface and display logic. Models can then be shared and reused by other applications that capture, display or process the same data. The previous incarnation of guides was known as “form guides,” and used an XDP form as both the model and host of the form guide definition. Form guides were built directly in LiveCycle Designer, and were rendered by LiveCycle Forms into a SWF (pronounced “swiff”) file for display in the Flash Player. With the release of LiveCycle ES2, the Guide Builder tool has been moved to LiveCycle Workbench and a new application model has been introduced. The application model (.fml) is created in the Data Modeler tool, which is also a new part of the LiveCycle Workbench in ES2.
    [Show full text]
  • NVM Express TCP Transport Specification 1.0A
    NVM Express® TCP Transport Specification Revision 1.0a July 22nd, 2021 Please send comments to [email protected] NVM Express® TCP Transport Specification Revision 1.0a NVM Express® TCP Transport Specification, revision 1.0a is available for download at http://nvmexpress.org. The NVMe TCP Transport Specification revision 1.0a incorporates NVMe TCP Transport Specification revision 1.0 and NVMe 2.0 ECN 001. SPECIFICATION DISCLAIMER LEGAL NOTICE: © 2021 NVM Express, Inc. ALL RIGHTS RESERVED. This NVM Express TCP Transport Specification revision 1.1 is proprietary to the NVM Express, Inc. (also referred to as “Company”) and/or its successors and assigns. NOTICE TO USERS WHO ARE NVM EXPRESS, INC. MEMBERS: Members of NVM Express, Inc. have the right to use and implement this NVM Express TCP Transport Specification revision 1.1 subject, however, to the Member’s continued compliance with the Company’s Intellectual Property Policy and Bylaws and the Member’s Participation Agreement. NOTICE TO NON-MEMBERS OF NVM EXPRESS, INC.: If you are not a Member of NVM Express, Inc. and you have obtained a copy of this document, you only have a right to review this document or make reference to or cite this document. Any such references or citations to this document must acknowledge NVM Express, Inc. copyright ownership of this document. The proper copyright citation or reference is as follows: “© 2021 NVM Express, Inc. ALL RIGHTS RESERVED.” When making any such citations or references to this document you are not permitted to revise, alter, modify, make any derivatives of, or otherwise amend the referenced portion of this document in any way without the prior express written permission of NVM Express, Inc.
    [Show full text]
  • 4648 SJD Obsoletes: 3548 October 2006 Category: Standards Track
    Network Working Group S. Josefsson Request for Comments: 4648 SJD Obsoletes: 3548 October 2006 Category: Standards Track The Base16, Base32, and Base64 Data Encodings Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data, use of padding in encoded data, use of non-alphabet characters in encoded data, use of different encoding alphabets, and canonical encodings. Josefsson Standards Track [Page 1] RFC 4648 Base-N Encodings October 2006 Table of Contents 1. Introduction ....................................................3 2. Conventions Used in This Document ...............................3 3. Implementation Discrepancies ....................................3 3.1. Line Feeds in Encoded Data .................................3 3.2. Padding of Encoded Data ....................................4 3.3. Interpretation of Non-Alphabet Characters in Encoded Data ..4 3.4. Choosing the Alphabet ......................................4 3.5. Canonical Encoding .........................................5 4. Base 64 Encoding ................................................5
    [Show full text]
  • List of NMAP Scripts Use with the Nmap –Script Option
    List of NMAP Scripts Use with the nmap –script option Retrieves information from a listening acarsd daemon. Acarsd decodes ACARS (Aircraft Communication Addressing and Reporting System) data in real time. The information retrieved acarsd-info by this script includes the daemon version, API version, administrator e-mail address and listening frequency. Shows extra information about IPv6 addresses, such as address-info embedded MAC or IPv4 addresses when available. Performs password guessing against Apple Filing Protocol afp-brute (AFP). Attempts to get useful information about files from AFP afp-ls volumes. The output is intended to resemble the output of ls. Detects the Mac OS X AFP directory traversal vulnerability, afp-path-vuln CVE-2010-0533. Shows AFP server information. This information includes the server's hostname, IPv4 and IPv6 addresses, and hardware type afp-serverinfo (for example Macmini or MacBookPro). Shows AFP shares and ACLs. afp-showmount Retrieves the authentication scheme and realm of an AJP service ajp-auth (Apache JServ Protocol) that requires authentication. Performs brute force passwords auditing against the Apache JServ protocol. The Apache JServ Protocol is commonly used by ajp-brute web servers to communicate with back-end Java application server containers. Performs a HEAD or GET request against either the root directory or any optional directory of an Apache JServ Protocol ajp-headers server and returns the server response headers. Discovers which options are supported by the AJP (Apache JServ Protocol) server by sending an OPTIONS request and lists ajp-methods potentially risky methods. ajp-request Requests a URI over the Apache JServ Protocol and displays the result (or stores it in a file).
    [Show full text]
  • The Base16, Base32, and Base64 Data Encodings
    Network Working Group S. Josefsson Request for Comments: 4648 SJD Obsoletes: 3548 October 2006 Category: Standards Track The Base16, Base32, and Base64 Data Encodings Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the “Internet Official Protocol Standards” (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright © The Internet Society (2006). All Rights Reserved. Abstract This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data, use of padding in encoded data, use of non-alphabet characters in encoded data, use of different encoding alphabets, and canonical encodings. RFC 4648 Base-N Encodings October 2006 Table of Contents 1 Introduction...............................................................................................................................................................3 2 Conventions Used in This Document..................................................................................................................... 4 3 Implementation Discrepancies................................................................................................................................ 5 3.1 Line Feeds in Encoded Data.................................................................................................................................5
    [Show full text]