Skip to content
Go to file
Cannot retrieve contributors at this time
34 lines (31 sloc) 1.97 KB
@prefix : <> .
@prefix ldr: <> .
@prefix skos: <> .
@prefix rdf: <> .
@prefix rdfs: <> .
@prefix owl: <> .
@prefix xsd: <> .
@prefix dcterms: <> .
@prefix foaf: <> .
@prefix dbr: <> .
@prefix dbo: <> .
<> a foaf:Person, ldr:User ;
foaf:firstName "Admin" ;
foaf:lastName "User" ;
foaf:organization <>;
foaf:mbox <> ;
foaf:homepage <> ;
foaf:accountName "admin" ;
foaf:member ldr:NormalUser ;
#password: demo1234
ldr:password "sha1$8b1159fb$1$c933edf77baaa6f6b7558b6b80178bfcb5a6c917";
ldr:isActive "1"^^xsd:Integer;
#this should be set only for the admin user who has access to all features
ldr:isSuperUser "1"^^xsd:Integer .
#non-super users will have the following access level properties:
#ldr:editorOf-> blank node ldr:dataset
# ldr:resource
# ldr:property
# ldr:scope
#authorization starts from dataset level and finishes at property level. i.e. if you give user permission to edit a dataset, by default all resources and all property of the resources can be edited. If you restrict user permission to resource level, by default all the properties of the resource can be edited. If you restrict user permission to property level, you can also specify the dataset/resource under which the property can be edited.
#caveat: superUser has access to all graphs, resources and properties!
You can’t perform that action at this time.