Update content/docs/Standards/owl.md, content/docs/Standards/IIIF.md,...

+++

title = "IIIF"

+++

# IIIF

Das International Image Interoperability Framework (IIIF) soll den applikationsunabhängigen Zugang zu Bildressourcen und deren Metadaten im Web verbessern. Folgende Ziele werden verfolgt:

* To give scholars an unprecedented level of uniform and rich access to image-based resources hosted around the world.

The IIIF is a set of shared application programming interface (API) specifications for interoperable functionality in digital image repositories. Using [JSON-LD](file:///home/seb/doku/linked/Konzepte/JSON-LD.txt), linked data, and standard W3C web protocols such as [Web Annotation](./Web_Annotation.md), IIIF makes it easy to parse and share digital image data, migrate across technology systems, and provide enhanced image access for scholars and researchers. In short, IIIF enables better, faster and cheaper image delivery. It lets you leverage interoperability and the fabric of the Web to access new possibilities and new users for your image-based resources, while reducing long term maintenance and technological lock in. IIIF gives users a rich set of baseline functionality for viewing, zooming, and assembling the best mix of resources and tools to view, compare, manipulate and work with images on the Web, an experience made portable–shareable, citable, and embeddable.

APIs

----

## APIs

IIIF definiert verschiedene APIs:

* [Image API](http://iiif.io/api/image/): Spezifiziert einen Web service, der ein Bild zurückgibt. Durch die URL können die Region, die Grösse, die Drehung, die Qualität und das Format des darzustellenden Bildes definiert werden

### Presentation API

The aim of the Presentation API is to provide the information necessary to allow a rich, online viewing environment for primarily image-based objects to be presented to a human user, likely in conjunction with the IIIF Image API. This is the sole purpose of the API and therefore the descriptive information is given in a way that is intended for humans to read, but not semantically available to machines. In particular, it explicitly does not aim to provide metadata that would drive discovery of the digitized objects.

#### Types

Basic:

* **Manifest**: Overall description of the structure and properties of the digital representation of an object. Carries descriptive information needed by the viewer for presentation to the user. Each manifest describes how to present a single object (e.g. a book, photograph, statue).

* **AnnotationList**: Ordered list of annotations, typically associated with a single canvas

* **Layer**: Ordered list of annotation lists. Allows higher level groupings of annotations to be recorded. For example, all of the English translation annotations of a medieval French document could be kept separate from the transcription or an edition in modern French.

* **Range**: Ordered list of canvases, and/or further ranges. Allows canvases, or parts thereof, to be grouped together in some way. This could be for textual reasons, such as to distinguish books, chapters, verses, sections etc. Equally, physical features might be important such as quires or gatherings, sections that have been added later and so forth.

 No newline at end of file

+++

title = "JSON-LD"

+++

# JSON-LD

Dokumentformen

--------------

## Dokumentformen

### Expanded

<http://www.w3.org/TR/json-ld/#expanded-document-form>

Profil-URI: <http://www.w3.org/ns/json-ld#expanded>

Alle IRIs, Typen und Werte sind in ausgeschriebenen Format, so dass kein eigener Kontext mehr nötig ist.

### Compacted

<http://www.w3.org/TR/json-ld/#compacted-document-form>

Profile-URI: <http://www.w3.org/ns/json-ld#compacted>

Gegenstück zur ausgeweiteten Dokumentenform: IRIs werden zu Termen bzw. abgekürzten IRIs, Werte zu einfachen Werttypen wie Strings oder Zahlen reduziert.

### Flattened

<http://www.w3.org/TR/json-ld/#flattened-document-form>

Profile-URI: <http://www.w3.org/ns/json-ld#flattened>

Einige Links

------------

## Einige Links

* [Projektwebsite](http://json-ld.org)

* [W3C Recommendation zur Syntax](http://www.w3.org/TR/json-ld/)

* [W3C Recommendation zu den Processing Algorithms und zur API](http://www.w3.org/TR/json-ld-api/)

* [W3C Draft zum JSON-LD-Framing](http://json-ld.org/spec/latest/json-ld-framing/)

* [W3C Draft zum JSON-LD-Normalization](http://json-ld.org/spec/latest/rdf-dataset-normalization/)

 No newline at end of file

+++

title = "OAI-PMH"

+++

# OAI-PMH

*Open Archives Initiative Protocol for Metadata Harvesting*

Ein Protokoll, welches zum Sammeln von Metadaten über archivische Unterlagen dient.

OAI-PMH enthält sechs Verben/Services, die über HTTP aufgerufen werden können.

Record

------

## Record

Ein Record enhält drei Teile:

* Header: Unique Identifier, Datestamp, 0 oder mehr ``setSpec``-Elemente (Zugehörigkeit(en) zu Set(s))

* ``transient``: Es wird nicht garantiert, dass die Liste der Löschungen persistent bzw. konsistent geführt wird.

Response

--------

## Response

* ``ListIdentifiers``

* ``ListRecords``

Requests / Responses

--------------------

## Requests / Responses

* ``GetRecord``

* ``ListIdentifiers``

* ``ListSets``

Selektives Harvesting

---------------------

## Selektives Harvesting

Selektives Harvesting mit den Verben ``ListRecords`` und ``ListIdentifiers`` kann auf Grundlage von

* Zeitstempeln und

geschehen.

### Zeitstempel

Gesucht werden kann mit den beiden Parametern ``from`` oder ``until`` oder beiden (jeweils inklusiv). Eine Response muss Records beinhalten, welche entweder im gesuchten Zeitraum entstanden oder modifiziert worden sind. Sie kann - bei entsprechen Einstellungen - auch im gesuchten Zeitraum gelöschte Records enthalten.

### Sets

Gesucht wird mit dem Parameter ``setSpec``. Die Response enthält Records, welche Teil des Sets sind, oder Teil eines Unter-Sets des gesuchten Sets.

Glossar

-------

## Glossar

* **Data Provider**: Partei, welche Systeme administriert, welche OAI-PMH zum Anbieten von Metadaten nutzen

* **Harvester**: Eine Clientapplikation, welche OAI-PMH-Requests absetzen kann

* **Set**: Ein Set ist ein optionales Kontrukt, um *Items* für selektives Harvesting zu gruppieren

Links

-----

## Links

* <https://www.openarchives.org/Register/BrowseSites>

* <http://re.cs.uct.ac.za/>

* <http://www.swissbib.org/wiki/index.php?title=Swissbib_oai>

 No newline at end of file

# Referenzblatt

RDF-Klassen

RDF-Eigenschaften

RDFS-Klassen

RDFS-Eigenschaften

OWL-Klassen

OWL-Eigenschaften

+++

title = "WebAssembly"

+++

# WebAssembly

Grundlagen

----------

## Grundlagen

* Code, welcher in modernen Browsers laufen kann

* Low-level, Assembler-ähnlich; kompaktes binäres Format

* Kann aus JavaScript aufgerufen werden ([WebAssembly JavaScript API](https://developer.mozilla.org/en-US/docs/WebAssembly/Using_the_JavaScript_API))

* [Webstandard](https://www.w3.org/wasm/)

Konzepte

--------

## Konzepte

* **Module**: Represents a WebAssembly binary that has been compiled by the browser into executable machine code.  A Module is stateless and thus, like a [Blob](https://developer.mozilla.org/en-US/docs/Web/API/Blob), can be explicitly shared between windows and workers (via [postMessage()](https://developer.mozilla.org/en-US/docs/Web/API/MessagePort/postMessage)).  A Module declares imports and exports just like an ES2015 module.

* **Memory**: A resizable ArrayBuffer that contains the linear array of bytes read and written by WebAssembly’s low-level memory access instructions.

* **Table**: A resizable typed array of references (e.g. to functions) that could not otherwise be stored as raw bytes in Memory (for safety and portability reasons).

* **Instance**: A Module paired with all the state it uses at runtime including a Memory, Table, and set of imported values.  An Instance is like an ES2015 module that has been loaded into a particular global with a particular set of imports.

The JavaScript API provides developers with the ability to create modules, memories, tables, and instances.  Given a WebAssembly instance, JavaScript code can synchronously call its exports, which are exposed as normal JavaScript functions.  Arbitrary JavaScript functions can also be synchronously called by WebAssembly code by passing in those JavaScript functions as the imports to a WebAssembly instance.

Since JavaScript has complete control over how WebAssembly code is downloaded, compiled and run, JavaScript developers could even think of WebAssembly as just a JavaScript feature for efficiently generating high-performance functions.

Tools

-----

## Tools

* [Emscripten](https://kripken.github.io/emscripten-site)

* [Compiling Rust to WebAssembly Guide](https://hackernoon.com/compiling-rust-to-webassembly-guide-411066a69fde)