public read flag for annotations

[olof.olsson@snd.gu.se]

If the user wants public read for all annotations (for users in the database) this will be marked in the posted annotation.

For example if the user wants all annotations to be readable this could be sent as an optional emement "publicPermission":

<permissions>
	<userWithPermission ref="...">
		<permission>writer</permission>
	</userWithPermission>
 	<publicPermission>
		<permission>read</permission>
	</publicPermission>
</permissions>

The annotation client will have this as a setting.

[olof.olsson@snd.gu.se]

public:
-none <-default
-read
-write

publicAccess ENUM('none', 'read', 'write') DEFAULT 'none'

This will result in no public access:

<permissions>
	<userWithPermission ref="...user1">
		<permission>writer</permission>
	</userWithPermission>
	<userWithPermission ref="...user2">
		<permission>read</permission>
	</userWithPermission>
</permissions>

This will result in public read access:

<permissions public="read">
	<userWithPermission ref="...user1">
		<permission>writer</permission>
	</userWithPermission>
	<userWithPermission ref="...user2">
		<permission>read</permission>
	</userWithPermission>
</permissions>

[olof.olsson@snd.gu.se]

This will be the new way of defining permissions:

<permissionList public="read">
  <permission principalRef="https://...user1ref" level="write" />
  <permission principalRef="https://...user2ref" level="write" />
</permissionList>

No public access:

<permissionList>
  <permission principalRef="https://...user1ref" level="write" />
  <permission principalRef="https://...user2ref" level="write" />
</permissionList>

OR:

<permissionList public="none">
  <permission principalRef="https://...user1ref" level="write" />
  <permission principalRef="https://...user2ref" level="write" />
</permissionList>

[Sander Maijers]

The project has ended.