IETF Logo Mail Archive

.well-known/openorg

Christopher Gutteridge <cjg@ecs.soton.ac.uk> Thu, 14 May 2015 16:25 UTC

Return-Path: <cjg@ecs.soton.ac.uk>
X-Original-To: wellknown-uri-review@ietfa.amsl.com
Delivered-To: wellknown-uri-review@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42D8B1A8835 for <wellknown-uri-review@ietfa.amsl.com>; Thu, 14 May 2015 09:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.469
X-Spam-Level: *
X-Spam-Status: No, score=1.469 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bjrIWrtdNfpc for <wellknown-uri-review@ietfa.amsl.com>; Thu, 14 May 2015 09:25:32 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FF8F1A8834 for <wellknown-uri-review@ietf.org>; Thu, 14 May 2015 09:25:31 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id t4EGPOMl008206 for <wellknown-uri-review@ietf.org>; Thu, 14 May 2015 17:25:24 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk t4EGPOMl008206
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1431620724; bh=Vgdn+YTKDLgOSBBhZ23P7X8M/3s=; h=Date:From:MIME-Version:To:Subject:References; b=5g1njQr4BeFWTlkhEtTtehkff7AiLxuZPbt944Na03Hac0MqBQCbTDL9qblBcBnnm A7y98x5Ytanlqc9QA37mJMK9vX/INC6tzwlVHWSO7lVn6DBHoWWj0krzZ+akTklUcD gYFod4J/gHoRRvZkGvDxR3Ckwxw5zp4GF8DmKKp0=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <cjg@ecs.soton.ac.uk> with ESMTP (valid=N/A) id r4DHPO1823009870ug ret-id none; Thu, 14 May 2015 17:25:24 +0100
Received: from koosy.local ([IPv6:2001:630:d0:ed09:a4e0:ed53:d328:172d]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id t4EGPO7R011483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <wellknown-uri-review@ietf.org>; Thu, 14 May 2015 17:25:24 +0100
Message-ID: <EMEW3|848ebc8d86e8edf95d0f8fe72a1dbb56r4DHPO03cjg|ecs.soton.ac.uk|5554CC73.3010309@ecs.soton.ac.uk>
Date: Thu, 14 May 2015 17:25:23 +0100
From: Christopher Gutteridge <cjg@ecs.soton.ac.uk>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: wellknown-uri-review@ietf.org
Subject: .well-known/openorg
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-smtpf-Report: sid=r4DHPO182300987000; tid=r4DHPO1823009870ug; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
References: <5554CC73.3010309@ecs.soton.ac.uk>
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: t4EGPOMl008206
X-ECS-MailScanner: Found to be clean
X-ECS-MailScanner-From: cjg@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/wellknown-uri-review/m1ZaKGscE8Ue-F0RQQkocHy1qZk>
X-BeenThere: wellknown-uri-review@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Well-Known URI review list <wellknown-uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wellknown-uri-review/>
List-Post: <mailto:wellknown-uri-review@ietf.org>
List-Help: <mailto:wellknown-uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2015 16:25:34 -0000

Hi, we've been using the above well-known in a pilot project for open 
data autodiscovery and it seems to work well.

It's been implemented by a few UK universities already.
http://www.ox.ac.uk/.well-known/openorg
http://www.southampton.ac.uk/.well-known/openorg
http://www.sgul.ac.uk/.well-known/openorg
http://www.surrey.ac.uk/.well-known/openorg
http://www.cranfield.ac.uk/.well-known/openorg
http://hal.dmu.ac.uk/subsites/opd/dmu.ttl
https://www.cam.ac.uk/.well-known/openorg
http://www.bbk.ac.uk/.well-known/openorg

We allow an alternate option of specifying a <link rel='openorg'> 
element in the homepage. It is easier for some orgs to alter their 
template, others their webserver config.

The primary driver for this is to autodiscover open data about research 
equipment to create the website http://equipment.data.ac.uk/ but we are 
encouraging people to extend the use into other applications. The site 
http://opd.data.ac.uk/ provides documentation and tools to help people 
get it right, and http://opd.data.ac.uk/docs/auto explains how to set up 
autodiscovery.

We feel this approach is complimentary to /.well-known/void as "openorg" 
is intended to discover data about the organisation for which this is 
the homepage, and "void" is intended to discover linked datasets on a 
webserver.

It would be good to get around to formally registering the 'openorg' 
.well-known officially. We're excited about the long term possibilities.



-- 
Christopher Gutteridge -- http://users.ecs.soton.ac.uk/cjg

University of Southampton Open Data Service: http://data.southampton.ac.uk/
You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/

v2.23.0 | Report a Bug | By Email