- From: Raphaël Troncy <raphael.troncy@eurecom.fr>
- Date: Thu, 23 Feb 2017 09:18:43 +0100
- To: Armin Haller <armin.haller@anu.edu.au>, "public-sdw-wg@w3.org" <public-sdw-wg@w3.org>
> Yes, your interpretation is correct. Were confused about the term “extension”? Any suggestions to change that name to make it clearer? Module? I would propose to rename: "2: One unified namespace and a separate extension namespace for terms only defined in SSN. Use of equivalent class and equivalent property relations in SSN to SOSA terms" by: "2: One unified namespace and a separate module namespace ONLY for terms that are further axiomitized in SSN. Use of equivalent class and equivalent property relations in SSN to SOSA terms" > You can get the terms that are only defined in the core, because mechanically we would do the same on the server Maxime proposed for Option 2 in the NamespaceIssue. Every term that is defined in the core, when put in the browser, will lead to the core, i.e. unify:Platform will give you SOSA. Any other term that is defined in SOSA will give you SOSA. Only terms that are defined under the extension URI in SSN will give you SSN. OK, but this means, I have to dereference each term to see whether it is a CORE term or not and I cannot simply rely on the "unify" namespace (per definition of unify). I think this should be written as an implication. Best regards. Raphaël -- Raphaël Troncy EURECOM, Campus SophiaTech Data Science Department 450 route des Chappes, 06410 Biot, France. e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com Tel: +33 (0)4 - 9300 8242 Fax: +33 (0)4 - 9000 8200 Web: http://www.eurecom.fr/~troncy/
Received on Thursday, 23 February 2017 08:19:17 UTC