Create Signature.md. (#50)

* - Updated version to 8.6.3
- Create Encryption document in Markdown format
- Added new Encryption document to SUMMARY.md for publishing.

* - Included package-lock.json

* - Converted the following documents in Markdown. format;
	- JSON Binding Rules,
	- Generic Transaction Patterns.
- Created the following sequence diagrams required in the documents;
	- figure63a.plantuml,
	- figure64a.plantuml,
	- figure65a.plantuml,
	- figure66a.plantuml.
- Updated the following sequence diagrams;
	- figure63.plantuml,
	- figure64.plantuml,
	- figure65.plantuml,
	- figure66.plantuml.
increase version to 8.8.1

* Format updates to accommodate auto numbering and Gitbooks display format.
Version too 8.8.1.

* Example on lifeline deactivation and activation (PayerFSP -> PayerFSP).

* Updated as per feedback received for issue #10.
• Fixed - 5.1.6.9 ATM-Initiated Cash-Out** <-- two stars (*) after section name
• Fixed - two delays added in Figure 34, between "Payer fee is 1 USD in Payer FSP  for ATM Cash-Out, total fee 2 USD" and "OTP is pre-generated", and similarly between "Validate OTP sent by Payee FSP, OTP OK" and "Reserve 102 USD from Payer account, 101 USD to Switch account, 1 USD to fee account". There should not be any delays. This seems to be present in other figures as well (for example Figure 36, 46, 51, 52, 66).
• Fixed - Some extra whitespace in at least Figure 34 and 36 in "PUT /transfers/" between the "PUT /transfers/" and "".
• Fixed - Misspelling in Figure 36, "Generated OTP, "12345"" should be "Generate OTP, "12345""
• Fixed - Listing 12 is strange with double * instead of bold.
• Fixed - 6.3.4.1, "Alternative URI: PUT /parties/{Type}/{ID}/{SubId}/error**" <-- double *
• Fixed - 7.2.3.1 Regular Expression** <-- double **
• Fixed - 7.2.4.1 Regular Expression** <-- double **
• Fixed - 7.2.5.1 Regular Expression** <-- double **

* Tiding up of sequence diagrams.

* Create "figure1_http_timeout" and "figure2_callback_timeout" sequence diagrams.
Create "Scheme Rules" in markdown.
Updated SUMMARY.md with new document for rendering in GitBooks.
Updated README.md file to reference to markdown documents.
Removed duplicated section in README.md
Updated version to 9.1.1.

* Added link to internal document reference.

* Updated Contributors.

* Created "Signature.md" document.
Updated "SUMMARY.md" to include "Signature.md" document.
Updated "Generic Transaction Patterns.md" and "JSON Binding Rules.md" to have the same look and feel as the other documents.
Corrected invalid index reference on "Scheme Rules.md".
Updated "README.md" to refer to "Signature.md".
Version 9.2.0.

* Changed the document version dates to "2018-03-13" as suggested.
Created "Use Cases.md" in markdown format
Update reference in "README.md" to point to "Use Cases.md"
Included "Use Cases.md" in SUMMARY.md.

Co-authored-by: Sam <[email protected]>

Author: HenkKodde

README.md

@@ -34,7 +34,7 @@ Information is shared in accordance with **Creative Commons Licensing**.
 [This document](https://github.com/mojaloop/mojaloop-specification/blob/master/documents/Generic%20Transaction%20Patterns.md) specifies the logical data model used by the API. Section 2 in the document lists elements used by each service. Section 3 in the document describes the data model in terms of basic elements, simple data types and complex data types.
 
 ## Use Cases
-The purpose of [this document](https://github.com/mojaloop/mojaloop-specification/blob/master/documents/supporting-documentation/Use%20Cases.pdf) is to define a set of use cases that can be implemented using the API. The use cases referenced within this document provide an overview of transaction processing flows and business rules of each transaction step as well as relevant error conditions. The primary purpose of the API is to support the movement of financial transactions between one Financial Services Provider (FSP) and another.
+The purpose of [this document](https://github.com/mojaloop/mojaloop-specification/blob/master/documents/Use%20Cases.md) is to define a set of use cases that can be implemented using the API. The use cases referenced within this document provide an overview of transaction processing flows and business rules of each transaction step as well as relevant error conditions. The primary purpose of the API is to support the movement of financial transactions between one Financial Services Provider (FSP) and another.
 
 It should be noted that the API is only responsible for message exchange between FSPs and a Switch when a cross-FSP transaction is initiated by an End User in one of the FSPs. This can occur in either of two scenarios: 
 - A bilateral scenario in which FSPs communicate with each other
@@ -84,7 +84,7 @@ The API should be implemented in an environment that consists of either:
 For more information about the environment, see Chapter 3, Network Topology. Chapters 4 and 5 identify management strategies for the CA and for the platform. Communication between platforms is performed using a REST (REpresentational State Transfer)-based HTTP protocol (for more information, see API Definition). Because this protocol does not provide a means for ensuring either integrity or confidentiality between platforms, extra security layers must be added to protect sensitive information from alteration or exposure to unauthorized parties.
 
 ## Signature
-[This document](https://github.com/mojaloop/mojaloop-specification/blob/master/documents/supporting-documentation/Signature.pdf) details security methods to be implemented for **the API** to ensure confidentiality of API messages between an API client and the API server.
+[This document](https://github.com/mojaloop/mojaloop-specification/blob/master/documents/Signature.md) details security methods to be implemented for **the API** to ensure confidentiality of API messages between an API client and the API server.
 
 In information security, confidentiality means that information is not made available or disclosed to unauthorized individuals, entities, or processes (Excerpt [ISO27000](http://www.27000.org/ ) ). For the API, confidentiality means that some sensitive fields in the payload of an API message cannot be accessed or identified in an unauthorized or undetected manner by the intermediaries involved in the API communication. That is, if some fields of an API message are encrypted by the API client, then only the expected API recipient can decrypt those fields.
 

SUMMARY.md

@@ -4,10 +4,13 @@
 * [Mojaloop Specifications Overview](README.md)
   * [Glossary](documents/Glossary.md)
   * [Generic Transaction Patterns](documents/Generic Transaction Patterns.md)
+  * [Use Cases](documents/Use Cases.md)
   * [API Definition v1.0](documents/API Definition v1.0.md)
   * [Scheme Rules](documents/Scheme Rules.md)
   * [JSON Binding Rules](documents/JSON Binding Rules.md)
+  * [Scheme Rules](documents/Scheme Rules.md)
   * [PKI Best Practices](documents/PKI Best Practices.md)
+  * [Signature](documents/Signature.md)
   * [Encryption](documents/Encryption.md)
 ### Change Control Board
 * [Change Control Board Overview](ccb-meetings/README.md)

documents/Encryption.md

@@ -53,7 +53,7 @@ The following conventions are used in this document to identify the specified ty
 
 | **Version** | **Date** | **Change Description** |
 | :--- | :--- | :--- |
-| **1.0** | 2019-02-22 | Initial version |
+| **1.0** | 2018-03-13 | Initial version |
 
 # 2. Introduction
 

documents/Generic Transaction Patterns.md

@@ -1,52 +1,52 @@
 # Generic Transaction Patterns
 
-## Open API for FSP Interoperability Specification
+## _Open API for FSP Interoperability Specification_
 
 **Table of Contents**
 
-[1. Preface](#1-preface)
+1. [Preface](#1-preface)
 
-[1.1 Conventions Used in This Document](#11-conventions-used-in-this-document)
+   1.1 [Conventions Used in This Document](#11-conventions-used-in-this-document)
 
-[1.2 Document Version Information](#12-document-version-information)
+   1.2 [Document Version Information](#12-document-version-information)
 
-[2. Introduction](#2-introduction)
+2. [Introduction](#2-introduction)
 
-[2.1 Open API for FSP Interoperability Specification](#21-open-api-for-fsp-interoperability-specification)
+   2.1 [Open API for FSP Interoperability Specification](#21-open-api-for-fsp-interoperability-specification)
 
-[3. Logical API Services](#3-logical-api-services)
+3. [Logical API Services](#3-logical-api-services)
 
-[3.1 Common Functionality](#31-common-functionality)
+   3.1 [Common Functionality](#31-common-functionality)
 
-[3.2 API Resource Participants](#32-api-resource-participants)
+   3.2 [API Resource Participants](#32-api-resource-participants)
 
-[3.3 API Resource Parties](#33-api-resource-parties)
+   3.3 [API Resource Parties](#33-api-resource-parties)
 
-[3.4 API Resource Transaction Requests](#34-api-resource-transaction-requests)
+   3.4 [API Resource Transaction Requests](#34-api-resource-transaction-requests)
 
-[3.5 API Resource Quotes](#35-api-resource-quotes)
+   3.5 [API Resource Quotes](#35-api-resource-quotes)
 
-[3.6 API Resource Authorizations](#36-api-resource-authorizations)
+   3.6 [API Resource Authorizations](#36-api-resource-authorizations)
 
-[3.7 API Resource Transfers](#37-api-resource-transfers)
+   3.7 [API Resource Transfers](#37-api-resource-transfers)
 
-[3.8 API Resource Transactions](#38-api-resource-transactions)
+   3.8 [API Resource Transactions](#38-api-resource-transactions)
 
-[3.9 API Resource Bulk Quotes](#39-api-resource-bulk-quotes)
+   3.9 [API Resource Bulk Quotes](#39-api-resource-bulk-quotes)
 
-[3.10 API Resource Bulk Transfers](#310-api-resource-bulk-transfers)
+   3.10 [API Resource Bulk Transfers](#310-api-resource-bulk-transfers)
 
-[4. Generic Transaction Patterns](#4-generic-transaction-patterns)
+4. [Generic Transaction Patterns](#4-generic-transaction-patterns)
 
-[4.1 Payer-Initiated Transaction](#41-payer-initiated-transaction)
+   4.1 [Payer-Initiated Transaction](#41-payer-initiated-transaction)
 
-[4.2 Payee-Initiated Transaction](#42-payee-initiated-transaction)
+   4.2 [Payee-Initiated Transaction](#42-payee-initiated-transaction)
 
-[4.3 Payee-Initiated Transaction using OTP](#43-payee-initiated-transaction-using-otp)
+   4.3 [Payee-Initiated Transaction using OTP](#43-payee-initiated-transaction-using-otp)
 
-[4.4 Bulk Transactions](#44-bulk-transactions)
+   4.4 [Bulk Transactions](#44-bulk-transactions)
 
-[5. References](#5-references)
+5. [References](#5-references)
 
 **Table of Figures**
 
@@ -77,7 +77,7 @@ The following conventions are used in this document to identify the specified ty
 
 |Version|Date|Change Description|
 |---|---|---|
-|**1.0**|2019-03-12|Initial version|
+|**1.0**|2018-03-13|Initial version|
 
 ## 2. Introduction
 

documents/Glossary.md

@@ -35,7 +35,7 @@ The following conventions are used in this document to identify the specified ty
 
 | **Version** | **Date** | **Change Description** |
 | :--- | :--- | :--- |
-| **1.0** | 2019-03-05 | Initial version |
+| **1.0** | 2018-03-13 | Initial version |
 
 # 2. Introduction
 

documents/JSON Binding Rules.md

@@ -1,78 +1,77 @@
 ---
 showToc: true
 ---
-
 # JSON Binding Rules
 
-## Open API for FSP Interoperability Specification
+## _Open API for FSP Interoperability Specification_
 
 **Table of Contents**
 
-[1. Preface](#1-preface)
+1. [Preface](#1-preface)
 
-[1.1 Conventions Used in This Document](#11-conventions-used-in-this-document)
+   1.1 [Conventions Used in This Document](#11-conventions-used-in-this-document)
 
-[1.2 Document Version Information](#12-document-version-information)
+   1.2 [Document Version Information](#12-document-version-information)
 
-[2. Introduction](#2-introduction)
+2. [Introduction](#2-introduction)
 
-[2.1 Open API for FSP Interoperability Specification](#21-open-api-for-fsp-interoperability-specification)
+   2.1 [Open API for FSP Interoperability Specification](#21-open-api-for-fsp-interoperability-specification)
 
-[3. Keywords and Usage](#3-keywords-and-usage)
+3. [Keywords and Usage](#3-keywords-and-usage)
 
-[3.1 Validation Keywords](#31-validation-keywords)
+   3.1 [Validation Keywords](#31-validation-keywords)
 
-[3.2 Metadata Keywords](#32-metadata-keywords)
+   3.2 [Metadata Keywords](#32-metadata-keywords)
 
-[3.3 Instance and \$ref](#33-instance-and-$ref)
+   3.3 [Instance and \$ref](#33-instance-and-$ref)
 
-[3.4 JSON Definitions and Examples](#34-json-definitions-and-examples)
+   3.4 [JSON Definitions and Examples](#34-json-definitions-and-examples)
 
-[4. Element and Basic Data Types](#4-element-and-basic-data-types)
+4. [Element and Basic Data Types](#4-element-and-basic-data-types)
 
-[4.1 Data Type Amount](#41-data-type-amount)
+   4.1 [Data Type Amount](#41-data-type-amount)
 
-[4.2 Data Type BinaryString](#42-data-type-binaryString)
+   4.2 [Data Type BinaryString](#42-data-type-binaryString)
 
-[4.3 Data Type BinaryString32](#43-data-type-binaryString32)
+   4.3 [Data Type BinaryString32](#43-data-type-binaryString32)
 
-[4.4 Data Type BopCode](#44-data-type-bopcode)
+   4.4 [Data Type BopCode](#44-data-type-bopcode)
 
-[4.5 Data Type Enum](#45-data-type-enum)
+   4.5 [Data Type Enum](#45-data-type-enum)
 
-[4.6 Data Type Date](#46-data-type-date)
+   4.6 [Data Type Date](#46-data-type-date)
 
-[4.7 Data Type DateTime](#47-data-type-datetime)
+   4.7 [Data Type DateTime](#47-data-type-datetime)
 
-[4.8 Data Type ErrorCode](#48-data-type-errorcode)
+   4.8 [Data Type ErrorCode](#48-data-type-errorcode)
 
-[4.9 Data Type Integer](#49-data-type-integer)
+   4.9 [Data Type Integer](#49-data-type-integer)
 
-[4.10 Data Type Latitude](#410-data-type-latitude)
+   4.10 [Data Type Latitude](#410-data-type-latitude)
 
-[4.11 Data Type Longitude](#411-data-type-longitude)
+   4.11 [Data Type Longitude](#411-data-type-longitude)
 
-[4.12 Data Type MerchantClassificationCode](#412-data-type-merchantclassificationcode)
+   4.12 [Data Type MerchantClassificationCode](#412-data-type-merchantclassificationcode)
 
-[4.13 Data Type Name](#413-data-type-name)
+   4.13 [Data Type Name](#413-data-type-name)
 
-[4.14 Data Type OtpValue](#414-data-type-otpvalue)
+   4.14 [Data Type OtpValue](#414-data-type-otpvalue)
 
-[4.15 Data Type String](#415-data-type-string)
+   4.15 [Data Type String](#415-data-type-string)
 
-[4.16 Data Type TokenCode](#416-data-type-tokencode)
+   4.16 [Data Type TokenCode](#416-data-type-tokencode)
 
-[4.17 Data Type UndefinedEnum](#417-data-type-undefinedenum)
+   4.17 [Data Type UndefinedEnum](#417-data-type-undefinedenum)
 
-[4.18 Data Type UUID](#418-data-type-uuid)
+   4.18 [Data Type UUID](#418-data-type-uuid)
 
-[5. Complex Type](#5-complex-type)
+5. [Complex Type](#5-complex-type)
 
-[5.1 Complex Type Definition, Transformation](#51-complex-type-definition,-transformation)
+   5.1 [Complex Type Definition, Transformation](#51-complex-type-definition,-transformation)
 
-[5.2 Types of objects in Requests or Responses](#52-types-of-objects-in-requests-or-responses)
+   5.2 [Types of objects in Requests or Responses](#52-types-of-objects-in-requests-or-responses)
 
-[6. References](#6-references)
+6. [References](#6-references)
 
 **Table of Listings**
 
@@ -157,7 +156,7 @@ The following conventions are used in this document to identify the specified ty
 
 |Version|Date|Change Description|
 |---|---|---|
-|**1.0**|2019-03-12|Initial version|
+|**1.0**|2018-03-13|Initial version|
 
 ## 2. Introduction
 

documents/PKI Best Practices.md

@@ -116,7 +116,7 @@ The following conventions are used in this document to identify the specified ty
 
 |Version|Date|Change Description|
 |---|---|---|
-|**1.0**|2019-03-12|Initial version|
+|**1.0**|2018-03-13|Initial version|
 
 ## 2. Introduction
 

documents/Scheme Rules.md

@@ -1,17 +1,17 @@
 ---
 showToc: true
 ---
+# Scheme Rules
 
-#Scheme Rules
-##Open API for FSP Interoperability Specification
+## _Open API for FSP Interoperability Specification_
 
 **Table of Contents**
 
 1. [Preface](#1-preface)
 
     1.1 [Conventions Used in This Document](#11-conventions-used-in-this-document)
 
-    1.2 Document Version Information](#12-document-version-information)
+    1.2 [Document Version Information](#12-document-version-information)
 
 2. [Introduction](#2-introduction)
 
@@ -104,7 +104,7 @@ The following conventions are used in this document to identify the specified ty
 
 |Version|Date|Change Description|
 |---|---|---|
-|**1.0**|2019-03-12|Initial version|
+|**1.0**|2018-03-13|Initial version|
 
 ##2. Introduction