add emojis

README.md

@@ -50,7 +50,7 @@ A user group can have one or more of the following permissions:
 - `ProjectAdminGroupRestrictedPermission`: is allowed to modify group info and group membership on certain groups of the project
 - `ProjectAdminRightsAllPermission`: is allowed to change the permissions on all objects belonging to the project
 
-The example file [project_data/F18E/APs_original.json](project_data/F18E/APs_original.json)
+📑 The example file [project_data/F18E/APs_original.json](project_data/F18E/APs_original.json)
 
 - grants to `knora-admin:ProjectAdmin` the rights to anything on project level, and to create resources of any class.
 - grants to `knora-admin:ProjectMember` the rights to create resources of any class.
@@ -100,7 +100,8 @@ There are **built-in groups** and **project specific groups**:
 ### 3. Permission strings / scopes
 
 **Rights** are mapped to **user groups** using **permission strings** (represented as **scopes** in this repo).
-The example file
+
+📑 The example file
 [project_data/F18E/OAPs_original/resource_XwwqVvWgSmuHRobQubg9uQ.json](project_data/F18E/OAPs_original/resource_XwwqVvWgSmuHRobQubg9uQ.json)
 shows that the resource `http://rdfh.ch/0102/XwwqVvWgSmuHRobQubg9uQ` has the rights
 `CR knora-admin:ProjectAdmin|D knora-admin:Creator|M knora-admin:ProjectMember|RV knora-admin:UnknownUser,knora-admin:KnownUser`.
@@ -116,7 +117,7 @@ DOAPs are always project-related, but more specifically, they are:
     - property-related: some properties are public, while other properties are restricted
     - or a combination of class/property-related
 
-The example file [project_data/F18E/DOAPs_original.json](project_data/F18E/DOAPs_original.json)
+📑 The example file [project_data/F18E/DOAPs_original.json](project_data/F18E/DOAPs_original.json)
 encodes the following information:
 
 - If a `ProjectAdmin` creates a resource, the resource gets the permissions `CR knora-admin:ProjectAdmin|D knora-admin:Creator,knora-admin:ProjectMember|V knora-admin:KnownUser,knora-admin:UnknownUser`.