[Fiware-webui] Action Points from last WebUI Meeting

[Toni Alatalo]

Hi - checked bikeshed earlier and respec now. respec seems to be
basically about writing HTML by hand. There were several versions but
was checking this now, seemed up-to-date:
https://www.w3.org/respec/guide.html & https://github.com/w3c/respec

WebTundra dev2 branch (upcoming 2.x release) is already documented
using YUIDoc, http://yui.github.io/yuidoc/ . For example the doc/spec
source of scene.entityById() getter is
https://github.com/realXtend/WebTundra/blob/dev2/src/core/scene/Scene.js#L676
and for viewing hosted now at
http://doc.meshmoon.com/doxygen/webrocket/classes/Scene.html#method_entityById

So most convenient and I think sensible too would be to continue using
that instead of duplicating the same information as respec's HTML too.
If respec is strictly required, might make sense then to look at
automatic conversion of the YUIDoc docs to respec too for a copy. But
better if that is not needed and we can for example just push the
YUIDoc HTMLs to gh-pages, I can test that if that's seen as a good
plan.

OTOH I'm not completely sure about the scope of these specs, the
guidelines doc didn't say anything about that. W3Cs specs featured in
respec's own docs are perhaps quite different? But I figure the spec
of a js lib is the same as the public api documentation of it, or?

observations so far,
~Toni

On Thu, Aug 13, 2015 at 1:25 PM, Torsten Spieldenner
<torsten.spieldenner at dfki.de> wrote:
> Hi,
>
> as promised, here some updates about the most important points from the
> WebUI Meeting last week:
>
> FIWARE Review Feedback: Philipp sent email to mailing list last week
> Travel Reports: Was clarified that the new table, and the related mailing
> list for reports, is for activities in the scope of the new project,
> FI-CORE. Reports that were done for the previous FIWARE project are not to
> be listed there
> Open Spec APIs: We have agreed to evaluate Respec for client side API's. The
> created HTML API documents will then be uploaded to the gh-pages branch, as
> also for the Apiary documentation. The XML3D engineering team is already
> trying respec to create the updated API for XML3D 5.0. We are asked to be
> consistent w.r.t the choice of tools. Thus I would like to ask you to try
> Respec for documentation and give feedback if this is a suitable choice. If
> so, the tool may be selected to be tool of choice also for other chapters.
> Please also keep the deadlines in mind, which are already pretty close.
>
> Best,
> Torsten
>
> --
> Torsten Spieldenner, M.Sc.
>
> Tel.: +49 6 81 / 8 57 75 - 77 48
> Fax.: +49 6 81 / 8 57 75 - 22 35
>
> Internet: http://www.dfki.de/web/forschung/asr/
>
> -------------------------------------------------------------
> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
> Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany
>
> Geschaeftsfuehrung:
> Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
> Dr. Walter Olthoff
>
> Vorsitzender des Aufsichtsrats:
> Prof. Dr. h.c. Hans A. Aukes
>
> Amtsgericht Kaiserslautern, HRB 2313
> -------------------------------------------------------------
>
>
> _______________________________________________
> Fiware-webui mailing list
> Fiware-webui at lists.fi-ware.org
> https://lists.fi-ware.org/listinfo/fiware-webui
>