We need to document which modules need to be externalized in webpack configuration in order to create web applications using rdflib and solid-auth-client.

Example external section of webpack configuration file:

  externals: {
    'node-fetch': 'fetch',
    'text-encoding': 'TextEncoder',
    'whatwg-url': 'window',
    'isomorphic-fetch': 'fetch',
    '@trust/webcrypto': 'cry

Currently we save every URI ever qname'd forever in here: https://github.com/RDFLib/rdflib/blob/master/rdflib/namespace.py#L289

If you serialize a big graph in a store that is off disk, we may run out of memory.

Either:

• Add a lru_cache (from py3 functools + this 2.7 implementation
• Depend on

This is of concern for systems that use hashes of documents for content-based addressing and also digital signatures. Hashing the result of jsonld.normalize is common practice for these purposes.
Hashing algorithms readily accept '' (an empty string) as a valid input. Since a valid hash is produced, this sort of issue may go unnoticed.

Would it be possible to throw an error instead of

Use semantic tags where appropriate in the application's HTML markup.

I'm trying to create a multiple snapshots/releases/versions of an article. I found rel:latest-version, rel:predecessor-version but no real-world example of a publication with versions. My approach would be:

• put current version at http://example.org/article
• put versions at http://example.org/article/X.Y.Z where X.Y.Z is a version number
• link versions with rel:latest-version,

Hi,
wanted to ask if anyone out there has used extruct on AWS lambda? I tested running extruct function which seems to fail to work for rdfa. Other default metadata types are fine.

A simple test case:

import pprint as pp
import requests
from extruct.rdfa import RDFaExtractor
import config_files.logging_config as log

logger = log.logger

def main():

    try:
        import e

I wanted to suggest that documentation for RDF.rb be moved into iRuby notebooks -- i.e., Jupyter notebooks running the Ruby kernel.

Github now supports the rendering of Jupyter notebooks in the browser (see my gist of some notes about Ruby).

The following is a response to an email I received, I'm answering it here to ensure the information is appropriately disseminated and can be referenced to.

Requiring the user to define all properties is not nice. Properties could be created automatically,
though they would need to be checked on every write, since new properties might be required. Creating property pages might also override

In #883 we realized that the docs will be out of date with the new vector-based searches. However, designs are still being finalized as we are already implementing parts of it. Therefore we aim to have this issue to group all documentation tasks into once the designs have been agreed upon

Todos

• Document Explore { Concepts }
  • usage
  • explain normalized distance
• [

Most irrelevant output from travis comes from ROBOTS InvalidReferenceViolation. These errors are virtually meaningless for ontology curators, but may provide inside for ontology engineers like myself. The goal of this issue is to first catalog and then clear the output of the QC pipeline. These are the subgoals:

• Identify all types of reference violations and divide into FIX and SUPPRESS