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

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

Namespace Prefixes

Prefix	IRI
wdrs	http://www.w3.org/2007/05/powder-s#
schema	http://schema.org/
n7	https://www.openlinksw.com/about/id/entity/urn/data:openlink:
n2	http://data.openlinksw.com/oplweb/faq/Virtuoso/AuditTrailAnswer#
n6	https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
rdf	http://www.w3.org/1999/02/22-rdf-syntax-ns#
n5	https://www.openlinksw.com/about/id/entity/urn/webdev:
xsdh	http://www.w3.org/2001/XMLSchema#

Statements

Subject Item

n2:this

wdrs:describedby

n5:virtuoso n6:virtuoso-general-faq-2023.ttl n7:products

schema:name

Answer to question: Does your platform feature an audit trail? If so, what type and level of events are captured? Answer to question: Does your platform feature an audit trail? If so, what type and level of events are captured?

rdf:type

schema:Answer

schema:answerExplanation

For HTTP interactions, you can use an enhanced HTTP log file that includes a User Identity field (i.e., a WebID or NetID, these being the identifiers used for OpenID Connect + OAuth connections). For SQL connections, these can be developed as custom logs that are informed by logging flags. For HTTP interactions, you can use an enhanced HTTP log file that includes a User Identity field (i.e., a WebID or NetID, these being the identifiers used for OpenID Connect + OAuth connections). For SQL connections, these can be developed as custom logs that are informed by logging flags.