. "TODO" . "Sebastian Hellmann" . "We built this ontology by looking at log4j version 1.2 and version 2 beta: http://logging.apache.org/log4j/2.x/manual/layouts.html, http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html \n\tIs this complete? No! But it will be sufficient for most use cases, please feel free to extend and adapt the ontology, if you need more. \n Loglevels: TRACE, DEBUG, INFO, WARN, ERROR and FATAL\n \n Feedback\n\tIf you'd like to leave feedback, please open an issue on GitHub (https://github.com/NLP2RDF/ontologies/issues) and read the README (https://github.com/NLP2RDF/ontologies#readme) or write an email to the mailing list: http://lists.informatik.uni-leipzig.de/mailman/listinfo/nlp2rdf\n\n\tVersioning process is explained here: http://persistence.uni-leipzig.org/nlp2rdf/specification/version.html\n \n Changelog:\n * 1.0.0 initial version\n * 1.0.1 added Error Code class and errcode property\n * 1.1.0 change Error Code class to Status Code\n "@en . "AKSW, University Leipzig" . "This ontology is licensed under Apache 2.0 (http://www.apache.org/licenses/LICENSE-2.0) and CC-BY (http://creativecommons.org/licenses/by/3.0/)"@en . . . "RLOG - an RDF Logging Ontology"@en . . "rlog" . "http://persistence.uni-leipzig.org/nlp2rdf/ontologies/rlog#" . "This is a helper ontology for NIF 2.0 to be able to log errors and warning messages."@en . "RLOG - an RDF Logging Ontology"@en . . "1.1.0" . . "0"^^ . . "The ALL has the lowest possible rank and is intended to turn on all logging."@en . "ALL"@en . . "2"^^ . . "The DEBUG Level designates fine-grained informational events that are most useful to debug an application."@en . "DEBUG"@en . . "5"^^ . . "The ERROR level designates error events that might still allow the application to continue running."@en . "ERROR"@en . . "An entry in a log."@en . "Log Entry"@en . . "6"^^ . . "The FATAL level designates very severe error events that will presumably lead the application to abort."@en . "FATAL"@en . . "3"^^ . . "The INFO level designates informational messages that highlight the progress of the application at coarse-grained level."@en . "INFO"@en . . "look here: http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html "@en . "Log Level"@en . . "7"^^ . . "The OFF has the highest possible rank and is intended to turn off logging."@en . "OFF"@en . . "A status code which can occur in an application. Instances of this class must put the name of the status as rdfs:label and describe it with rdfs:comment."@en . "Status Code"@en . . "1"^^ . . "The TRACE Level designates finer-grained informational events than the DEBUG."@en . "TRACE"@en . . "4"^^ . . "The WARN level designates potentially harmful situations."@en . "WARN"@en . . "Outputs the fully qualified class name of the caller issuing the logging request."@en . . "class name"@en . . "The numerical value of the code, e.g. 200, 404 or 42."@en . . "code id"@en . . . "Logging datetime (or just date)"@en . . . "Links a log message to a status code."@en . . "has code"@en . . . . "logLevel"@en . . . . "Logging message"@en . . "org.nlp2rdf.core.SPARQLValidator" . "2013-06-08T17:00:00Z"^^ . . "Example log message, put whatever you want."@en . . . "Attention: the ids here can change, they are just used to define an order over the levels!"@en . . "logLevel"@en . . . "If we mix normal and log output, this can be used to refer to the resource in the RDF the error is connected to. "@en . . "an associated resource"@en .