From 2c8fa58a6606bfc1a0783abf1a7ce34ea4e6803f Mon Sep 17 00:00:00 2001 From: Pierre-Antoine Champin Date: Tue, 19 Mar 2019 18:09:39 +0100 Subject: [PATCH] describing property-based indexing as a variant of data indexing --- index.html | 193 ++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 191 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index 57086fbe..c1f50822 100644 --- a/index.html +++ b/index.html @@ -6055,8 +6055,8 @@

Using the Document Base for the Default Vocabulary

Databases are typically used to make access to data more efficient. Developers often extend this sort of functionality into - their application data to deliver similar performance gains. Often this - data does not have any meaning from a Linked Data standpoint, but is + their application data to deliver similar performance gains. + This data may have no meaning from a Linked Data standpoint, but is still useful for an application.

JSON-LD introduces the notion of index maps @@ -6441,6 +6441,195 @@

Using the Document Base for the Default Vocabulary

--> + +

Property-based data indexing

+

In its simplest form (as in the examples above), + data indexing assigns no semantics to the keys of an index map. + However, in some situations, + the keys used to index objects are semantically linked to these objects, + and should be preserved not only syntactically, but also semantically. +

+

If the processing mode is set to json-ld-1.1, + "@container": "@index" in a term description can be accompanied with + an "@index" key. The value of that key must map to an IRI, + which identifies the semantic property linking each object to its key. +

+ +
+

Language Indexing