DOCSLIB.ORG

Pub. No.: US 2012/0036226A1 Chor (43) Pub

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Pub. No.: US 2012/0036226A1 Chor (43) Pub US 2012.0036226A1 (19) United States (12) Patent Application Publication (10) Pub. No.: US 2012/0036226A1 Chor (43) Pub. Date: Feb. 9, 2012 (54) URI SERVICE SYSTEMAND METHOD Publication Classification (75) Inventor: Jesse Chor, Bellevue, WA (US) (51) Int. Cl. G06F 5/16 (2006.01) (73) Assignee: MSKYNET, INC., Bellevue, WA (US) (21) Appl. No.: 12/908,547 (52) U.S. Cl. ........................................................ 709/219 (22) Filed: Oct. 20, 2010 Related U.S. Application Data (57) ABSTRACT (63) Continuation-in-part of application No. 12/852,730, A URI-redirection via machine-scannable-code system and filed on Aug. 9, 2010. method are provided herein. Patent Application Publication Feb. 9, 2012 Sheet 1 of 15 US 2012/0036226 A1 $$$$$$$ voyo 8. Patent Application Publication Feb. 9, 2012 Sheet 2 of 15 US 2012/0036226 A1 888. 88: xxx - : | E-REE BE 88: Patent Application Publication Feb. 9, 2012 Sheet 3 of 15 US 2012/0036226 A1 - 3: sorror-rror: :::::::: 88: -** 8:888 × ^ -385 ; : R-3E 8: E 88: 88-83-8:88:::::::::: 88.888.888: 88883 Patent Application Publication Feb. 9, 2012 Sheet 4 of 15 US 2012/0036226 A1 ###########:;$3&###### #### }}}}}}}}}} }}}}}{{### ######## ?ae ###########3 ************************? §§§§§ ??º?###3&##§############## Patent Application Publication Feb. 9, 2012 Sheet 5 of 15 US 2012/0036226 A1 it wo. Y. «-». ^ ::::::::: 8:8:... ESR 8888 8: 888 ------ass ·-8-ox. E.58EDD t is -535 — Patent Application Publication Feb. 9, 2012 Sheet 6 of 15 US 2012/0036226 A1 Patent Application Publication Feb. 9, 2012 Sheet 7 of 15 US 2012/0036226 A1 -* ...' ... ...x^* - N is is: ...-- its Y- :::::::::: i: . ^ SCNABLE CIOE ENCEDELE.E.E. E. CNE. > 8::::::::::: 72N-(DELNERtitle as NE {{SIRE : s 8. ***. x «xo~.--------------------------------------------------------------- Patent Application Publication Feb. 9, 2012 Sheet 8 of 15 US 2012/0036226 A1 R.E. iii. 3888; iii. 8. BEEEEEEEE::::::::::::::::: YPE/PSEs3888 “. : 8 888 SEERE: - - - 3xx's 88: 888 88: :::::::::RESE8 E. E. : 88:3888: it is: sis g 883 - ::::::: D Patent Application Publication Feb. 9, 2012 Sheet 9 of 15 US 2012/0036226 A1 Patent Application Publication Feb. 9, 2012 Sheet 10 of 15 US 2012/0036226 A1 Patent Application Publication Feb. 9, 2012 Sheet 11 of 15 US 2012/0036226 A1 §§§§§§§ Patent Application Publication Feb. 9, 2012 Sheet 12 of 15 US 2012/0036226 A1 ######## &####### *******************************************************************************************************************************************************************************************************************************************::::::::::::::: Patent Application Publication Feb. 9, 2012 Sheet 14 of 15 US 2012/0036226 A1 “Elits - E 145 -N-15S.NSICAE isArts 1." . 88: EEEEEE :::::::::::::::: Si::::::::::::::: Patent Application Publication Feb. 9, 2012 Sheet 15 of 15 US 2012/0036226 A1 US 2012/0036226 A1 Feb. 9, 2012 UR SERVICE SYSTEMAND METHOD 0006. However, not all actionable text formats are so uni versally recognizable, and many different mobile device CROSS REFERENCE TO RELATED manufacturers and/or mobile device operating system pro APPLICATIONS viders may implement proprietary standards for formatting actionable text in two-dimensional barcodes. For example, 0001. This application is a continuation in part of U.S. mobile devices provided by NTT DoCoMo, Inc. of Tokyo, application Ser. No. 12/852,730, filed on Aug. 9, 2010 (pend Japan may recognize URLs encoded using an alternate for ing), titled “REMOTE APPLICATIONINVOCATIONSYS mat, e.g. “MEBKM:TITLE:NTT DOCOMO:URL:httpY://i. TEM AND METHOD,” naming inventor Jesse Chor, and nttdocomo.co.jp/f7;”. While mobile devices provided by NTT having Attorney Docket number MSKY-2010003. The DoCoMo may recognize such a URI, other types of mobile above-cited application is incorporated herein by reference in device may not recognize Such a URI. its entirety, for all purposes. 0007 Similarly, differing formal and/or de-facto stan dards may be used by different types of mobile devices for FIELD interpreting encoded contact information, event/appointment information, and other types of information. Consequently, it 0002 The present disclosure relates to networked comput may be difficult or even impossible in some cases to provide ing services, and more particularly to handling URIs via a single two-dimensional barcode that will cause a variety of machine-scannable codes. different types of mobile devices to perform a desired action. 0008. In addition, different types of mobile devices may BACKGROUND implement cameras or other scanning components that have 0003. The term “mobile tagging refers to the process of differing capture capabilities. While various types of two providing data to mobile devices, commonly through the use dimensional barcode may be able to encode several kilobytes of data (e.g., a Uniform Resource Locator or “URL) encoded (or more) of information, not all mobile devices may be able in a two-dimensional barcode. For example, addresses and/or to properly recognize many densely-packed two-dimensional URLs are commonly encoded in two-dimensional barcodes barcodes. For example, a first mobile device with an auto (e.g., QR Codes, Data Matrix codes, High Capacity Color focus macro lens may be able to capture and resolve a two Barcodes or “HCCBs, and the like) that are printed in maga dimensional barcode encoded with several kilobytes of data, Zines, on signs, buses, business cards, or other object. Users while a second mobile device, with a fixed-focus lens, may with a camera phone equipped with an appropriate reader only be able to resolve as little as 200 bytes of data. Conse application can scan the image of the two-dimensional bar quently, even if the first and second devices both Supported code to display text, contact information, connect to a wire the same actionable text format, the second device may still less network, open a webpage in the phone's browser, and/or be incapable of acting on an information-dense two-dimen perform other operations. For example, the Android operat sional barcode due to hardware limitations of the second ing system for mobile devices (provided by Google Inc. of device's capture components. Menlo Park, Calif.) supports the use of QR codes by natively including a barcode scanner application on Some device mod BRIEF DESCRIPTION OF THE DRAWINGS els and by including a browser that Supports Uniform Resource Identifier (“URI) redirection, which allows QR 0009 FIG. 1 illustrates an exemplary remote application Codes to send metadata to existing applications on the device. invocation system according to one embodiment. The Symbian OS (provided by Nokia Corporation of Tem 0010 FIG. 2 illustrates several components of an exem pere, Finland) also includes a barcode scanner that is able to plary URI-service server. read QR Codes. 0011 FIG. 3 illustrates several components of an exem 0004 Generally speaking two-dimensional barcodes plary mobile device. encode some sort of actionable text (or other data). For 0012 FIG. 4 illustrates an sequence of data communica example, text representing contact information, when recog tions for an exemplary remote-application invocation sce nized by a barcode scanner application, could add the contact nario, in accordance with one embodiment. information to an address book on the device. Similarly, text 0013 FIG. 5 illustrates a remote-application invocation representing an event or appointment, when recognized, routine in accordance with one embodiment. could add the event or appointment to a calendar on the 0014 FIG. 6 illustrates an exemplary device/payload device; text representing geo-location information, when rec ognized, could open a map application on the device; and so mapping Subroutine, in accordance with one embodiment. O. 0015 FIG. 7 illustrates an exemplary unique URL expo 0005. However, actionable text, such as the examples Sure Subroutine, in accordance with one embodiment. mentioned above, can only be acted on when the barcode 0016 FIG. 8 illustrates an exemplary unique-URL-re scanner application understands the format of the actionable quest processing Subroutine, in accordance with one embodi text encoded in the two-dimensional barcode. Some format ment. standards exist and are commonly used for encoding action (0017 FIG. 9 illustrates a SPARQCodeTM two-dimen able text in a two-dimensional barcode. For example, perhaps sional barcode, Such as may be employed as a machine the most common actionable text encoded in two-dimen scannable code in various embodiments in one embodiment. sional barcodes is text that represents a URL, e.g. "http:// 0018 FIG. 10 illustrates a web application, such as may be google.com/m'. This string of text would be generally rec provided by URI-service server in one embodiment, for han ognized as a URL by virtually all barcode scanner dling a geo-location payload. applications, and the resulting action would typically be to 0019 FIG. 11 illustrates a web application, such as may be open the URL in a browser application on the device. provided by URI-service server, for handling a URL payload. US 2012/0036226 A1 Feb. 9, 2012 0020 FIG. 12 illustrates a web application, such as may be other Suitable communication technology. In some embodi provided by URI-service server in one embodiment, for han ments, URI-service server 200, publisher device 110, and/or dling an event or appointment payload. database 115 may comprise one or more replicated and/or 0021 FIG. 13 illustrates an sequence of data communica distributed physical or logical devices. tions for an exemplary dynamic machine-Scannable-code 0030. In various embodiments, network 150 may include generation and URI-handling scenario, in accordance with the Internet, a local area network (“LAN”), a wide area net one embodiment. work (“WAN”), a cellular data network, and/or other data 0022 FIG. 14 illustrates a dynamic machine-scannable network. In many embodiments, there may be more mobile code generation routine. Such as may be performed by URI devices 300 than are illustrated. service server in accordance with one embodiment. 0031 FIG. 2 illustrates several components of an exem 0023 FIG. 15 illustrates a URI-redirection routine, such plary URI-service server 200.
Load more

Recommended publications
  • Mac OS X Includes Built-In FTP Support, Easily Controlled Within a fifteen-Mile Drive of One-Third of the US Population
    Cover 8.12 / December 2002 ATPM Volume 8, Number 12 About This Particular Macintosh: About the personal computing experience™ ATPM 8.12 / December 2002 1 Cover Cover Art Robert Madill Copyright © 2002 by Grant Osborne1 Belinda Wagner We need new cover art each month. Write to us!2 Edward Goss Tom Iov ino Editorial Staff Daniel Chvatik Publisher/Editor-in-Chief Michael Tsai Contributors Managing Editor Vacant Associate Editor/Reviews Paul Fatula Eric Blair Copy Editors Raena Armitage Ya n i v E i d e l s t e i n Johann Campbell Paul Fatula Ellyn Ritterskamp Mike Flanagan Brooke Smith Matt Johnson Vacant Matthew Glidden Web E ditor Lee Bennett Chris Lawson Publicity Manager Vacant Robert Paul Leitao Webmaster Michael Tsai Robert C. Lewis Beta Testers The Staff Kirk McElhearn Grant Osborne Contributing Editors Ellyn Ritterskamp Sylvester Roque How To Ken Gruberman Charles Ross Charles Ross Gregory Tetrault Vacant Michael Tsai Interviews Vacant David Zatz Legacy Corner Chris Lawson Macintosh users like you Music David Ozab Networking Matthew Glidden Subscriptions Opinion Ellyn Ritterskamp Sign up for free subscriptions using the Mike Shields Web form3 or by e-mail4. Vacant Reviews Eric Blair Where to Find ATPM Kirk McElhearn Online and downloadable issues are Brooke Smith available at http://www.atpm.com. Gregory Tetrault Christopher Turner Chinese translations are available Vacant at http://www.maczin.com. Shareware Robert C. Lewis Technic a l Evan Trent ATPM is a product of ATPM, Inc. Welcome Robert Paul Leitao © 1995–2002, All Rights Reserved Kim Peacock ISSN: 1093-2909 Artwork & Design Production Tools Graphics Director Grant Osborne Acrobat Graphic Design Consultant Jamal Ghandour AppleScript Layout and Design Michael Tsai BBEdit Cartoonist Matt Johnson CVL Blue Apple Icon Designs Mark Robinson CVS Other Art RD Novo DropDMG FileMaker Pro Emeritus FrameMaker+SGML RD Novo iCab 1.
    [Show full text]
  • Bleach Documentation Release 3.0.1 20181009
    Bleach Documentation Release 3.0.1 20181009 Will Kahn-Greene Oct 09, 2018 Contents 1 Reporting Bugs 3 2 Security 5 3 Installing Bleach 7 4 Upgrading Bleach 9 5 Basic use 11 6 Code of conduct 13 7 Contents 15 7.1 Sanitizing text fragments......................................... 15 7.2 Linkifying text fragments........................................ 23 7.3 Goals of Bleach............................................. 29 7.4 Bleach development........................................... 32 7.5 Bleach changes.............................................. 34 8 Indices and tables 43 i ii Bleach Documentation, Release 3.0.1 20181009 Bleach is an allowed-list-based HTML sanitizing library that escapes or strips markup and attributes. Bleach can also linkify text safely, applying filters that Django’s urlize filter cannot, and optionally setting rel attributes, even on links already in the text. Bleach is intended for sanitizing text from untrusted sources. If you find yourself jumping through hoops to allow your site administrators to do lots of things, you’re probably outside the use cases. Either trust those users, or don’t. Because it relies on html5lib, Bleach is as good as modern browsers at dealing with weird, quirky HTML fragments. And any of Bleach’s methods will fix unbalanced or mis-nested tags. The version on GitHub is the most up-to-date and contains the latest bug fixes. You can find full documentation on ReadTheDocs. Code https://github.com/mozilla/bleach Documentation https://bleach.readthedocs.io/ Issue tracker https://github.com/mozilla/bleach/issues IRC #bleach on irc.mozilla.org License Apache License v2; see LICENSE file Contents 1 Bleach Documentation, Release 3.0.1 20181009 2 Contents CHAPTER 1 Reporting Bugs For regular bugs, please report them in our issue tracker.
    [Show full text]
  • Diplomarbeit Kalenderstandards Im Internet
    Diplomarbeit Kalenderstandards im Internet Eingereicht von Reinhard Fischer Studienkennzahl J151 Matrikelnummer: 9852961 Diplomarbeit am Institut für Informationswirtschaft WIRTSCHAFTSUNIVERSITÄT WIEN Studienrichtung: Betriebswirtschaft Begutachter: Prof. DDr. Arno Scharl Betreuender Assistent: Dipl.-Ing. Mag. Dr. Albert Weichselbraun Wien, 20. August 2007 ii Inhaltsverzeichnis Abbildungsverzeichnis vi Abkürzungsverzeichnis vii 1 Einleitung 1 1.1 Problemstellung . 1 1.2 Inhalt und Vorgehensweise . 3 2 Standards für Kalender im Internet 5 2.1 iCalendar und darauf basierende Standards . 6 2.1.1 iCalendar und vCalendar . 6 2.1.2 Transport-Independent Interoperability Protocol (iTIP) . 8 2.1.3 iCalendar Message-Based Interoperability Protocol (iMIP) . 8 2.1.4 iCalendar über WebDAV (WebCAL) . 10 2.1.5 Storage of Groupware Objects in WebDAV (GroupDAV) . 11 2.1.6 Calendaring and Scheduling Extensions to WebDAV (CalDAV) . 12 2.1.7 IETF Calendar Access Protocol (CAP) . 13 2.2 XML-basierte Formate . 15 2.2.1 XML iCalendar (xCal) . 15 2.2.2 RDF Calendar (RDFiCal) . 16 2.2.3 RDFa (RDF/A) . 16 2.2.4 OWL-Time . 17 2.3 Mikroformate (hCalendar) . 18 2.4 SyncML . 20 2.5 Weitere Formate . 21 2.6 Zusammenfassung . 22 iii 3 Offene Kalenderanwendungen im Internet 24 3.1 Server . 24 3.1.1 Citadel/UX . 24 3.1.2 Open-Xchange . 26 3.1.3 OpenGroupware.org . 26 3.1.4 Kolab2 . 27 3.1.5 Weitere Server . 28 3.2 Clients . 29 3.2.1 Mozilla Calendar Project . 29 3.2.2 KDE Kontact . 30 3.2.3 Novell Evolution . 30 3.2.4 OSAF Chandler . 31 3.2.5 Weitere Open-Source- und Closed-Source-Clients .
    [Show full text]
  • CHAPTER 15 Accessing Online Calendars and Event Aggregators
    CHAPTER 15 Accessing Online Calendars and Event Aggregators Online calendars will move from being merely trendy to virtually indispensable as our lives move increasingly to the network. Calendaring (scheduling appointments and coordinating calendars) is something most of us can relate to since we all have appointments that we make and keep. As we use electronic calendars, there is a good chance that we will have more than one calendar to synchronize—people use different calendars or work with people with other calendars, no matter how much Microsoft, Apple, Google, or Yahoo! might want everyone to use its calendar alone. A lot of this calendaring activity has moved to not only digital form but specifically to a networked digital form. In addition to the old calendars, new generations of online calendars are coming into existence—that’s the focus of this chapter. Online calendars exist in the context of other digital calendars: desktop calendars such as Microsoft Outlook and Apple iCal and calendars on handheld devices such as the Palm calendar. Much work has been done on synchronizing these calendars. Of course, calendar synchronization has been operant for a while, but these approaches (specialized conduits/SyncML1) have been more opaque than the APIs now available.2 Today’s online calendars with APIs generally make synchronization easier. In addition to the proliferation of online calendars, event aggregation sites such as Upcoming.yahoo.com and Eventful.com are starting to create a marketplace of event data. They are focused on public events, whereas online calendars have as their focal point individuals and private events.
    [Show full text]
  • Calendar Subscription Upgrades
    Table of Contents ▲ Workgroup: Network Working Group Internet-Draft: draft-ietf-calext-subscription-upgrade-02 : Updates: 5988 (if approved) Published: 29 July 2020 Intended Status: Standards Track Expires: 30 January 2021 Author: M. Douglass Calendar subscription upgrades Abstract This specification updates [RFC5545] to add the value DELETED to the STATUS property. This specification also updates [RFC7240] to add the subscribe- enhanced-get and limit preferences. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 30 January 2021. Copyright Notice Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
    [Show full text]
  • Links in an Event Description
    1. Home . 3 1.1 Frequently Asked Questions (FAQ) . 3 1.1.1 Remove Calendar Ads . 8 1.1.2 Why is my calendar cut off on the bottom . 9 1.2 Overview of the localendar menu . 9 1.3 Entering and Editing Events . 11 1.3.1 Adding New Events . 12 1.3.1.1 Add Links in an Event Description . 15 1.3.2 Editing Existing Events . 16 1.3.3 Preview an Event . 16 1.3.4 Adding Clipart to an Event . 17 1.3.5 Uploading your own Images . 20 1.3.6 Repeating Events . 23 1.3.7 Entering a Multi-Day Event . 27 1.3.8 Entering a Multi-Day Event that Repeats . 29 1.3.9 Setting up Reminders . 32 1.3.10 Custom HTML in Events . 32 1.3.11 Tips and Tricks for Events . 33 1.3.12 Creating Events that Accept RSVPs, Payments, and More . 34 1.3.13 Attaching files to Events . 36 1.4 Deleting Events . 38 1.5 Publishing a Calendar . 38 1.5.1 Common Publishing Questions . 39 1.5.2 Gallery of Calendar Styles . 40 1.5.2.1 Timeline View . 44 1.5.3 Your Calendar's URL and Parameters . 46 1.5.4 The Publish Wizard . 47 1.6 Customizing your localendar . 48 1.6.1 General Options . 49 1.6.1.1 Additional General Options . 51 1.6.1.2 Using an Email Group for Reminders . 52 1.6.1.3 Visitor-Submitted Events . 52 1.6.2 Event Options . 52 1.6.3 Colors and Backgrounds .
    [Show full text]
  • Groupware Reference
    IceWarp Unified Communications GroupWare Reference Version 10.4 Printed on 20 December, 2012 Contents GroupWare 1 About.............................................................................................................................................................................. 2 Pre-requisities ................................................................................................................................................................ 3 Database ............................................................................................................................................... 3 Supported clients .................................................................................................................................. 3 Licenses ................................................................................................................................................. 4 General Setup ........................................................................................................................................ 4 Terminology, Abbreviations ........................................................................................................................................... 5 Sharing Concepts ............................................................................................................................................................ 7 User Groups ......................................................................................................................................................
    [Show full text]
  • Vdirsyncer Documentation Release 0.18.1.Dev82+Gdb6da70
    vdirsyncer Documentation Release 0.18.1.dev82+gdb6da70 Markus Unterwaditzer Sep 22, 2021 Users 1 When do I need Vdirsyncer?3 2 Installation 5 3 Tutorial 9 4 SSL and certificate validation 15 5 Storing passwords 17 6 Syncing with read-only storages 19 7 Full configuration manual 21 8 Other tutorials 31 9 Known Problems 39 10 Contributing to this project 41 11 The Vdir Storage Format 45 12 Packaging guidelines 47 13 Support and Contact 49 14 Changelog 51 15 Credits and License 65 16 Donations 67 Bibliography 69 Index 71 i ii vdirsyncer Documentation, Release 0.18.1.dev82+gdb6da70 • Documentation • Source code Vdirsyncer is a command-line tool for synchronizing calendars and addressbooks between a variety of servers and the local filesystem. The most popular usecase is to synchronize a server with a local folder and use a set of other programs to change the local events and contacts. Vdirsyncer can then synchronize those changes back to the server. However, vdirsyncer is not limited to synchronizing between clients and servers. It can also be used to synchronize calendars and/or addressbooks between two servers directly. It aims to be for calendars and contacts what OfflineIMAP is for emails. Users 1 vdirsyncer Documentation, Release 0.18.1.dev82+gdb6da70 2 Users CHAPTER 1 When do I need Vdirsyncer? 1.1 Why not Dropbox + todo.txt? Projects like todo.txt criticize the complexity of modern productivity apps, and that rightfully. So they set out to create a new, super-simple, human-readable format, such that vim suffices for viewing the raw data.
    [Show full text]
  • Calendaring and Scheduling — Calendar Subscription Upgrades
    CC/CD 51005:2018 Calendaring and scheduling — Calendar subscription upgrades THE CALENDARING AND SCHEDULING CONSORTIUM TC CALENDAR Michael Douglass AUTHOR CALCONNECT STANDARD COMMITTEE DRAFT WARNING FOR DRAFTS This document is not a CalConnect Standard. It is distributed for review and comment, and is subject to change without notice and may not be referred to as a Standard. Recipients of this draft are invited to submit, with their comments, notication of any relevant patent rights of which they are aware and to provide supporting documentation. © 2018 The Calendaring and Scheduling Consortium, Inc. All rights reserved. Unless otherwise specied, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from the address below. The Calendaring and Scheduling Consortium, Inc. 4390 Chaffin Lane McKinleyville California 95519 United States of America [email protected] www.calconnect.org CONTENTS Foreword Introduction 1. Scope 2. Normative references 3. Terms and denitions 4. Enhanced GET 4.1. General 4.2. Deletions 5. Changes to the iCalendar specications 6. Discovering alternative access methods 6.1. General 6.2. subscribe-caldav 6.3. subscribe-caldav-auth 6.4. subscribe-webdav-sync 6.5. subscribe-enhanced-get 7. Security Considerations 8. IANA Considerations 8.1. Link Relation Registrations 9. Acknowledgements Appendix A(informative) Open issues Appendix B(informative) Change log Bibliography FOREWORD The Calendaring and Scheduling Consortium (“CalConnect”) is a global non-prot organization with the aim to facilitate interoperability of collaborative technologies and tools through open standards.
    [Show full text]
  • Novell Access Manager 3.1 SP3 Installation Guide Contents
    AUTHORIZED DOCUMENTATION Installation Guide Novell® Access Manager 3.1 SP3 February 02, 2011 www.novell.com Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software.
    [Show full text]
  • Bleach Documentation Release 3.0.2 20181011
    Bleach Documentation Release 3.0.2 20181011 Will Kahn-Greene Nov 09, 2018 Contents 1 Reporting Bugs 3 2 Security 5 3 Installing Bleach 7 4 Upgrading Bleach 9 5 Basic use 11 6 Code of conduct 13 7 Contents 15 7.1 Sanitizing text fragments......................................... 15 7.2 Linkifying text fragments........................................ 23 7.3 Goals of Bleach............................................. 29 7.4 Bleach development........................................... 32 7.5 Bleach changes.............................................. 34 8 Indices and tables 43 i ii Bleach Documentation, Release 3.0.2 20181011 Bleach is an allowed-list-based HTML sanitizing library that escapes or strips markup and attributes. Bleach can also linkify text safely, applying filters that Django’s urlize filter cannot, and optionally setting rel attributes, even on links already in the text. Bleach is intended for sanitizing text from untrusted sources. If you find yourself jumping through hoops to allow your site administrators to do lots of things, you’re probably outside the use cases. Either trust those users, or don’t. Because it relies on html5lib, Bleach is as good as modern browsers at dealing with weird, quirky HTML fragments. And any of Bleach’s methods will fix unbalanced or mis-nested tags. The version on GitHub is the most up-to-date and contains the latest bug fixes. You can find full documentation on ReadTheDocs. Code https://github.com/mozilla/bleach Documentation https://bleach.readthedocs.io/ Issue tracker https://github.com/mozilla/bleach/issues IRC #bleach on irc.mozilla.org License Apache License v2; see LICENSE file Contents 1 Bleach Documentation, Release 3.0.2 20181011 2 Contents CHAPTER 1 Reporting Bugs For regular bugs, please report them in our issue tracker.
    [Show full text]
  • Nextcloud Server Administration Manual Release Latest
    Nextcloud Server Administration Manual Release latest The Nextcloud developers Oct 10, 2021 CONTENTS 1 Introduction 1 1.1 Videos and blogs.............................................1 1.2 Target audience..............................................1 2 Release notes 3 3 Maintenance and release schedule5 3.1 Major releases..............................................5 3.2 Maintenance releases...........................................5 3.3 Older versions..............................................6 4 Installation and server configuration7 4.1 System requirements...........................................7 4.2 Deployment recommendations......................................9 4.3 Installation on Linux...........................................9 4.4 Installation wizard............................................ 17 4.5 Installing from command line...................................... 21 4.6 Supported apps.............................................. 22 4.7 SELinux configuration.......................................... 24 4.8 NGINX configuration.......................................... 27 4.9 Hardening and security guidance.................................... 35 4.10 Server tuning............................................... 40 4.11 Example installation on Ubuntu 20.04 LTS............................... 42 4.12 Example installation on CentOS 8.................................... 44 5 Nextcloud configuration 49 5.1 Warnings on admin page......................................... 49 5.2 Using the occ command........................................
    [Show full text]