fbuchinger

#==============================================================
#      .picasa.ini FILE STRUCTURE
# 
#   reverse-engineered by Franz Buchinger <fbuchinger@gmail.com>
#   licensed to the public domain
#
#   Picasa Version(s): 3.8.0
#
#  Changelog:
#  v0.1: initial release

jiemakel

<?xml version="1.0"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:ohmdm="http://schemas.openhistoricalmap.org/#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:owl="http://www.w3.org/2002/07/owl#">
	<rdf:Description xmlns:tags="http://schemas.openhistoricalmap.org/tag#" xmlns:element="http://schemas.openhistoricalmap.org/element#" rdf:about="http://www.openhistoricalmap.org/way/198179683">
		<ohmdm:createdDate>2015-03-06</ohmdm:createdDate>
		<ohmdm:latestChangeDate>2015-04-11</ohmdm:latestChangeDate>
		<ohmdm:elementType rdf:resource="http://schemas.openhistoricalmap.org/element#way"/>
		<ohmdm:osmVersion>0.6</ohmdm:osmVersion>
		<ohmdm:osm format="XML">http://www.openhistoricalmap.org/api/0.6/way/198179683</ohmdm:osm>

		<ohmdm:changeset>1141</ohmdm:changeset>

mitselek

Teenus on iseseisev HTML äpp.

Ilma sessioonita, kasutajata, andmebaasita. Peaasi, et ta kuskilt veebis kätte on saada - ntx github pages.

Teenuse poole pöördudes annab teenust kasutav keskkond (tellija) kaasa:

• teenust kasutav keskkond genereerib enda poolt allkirjastatud JWT tokeni, kuhu ta lisab endale tarviliku info, et ära tunda ja valideerida teenuse poolt kunagi hiljem saadav vastus (kasutaja, meedia ID, mida annoteeritakse, tokeni kehtivusaeg, ...)
• API URL .../api/annotate/configuration, kust teenus tirib endale konfiguratsiooni

Teenus teeb päringu GET .../api/annotate/configuration/{JWT token}

mitselek

Media-tag

An independent sessionless, userless, storageless HTML5 app for adding rich metadata to different media types. Actually any file or internet address could be annotated by this convention.

Scope

There are often situations, where some media needs to be annotated and EXIF is not really helpful because its only relevant for single picture.

• add geolocation, timestamps, links, descriptions, titles etc to media (like EXIF, but universal for all media types);
• mark regions on media;
• add multilingual subtitles to videos;
• create in-video navigation;

tomcrane

Wikimedia and IIIF

Why should Wikimedia implement IIIF? And what does that mean? There are several things they could do, some possibly quite straightforward.

Clarify two different things:

1. Bring Wikimedia assets (images, audio, video) into shared IIIF annotation space, so that they become part of the IIIF Universe, can be annotated, referenced, mashed up, reused as Presentation API
2. Allow image reuse via IIIF Image api:

• statically, via level 0 (extreme level 0) service