From f61f80b5454a8fcab90c1684826dde649c604fa3 Mon Sep 17 00:00:00 2001 From: Keith Hazelton Date: Wed, 13 May 2020 12:08:53 -0500 Subject: [PATCH] Update README.adoc --- README.adoc | 57 ++++++++++++++++++++++++++--------------------------- 1 file changed, 28 insertions(+), 29 deletions(-) diff --git a/README.adoc b/README.adoc index bcc9689..94d59e0 100644 --- a/README.adoc +++ b/README.adoc @@ -24,39 +24,13 @@ Challenge: Express the link:https://docs.evolveum.com/midpoint/midprivacy/phases * json-ld provides the ability to declare and use multiple namespaces. -[NOTE] -==== -link:https://github.com/schemaorg/schemaorg[Schema.org] uses Web standards such as JSON-LD, Microdata and RDFa to allow for independent extension (for example, see GS1's vocabulary) -==== * See if the rest of the Axiom specification can be expressed in JSON-LD (which is itself valid JSON) -* See if the shortcomings of other schema languages can be overcome with this approach - -. - -- - - - -==== The Axiom Schema Language - -“Axiom is a [proposed] data modeling language used to model data and metadata for Prism and the midPrivacy project, with the intention to replace XSD as the go-to modeling language for Prism.” - -link:https://docs.evolveum.com/midpoint/midprivacy/phases/01-data-provenance-prototype/axiom-notes/[Axiom Design Notes] - -link:https://docs.evolveum.com/midpoint/midprivacy/phases/01-data-provenance-prototype/axiom/[Axiom Draft V0.1] - -link:https://docs.evolveum.com/midpoint/midprivacy/phases/01-data-provenance-prototype/existing-languages-analysis/[Existing Schema Language Analysis] +* See if the identified shortcomings of other schema languages can be overcome with this approach -ConnID 2.0 Notes <= Toward a next generation connector framework - -Midpoint user list as a place to start - -Evolveum team is prototyping Axiom use in the mP UI +* Midpoint user list as a place to start the discussion once this document is shareable -Background: Connid-dev Google Groups posts re ConnID 2.0 - -https://docs.evolveum.com/midpoint/midprivacy/
 <= midPrivacy Project: Develop open source privacy-enhancing identity management solution on top of midPoint. - -https://docs.evolveum.com/midpoint/midprivacy/phases/01-data-provenance-prototype/ <= Data Provenance Prototype: First work package in midPrivacy Project: To improve transparency and accountability of personal data processing. +. JSON-LD Example: ``` @@ -83,3 +57,28 @@ JSON-LD Example: ``` - - - + + +- - - + +==== The Axiom Schema Language + +“Axiom is a [proposed] data modeling language used to model data and metadata for Prism and the midPrivacy project, with the intention to replace XSD as the go-to modeling language for Prism.” + +link:https://docs.evolveum.com/midpoint/midprivacy/phases/01-data-provenance-prototype/axiom-notes/[Axiom Design Notes] + +link:https://docs.evolveum.com/midpoint/midprivacy/phases/01-data-provenance-prototype/axiom/[Axiom Draft V0.1] + +link:https://docs.evolveum.com/midpoint/midprivacy/phases/01-data-provenance-prototype/existing-languages-analysis/[Existing Schema Language Analysis] + +ConnID 2.0 Notes <= Toward a next generation connector framework + +Evolveum team is prototyping Axiom use in the mP UI + +Background: Connid-dev Google Groups posts re ConnID 2.0 + +https://docs.evolveum.com/midpoint/midprivacy/
 <= midPrivacy Project: Develop open source privacy-enhancing identity management solution on top of midPoint. + +https://docs.evolveum.com/midpoint/midprivacy/phases/01-data-provenance-prototype/ <= Data Provenance Prototype: First work package in midPrivacy Project: To improve transparency and accountability of personal data processing. + +- - -