Deprecated. This material represents early efforts and may be of interest to historians. It doe not describe current VIVO efforts.
...
You would need to remove this triple in order for the more restrictive triple to take effect.
VIVO uses the same permissions model to restrict Linked Open Data that it uses to restrict displays or updates. So if you are logged in to VIVO as the root user, and you request Linked Open Data, no restrictions would be applied.
This is consistent with VIVO's authorization model.
An external application could take advantage of this fact to obtain full RDF about individuals. Since there is no authorization parameter on the Linked Open Data request, the client application would need to begin by logging in to VIVO as an administrator, and then retain the session cookie to submit with subsequent requests.
If you ask for Linked Open Data for a non-existent individual, regardless of the form you use, VIVO will return a response code of 404 not found
.
...