odpi/egeria#6907 rename master to main

Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>

demonstrations/repo-to-repo/demo-overview.md

@@ -19,7 +19,7 @@ OMRS is limited at this point in its early release to RDBMS and Business Term ar
 
 ## Demo Scenario
 
-The script describes two persona that are important to GDPR and Data Privacy Management.    An "Asset Owner" and a "Data Privacy Officer".    They will be described  as working at Coco Pharmaceuticals (see other links in the project, such as https://github.com/odpi/data-governance/tree/master/data-privacy-pack and https://github.com/odpi/data-governance/tree/master/docs/coco-pharmaceuticals), where the Data Privacy Officer is responsible for evaluating new systems and application offerings, setting privacy policies, and leading data privacy assessments, and the Asset Owner being someone with responsibility/ownership/management of a new offering for customers/new business, etc. [proposed participants for the demo script will be "Faith" (Data Privacy Officer) and then Erin, Tessa and Jules, as team members with architecture or data steward responsibility surrounding clinical research]. The demo script won't have time to go into deep detail on their roles, but will establish their positions and responsibilities. The Asset Owner is part of a team that is proposing and building, or soon to deploy, a mobile clinical trials application for monitoring drug use.   Before the application can be approved, it must first be reviewed by the Data Privacy team.   How extensive that review is, and whether a detailed Privacy Impact Assessment must be scheduled, is the responsibility of the Data Privacy Officer.  
+The script describes two persona that are important to GDPR and Data Privacy Management.    An "Asset Owner" and a "Data Privacy Officer".    They will be described  as working at Coco Pharmaceuticals (see other links in the project, such as https://github.com/odpi/data-governance/tree/main/data-privacy-pack and https://github.com/odpi/data-governance/tree/main/docs/coco-pharmaceuticals), where the Data Privacy Officer is responsible for evaluating new systems and application offerings, setting privacy policies, and leading data privacy assessments, and the Asset Owner being someone with responsibility/ownership/management of a new offering for customers/new business, etc. [proposed participants for the demo script will be "Faith" (Data Privacy Officer) and then Erin, Tessa and Jules, as team members with architecture or data steward responsibility surrounding clinical research]. The demo script won't have time to go into deep detail on their roles, but will establish their positions and responsibilities. The Asset Owner is part of a team that is proposing and building, or soon to deploy, a mobile clinical trials application for monitoring drug use.   Before the application can be approved, it must first be reviewed by the Data Privacy team.   How extensive that review is, and whether a detailed Privacy Impact Assessment must be scheduled, is the responsibility of the Data Privacy Officer.  
 
 [Note:  depending on the "current" level of metadata sharing support among OMRS Connector implementations, the demo script might start with the creation and sharing of a Business Term, or perhaps the creation and sharing of the metadata for a relational table, but ultimately the goal is to illustrate bi-directional sharing of "new" metadata and then also the "assignment" of terminology to a particular data asset....but the exact "order" of creation/sharing may vary from the script described below based on what amount of functionality is available ---- particularly for an initial demo implementation targeted for Vancouver North America Summit (August, 2018).]
 
@@ -31,4 +31,4 @@ From a technical perspective, the demo illustrates automated and real-time shari
 
 ----
 License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/),
-Copyright Contributors to the ODPi Egeria project.
+Copyright Contributors to the ODPi Egeria project.

docs/coco-pharmaceuticals/personas/faith-broker.md

@@ -3,7 +3,7 @@
 
 # Faith Broker - HR Director and Privacy Officer
 
-<img src="https://raw.githubusercontent.com/odpi/data-governance/master/docs/coco-pharmaceuticals/personas/faith-broker.png" style="float:left">
+<img src="https://raw.githubusercontent.com/odpi/data-governance/main/docs/coco-pharmaceuticals/personas/faith-broker.png" style="float:left">
 
 Age: 35
 

docs/coco-pharmaceuticals/scenarios/building-the-governance-team/README.md

@@ -27,10 +27,10 @@ This makes her a deputy for Jules and recognizes her
 role in ensure data is properly managed by IT.
 
 ODPi Egeria includes a sample client
-([docs](https://github.com/odpi/egeria/blob/master/open-metadata-resources/open-metadata-samples/access-services-samples/governance-program-client-samples/governance-leadership.md), 
-[code](https://github.com/odpi/egeria/blob/master/open-metadata-resources/open-metadata-samples/access-services-samples/governance-program-client-samples/src/main/java/org/odpi/openmetadata/accessservices/governanceprogram/samples/GovernanceLeadershipSample.java))
+([docs](https://github.com/odpi/egeria/blob/main/open-metadata-resources/open-metadata-samples/access-services-samples/governance-program-client-samples/governance-leadership.md), 
+[code](https://github.com/odpi/egeria/blob/main/open-metadata-resources/open-metadata-samples/access-services-samples/governance-program-client-samples/src/main/java/org/odpi/openmetadata/accessservices/governanceprogram/samples/GovernanceLeadershipSample.java))
 that issues the appropriate API calls to set up this team through the
-[Governance Program OMAS](https://github.com/odpi/egeria/blob/master/open-metadata-implementation/access-services/governance-program/README.md) Governance Leadership Interface.
+[Governance Program OMAS](https://github.com/odpi/egeria/blob/main/open-metadata-implementation/access-services/governance-program/README.md) Governance Leadership Interface.
 
 
 ----

docs/common-data-definitions/anatomy-of-a-glossary.md

@@ -120,8 +120,8 @@ is used.
 
 ## Further information
 * [Defining a glossary scenario](../coco-pharmaceuticals/scenarios/defining-a-glossary/README.md)
-* [Open metadata types for a glossary](https://github.com/odpi/egeria/blob/master/open-metadata-publication/website/open-metadata-types/Area-3-models.md)
-* [Subject Area OMAS API for defining and storing information](https://github.com/odpi/egeria/blob/master/open-metadata-implementation/access-services/subject-area/README.md)
+* [Open metadata types for a glossary](https://github.com/odpi/egeria/blob/main/open-metadata-publication/website/open-metadata-types/Area-3-models.md)
+* [Subject Area OMAS API for defining and storing information](https://github.com/odpi/egeria/blob/main/open-metadata-implementation/access-services/subject-area/README.md)
 ----
 License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/),
 Copyright Contributors to the ODPi Egeria project.

work-groups/semantic/meeting-minutes/6th February 2020.md

@@ -18,7 +18,7 @@
 * we introduced ourselves and what we are looking for from this workgroup
 * David is interested in semantic models and wants to share , publicise, improve the subject area omas, see how Egeria can consume model content and how this is visualised for different personals in Egeria .
 * Michal is interested in using Egeria as a way to get the IBM industry models to new audiences by having the IBM industry models in an open format that Egeria can take in. Michal talked of models moving from being ER models to the glossary terms being the primary artifact to encapsulate enterprise knowledge. Logical models and glossaries together give an ontology. He is trying to capture glossaries in an ontological way. He would like to view metadata like a graph db, utilizing schema content. He has experience of attempting to visualize glossary content. We talked about Egeria needing to have the capability to take licensed model content -(David observation - this probably means Egeria stores the license with the model elements and glossary terms).          
-* Michal asked what was a SubjectArea ( by this he meant the Egeria type SubjectArea - which is a classification of a category ). David said he would supply a link to the Coco Pharmaceuticals use case sround subject areas - this is here https://github.com/odpi/data-governance/blob/master/docs/coco-pharmaceuticals/scenarios/defining-subject-areas/README.md
+* Michal asked what was a SubjectArea ( by this he meant the Egeria type SubjectArea - which is a classification of a category ). David said he would supply a link to the Coco Pharmaceuticals use case sround subject areas - this is here https://github.com/odpi/data-governance/blob/main/docs/coco-pharmaceuticals/scenarios/defining-subject-areas/README.md
 * We talked about how Apache Atlas implemented glossary content and how that can be brought into Egeria using a read only connector.
 * David described the subject area OMAS , what is does and how it differs from Apache Atlas.
 * We then discussed 2 UI capabilities relevant to semantics and models. The first is TEX (coded) to explore the Egeria type system and REX (work in progress) an OMRS D3 visualisation to facilitate metadata exploration using a combination of full text search , filters and graph navigation. The REX UI was not for a business user, but was useful for education, demos, diagnostics of a cohort. The 2nd UI capability is to take this UI component and reuse and extend it on top of an OMAS API to expose a persona / business oriented version of this metadata explorer.
@@ -28,4 +28,4 @@
 Due to Michal's availability we will run the next session on Thursday the 20th of February 3PM UK time and weekly after that. If this time is not working for you - let me know and I will try to find a better slot. .
 Michal to present assessment of model formats and propose options that would be useful for Egeria to adopt - so we can discuss and get consensus.    
 
-I am looking at putting these minutes on the data governance website.
+I am looking at putting these minutes on the data governance website.

workshops/may-2020/EgeriaDojoLive-Day1-Chat.txt

@@ -11,7 +11,7 @@
 05/26/2020    12:12:13 PM    from Susan Malaika (IBM) to Everyone:	Yes - Please make sure you are in the slack  Slack https://slack.odpi.org/ Channel #egeria-dojo-live	
 05/26/2020    12:15:36 PM    from Susan Malaika (IBM) to Everyone:	Mandy is showing https://egeria.odpi.org/open-metadata-resources/open-metadata-tutorials/egeria-dojo/	
 05/26/2020    12:18:01 PM    from Susan Malaika (IBM) to Everyone:	Now https://egeria.odpi.org/open-metadata-resources/open-metadata-tutorials/egeria-dojo/egeria-dojo-day-1-1-introduction.html 	
-05/26/2020    12:19:26 PM    from Susan Malaika (IBM) to Everyone:	Slides here https://github.com/odpi/data-governance/blob/master/workshops/may-2020/egeria-dojo-day-1-1-introduction.pptx	
+05/26/2020    12:19:26 PM    from Susan Malaika (IBM) to Everyone:	Slides here https://github.com/odpi/data-governance/blob/main/workshops/may-2020/egeria-dojo-day-1-1-introduction.pptx
 05/26/2020    12:23:53 PM    from Susan Malaika (IBM) to Everyone:	Repasting : Please make sure you are in the slack https://slack.odpi.org/ Channel #egeria-dojo-live	
 05/26/2020    12:26:54 PM    from Ayoub RIHI (External) to Everyone:	We can't see the shared screen	
 05/26/2020    12:28:26 PM    from Susan Malaika (IBM) to Everyone:	@yaoub - can you see the screen now?	
@@ -21,7 +21,7 @@
 05/26/2020    12:30:24 PM    from Ayoub RIHI (External) to Everyone:	Its ok now thank you!	
 05/26/2020    12:33:39 PM    from Susan Malaika (IBM) to Everyone:	Good @ayoub 	
 05/26/2020    12:34:08 PM    from Susan Malaika (IBM) to Everyone:	This is what Mandy is sharing  https://egeria.odpi.org/open-metadata-resources/open-metadata-tutorials/egeria-dojo/	
-05/26/2020    12:34:31 PM    from Susan Malaika (IBM) to Everyone:	Presentation  https://github.com/odpi/data-governance/blob/master/workshops/may-2020/egeria-dojo-day-1-1-introduction.pptx	
+05/26/2020    12:34:31 PM    from Susan Malaika (IBM) to Everyone:	Presentation  https://github.com/odpi/data-governance/blob/main/workshops/may-2020/egeria-dojo-day-1-1-introduction.pptx
 05/26/2020    12:47:45 PM    from Susan Malaika (IBM) to Everyone:	I think we are here now https://egeria.odpi.org/open-metadata-resources/open-metadata-tutorials/egeria-dojo/egeria-dojo-day-1-2-project-introduction.html	
 05/26/2020    12:48:52 PM    from Sagarika Mukesh (IBM) to Everyone:	No metadata	
 05/26/2020    12:48:54 PM    from TRINETTE BROWNHILL (IBM) to Everyone:	metadata - yes