- From: <Simon.Cox@csiro.au>
- Date: Wed, 9 Nov 2016 05:33:53 +0000
- To: <kerry.taylor@anu.edu.au>, <armin.haller@anu.edu.au>, <jano@geog.ucsb.edu>, <danh.lephuoc@tu-berlin.de>
- CC: <public-sdw-wg@w3.org>
- Message-ID: <89ffc179cbfe47c5991cf435385a41db@exch1-mel.nexus.csiro.au>
Parrot appears to have broken, and I have also failed to contact the maintainers. For ontologies hosted at def.seegrid.csiro.au I had reverted to LODE ... but currently that is not functioning either :( On naming - it always struck me that the 'N' part of SSN got left behind in what was delivered. And if we are now including samples and actuators, then the product will have drifted even further from the original intention. So it comes down to branding. I agree that SSN is a strong brand in the semantic web community. Mind you, O&M is a strong brand in the geospatial community, and in lots of operational services (though not as an 'ontology'). Since this is a joint OGC/W3C project, there is an opportunity to align the name with the product. That was why we chose one that reflected the contents, and did not preference either of the precedents. SO I would vote SOSA. Simon From: Kerry Taylor [mailto:kerry.taylor@anu.edu.au] Sent: Wednesday, 9 November 2016 12:22 PM To: Armin Haller <armin.haller@anu.edu.au>; Krzysztof Janowicz <jano@geog.ucsb.edu>; Le Phuoc, Danh <danh.lephuoc@tu-berlin.de> Cc: SDW WG Public List <public-sdw-wg@w3.org> Subject: ssn: readying for WD publication SSN EDITORS please read Please see current draft here: http://w3c.github.io/sdw/ssn/. Some of the issues still recorded there have since been resolved - and I will update to reflect that. But the REALLY BIG ISSUE is: There is NO sosa-core in that draft. To get it there, heavily marked-up with known issues we need at the very least both (a) and (b) (a) Choice of an automated documentation tool. We cannot use LODE again as extensively discussed already. This is needed for both the ssn as well as the sosa-core extensions. Someone suggested Parrot but Danh found it failed for ssn. A TopBraid tool looks nice - can we use it without hindrance?. There is a dated list here https://www.w3.org/2011/prov/wiki/Generating_HTML_documentation_of_OWL but many of these are broken. This one might work : http://code.google.com/p/co-ode-owl-plugins/wiki/OWLDoc and also here http://neon-toolkit.org/wiki/Download/2.5.2.html and here is an example https://dvcs.w3.org/hg/prov/raw-file/92862c7b2e3c/ontology/DocExamples/OWLDOC/index.html but it might be broken too. Specgen seems popular enough and this is the best version I can spot: https://smiy.wordpress.com/2010/07/13/my-specgen-version-6/ with examples there. This need not be a binding decision for the next WD (I actually think we might end up doing some stuff by hand, as Danh suggests, but I am not going to be the bunny that does that by 1 December). I can probably get hold of the stuff Laurent built for the ssn-xg but surely there must be better out there by now? Can someone point to exactly what we need, please? (b) A name for SOSA-core --- my vote: simply "ssn core" or "core". I would have all its terms in the same namespace as the rest of ssn and owl:import it into the rest of ssn ontology , but even then it needs a name for the core ontology and also an ontology iri. Even if the exact relationship is an issue, it still needs a name before WD. I will not vote in favour of a WD if we have not agreed on a name. Editors, If you are making changes to the ed draft PLEASE PLEASE PLEASE ensure you update the change history in Section B. It will be near-impossible to fill this in later on, and I am not going to attempt it. --Kerry
Received on Wednesday, 9 November 2016 05:34:44 UTC