ISSUE-24: clarification of lightweight APIs requirement

clarification of lightweight APIs requirement

State:
CLOSED
Product:
Use Cases and Requirements
Raised by:
Frans Knibbe
Opened on:
2015-06-10
Description:
The "lightweight API" requirement could do with some clarification. The current phrasing is "A lightweight API is needed for implementation on Internet of Things (IoT) devices."

Questions:
1) If this requirement is only about the IoT, shouldn't this be reflected in the title?
2) Exactly what needs to be implemented? What should the API make possible? Does this requirement want a new API? Or adaptation of existing API's? If so, which existing API's should be adapted?
3) Current phrasing looks like it incorporates a solution to a problem (something needs to be implemented on IoT devices). Could the requirement be rephrased to describing needs?
4) Is this asking for a subset of SSN (a profile) that can be implemented on IoT devices?

Related Actions Items:
Related emails:
  1. Re: Wanted: feedback on UCR requirements (from bill@swirrl.com on 2016-08-16)
  2. Re: Wanted: feedback on UCR requirements (from frans.knibbe@geodan.nl on 2016-08-16)
  3. Re: Wanted: feedback on UCR requirements (from bill@swirrl.com on 2016-08-15)
  4. Re: Wanted: feedback on UCR requirements (from frans.knibbe@geodan.nl on 2016-08-15)
  5. Re: Wanted: feedback on UCR requirements (from frans.knibbe@geodan.nl on 2016-07-25)
  6. Re: Wanted: feedback on UCR requirements (from matthew.perry@oracle.com on 2016-07-14)
  7. Re: Wanted: feedback on UCR requirements (from frans.knibbe@geodan.nl on 2016-07-14)
  8. Re: Wanted: feedback on UCR requirements (from j.d.blower@reading.ac.uk on 2016-07-14)
  9. Re: Wanted: feedback on UCR requirements (from frans.knibbe@geodan.nl on 2016-07-14)
  10. Re: Wanted: feedback on UCR requirements (from matthew.perry@oracle.com on 2016-07-13)
  11. Re: Wanted: feedback on UCR requirements (from j.d.blower@reading.ac.uk on 2016-07-13)
  12. [Minutes-SSN] 2016-07-12 (from phila@w3.org on 2016-07-13)
  13. Re: Wanted: feedback on UCR requirements (from frans.knibbe@geodan.nl on 2016-07-13)
  14. Re: UCR issue-20 and issue-24 (from frans.knibbe@geodan.nl on 2016-07-13)
  15. RE: UCR issue-20 and issue-24 (from kerry.taylor@anu.edu.au on 2016-07-13)
  16. Re: UCR issue-20 and issue-24 (from frans.knibbe@geodan.nl on 2016-07-13)
  17. UCR issue-20 and issue-24 (from kerry.taylor@anu.edu.au on 2016-07-12)
  18. RE: Wanted: feedback on UCR requirements (from l.vandenbrink@geonovum.nl on 2016-07-12)
  19. [sdw] ssn meeting this week (from kerry.taylor@anu.edu.au on 2016-07-11)
  20. Re: Wanted: feedback on UCR requirements (from frans.knibbe@geodan.nl on 2016-07-11)
  21. RE: Wanted: feedback on UCR requirements (from Simon.Cox@csiro.au on 2016-07-08)
  22. RE: Wanted: feedback on UCR requirements (from chris.little@metoffice.gov.uk on 2016-07-07)
  23. Re: Wanted: feedback on UCR requirements (from frans.knibbe@geodan.nl on 2016-07-07)
  24. RE: Wanted: feedback on UCR requirements (from chris.little@metoffice.gov.uk on 2016-07-07)
  25. Re: Wanted: feedback on UCR requirements (from bill@swirrl.com on 2016-07-06)
  26. Re: Wanted: feedback on UCR requirements (from frans.knibbe@geodan.nl on 2016-07-06)
  27. [Minutes] 2015-11-11 (from phila@w3.org on 2015-11-11)
  28. UCR ISSUE-24: clarification of lightweight APIs requirement (from frans.knibbe@geodan.nl on 2015-10-08)
  29. Re: Frozen copy? (from frans.knibbe@geodan.nl on 2015-06-10)

Related notes:

[frans]: SSN

11 Nov 2015, 20:16:25

The phrasing of the requirement was changed.

Frans Knibbe, 13 Jul 2016, 11:55:26

Display change log ATOM feed


Ed Parsons <eparsons@google.com>, Kerry Taylor <kerry.taylor@anu.edu.au>, Chairs, Fran├žois Daoust <fd@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $