- From: Kerry Taylor <kerry.taylor@anu.edu.au>
- Date: Sun, 5 Feb 2017 10:58:43 +0000
- To: SDW WG Public List <public-sdw-wg@w3.org>
- CC: Francois Daoust <fd@w3.org>, "Kolozali, Sefki" <sefki.kolozali@kcl.ac.uk>
- Message-ID: <SYXPR01MB1536E21219611C10615820FFA4410@SYXPR01MB1536.ausprd01.prod.outlook.com>
Dear SSN-ers, One of the things we have to do before we finish up is to show how our ssn spec meets out use cases and requirements. If I recall (there was quite a bit of discussion about this) this CAN be done on the wiki, or better still it should be done inside our spec. I propose a separate section, probably tabular. Links would best be done linked to the UCR, like you can see in here, https://www.w3.org/TR/eo-qb/ and look for "CRS Definition" that anchors https://www.w3.org/TR/sdw-ucr/#CRSDefinition for example. I suggest an analysis of the UCRs would best be supported by a pointer to *where* the use case is met --- full ssn or the sosa core as appropriate and what terms are needed? - or both ssn and sosa (I suspect for most it is both)). Is anyone willing to take on the task of working on this? I am reasonably confident *most* of the UCRs are covered, while I am aware of a few that are not. @Francois - while looking at this I can see the fragment part of the urls into the UCR document do not get to the right place in the document. We are used to them not working on github instances - but shouldn't it work on these docs in TR space? You can use this as an example. https://www.w3.org/TR/sdw-ucr/#CRSDefinition Whether it works or not seems to depend on something in browser state (as it seems to be ok once navigating within the page). Or am I doing something wrong? But it does seem to work as I'd expect on at least some other TR space documents. --Kerry Dr Kerry Taylor Associate Professor (Data Science) Research School of Computer Science ANU College of Engineering and Computer Science Canberra ACT 2601 Australia +61 2 6125 8560
Received on Sunday, 5 February 2017 10:59:24 UTC