A significant drawback is the overload of the named graph parameter with an identifier instead of the file or source that produced the triple.

What RDF* Improves

Technically, this is a fourth element, which can be attached to the <subject, predicate, object> triple

Any segment size is possible

RDF Signify

Distributed Mutable Containers

shard parity

Datashard ocaps

capabilities

all depending on need and threat analysis

Also things of a certain type could become widgets by giving them a @view

In particular we intend to use content-addressed ActivityStreams over XMPP.

difficulties in providing reproducible development environments

It requires the usage of algorithms (e.g. the Expansion Algorithm or the Framing Algorithm) that are incomprehensible and just pure madness.

while the result of the checkout is called a working directory

Updating a working copy with the latest files from the repository is simply called update

test.txt v1

git-cat-file

By operation of the pigeonhole principle, no lossless compression algorithm can efficiently compress all possible data.

http://purl.org/ca-rdf

Composing knowledge from events In any multi-actor system, like a team of collaborating robots, every actor must make decisions based on some current knowledge: a local world model, or an evolving set of goals. It may not be possible to centralise that knowledge – for example if the actors can lose their network connection; or the latency or locking behaviour of a central database is not acceptable. If the contributing data events are frequent, for example from sensors, every update has to be synthesised by every actor into their knowledge. This can rapidly become a computational headache. m-ld can help. The knowledge itself is maintained as convergent shared state, and each actor only needs to apply their own updates. The rich query syntax then lets them act upon what they need to know, when they need to act.

Connections between users of a social network

There is no single best way to structure one’s data; every choice comes with significant tradeoffs. The larger our dataset becomes, the more important it is to tailor its structure to the way we intend to use and access it.

pics
├── 2018
│   ├── 2018-02-23-tabby.png
│   └── 2018-04-14-tropical.png
├── cats
│   ├── 2018-02-23-tabby.png
│   └── 2019-12-16-black.png
└── fish
    ├── 2017-03-05-freshwater.png
    ├── 2018-04-14-tropical.png
    └── 2020-10-02-blowfish.png

and the functions or operations that can be applied to the data

Annotation with a SpecificResource that has a Selector for each of the Body and the Target

Describe the style in which the source resource should be presented for the Annotation

or simply the location where the current harvesting system discovered the resource

Other Identities

is NOT RECOMMENDED for uses where the Body may need to be referred to from outside of the Annotation

Hannah associates a tag and a description with two images using a single annotation

Her client associates a stylesheet with the Annotation

is NOT RECOMMENDED for uses where the Body may need to be referred to from outside of the Annotation

The identity of the SpecificResource is separate from the descriptions of the constraints.

fragments for HTML cannot be used to describe an arbitrary range of text

"type": "Video"

"type": "Video"

3.2.2 Classes

it is also useful for a client to know that a resource with the format text/csv should not simply be rendered as plain text

It is useful for clients to know the general type of a Web Resource in advance.

if information provided by the external resource contradicts the information provided by the annotation about it, then the external resource is authoritative and the information from the annotation should be disregarded

if information provided by the external resource contradicts the information provided by the annotation about it, then the external resource is authoritative and the information from the annotation should be disregarded

if information provided by the external resource contradicts the information provided by the annotation about it, then the external resource is authoritative and the information from the annotation should be disregarded

textDirection

processingLanguage

This information may be recorded as part of the Annotation, even if the representation of the resource must be retrieved from the Web.

the Body may also be embedded within the Annotation

the Body may also be embedded within the Annotation

An Annotation is a Web Resource.

Class Resources may be divided, conceptually, into groups called "classes"; members of a class are known as Instances of the class. Resources are associated with a particular class through typing. Classes are identified by IRIs, i.e., they are also Web Resources themselves. Type A special Relationship that associates an Instance of a class to the Class it belongs to. Instance An element of a group of Resources represented by a particular Class.

representation of the Annotation

are not to be considered authoritative information

collections

The Body resource may be a choice between multiple resources.

The Target or Body resource may be included in the Annotation to play a specific role.

The Target or Body resource may be included in the Annotation to play a specific role.

The Target or Body resource may be a specific state of the resource.

The Target or Body resource may be a specific state of the resource.

The Target or Body resource may be styled in a specific way.

rooted

associations between resources

structured model and format

it’s really annoying

Comments can lead you astray, because they get out of date. The code is the only source of truth.

These shouldn’t be comments! They should be in commit messages, or the wiki, or the issue tracker, etc

RDF is an abstract knowledge representation model that does not differentiate data from metadata.

Nested Embedded Triples

What RDF* Improves

:hasSpouse is a symmetric relation so that it can be inferred in the opposite direction

the metadata in the opposite direction is not asserted automatically, so it needs to be added

<<:man :hasSpouse :woman>>

What RDF* Improves

<< <<:man :hasSpouse :woman>> :startDate "2020-02-11"^^xsd:date >>

According to the formal semantics of RDF*, each embedded triple also asserts the referenced statement and its retraction – deletes it. Unfortunately, this requirement breaks the compatibility with the standard reification and causes a non-transparent behavior when dealing with triples stored in multiple named graphs. GraphDB implements the embedded triples by introducing a new additional RDF type next to IRI, blank node, and literal.

GraphDB implements the embedded triples by introducing a new additional RDF type next to IRI, blank node, and literal.

According to the formal semantics of RDF*, each embedded triple also asserts the referenced statement and its retraction – deletes it.

RDF reification as demonstrated in the example has two major shortcomings

Scalability: In a many-to-many system, scale is essentially unlimited. Hardware (nodes) can be added at ease in any home or office by anyone, which is not the case with the current data center model.

standard

to be maintained over time

with a standard

it is possible so make following a link fire up a special application

One must also be able to annotate links

a user de-fined extension namespaces

Each SPARQL implementation has its own protocol torealize the binding between extension namespaces and function definitions

limits the interoperability of the query

query and search

Given the restrictions of the sandboxed iframe, it is not able to make calls outside of its own frame, nor is it able to read or modify anything about the parent page.

they can perform I/O using XMLHttpRequest (although the responseXML and channel attributes are always null) or fetch (with no such restrictions).

It is an isolated environment that is insulated from the window object, the document object, direct internet access

more difficult to maintain

make our components larger

convolute the code

Notes

All components will share the library code

Automatic linking of other resources and discussions

Portability across hosting services

Rich connections to other online resources

Discovery and linking of annotations across different content instances (html vs. pdf)

Rich

Many different clients that support basic functionality

Tags that help filter, sort, identify annotations by date, relevance, topic…factual annotations vs. comments  (pragmatic vs. true semantic interoperability)

People identifiers within groups and globally (SSO including with ORCID), w/ Twitter, other SM groups

repositories

versions of content

Selection

ability to evolve permissions on selected annotations

branded

authoritative

private group

but