[esip-semantictech] SWEET issues?

[Simon.Cox at csiro.au]

Hi folks -

Trying to track down the current issue list relating to SWEET.
On the GitHub site I find this: https://github.com/ESIPFed/stc/issues?q=is%3Aopen but it doesn't appear to have any content-related issues yet.

For example, most of SWEET has no annotations - no labels, no comments, no definitions, no titles, etc.
So meaning has to be gleaned from the axiomatization, which is OK for a reasoner but tough on a human.
This is an overall style/practice issue, not a subject-matter-expert issue.

At what point do you expect these to be fed into the process? Is there another document collecting fine-grained issues?

Simon J D Cox
Research Scientist
Environmental Informatics
CSIRO Land and Water<http://www.csiro.au/Research/LWF>

E simon.cox at csiro.au<mailto:simon.cox at csiro.au> T +61 3 9545 2365 M +61 403 302 672
   Mail: Private Bag 10, Clayton South, Vic 3169
   Visit: Central Reception, Research Way, Clayton, Vic 3168
   Deliver: Gate 3, Normanby Road, Clayton, Vic 3168
people.csiro.au/Simon-Cox<http://people.csiro.au/Simon-Cox>
orcid.org/0000-0002-3884-3420<http://orcid.org/0000-0002-3884-3420>
researchgate.net/profile/Simon_Cox3<https://www.researchgate.net/profile/Simon_Cox3>
github.com/dr-shorthair<https://github.com/dr-shorthair>

PLEASE NOTE
The information contained in this email may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this email in error, please delete it immediately and notify the sender by return email. Thank you. To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference.

Please consider the environment before printing this email.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deltaforce.net/pipermail/esip-semanticweb/attachments/20170724/e4a9d827/attachment.html>