Update README.md
Browse files
README.md
CHANGED
|
@@ -6,5 +6,23 @@ colorTo: gray
|
|
| 6 |
sdk: static
|
| 7 |
pinned: false
|
| 8 |
---
|
|
|
|
|
|
|
| 9 |
|
| 10 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 6 |
sdk: static
|
| 7 |
pinned: false
|
| 8 |
---
|
| 9 |
+
### What is PIISA?
|
| 10 |
+
We are Canadian Non-Profit that spawend from the BigScience Piracy Working Group. PIISA stands for a Personally Identifiable Information Standard Architecture. This open source and interoperableframework creates a standard designed to allow seamless interoperability between various PII processing frameworks.
|
| 11 |
|
| 12 |
+
### Rationale
|
| 13 |
+
Our mission statement stems from these facts:
|
| 14 |
+
|
| 15 |
+
Proper PII management is hard, and has many facets.
|
| 16 |
+
|
| 17 |
+
There are solutions available for PII processing, both open source and commercial
|
| 18 |
+
|
| 19 |
+
We might want to combine several solutions to achieve better results, or to adapt to specific use cases
|
| 20 |
+
|
| 21 |
+
However there is no practical way of achieving such combination, or of customizing solutions
|
| 22 |
+
|
| 23 |
+
Our approach has been let's define an architecture that decomposes the PII problem into blocks, and let's define interfaces between those blocks
|
| 24 |
+
|
| 25 |
+
Therefore the PIISA specification, and its reference implementation, tries to follow the approach of independent components that pass data between them to compose a full solution
|
| 26 |
+
|
| 27 |
+
### Join Us
|
| 28 |
+
Reach out to us by opening the 'community' link above and sending us a message.
|