Programme of Work (As on 1 April 2011)
Total Page:16
File Type:pdf, Size:1020Kb

Load more
Recommended publications
-
Payment Initiation API Specification V1.0 Contents
Coventry Building Society Payment Initiation API Specification V1.0 Contents Coventry Building Society .................................................................................................................................................... 1 Version control ..................................................................................................................................................................... 4 Overview .............................................................................................................................................................................. 5 Document Overview ........................................................................................................................................................ 5 Design Principles ............................................................................................................................................................. 5 RESTful APIs ............................................................................................................................................................... 5 Idempotency ................................................................................................................................................................ 6 Payment API - Scheme Agnostic ................................................................................................................................ 6 Status Codes .............................................................................................................................................................. -
Standards at Transactional and Aggregated Level
Standards at transactional and aggregated level 7th May 2014 eSupervision Workshop, Rome Overview The value, need and ability to capture transactions in a standard way in repositories as a foundation for regulatory analysis using the example of ISO 20022 The value of and need for connecting the transactional and detailed-level data standards and models (ISO 20022, ACORD, FpML, FIBO, FIX) with regulatory or aggregated data standards (XBRL, SDMX, XML) First, a look at internationally developed data standards for financial services and the ISO 20022 standard International Standards for Financial Services, ISO/TC68 ISO Technical Committee TC68 Financial Services SC2 SC4 SC7 ISO 20022 Security Securities Core Banking Standard ISO 20022 WG5 Registration ISO 20022 Technical LEI Management Standard Standard Group ISO 17442 Technical Registration Support Authority Group Standard Evaluation Groups Standards Managed by ISO/TC68/SC2, Security ISO TC68/SC2 Financial Services, Security Published Standards – ISO 9564 Personal Identification Number (PIN) management and security – ISO 11568 Key management (retail) – ISO 13491 Secure cryptographic devices (retail) – ISO 13492 Key management related data element -- Application and usage of ISO 8583 data elements 53 and 96 – ISO 15782 Certificate management for financial services (PKI) – ISO 16609 Requirements for message authentication using symmetric techniques – ISO 21188 Public key infrastructure management for financial services - Practices and policy framework Technical Reports ISO 13569 Information -
ISO/TC46 (Information and Documentation) Liaison to IFLA
ISO/TC46 (Information and Documentation) liaison to IFLA Annual Report 2015 TC46 on Information and documentation has been leading efforts related to information management since 1947. Standards1 developed under ISO/TC46 facilitate access to knowledge and information and standardize automated tools, computer systems, and services relating to its major stakeholders of: libraries, publishing, documentation and information centres, archives, records management, museums, indexing and abstracting services, and information technology suppliers to these communities. TC46 has a unique role among ISO information-related committees in that it focuses on the whole lifecycle of information from its creation and identification, through delivery, management, measurement, and archiving, to final disposition. *** The following report summarizes activities of TC46, SC4, SC8 SC92 and their resolutions of the annual meetings3, in light of the key-concepts of interest to the IFLA community4. 1. SC4 Technical interoperability 1.1 Activities Standardization of protocols, schemas, etc. and related models and metadata for processes used by information organizations and content providers, including libraries, archives, museums, publishers, and other content producers. 1.2 Active Working Group WG 11 – RFID in libraries WG 12 – WARC WG 13 – Cultural heritage information interchange WG 14 – Interlibrary Loan Transactions 1.3 Joint working groups 1 For the complete list of published standards, cfr. Appendix A. 2 ISO TC46 Subcommittees: TC46/SC4 Technical interoperability; TC46/SC8 Quality - Statistics and performance evaluation; TC46/SC9 Identification and description; TC46/SC 10 Requirements for document storage and conditions for preservation - Cfr Appendix B. 3 The 42nd ISO TC46 plenary, subcommittee and working groups meetings, Beijing, June 1-5 2015. -
Securetrust Service Description Web Risk Monitoring
SecureTrust Service Description Web Risk Monitoring Copyright © 2018 Trustwave Holdings, Inc. All rights reserved. 1 SecureTrust WRM Service Description - January 27, 2021 WEB RISK MONITORING (WRM) ................................................................................................................ 3 SERVICE DESCRIPTION ................................................................................................................................. 3 BASE SERVICE FEATURES ............................................................................................................................. 3 WRM Overview ....................................................................................................................................... 3 Content Monitoring ................................................................................................................................. 5 Merchant Intelligence.............................................................................................................................. 5 Malware Monitoring ................................................................................................................................ 7 Custom Monitoring.................................................................................................................................. 8 Transaction Laundering Detection (TLD) ............................................................................................... 8 Merchant MCC Code Matching ............................................................................................................. -
Czech Standard for Open Banking (V 3.0)
Banking Activities Standards Standard ČBA Czech Standard for Open Banking Version 3.0 Public from: 1.4. 2019 Valid from: 1.1. 2020 1 Changes Date Note Author 15.11.2017 Basic document v.01 ČS Petr Michalík 27.7.2018 Document version 1.2 - Correction of typing errors, new error codes, new ČS Petr Michalík chart visualizations, coupled payment type codes in response to initiation of payment (Chapter 4.24.2.1) and general element descriptions added / specified. 9.4.2018 Document v.02.0 -- An extension to initiate Instant Payment has been ČS Petr Michalík added to the standard. Any further processing of such initiated payment is done according to the rules of this scheme. Chapter 3.2.4, 4.24.1 and 4.25 18.5.2018 Added new request header parameters for original TPP identification ČS Petr Michalík 19.9.2018 Extended description of the use of certificates in chaper 1.4.8 ČS Petr Michalík 2.10.2018 New request body element “redirectUrl”. Address in this element ČS Petr Michalík is used by the federated bank authorization to redirect back to the TPP application after authorization is complete. Chapter 3.2.10.1 and example in chapter 5.11.1 2.10.2018 Error response extension for NO_PART error code during ČS Petr Michalík payment initiation. Chapter 3.2.4 and new example in chapter 5.5.6 1.12.2018 Specification the use of the character set for each resource. ČS Petr Michalík Chapter 1.2.5, 3.1.1, 3.2.1, 3.3.1, 3.2.3, 3.2.4 – 11, 3.3.3 21.12.2018 Final public document COBS 2.0 ČS Petr Michalik 3.1.2019 New version document – v.03 ČS Petr Michalík 4.1.2019 Standing order resource for PIS services ČS Petr Michalík Chapters 3.2.12 – 3.2.18 4.1.2019 For each source, information on the implementation obligation has been ČS Petr Michalík added (see resource parameter Mandatory: yes/no) 5.1.2019 Consent management resources (POST and DELETE) ČS Petr Michalík See Chapter 1.6.x 12.1.2019 Common header parameters ČS Petr Michalík See Chapter 1.5 and changes in the header parameters specifications of the all defined resources. -
Descriptive Metadata Guidelines for RLG Cultural Materials I Many Thanks Also to These Individuals Who Reviewed the Final Draft of the Document
������������������������������� �������������������������� �������� ����������������������������������� ��������������������������������� ��������������������������������������� ���������������������������������������������������� ������������������������������������������������� � ���������������������������������������������� ������������������������������������������������ ����������������������������������������������������������� ������������������������������������������������������� ���������������������������������������������������� �� ���������������������������������������������� ������������������������������������������� �������������������� ������������������� ���������������������������� ��� ���������������������������������������� ����������� ACKNOWLEDGMENTS Many thanks to the members of the RLG Cultural Materials Alliance—Description Advisory Group for their participation in developing these guidelines: Ardie Bausenbach Library of Congress Karim Boughida Getty Research Institute Terry Catapano Columbia University Mary W. Elings Bancroft Library University of California, Berkeley Michael Fox Minnesota Historical Society Richard Rinehart Berkeley Art Museum & Pacific Film Archive University of California, Berkeley Elizabeth Shaw Aziza Technology Associates, LLC Neil Thomson Natural History Museum (UK) Layna White San Francisco Museum of Modern Art Günter Waibel RLG staff liaison Thanks also to RLG staff: Joan Aliprand Arnold Arcolio Ricky Erway Fae Hamilton Descriptive Metadata Guidelines for RLG Cultural Materials i Many -
| Prolibis – Solutions for Libraries in the Digital Age
| ProLibis – Solutions for Libraries in the Digital Age Automation of Core Library Business Processes We see a modern library not The ProLibis products include the following software functionality: only as a book repository, but also and most importantly Oracle as a state-of-the-art, open and • Cataloguing – page 4. interactive information and • Acquisition – page 5. • Circulation (Customer Service) – page 5. knowledge centre. This is the • OPAC and WWW-OPAC – page 6. vision underlying ProLibis • Interlibrary Loan – page 7. • Database of Authority Records (Names, Titles and solutions. Subjects) – page 7. • Bibliographic Service – page 7. • Universal Decimal Classification (UDC) Asseco Lithuania, with its Management – page 7. extensive experience and • System Administration Functions – page 8. • General Databases (Union Catalogue, Analytic thorough understanding of Records, Common Readers Database) – page 9. library’s needs, offers products • Special Databases (Publishers, Pseudonyms, Electronic Resources) – page 9. and highly advanced software • Digital Material Management – page 9. solutions for a modern library of Postgre SQL Apache almost any size, ranging from a large national library, medium size Affordable Software Solution for Small Libraries – page 10. public library to a small school library. It’s even able to introduce an integrated system for the whole Technical Information and Abbreviations – network of libraries. page 11. 2 | Asseco Lithuania Solutions • Multilingual and multiscript: library documents can be described in source -
BNP Paribas PF PSD2 Services
Central and Eastern Europe region: API Developer Portal – PSD2 services BNP Paribas PF PSD2 Services BNP Paribas PF provides the following open-banking APIs: TPP management Authentication service (oAuth 2.0) Balance check for card-issuing providers (CIS) Account information service (AIS) Payment initiation service (PIS) Standing orders service For SandBox setup and testing, we do recommend to download to use Swagger 2.0 TPP Management TPP Management API can be used for registration of TPP to the Bank. swagger: '2.0' info: title: TPP Management API description: API for managing Third Party Payment Providers version: 1.7.0 host: api.hellobank.cz schemes: - https produces: - application/json basePath: /tpp-management/api/v1 paths: /tpps: post: summary: TPP Registration description: | The TPP Registration Endpoint. consumes: - application/json parameters: - $ref: '#/parameters/x-api-header' - $ref: '#/parameters/x-user-agent-info' - in: body name: profile BNP Paribas PF CEE region – API Documentation required: true schema: $ref: '#/definitions/TPPRegistrationRequest' tags: - tpps responses: '201': description: Created schema: $ref: '#/definitions/RegistrationResponse' '400': description: >- Invalid request. A mandatory field is missing in the request, or it is in an unsuitable / invalid format. schema: $ref: '#/definitions/Errors' '401': description: The client is not unauthorized to execute the request. schema: $ref: '#/definitions/Errors' '403': description: Insufficient authorization to use the required scope. schema: $ref: '#/definitions/Errors' '500': description: Server error. schema: $ref: '#/definitions/Errors' definitions: TPPRegistrationRequest: type: object required: - redirect_uris - scopes properties: applicationType: type: string description: >- Type of application which uses this account (web or native). Will not be used for CZ. This field will be ignored if comming on the request. -
Using the OCLC Worldcat Apis
FEATURE FEATURE Using the OCLC WorldCat APIs by by Mark A. Matienzo Mashups combine information from several web services into a single web user experience — but what do they look like in practice? Here are the gritty details of connecting an industry leading online catalog with Google maps, and how Python made it easy. ike other communities, the library world has begun providing APIs to allow developers to reuse REQUIREMENTS Ldata in various ways. OCLC, the world’s largest library consortium, provides several APIs for develop- PYTHON: 2.4 - 2.7 ers, including APIs to search and retrieve bibliographic records and data about their participating institutions. Useful/Related Links: This article describes the available APIs provided by WorldCat Facts and Statistics - http://www.oclc.org/ OCLC and a sample application to map library holdings us/en/worldcat/statistics/default.htm on a Google Map using worldcat, a Python module “Extending the OCLC cooperative” - http://web. Licensed to 53763 - Mark Matienzo ([email protected]) written to work with these APIs. archive.org/web/20010615111317/www.oclc.org/strategy/ strategy_document.pdf OCLC Office of Research - http://www.oclc.org/re- About OCLC, WorldCat, and WorldCat.org search/projects/frbr/algorithm.htm The Online Computer Library Center, Inc. (OCLC), is Requesting a WorldCat API key - an international, non-profit cooperative that pro- http://worldcat.org/devnet/wiki/SearchAPIWhoCanUse vides a variety of services to libraries, archives and SIMILE Exhibit API - http://simile-widgets.org/exhibit/ museums, and engages in research and programmatic Babel for SIMILE - http://simile.mit.edu/wiki/Babel work for them. -
J-ISIS Reference Manual
21 June 2014 Author: Jean-Claude Dauphin [email protected] J-ISIS Reference Manual The latest J-ISIS Distribution zip file can be downloaded from: http://kenai.com/projects/j-isis/downloads (Version 1.3) 21/06/2014 J-ISIS Reference Manual – 21 June 2014 Page 1 Other documents providing details on specific J-ISIS features: Data Entry with Pick Lists, Validation Rules. BLOB Images. Plus Digital Data Entry Documentation Library documents. How to transfer a WinISIS Step-by-Step Instructions for moving a WinISIS or DOS CDS/ISIS Database database to J- ISIS to J-ISIS J-ISIS Network Client Server This document explains how to use J-ISIS in a network. This document explains how to install and customize J-ISIS on Mac OS X J-ISIS Intallation On Mac OSX Mountain Lion This document explains how J-ISIS is related to Web technologies and how to J-ISIS and Web Technologies use J-ISIS formats (CDS/ISIS formatting language) for creating HTML/XHTML display formats that contain hypertext. Pick Lists Validation Pick Lists For Data Entry and Data Validation Documentation Retrieving MARC Format Step by Step Instructions for Retrieving MARC Format Bibliographic Bibliographic Records from Records from Z39.50 Servers using J-ISIS Z39.50 client and Importing them Z39.50 Servers using J-ISIS Z to J-ISIS 39.50 client Step by Step Instructions for As an example, the public domain Gutenberg MARC format bibliographic Importing MARC Format records are imported to J-ISIS and it is shown how to update a record for Bibliographic Records to J-ISIS displaying html hyperlink to the original document. -
Nextgenpsd2 Framework
Joint Initiative on a PSD2 Compliant XS2A Interface NextGenPSD2 XS2A Framework Implementation Guidelines Version 1.3.8 30 October 2020 License Notice This Specification has been prepared by the Participants of the Joint Initiative pan-European PSD2-Interface Interoperability* (hereafter: Joint Initiative). This Specification is published by the Berlin Group under the following license conditions: "Creative Commons Attribution-NoDerivatives 4.0 International Public License" This means that the Specification can be copied and redistributed in any medium or format for any purpose, even commercially, and when shared, that appropriate credit must be given, a link to the license must be provided, and indicated if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. In addition, if you remix, transform, or build upon the Specification, you may not distribute the modified Specification. Implementation of certain elements of this Specification may require licenses under third party intellectual property rights, including without limitation, patent rights. The Berlin Group or any contributor to the Specification is not, and shall not be held responsible in any manner for identifying or failing to identify any or all such third party intellectual property rights. The Specification, including technical data, may be subject to export or import regulations in different countries. Any user of the Specification agrees to comply strictly with all such regulations and acknowledges that it has the responsibility to obtain licenses to export, re-export, or import (parts of) the Specification. * The ‘Joint Initiative pan-European PSD2-Interface Interoperability’ brings together participants of the Berlin Group with additional European banks (ASPSPs), banking associations, payment associations, payment schemes and interbank processors. -
Message Definition Report Document
Standards E-invoice Electronic Presentment and Presentment Service Standards MX Message Definition Report Document For public consultation and review This document provides details of the messages for E-invoice Electronic Presentment and Presentment Service. 14 June 2019 Message Definition Report Document Table of Contents For public consultation and review E-invoice Electronic Presentment and Presentment Service for Standards MX Table of Contents 1 Message Set Overview ...................................................................................................................................... 3 1.1 List of MessageDefinitions ........................................................................................................................... 3 2 MX DRAFT3reda.066.001.01 EIPPCreditorEnrolmentRequestV01 ................................................ 4 2.1 MessageDefinition Functionality .................................................................................................................. 4 2.2 Structure .......................................................................................................................................................... 5 2.3 Constraints ...................................................................................................................................................... 6 2.4 Message Building Blocks .............................................................................................................................. 7 3 MX DRAFT3reda.070.001.01 EIPPDebtorActivationRequestV01