# rdflib.plugins.parsers package

## Submodules

## rdflib.plugins.parsers.RDFVOC module

class rdflib.plugins.parsers.RDFVOC.RDFVOC

  Bases: `RDF`

  Description: URIRef = rdflib.term.URIRef('http://www.w3.org/1999/02/22-rdf-syntax-ns#Description')
  ID: URIRef = rdflib.term.URIRef('http://www.w3.org/1999/02/22-rdf-syntax-ns#ID')
  RDF: URIRef = rdflib.term.URIRef('http://www.w3.org/1999/02/22-rdf-syntax-ns#RDF')
  __annotations__ = {'Alt': 'URIRef', 'Bag': 'URIRef', 'CompoundLiteral': 'URIRef', 'Description': <class 'rdflib.term.URIRef'>, 'HTML': 'URIRef', 'ID': <class 'rdflib.term.URIRef'>, 'JSON': 'URIRef', 'List': 'URIRef', 'PlainLiteral': 'URIRef', 'Property': 'URIRef', 'RDF': <class 'rdflib.term.URIRef'>, 'Seq': 'URIRef', 'Statement': 'URIRef', 'XMLLiteral': 'URIRef', 'about': <class 'rdflib.term.URIRef'>, 'datatype': <class 'rdflib.term.URIRef'>, 'direction': 'URIRef', 'first': 'URIRef', 'langString': 'URIRef', 'language': 'URIRef', 'li': <class 'rdflib.term.URIRef'>, 'nil': 'URIRef', 'nodeID': <class 'rdflib.term.URIRef'>, 'object': 'URIRef', 'parseType': <class 'rdflib.term.URIRef'>, 'predicate': 'URIRef', 'resource': <class 'rdflib.term.URIRef'>, 'rest': 'URIRef', 'subject': 'URIRef', 'type': 'URIRef', 'value': 'URIRef'}
  __module__ = 'rdflib.plugins.parsers.RDFVOC'
  about: URIRef = rdflib.term.URIRef('http://www.w3.org/1999/02/22-rdf-syntax-ns#about')
  datatype: URIRef = rdflib.term.URIRef('http://www.w3.org/1999/02/22-rdf-syntax-ns#datatype')
  li: URIRef = rdflib.term.URIRef('http://www.w3.org/1999/02/22-rdf-syntax-ns#li')
  nodeID: URIRef = rdflib.term.URIRef('http://www.w3.org/1999/02/22-rdf-syntax-ns#nodeID')
  parseType: URIRef = rdflib.term.URIRef('http://www.w3.org/1999/02/22-rdf-syntax-ns#parseType')
  resource: URIRef = rdflib.term.URIRef('http://www.w3.org/1999/02/22-rdf-syntax-ns#resource')

## rdflib.plugins.parsers.hext module

This is a rdflib plugin for parsing Hextuple files, which are Newline-Delimited JSON (ndjson) files, into Conjunctive. The store that backs the graph must be able to handle contexts, i.e. multiple graphs.

class rdflib.plugins.parsers.hext.HextuplesParser

  Bases: `Parser`

  An RDFLib parser for Hextuples

  __annotations__ = {}
  __dict__ = mappingproxy({'__module__': 'rdflib.plugins.parsers.hext', '__doc__': '\n An RDFLib parser for Hextuples\n\n ', '__init__': <function HextuplesParser.__init__>, '_load_json_line': <function HextuplesParser._load_json_line>, '_parse_hextuple': <function HextuplesParser._parse_hextuple>, 'parse': <function HextuplesParser.parse>, '__dict__': <attribute '__dict__' of 'HextuplesParser' objects>, '__weakref__': <attribute '__weakref__' of 'HextuplesParser' objects>, '__annotations__': {}})
  __init__()
  __module__ = 'rdflib.plugins.parsers.hext'
  __weakref__

    list of weak references to the object

  parse(source, graph, **kwargs)

## rdflib.plugins.parsers.jsonld module

This parser will interpret a JSON-LD document as an RDF Graph. See:

> http://json-ld.org/

Example usage:

    >>> from rdflib import Graph, URIRef, Literal
    >>> test_json = '''
    ... {
    ...     "@context": {
    ...         "dc": "http://purl.org/dc/terms/",
    ...         "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    ...         "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
    ...     },
    ...     "@id": "http://example.org/about",
    ...     "dc:title": {
    ...         "@language": "en",
    ...         "@value": "Someone's Homepage"
    ...     }
    ... }
    ... '''
    >>> g = Graph().parse(data=test_json, format='json-ld')
    >>> list(g) == [(URIRef('http://example.org/about'),
    ...     URIRef('http://purl.org/dc/terms/title'),
    ...     Literal("Someone's Homepage", lang='en'))]
    True

class rdflib.plugins.parsers.jsonld.JsonLDParser

  Bases: `Parser`

  __annotations__ = {}
  __dict__ = mappingproxy({'__module__': 'rdflib.plugins.parsers.jsonld', '__init__': <function JsonLDParser.__init__>, 'parse': <function JsonLDParser.parse>, '__dict__': <attribute '__dict__' of 'JsonLDParser' objects>, '__weakref__': <attribute '__weakref__' of 'JsonLDParser' objects>, '__doc__': None, '__annotations__': {}})
  __init__()
  __module__ = 'rdflib.plugins.parsers.jsonld'
  __weakref__

    list of weak references to the object

  parse(source, sink, **kwargs)

rdflib.plugins.parsers.jsonld.to_rdf(data, dataset, base=None, context_data=None, version=None, generalized_rdf=False, allow_lists_of_lists=None)

## rdflib.plugins.parsers.notation3 module

notation3.py - Standalone Notation3 Parser Derived from CWM, the Closed World Machine

Authors of the original suite:

- Dan Connolly <@@>

- Tim Berners-Lee <@@>

- Yosi Scharf <@@>

- Joseph M. Reagle Jr. <reagle@w3.org>

- Rich Salz <rsalz@zolera.com>

http://www.w3.org/2000/10/swap/notation3.py

Copyright 2000-2007, World Wide Web Consortium. Copyright 2001, MIT. Copyright 2001, Zolera Systems Inc.

License: W3C Software License http://www.w3.org/Consortium/Legal/copyright-software

Modified by Sean B. Palmer Copyright 2007, Sean B. Palmer.

Modified to work with rdflib by Gunnar Aastrand Grimnes Copyright 2010, Gunnar A. Grimnes

exception rdflib.plugins.parsers.notation3.BadSyntax(uri, lines, argstr, i, why)

  Bases: `SyntaxError`

  __init__(uri, lines, argstr, i, why)
  __module__ = 'rdflib.plugins.parsers.notation3'
  __str__()

    Return str(self).

  __weakref__

    list of weak references to the object

  property message

class rdflib.plugins.parsers.notation3.N3Parser

  Bases: `TurtleParser`

  An RDFLib parser for Notation3

  See http://www.w3.org/DesignIssues/Notation3.html

  __annotations__ = {}
  __init__()
  __module__ = 'rdflib.plugins.parsers.notation3'
  parse(source, graph, encoding='utf-8')

class rdflib.plugins.parsers.notation3.TurtleParser

  Bases: `Parser`

  An RDFLib parser for Turtle

  See http://www.w3.org/TR/turtle/

  __annotations__ = {}
  __dict__ = mappingproxy({'__module__': 'rdflib.plugins.parsers.notation3', '__doc__': '\n An RDFLib parser for Turtle\n\n See http://www.w3.org/TR/turtle/\n ', '__init__': <function TurtleParser.__init__>, 'parse': <function TurtleParser.parse>, '__dict__': <attribute '__dict__' of 'TurtleParser' objects>, '__weakref__': <attribute '__weakref__' of 'TurtleParser' objects>, '__annotations__': {}})
  __init__()
  __module__ = 'rdflib.plugins.parsers.notation3'
  __weakref__

    list of weak references to the object

  parse(source, graph, encoding='utf-8', turtle=True)

rdflib.plugins.parsers.notation3.base()

  The base URI for this process - the Web equiv of cwd

  Relative or absolute unix-standard filenames parsed relative to this yield the URI of the file. If we had a reliable way of getting a computer name, we should put it in the hostname just to prevent ambiguity

rdflib.plugins.parsers.notation3.hexify(ustr)

  Use URL encoding to return an ASCII string corresponding to the given UTF8 string

      >>> hexify("http://example/a b")
      b'http://example/a%20b'

rdflib.plugins.parsers.notation3.join(here, there)

  join an absolute URI and URI reference (non-ascii characters are supported/doctested; haven’t checked the details of the IRI spec though)

  `here` is assumed to be absolute. `there` is URI reference.

      >>> join('http://example/x/y/z', '../abc')
      'http://example/x/abc'

  Raise ValueError if there uses relative path syntax but here has no hierarchical path.

      >>> join('mid:foo@example', '../foo')
      Traceback (most recent call last):
          raise ValueError(here)
      ValueError: Base <mid:foo@example> has no slash
      after colon - with relative '../foo'.

      >>> join('http://example/x/y/z', '')
      'http://example/x/y/z'

      >>> join('mid:foo@example', '#foo')
      'mid:foo@example#foo'

  We grok IRIs

      >>> len(u'Andr\xe9')
      5

      >>> join('http://example.org/', u'#Andr\xe9')
      u'http://example.org/#Andr\xe9'

rdflib.plugins.parsers.notation3.runNamespace()

  Returns a URI suitable as a namespace for run-local objects

rdflib.plugins.parsers.notation3.splitFragP(uriref, punct=0)

  split a URI reference before the fragment

  Punctuation is kept.

  e.g.

      >>> splitFragP("abc#def")
      ('abc', '#def')

      >>> splitFragP("abcdef")
      ('abcdef', '')

rdflib.plugins.parsers.notation3.uniqueURI()

  A unique URI

## rdflib.plugins.parsers.nquads module

This is a rdflib plugin for parsing NQuad files into Conjunctive graphs that can be used and queried. The store that backs the graph must be able to handle contexts.

    >>> from rdflib import ConjunctiveGraph, URIRef, Namespace
    >>> g = ConjunctiveGraph()
    >>> data = open("test/nquads.rdflib/example.nquads", "rb")
    >>> g.parse(data, format="nquads")
    <Graph identifier=... (<class 'rdflib.graph.Graph'>)>
    >>> assert len(g.store) == 449
    >>> # There should be 16 separate contexts
    >>> assert len([x for x in g.store.contexts()]) == 16
    >>> # is the name of entity E10009 "Arco Publications"?
    >>> #   (in graph http://bibliographica.org/entity/E10009)
    >>> # Looking for:
    >>> # <http://bibliographica.org/entity/E10009>
    >>> #   <http://xmlns.com/foaf/0.1/name>
    >>> #   "Arco Publications"
    >>> #   <http://bibliographica.org/entity/E10009>
    >>> s = URIRef("http://bibliographica.org/entity/E10009")
    >>> FOAF = Namespace("http://xmlns.com/foaf/0.1/")
    >>> assert(g.value(s, FOAF.name).eq("Arco Publications"))

class rdflib.plugins.parsers.nquads.NQuadsParser(sink=None, bnode_context=None)

  Bases: `W3CNTriplesParser`

  __dict__ = mappingproxy({'__module__': 'rdflib.plugins.parsers.nquads', 'parse': <function NQuadsParser.parse>, 'parseline': <function NQuadsParser.parseline>, '__dict__': <attribute '__dict__' of 'NQuadsParser' objects>, '__weakref__': <attribute '__weakref__' of 'NQuadsParser' objects>, '__doc__': None, '__annotations__': {}})
  __module__ = 'rdflib.plugins.parsers.nquads'
  __weakref__

    list of weak references to the object

  buffer
  file
  line
  parse(inputsource, sink, bnode_context=None, **kwargs)

    Parse inputsource as an N-Quads file.

    Parameters:

      - inputsource (`rdflib.parser.InputSource`) – the source of N-Quads-formatted data

      - sink (`rdflib.graph.Graph`) – where to send parsed triples

      - bnode_context (`dict`, optional) – a dict mapping blank node identifiers to `BNode` instances. See `NTriplesParser.parse`

  parseline(bnode_context=None)
  sink

## rdflib.plugins.parsers.ntriples module

N-Triples Parser License: GPL 2, W3C, BSD, or MIT Author: Sean B. Palmer, inamidst.com

class rdflib.plugins.parsers.ntriples.NTGraphSink(graph)

  Bases: `object`

  __init__(graph)
  __module__ = 'rdflib.plugins.parsers.ntriples'
  __slots__ = ('g',)
  g
  triple(s, p, o)

class rdflib.plugins.parsers.ntriples.NTParser

  Bases: `Parser`

  parser for the ntriples format, often stored with the .nt extension

  See http://www.w3.org/TR/rdf-testcases/#ntriples

  __annotations__ = {}
  __module__ = 'rdflib.plugins.parsers.ntriples'
  __slots__ = ()
  classmethod parse(source, sink, **kwargs)

    Parse the NT format

    Parameters:

      - source (`rdflib.parser.InputSource`) – the source of NT-formatted data

      - sink (`rdflib.graph.Graph`) – where to send parsed triples

      - kwargs – Additional arguments to pass to `NTriplesParser.parse`

class rdflib.plugins.parsers.ntriples.W3CNTriplesParser(sink=None, bnode_context=None)

  Bases: `object`

  An N-Triples Parser. This is a legacy-style Triples parser for NTriples provided by W3C Usage:

      p = NTriplesParser(sink=MySink())
      sink = p.parse(f) # file; use parsestring for a string

  To define a context in which blank node identifiers refer to the same blank node across instances of NTriplesParser, pass the same dict as `bnode_context` to each instance. By default, a new blank node context is created for each instance of `NTriplesParser`.

  __annotations__ = {}
  __init__(sink=None, bnode_context=None)
  __module__ = 'rdflib.plugins.parsers.ntriples'
  __slots__ = ('_bnode_ids', 'sink', 'buffer', 'file', 'line')
  buffer
  eat(pattern)
  file
  line
  literal()
  nodeid(bnode_context=None)
  object(bnode_context=None)
  parse(f, bnode_context=None)

    Parse f as an N-Triples file.

    Parameters:

      - f (file object) – the N-Triples source

      - bnode_context (`dict`, optional) – a dict mapping blank node identifiers (e.g., `a` in `_:a`) to `BNode` instances. An empty dict can be passed in to define a distinct context for a given call to `parse`.

  parseline(bnode_context=None)
  parsestring(s, **kwargs)

    Parse s as an N-Triples string.

  peek(token)
  predicate()
  readline()

    Read an N-Triples line from buffered input.

  sink
  subject(bnode_context=None)
  uriref()

rdflib.plugins.parsers.ntriples.unquote(s)

  Unquote an N-Triples string.

rdflib.plugins.parsers.ntriples.uriquote(uri)

## rdflib.plugins.parsers.rdfxml module

An RDF/XML parser for RDFLib

class rdflib.plugins.parsers.rdfxml.BagID(value: str, base: str | None = None)

  Bases: `URIRef`

  __annotations__ = {}
  __init__(val)
  __module__ = 'rdflib.plugins.parsers.rdfxml'
  __slots__ = ['li']
  li
  next_li()

class rdflib.plugins.parsers.rdfxml.ElementHandler

  Bases: `object`

  __init__()
  __module__ = 'rdflib.plugins.parsers.rdfxml'
  __slots__ = ['start', 'char', 'end', 'li', 'id', 'base', 'subject', 'predicate', 'object', 'list', 'language', 'datatype', 'declared', 'data']
  base
  char
  data
  datatype
  declared
  end
  id
  language
  li
  list
  next_li()
  object
  predicate
  start
  subject

class rdflib.plugins.parsers.rdfxml.RDFXMLHandler(store)

  Bases: `ContentHandler`

  __init__(store)
  __module__ = 'rdflib.plugins.parsers.rdfxml'
  absolutize(uri)
  add_reified(sid, spo)
  characters(content)

    Receive notification of character data.

    The Parser will call this method to report each chunk of character data. SAX parsers may return all contiguous character data in a single chunk, or they may split it into several chunks; however, all of the characters in any single event must come from the same external entity so that the Locator provides useful information.

  convert(name, qname, attrs)
  property current
  document_element_start(name, qname, attrs)
  endElementNS(name, qname)

    Signals the end of an element in namespace mode.

    The name parameter contains the name of the element type, just as with the startElementNS event.

  endPrefixMapping(prefix)

    End the scope of a prefix-URI mapping.

    See startPrefixMapping for details. This event will always occur after the corresponding endElement event, but the order of endPrefixMapping events is not otherwise guaranteed.

  error(message)
  get_current()
  get_next()
  get_parent()
  ignorableWhitespace(content)

    Receive notification of ignorable whitespace in element content.

    Validating Parsers must use this method to report each chunk of ignorable whitespace (see the W3C XML 1.0 recommendation, section 2.10): non-validating parsers may also use this method if they are capable of parsing and using content models.

    SAX parsers may return all contiguous whitespace in a single chunk, or they may split it into several chunks; however, all of the characters in any single event must come from the same external entity, so that the Locator provides useful information.

  list_node_element_end(name, qname)
  literal_element_char(data)
  literal_element_end(name, qname)
  literal_element_start(name, qname, attrs)
  property next
  node_element_end(name, qname)
  node_element_start(name, qname, attrs)
  property parent
  processingInstruction(target, data)

    Receive notification of a processing instruction.

    The Parser will invoke this method once for each processing instruction found: note that processing instructions may occur before or after the main document element.

    A SAX parser should never report an XML declaration (XML 1.0, section 2.8) or a text declaration (XML 1.0, section 4.3.1) using this method.

  property_element_char(data)
  property_element_end(name, qname)
  property_element_start(name, qname, attrs)
  reset()
  setDocumentLocator(locator)

    Called by the parser to give the application a locator for locating the origin of document events.

    SAX parsers are strongly encouraged (though not absolutely required) to supply a locator: if it does so, it must supply the locator to the application by invoking this method before invoking any of the other methods in the DocumentHandler interface.

    The locator allows the application to determine the end position of any document-related event, even if the parser is not reporting an error. Typically, the application will use this information for reporting its own errors (such as character content that does not match an application’s business rules). The information returned by the locator is probably not sufficient for use with a search engine.

    Note that the locator will return correct information only during the invocation of the events in this interface. The application should not attempt to use it at any other time.

  startDocument()

    Receive notification of the beginning of a document.

    The SAX parser will invoke this method only once, before any other methods in this interface or in DTDHandler (except for setDocumentLocator).

  startElementNS(name, qname, attrs)

    Signals the start of an element in namespace mode.

    The name parameter contains the name of the element type as a (uri, localname) tuple, the qname parameter the raw XML 1.0 name used in the source document, and the attrs parameter holds an instance of the Attributes class containing the attributes of the element.

    The uri part of the name tuple is None for elements which have no namespace.

  startPrefixMapping(prefix, namespace)

    Begin the scope of a prefix-URI Namespace mapping.

    The information from this event is not necessary for normal Namespace processing: the SAX XML reader will automatically replace prefixes for element and attribute names when the http://xml.org/sax/features/namespaces feature is true (the default).

    There are cases, however, when applications need to use prefixes in character data or in attribute values, where they cannot safely be expanded automatically; the start/endPrefixMapping event supplies the information to the application to expand prefixes in those contexts itself, if necessary.

    Note that start/endPrefixMapping events are not guaranteed to be properly nested relative to each-other: all startPrefixMapping events will occur before the corresponding startElement event, and all endPrefixMapping events will occur after the corresponding endElement event, but their order is not guaranteed.

class rdflib.plugins.parsers.rdfxml.RDFXMLParser

  Bases: `Parser`

  __annotations__ = {}
  __dict__ = mappingproxy({'__module__': 'rdflib.plugins.parsers.rdfxml', '__init__': <function RDFXMLParser.__init__>, 'parse': <function RDFXMLParser.parse>, '__dict__': <attribute '__dict__' of 'RDFXMLParser' objects>, '__weakref__': <attribute '__weakref__' of 'RDFXMLParser' objects>, '__doc__': None, '__annotations__': {}})
  __init__()
  __module__ = 'rdflib.plugins.parsers.rdfxml'
  __weakref__

    list of weak references to the object

  parse(source, sink, **args)

rdflib.plugins.parsers.rdfxml.create_parser(target, store) → XMLReader

## rdflib.plugins.parsers.trig module

class rdflib.plugins.parsers.trig.TrigParser

  Bases: `Parser`

  An RDFLib parser for TriG

  __annotations__ = {}
  __dict__ = mappingproxy({'__module__': 'rdflib.plugins.parsers.trig', '__doc__': '\n An RDFLib parser for TriG\n\n ', '__init__': <function TrigParser.__init__>, 'parse': <function TrigParser.parse>, '__dict__': <attribute '__dict__' of 'TrigParser' objects>, '__weakref__': <attribute '__weakref__' of 'TrigParser' objects>, '__annotations__': {}})
  __init__()
  __module__ = 'rdflib.plugins.parsers.trig'
  __weakref__

    list of weak references to the object

  parse(source, graph, encoding='utf-8')

class rdflib.plugins.parsers.trig.TrigSinkParser(store, openFormula=None, thisDoc='', baseURI=None, genPrefix='', why=None, turtle=False)

  Bases: `SinkParser`

  __module__ = 'rdflib.plugins.parsers.trig'
  directiveOrStatement(argstr, h)
  graph(argstr, i)

    Parse trig graph, i.e.

    > <urn:graphname> = { .. triples .. }

    return -1 if it doesn’t look like a graph-decl raise Exception if it looks like a graph, but isn’t.

  labelOrSubject(argstr, i, res)

rdflib.plugins.parsers.trig.becauseSubGraph(*args, **kwargs)

## rdflib.plugins.parsers.trix module

A TriX parser for RDFLib

class rdflib.plugins.parsers.trix.TriXHandler(store)

  Bases: `ContentHandler`

  An Sax Handler for TriX. See http://sw.nokia.com/trix/

  __annotations__ = {}
  __init__(store)
  __module__ = 'rdflib.plugins.parsers.trix'
  characters(content)

    Receive notification of character data.

    The Parser will call this method to report each chunk of character data. SAX parsers may return all contiguous character data in a single chunk, or they may split it into several chunks; however, all of the characters in any single event must come from the same external entity so that the Locator provides useful information.

  endElementNS(name, qname)

    Signals the end of an element in namespace mode.

    The name parameter contains the name of the element type, just as with the startElementNS event.

  endPrefixMapping(prefix)

    End the scope of a prefix-URI mapping.

    See startPrefixMapping for details. This event will always occur after the corresponding endElement event, but the order of endPrefixMapping events is not otherwise guaranteed.

  error(message)
  get_bnode(label)
  ignorableWhitespace(content)

    Receive notification of ignorable whitespace in element content.

    Validating Parsers must use this method to report each chunk of ignorable whitespace (see the W3C XML 1.0 recommendation, section 2.10): non-validating parsers may also use this method if they are capable of parsing and using content models.

    SAX parsers may return all contiguous whitespace in a single chunk, or they may split it into several chunks; however, all of the characters in any single event must come from the same external entity, so that the Locator provides useful information.

  processingInstruction(target, data)

    Receive notification of a processing instruction.

    The Parser will invoke this method once for each processing instruction found: note that processing instructions may occur before or after the main document element.

    A SAX parser should never report an XML declaration (XML 1.0, section 2.8) or a text declaration (XML 1.0, section 4.3.1) using this method.

  reset()
  setDocumentLocator(locator)

    Called by the parser to give the application a locator for locating the origin of document events.

    SAX parsers are strongly encouraged (though not absolutely required) to supply a locator: if it does so, it must supply the locator to the application by invoking this method before invoking any of the other methods in the DocumentHandler interface.

    The locator allows the application to determine the end position of any document-related event, even if the parser is not reporting an error. Typically, the application will use this information for reporting its own errors (such as character content that does not match an application’s business rules). The information returned by the locator is probably not sufficient for use with a search engine.

    Note that the locator will return correct information only during the invocation of the events in this interface. The application should not attempt to use it at any other time.

  startDocument()

    Receive notification of the beginning of a document.

    The SAX parser will invoke this method only once, before any other methods in this interface or in DTDHandler (except for setDocumentLocator).

  startElementNS(name, qname, attrs)

    Signals the start of an element in namespace mode.

    The name parameter contains the name of the element type as a (uri, localname) tuple, the qname parameter the raw XML 1.0 name used in the source document, and the attrs parameter holds an instance of the Attributes class containing the attributes of the element.

    The uri part of the name tuple is None for elements which have no namespace.

  startPrefixMapping(prefix, namespace)

    Begin the scope of a prefix-URI Namespace mapping.

    The information from this event is not necessary for normal Namespace processing: the SAX XML reader will automatically replace prefixes for element and attribute names when the http://xml.org/sax/features/namespaces feature is true (the default).

    There are cases, however, when applications need to use prefixes in character data or in attribute values, where they cannot safely be expanded automatically; the start/endPrefixMapping event supplies the information to the application to expand prefixes in those contexts itself, if necessary.

    Note that start/endPrefixMapping events are not guaranteed to be properly nested relative to each-other: all startPrefixMapping events will occur before the corresponding startElement event, and all endPrefixMapping events will occur after the corresponding endElement event, but their order is not guaranteed.

class rdflib.plugins.parsers.trix.TriXParser

  Bases: `Parser`

  A parser for TriX. See http://sw.nokia.com/trix/

  __annotations__ = {}
  __dict__ = mappingproxy({'__module__': 'rdflib.plugins.parsers.trix', '__doc__': 'A parser for TriX. See http://sw.nokia.com/trix/', '__init__': <function TriXParser.__init__>, 'parse': <function TriXParser.parse>, '__dict__': <attribute '__dict__' of 'TriXParser' objects>, '__weakref__': <attribute '__weakref__' of 'TriXParser' objects>, '__annotations__': {}})
  __init__()
  __module__ = 'rdflib.plugins.parsers.trix'
  __weakref__

    list of weak references to the object

  parse(source, sink, **args)

rdflib.plugins.parsers.trix.create_parser(store)

## Module contents