DOCSLIB.ORG

Mopria Alliance Escl Scan Technical Specification

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Mopria Alliance Escl Scan Technical Specification 1 2 3 Technical Working Group 4 5 Mopria Alliance eSCL Scan 6 Technical Specification 7 8 Version 2.8.00 9 Final Draft approved by the Board of Directors 10 October 22, 2018 11 Mopria Alliance Confidential 12 13 Disclaimer Boiler Plate 14 This document may be used with the permission of Mopria Alliance under the terms set forth herein. 15 By your use of the document, you are agreeing to these terms. Unless this document is clearly designated as an approved 16 specification, this document is a work in process and is not an approved Mopria Alliance specification. This document is subject to 17 revision or removal at any time without notice. Information contained in this document may be used at your sole risk. Mopria Alliance 18 assumes no responsibility for errors or omissions in this document. This copyright permission does not constitute an endorsement of 19 the products or services. Mopria Alliance trademarks and certification marks may not be used unless specifically allowed by Mopria 20 Alliance. 21 22 Mopria Alliance has not conducted an independent intellectual property rights ("IPR") review of this document and the information 23 contained herein, and makes no representations or warranties regarding IPR, including without limitation patents, copyrights or trade 24 secret rights. This document may contain inventions for which you must obtain licenses from third parties before making, using or 25 selling the inventions. 26 27 Mopria Alliance owns the copyright in this document and reserves all rights therein. A user of this document may duplicate and 28 distribute copies of the document in connection with the authorized uses described herein, provided any duplication in whole or in 29 part includes the copyright notice and the disclaimer text set forth herein. Unless prior written permission has been received from 30 Mopria Alliance, any other use of this document and all other duplication and distribution of this document are prohibited. 31 Unauthorized use, duplication, or distribution is an infringement of Mopria Alliance’s copyright. 32 33 NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE MADE BY MOPRIA ALLIANCE AND 34 MOPRIA ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY DIRECT, INDIRECT, PUNITIVE, SPECIAL, 35 INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF 36 THISDOCUMENT AND ANY INFORMATION CONTAINED IN THIS DOCUMENT. 37 “Notwithstanding the Copyright License Grant in Part 1 (b) of Attachment A “License to Final 38 Specification” of the Intellectual Property Rights Policy of the Mopria Alliance, Inc. Membership 39 Agreement, the copyright license grant to HP to the Final Specification based on the eSCL Contribution 40 from HP shall include the right to modify, create derivative works, distribute and sublicense the Final 41 Specification (including any Contribution of any Member to the Final Specification) to third parties. 42 By contributing the eSCL specification to the Mopria Alliance, HP allows claims in US7263524 and no 43 other HP Intellectual property is allowed or implied. See the following page for specific uses cases: 44 45 46 47 48 49 Claims in US7263524 allow for Scenarios 1 & 2 and do not allow Scenario 3. 50 51 52 Mopria Alliance Confidential Page 2 of 76 Mopria Alliance Scan Specification v2.8 1 Document History Version Date Status Comments 0.30 02/06/2014 Draft Initial draft 0.31 02/19/2014 Draft Fixed some editorials and started tightening up the Security section 2.6 06/11/2014 Draft More security related concerns addressed – making HTTPS mandatory and adding UUID to the JobURI. Added push scan support for multiple destinations. 2.6 e 11/12/2014 Draft Added uscans advertisement in Bonjour Added StoredJobRequests. Security updates for admin to mandate secure scans. Added ReferenceID to to the destination URI for the PUSH scans Added clarity to use of CertificateValidation Added more response codes for individual URIs Updated with review comments from Mopria. 2.6.f 01/12/2014 Draft Updated security section for USB requests. Added UriSchemes and PreConfiguredDestinations for PUSH scan capabilities. Removed DestinationUri and added DestinationReferenceID in ScannerStatus for PUSH scans. 2.7 08/13/2017 Draft Added support for uscans SRV record Added a new section for explaining StoredJobs Added UUID, AdminURI, IconURI, to capabilities Added FeedDirections, BlankPageDetection support Added ActualBytesPerLine, BlankPageDetected to ScanImageInfo 2.8 04/19/2018 Draft Added Manufacturer and Certifications elements to ScannerCapabilities 2.8 2018-10-22 Final Final Draft approved by the Board of Directors Mopria Alliance Confidential Page 3 of 76 Mopria Alliance Scan Specification v2.8 1 Contents 2 1 Introduction ............................................................................................................................. 6 3 1.1 Intents ...................................................................................................................... 6 4 1.2 References ............................................................................................................... 6 5 1.3 Definitions............................................................................................................... 7 6 1.4 Abbreviations and acronyms................................................................................... 7 7 2 HTTP Error Codes .................................................................................................................. 7 8 3 Discovery ................................................................................................................................ 9 9 4 eSCL Resources .................................................................................................................... 13 10 5 Intents .................................................................................................................................... 14 11 6 Data Formats ......................................................................................................................... 16 12 7 Scan Settings ......................................................................................................................... 17 13 7.1 Coordinate Conventions........................................................................................ 24 14 8 Capabilities ........................................................................................................................... 25 15 8.1 Data Formats ......................................................................................................... 25 16 8.1.1 Resolution Capabilities ......................................................................................... 25 17 8.1.2 Setting Profile ....................................................................................................... 27 18 8.1.3 InputSourceCaps ................................................................................................... 31 19 8.1.3.1 Edge Detection ....................................................................................... 32 20 8.1.3.2 Output Orientation ................................................................................. 32 21 8.1.4 Capabilities ........................................................................................................... 33 22 8.2 Interface ................................................................................................................ 35 23 8.3 Usage Flow ........................................................................................................... 35 24 9 Status ..................................................................................................................................... 39 25 9.1 Data Format .......................................................................................................... 39 26 9.2 Interface ................................................................................................................ 41 27 9.3 Usage Flow ........................................................................................................... 41 28 10 Scan Buffer Info .................................................................................................................... 43 29 10.1 Data Format .......................................................................................................... 43 30 10.2 Interface ................................................................................................................ 43 31 10.3 Usage Flow ........................................................................................................... 44 32 11 Scan Job ................................................................................................................................ 47 Mopria Alliance Confidential Page 4 of 76 Mopria Alliance Scan Specification v2.8 1 11.1 Description ............................................................................................................ 47 2 11.2 Scan Image Info .................................................................................................... 47 3 11.3 Data Format .......................................................................................................... 48 4 11.4 Interface ................................................................................................................ 48 5 11.5 Usage Flow ..........................................................................................................
Load more

Recommended publications
  • FAA-STD-075, Creating Service Identifiers
    FAA-STD-075 June 29, 2021 SUPERSEDING FAA-STD-063 May 1, 2009 U.S. Department of Transportation Federal Aviation Administration U.S. Department of Transportation Federal Aviation Administration Standard Practice CREATING SERVICE IDENTIFIERS FAA-STD-075 June 29, 2021 FOREWORD This standard is approved for use by all Departments of the Federal Aviation Administration (FAA). This standard sets forth requirements for creating globally-unique identifiers for FAA service-oriented architecture (SOA)-based services. This standard has been prepared in accordance with FAA-STD-068, Department of Transportation Federal Aviation Administration, Preparation of Standards [STD068]. Comments, suggestions, or questions on this document shall be addressed to: Federal Aviation Administration System Wide Information Management (SWIM) Program Office, AJM-316 800 Independence Avenue, SW Washington, DC 20591 https://www.faa.gov/air_traffic/technology/swim/contacts/ i FAA-STD-075 June 29, 2021 Table of Contents 1 SCOPE ..................................................................................................................................................1 1.1 INTRODUCTION ...........................................................................................................................................1 1.2 INTENDED AUDIENCE ....................................................................................................................................1 1.3 BASIC CONCEPTS .........................................................................................................................................2
    [Show full text]
  • The Semantic Web
    The Semantic Web Ovidiu Chira IDIMS Report 21st of February 2003 1. Introduction 2. Background 3. The structure of the Semantic Web 4. Final Remarks 1 1. Introduction One of the most successful stories of the information age is the story of the World Wide Web (WWW). The WWW was developed in 1989 by Tim Berners-Lee to enable the sharing of information among geographically dispersed teams of researchers within the European Laboratory for Particle Physics (CERN). The simplicity of publishing on WWW and the envisioned benefits attracted an increasing number of users from beyond the boundaries of the research community. The WWW grew rapidly to support not only information sharing between scientists (as it was intended), but to support information sharing among different kind of people communities, from simple homepages to large business applications. The Web became an “universal medium for exchanging data and knowledge: for the first time in history we have a widely exploited many-to-many medium for data interchange” [Decker, Harmelen et al. 2000]. The WWW is estimated to consist from around one billion documents and more than 300 millions users access them, and these numbers are growing fast [Fensel 2001; Benjamins, Contreras et al. 2002]. Soon, as a ”medium for human communication, the Web has reached critical mass […] but as a mechanism to exploit the power of computing in our every-day life, the Web is in its infancy” [Connolly 1998; Cherry 2002]. On one hand it became clear that while the Web enables human communication and human access to information it lacks of tools or technologies to ease the management of Web’s resources [Fensel 2000; Fensel 2001; Palmer 2001].
    [Show full text]
  • RDF and the Semantic Web.(Database and Network Journal-Intelligence) © COPYRIGHT 2003 A.P
    Database and Network Journal Oct 2003 v33 i5 p3(2) Page 1 RDF and the Semantic Web.(Database And Network Journal-Intelligence) © COPYRIGHT 2003 A.P. Publications Ltd. that developing a consistent universal data format would not be too great a task. However, it has proved in the past Part 1--The Semantic Web that it is almost impossible to get two companies to agree on a specific definition of "data". There has never been The World Wide Web’s simplicity was a key factor in its complete agreement as to data exchange formats. The rapid adoption. But as it grows ever larger and more arrival of XML offers hope of a wide acceptance of its complex, that simplicity has begun to hinder our ability to syntax or syntactic rules which no one faction can claim. make intelligent use of the vast store of data on the Web. In response to that challenge, the Worm Wide Web The Semantic Web is generally built on syntaxes which Consortium (W3C) has spearheaded an effort to create an use URIs to represent data, usually in triples based extension of the Web that brings meaning and order to structures: i.e. many triples of URI data that can be held in web data. It’s called the Semantic Web, and at its core is databases, or interchanged on the world Wide Web using the Resource Description Framework (RDF), an a set of particular syntaxes developed especially for the application of XML. However, whilst the creation of the task. These syntaxes are called "Resource Description Semantic Web is dependant on RDF, it is conceivable that Framework" syntaxes.
    [Show full text]
  • DCA D32 Recommendationsc
    DELIVERABLE Project Acronym: DCA Grant Agreement number: 270927 Project Title: Digitising Contemporary Art D3.2 Recommendations on Contextualisation and Enrichment of Contemporary Art Revision: V1.1 Author(s): Sam Coppens (iMinds/MMLab) Erik Mannens (iMinds/MMLab) Project co-funded by the European Commission within the ICT Policy Support Programme Dissemination Level P Public X C Confidential, only for members of the consortium and the Commission Services DCA_D32_RecommendationsContextualisationAndEnrichment_V1.1.doc 1 1.1.1 REVISION HISTORY AND STATEMENT OF ORIGINALITY Revision History Revision Date Author Organisation Description 0.1 14/12/2012 Sam iMinds/MMLab First draft Coppens / Eric Lammens 0.2 17/12/2012 Kathryn Central External review Mathe European University 0.3. 19/12/2012 Sam IBBT/MMLab Second draft Coppens / Eric Lammens 1.0. 31/12/2012 Rony Vissers PACKED Internal review and final version 1.1 17/01/2013 Rony Vissers PACKED Appendix proofread by native English speaker Statement of originality: This deliverable contains original unpublished work except where clearly indicated otherwise. Acknowledgement of previously published material and of the work of others has been made through appropriate citation, quotation or both. DCA_D32_RecommendationsContextualisationAndEnrichment_V1.1.doc 2 Content Table 1 SEMANTIC WEB 5 1.1 Introduction 5 1.2 URIs: Identify Resources 6 1.3 RDF: Describe Resources 6 1.4 Linked Open Data: Publish RDF 9 1.5 SPARQL: Query RDF 10 1.6 RDFS / OWL: Add Semantics 11 1.7 Benefits of applying Semantic Web
    [Show full text]
  • Network File Sharing Protocols
    Network File Sharing Protocols Lucius quests her hotchpotch ethnologically, she contradistinguish it self-righteously. Dialogic Millicent catch prayingly. Sheridan usually foils stintedly or pirouette anaerobiotically when trilobed Saxon disposes genotypically and homeward. It is recommended that this type be accepted by all FTP implementations. So how do you protect yourself from these malware infected movies? Which protocol is even an option for you is based on your use scenario. Learn about the latest issues in cybersecurity and how they affect you. As more clients access the file, share important files digitally and work as a team even sitting miles apart. Friendly name of the printer object. SMB is built in to every version of Windows. As you can see NFS offers a better performance and is unbeatable if the files are medium sized or small. Processes utilizing the network that do not normally have network communication or have never been seen before are suspicious. You are correct, thank you. It syncs files between devices on a local network or between remote devices over the internet. Sets the maximum number of channels for all subsequent sessions. Session control packets Establishes and discontinues a connection to shared server resources. Please fill in all required fields before continuing. File names in CIFS are encoded using unicode characters. The configured natural language of the printer. After entering its resources or network protocols that protocol over the server supports file services while originally connected you must be set. Download a free fully functional evaluation of JSCAPE MFT Server. The File Transfer Protocol follows the specifications of the Telnet protocol for all communications over the control connection.
    [Show full text]
  • 1.1 UAPROF User Agent Profile
    1.1 UAPROF User Agent Profile El problema de la heterogeneidad (en términos de diferentes tipos de dispositivo de acceso, ancho de banda de la red, preferencias y características del usuario, etc.) es uno de los grandes inconvenientes que ha de ser resuelto en Internet. Para la determinación de las características tecnológicas de los dispositivos con acceso a Internet, se utilizarán dos estándares: CC/PP (Composite Capabilities / Preferences Profile) para la modelización del perfil de los usuarios y UAProf (User Agent Profile) para dispositivos WAP. Estos dos estándares, están basados en RDF (Resource Description Framework), y permiten describir y administrar las características tecnológicas del usuario. Está diseñado para trabajar con una amplia variedad de dispositivos con capacidad de acceso a Internet (tales como PDAs, PC de escritorio, portátiles, teléfonos móviles, etc.). De esta forma, cuando se realiza una petición al servidor, es posible enviar a través de CC/PP y UAProf información sobre las capacidades del dispositivo, a fin de que este último pueda entregar los contenidos adaptados teniendo en cuenta estas características. UAPROF básicamente advierte de las capacidades de los terminales a los servidores de aplicaciones y otras entidades con objeto de adaptar los contenidos a dichas capacidades. [10] UAPROF al igual que CC/PP se divide en componentes y éstos a su vez se dividen en atributos. Los distintos componentes en los que se divide son: · HardwarePlatform Component · SoftwarePlatform Component · NetworkCharacteristics
    [Show full text]
  • SSRF Bible. Cheatsheet
    SSRF bible. Cheatsheet Revision 1.03 26 Jan 2017 Authors: @Wallarm @d0znpp research team Wallarm.com|lab.wallarm.com ​ ​ Try our new product. Wallarm FAST: security tests from traffic ​ ​ https://wallarm.com/wallarm-fast/ wallarm.com 1 Table of contents Table of contents Basics Typical attack steps File Descriptors exploitation way URL schema support Protocols SSRF smuggling Smuggling examples Apache web-server HTTP parser Nginx web-server HTTP parser Vulnerabilities Basics Examples Google Docs ZeroNights hackquest challenge Exploitation tricks Bypassing restrictions Input validation Unsafe redirect DNS pinning DNS pinning race condition PHP fsockopen() url parsing tricks Network restrictions Protocol fingerprinting Examples HTTP Memcached Retrieving data Examples HTTP response encapsulation into XML formatted response Console cURL wildcards URL responses concatenation SMBRelay exploitation Original request data sniffing Examples Memcached wallarm.com 2 Exploits PHP-FPM Syslog Exploits Zabbix agentd Exploits Postgres Exploits MongoDB Redis CouchDB Exploits FFmpeg References Tools Researches wallarm.com 3 Basics SSRF - Server Side Request Forgery attacks. The ability to create requests from the vulnerable server to intra/internet. Using a protocol supported by available URI schemas, you can communicate with services running on other protocols. Here we collect the various options and examples (exploits) of such interaction. See for introduction related researches. ​ ​ Typical attack steps 1. Scan internal network to determine internal infrastructure which you may access 2. Collect opened ports at localhost and other internal hosts which you want (basically by time-based determination) 3. Determine services/daemons on ports using wiki or daemons banners (if you may watch ​ ​ output) 4. Determine type of you SSRF combination: ○ Direct socket access (such as this example) ​ ​ ○ Sockets client (such as java URI, cURL, LWP, others) 5.
    [Show full text]
  • Guidelines for the Encoding of Spatial Data
    INSPIRE Infrastructure for Spatial Information in Europe Guidelines for the encoding of spatial data Title D2.7: Guidelines for the encoding of spatial data, Version 3.3rc3 Status Version for Annex II/III data specifications v3.0rc3 Creator INSPIRE Drafting Team "Data Specifications" Date 2013-06-11 Subject Guidelines for the encoding of spatial data Publisher INSPIRE Drafting Team "Data Specifications" Type Text Description Guidelines for the encoding of spatial data Contributor Members of the INSPIRE Drafting Team "Data Specifications", INSPIRE Spatial Data Interest Communities & Legally Mandated Organisations, INSPIRE Consolidation Teams and other Drafting Teams Format Portable document format (pdf) Source INSPIRE Drafting Team "Data Specifications" Rights Public Identifier D2.7_v3.3rc3 Language En Relation n/a Coverage Project duration INSPIRE Data Specifications Reference: D2.7_v3.3rc3 Guidelines for the encoding of spatial data 2013-06-11 Page II Table of contents Foreword ............................................................................................................................................1 Introduction .........................................................................................................................................3 1 Scope .........................................................................................................................................6 2 Conformance ..............................................................................................................................6
    [Show full text]
  • Etsi Ts 127 007 V11.4.0 (2012-10)
    ETSI TS 127 007 V11.4.0 (2012-10) Technical Specification Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; AT command set for User Equipment (UE) (3GPP TS 27.007 version 11.4.0 Release 11) 3GPP TS 27.007 version 11.4.0 Release 11 1 ETSI TS 127 007 V11.4.0 (2012-10) Reference RTS/TSGC-0127007vb40 Keywords GSM, 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]
  • Network Scan Service Semantic Model and Service Interface
    April 10, 2009 Candidate Standard 5108.02-2009 The Printer Working Group Network Scan Service Semantic Model and Service Interface Version 1.0 Status: Approved Abstract: Network print devices have evolved to support additional multifunction services, in particular Scan Service. When network Scanners are installed in local office or enterprise networks, they need remote service, device, and job management capabilities so that administrators, operators, and End Users can monitor their health and status. In addition, such network Scanners need remote request for job creation capabilities so that operators and End Users can create Scan Jobs without depending entirely on local console interfaces. This document defines a semantic model for service, device, and job management and request for job creation for these network Scanners. This document is a PWG Candidate Standard. For a definition of a "PWG Candidate Standard", see: ftp://ftp.pwg.org/pub/pwg/general/pwg-process20.pdf This document is available electronically at: ftp://ftp.pwg.org/pub/pwg/candidates/cs-sm20-scan10-20090410-5108.02.pdf, .doc Copyright © 2007-2009, Printer Working Group. All rights reserved. PWG 5108.02-2009 MFD: Scan Service April 10, 2009 Copyright (C) 2007-2008, The Printer Working Group. All rights reserved. This document may be copied and furnished to others, and derivative works that comment on, or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice, this paragraph and the title of the Document as referenced below are included on all such copies and derivative works.
    [Show full text]
  • Device Repository Guide
    BEA WebLogic Mobility Server Device Repository Guide Version 3.6 SP1 Oct 2007 Contents Copyright Copyright © 1995-2007 BEA Systems, Inc. All Rights Reserved. Restricted Rights Legend This software is protected by copyright, and may be protected by patent laws. No copying or other use of this software is permitted unless you have entered into a license agreement with BEA authorizing such use. This document is protected by copyright and may not be copied photocopied, reproduced, translated, or reduced to any electronic medium or machine readable form, in whole or in part, without prior consent, in writing, from BEA Systems, Inc. Information in this document is subject to change without notice and does not represent a commitment on the part of BEA Systems. THE DOCUMENTATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, BEA SYSTEMS DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE DOCUMENT IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. Trademarks and Service Marks Copyright © 1995-2007 BEA Systems, Inc. All Rights Reserved.BEA, BEA JRockit, BEA WebLogic Portal, BEA WebLogic Server, BEA WebLogic Workshop, Built on BEA, Jolt, JoltBeans, SteelThread, Top End, Tuxedo, and WebLogic are registered trademarks of BEA Systems, Inc. BEA AquaLogic, BEA AquaLogic Data Services Platform, BEA AquaLogic Enterprise Security, BEA AquaLogic Service Bus, BEA AquaLogic Service
    [Show full text]
  • The Semantic Web: an Introduction 2/24/04 2:29 AM
    The Semantic Web: An Introduction 2/24/04 2:29 AM The Semantic Web: An Introduction This document is designed as being a simple but comprehensive introductory publication for anybody trying to get into the Semantic Web: from beginners through to long time hackers. Recommended pre-reading: the Semantic Web in Breadth. Table Of Contents 1. What Is The Semantic Web? 2. Simple Data Modelling: Schemata 3. Ontologies, Inferences, and DAML 4. The Power Of Semantic Web Languages 5. Trust and Proof 6. Ambient Information and SEM 7. Evolution 8. Does It Work? What Semantic Web Applications Are There? 9. What Now? Further Reading What Is The Semantic Web? The Semantic Web is a mesh of information linked up in such a way as to be easily processable by machines, on a global scale. You can think of it as being an efficient way of representing data on the World Wide Web, or as a globally linked database. The Semantic Web was thought up by Tim Berners-Lee, inventor of the WWW, URIs, HTTP, and HTML. There is a dedicated team of people at the World Wide Web consortium (W3C) working to improve, extend and standardize the system, and many languages, publications, tools and so on have already been developed. However, Semantic Web technologies are still very much in their infancies, and although the future of the project in general appears to be bright, there seems to be little consensus about the likely direction and characteristics of the early Semantic Web. What's the rationale for such a system? Data that is geneally hidden away in HTML files is often useful in some contexts, but not in others.
    [Show full text]