This HTML5 document contains 16 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

PrefixNamespace IRI
n5http://www.openlinksw.com/ontology/acl#
dctermshttp://purl.org/dc/terms/
n4http://www.openlinksw.com/ontology/webservices#
n2urn:virtuoso:val:scopes:sponger:
n6http://www.w3.org/2007/05/powder-s#
rdfshttp://www.w3.org/2000/01/rdf-schema#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n7http://www.w3.org/ns/auth/
xsdhhttp://www.w3.org/2001/XMLSchema#
Subject Item
n2:describe
rdf:type
n4:WebService n5:Scope
rdfs:label
Sponger /describe endpoint scope Faceted Browsing based Entity Description Service ACL Scope
rdfs:comment
This class of service is endowed with properties that enable it to be constrained by fine-grained access controls (ACLs) that cover identity-scoped privileges such as: read, sponger middleware service controlled write, and general write. By default all identity principals (users) are granted read access and sponger controlled write . Sponger ACL scope which contains all ACL rules granting access to the /describe service. The scope includes two access modes: sponge and read. Read access allows use of the /describe service to view Linked Data descriptions of resources. Sponge access allows use of the Sponger via the /describe service to generate the Linked Data descriptions. By default all users have full use of the service.
n6:describedBy
n7:acl
n4:endpointURLString
http://{cname}/describe/
n4:uriTemplate
/describe/?uri={entity-uri}&sponger:get=add /describe/?uri={entity-uri} /describe/?uri={entity-uri}&sponger:get=replace
n5:hasApplicableAccess
n5:Sponge n5:Read
n5:hasDefaultAccess
n5:Sponge n5:Read
dcterms:description
Entity description page that enables flexible exploration of an entity description via navigation over different entity relationship types [a/k/a deep follow-your-nose exploration]. The sophisticated interface provided by this service exposes instances of classes [or entity types]. It also provides the ability to perform inference and reasoning based on the semantics of different entity relationship types [relations].