W3C home > Mailing lists > Public > public-sdw-wg@w3.org > October 2016

SSN namespace (was Re: phil! Question please!)

From: Kerry Taylor <kerry.taylor@anu.edu.au>
Date: Tue, 11 Oct 2016 22:17:31 +0000
To: "public-sdw-wg@w3.org" <public-sdw-wg@w3.org>
Message-ID: <PS1PR06MB1740A9DE796D9DE08B4CAD04A4DA0@PS1PR06MB1740.apcprd06.prod.outlook.com>
Reposting as people seem to have missed it in the meeting today.

-----Original Message-----
From: Phil Archer [mailto:phila@w3.org] 
Sent: Thursday, 6 October 2016 8:23 PM
To: Kerry Taylor <kerry.taylor@anu.edu.au>
Cc: SDW WG Public List <public-sdw-wg@w3.org>
Subject: SSN namespace (was Re: phil! Question please!)

cc our public list.

On 06/10/2016 05:19, Kerry Taylor wrote:
> Phil,
> Re "implementation" for ontologies.
>
> Say we are using this namespace for ssn: http://www.w3.org/ns/ssn/.  (and I think we are).
> This is a new namespace.  There are almost  zero implementations for ssn terms in this namespace out there in the world.
>
> Am I right in thinking that implementations of  ssn terms of this namespace: http://purl.oclc.org/NET/ssnx/ssn#Section_Skeleton  , (and otherwise all aspects of the terms are  unchanged ) count as implementation in the new namespace  for the purposes of our rec track work?

I don't think that would fly with the Director, no. New namespace - new terms, new implementations needed - BUT! - don't panic.

>
> If I am wrong, then this might  create a big issue for us --- and , I 
> suspect, forces us to stick to purl, despite the obvious attraction of 
> : http://www.w3.org/ns/ssn/

>
> Which means I need to know more about how purl is dying - I have only heard this from you- but I would like to know more..

purl.org is back up and running as the news item you found describes. 
This is good news and means that the option of retaining the old namespace is real and OK. The existing redirection is in place and functional. We can edit the pages to which it redirects as well as the redirection that takes place on our side.

But...

Now that you can, you might want to redirect the old purls to the new namespace. You can then declare, say,

http://purl.oclc.org/NET/ssnx/ssn#FeatureOfInterest owl:equivalentClass http://www.w3.org/ns/ssn/FeatureOfInterest


and so on. That gives you a path to:
- using the new namespace;
- retaining implementation evidence from previous work.

But you would need to copy the whole of the old to the new, marking deprecated terms etc.

>
> All I can find is this on Wikipedia (which is very fresh!):
>
> On 27th September 2016 OCLC announced<http://www.oclc.org/news/releases/2016/201623dublin.en.html> a cooperation with the Internet Archive<https://en.wikipedia.org/wiki/Internet_Archive> resulting in the transfer of the resolver service and its administration interface to Internet Archive. This service is supported on newly created software, separate from all previous implementations. This transfer reenabled the ability manage PURL definitions that had been disabled in the OCLC hosted service for several months. This service hosted on Internet Archive Servers supports access via purl.org<http://purl.org/>, purl.net<http://purl.net/>, purl.info<http://purl.info/>, and purl.com<http://purl.com/>. OCLC are now redirecting DNS requests for purl.oclc.org<http://purl.oclc.org/> to purl.org<http://purl.org/>.
>
>
> I *think* this issue does not matter for owl-time as its namespace is unchanging, right?   http://www.w3.org/2006/time# If so, then the namespace document that has been sitting there all these years *will* have to change though (echoes of a TPAC meeting in which I may have cut off my nose to... But I was thinking recommendations then).  But I think this is ok. And all those existing implementations in the wild can be used.

Yep, OWL Time is staying put AFAIK.

HTH

Phil.

>
> Advice please!
> (Feel free to post to the group - including this - as you wish) Kerry
>

-- 


Phil Archer
W3C Data Activity Lead
http://www.w3.org/2013/data/


http://philarcher.org

+44 (0)7887 767755
@philarcher1
Received on Tuesday, 11 October 2016 22:18:08 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:31:26 UTC