From 33155e68bb2513801020144f50dae39c10c33544 Mon Sep 17 00:00:00 2001 From: Tim Berners-Lee Date: Wed, 2 Aug 2023 16:02:25 -0400 Subject: [PATCH 1/4] The AddressBook is actually #this in that file --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index 0bccf0a..05cda9f 100644 --- a/index.html +++ b/index.html @@ -1125,7 +1125,7 @@

Public Type Index

<#ab09fd> a solid:TypeRegistration; solid:forClass vcard:AddressBook; - solid:instance </public/contacts/myPublicAddressBook.ttl>. + solid:instance </public/contacts/myPublicAddressBook.ttl#this>. <#bq1r5e> a solid:TypeRegistration; solid:forClass bk:Bookmark; @@ -1135,7 +1135,7 @@

Public Type Index

Type registration containing a public resource of type vcard:AddressBook located at the resource address - </public/contacts/myPublicAddressBook.ttl>. + </public/contacts/myPublicAddressBook.ttl#this>. And a resources of type bk:Bookmark located in the container address </public/myBookmarks/>. From 532cb4443e3a5c627cef0df427e791fb250aeb67 Mon Sep 17 00:00:00 2001 From: Tim Berners-Lee Date: Wed, 2 Aug 2023 16:40:51 -0400 Subject: [PATCH 2/4] Table of examples for domain specific indexes --- index.html | 22 ++++++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index 05cda9f..c8731e3 100644 --- a/index.html +++ b/index.html @@ -824,8 +824,26 @@

Table of Contents

In the Solid ecosystem, storages and clients are loosely coupled. This means clients are tight to data models. Furthermore, clients and thus storages should be able to be connected in a network of knowledge. The connection is only achievable if the data itself is easy to be interconnected. - This specification is written for Solid application developers as a solution that shows how to interconnect clients and data on storages. This specification details the use of Type Indexes which were implemented already in different clients. Type Indexes offer a fine-grained approach to describing the location of specific types of resources on a storage. - + This specification is written for Solid application developers as a solution that shows how to interconnect clients and data on storages. This specification details the use of Type Indexes which were implemented already in different clients. + Type Indexes offer a first step, high level approach to describing the location of specific types of resources on a storage. +

+

+ The type indexes are high level in that they typically point not to infividual resources like photos, audio files or isses, but + to the high level structures like Photo Libraries, Music Libraries, Issue Trackers which then keep track of the individual resources + within each system. Typically, each Library has its own domain specfic index, which + indexes in a way specific to that application. Here are some putative examples (though some have running code) + to give an idea of how this works in general. +

+ + + + + + + + +
LibraryItemIndexed by, say,
Music LibrarySong, PlaylistArists, Album, Genre
Issue TrackerIssueDate, Status, Category, Assignee, Owner
Address BookContact, GroupName, email, group
Photo LibraryPhotoDate, Aperture, Focal Length, Location
CookbookRecipeIngredients, Preparation time,...
+

This specification is accompanied with shape documents, [SHACL] and [ShEx], to help developers improve their implementations and maximize the promise of interconnected data.

From 8ed788362fb81e2ecbbb92da180bdd3dc6311455 Mon Sep 17 00:00:00 2001 From: Timea <4144203+timea-solid@users.noreply.github.com> Date: Mon, 11 Sep 2023 11:44:54 +0200 Subject: [PATCH 3/4] Update index.html --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index c8731e3..b860417 100644 --- a/index.html +++ b/index.html @@ -828,7 +828,7 @@

Table of Contents

Type Indexes offer a first step, high level approach to describing the location of specific types of resources on a storage.

- The type indexes are high level in that they typically point not to infividual resources like photos, audio files or isses, but + The type indexes are high-level in that they typically point not to individual resources like photos, audio files, or issues, but to the high level structures like Photo Libraries, Music Libraries, Issue Trackers which then keep track of the individual resources within each system. Typically, each Library has its own domain specfic index, which indexes in a way specific to that application. Here are some putative examples (though some have running code) From f7fd941ef2a69316d806de638d1ef0c962df7c19 Mon Sep 17 00:00:00 2001 From: Timea <4144203+timea-solid@users.noreply.github.com> Date: Mon, 11 Sep 2023 11:44:59 +0200 Subject: [PATCH 4/4] Update index.html --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index b860417..96c79c0 100644 --- a/index.html +++ b/index.html @@ -830,7 +830,7 @@

Table of Contents

The type indexes are high-level in that they typically point not to individual resources like photos, audio files, or issues, but to the high level structures like Photo Libraries, Music Libraries, Issue Trackers which then keep track of the individual resources - within each system. Typically, each Library has its own domain specfic index, which + within each system. Typically, each Library has its own domain specific index, which indexes in a way specific to that application. Here are some putative examples (though some have running code) to give an idea of how this works in general.