This is the Cloud Chapter's review of Web UI:
3D-UI (reviewed by Ken)
=====
Open Specification
-----------------------------
I suggest that you describe what the GE is about and why it is important
in the overview.
Currently the overview does not introduce the reader to the subject.
Rather it is is a background. After that a lot of details about xml
elements. It is not until the reader gets to the Generic Architecture
that the reader is introduced to what the GE is all about.
All of the technical term, e.g. WebGL XML3D, HTML5, etc. should have
hyperlinks
Is XML3D and 3D-UI GE the same thing. It is not clear from the
description?
My overall impression is that the Open Specification is unclear.
Other Links
----------------
Why no Github Repository, ReadtheDocs, Github Release
Sychronization (reviewed by Ken)
==============
Open Specification
------------------
My overall impression is that the Open Specification is well written and
thorough.
Other Links
----------- -----
Why no Github Repository, ReadtheDocs, Docker Container, Github Release?
Agmented Reality (reviewed by Ken)
================
Open Specification
-----------------------------
Add hyperlinks to HTML5, XML3D, POI Data Provider. The first time that
AR is used should contain the full name, i.e. Augemented Reality (AR).
Re-write "Especially in the case of more complex vision based techniques."
This a dangling phrase not a sentence, maybe "real-time registration and
tracking is especially problematic for complex vision based techniques".
Re-write example to contain articles before nouns: " One use-case could
be, that an AR application searches nearby restaurants from a remote
service (POI Data Provider), fetches the locations of restaurants and
displays information like restaurant menu, opening hours, user reviews and
so on.
Thrift IDL is a broken link.
My overall impression is that the Open Specification is well written and
thorough.
Other Links
-----------
Why isApiary Project N/A
Why no GitHub Repository, ReadTheDocs, Docker Container, Github Release?
Virtual Characters (Reviewed by Fernando)
================
OpenSpec
--------------
- ?Video games and film have for long used systems which provide
rendering, animation and interactions for virtual characters.? sentence is
too complex I suggest to reword but it it is not done I suggest to write
games and films.
- ?Web applications will be able to create, display and animate
virtual characters utilizing ?? I prefer use using.
- ?The characters can be composed of multiple mesh parts, to e.g.
?? why not ?The characters can be composed of multiple mesh parts (e.g.
allow easily swappable parts like upper or lower bodies and attached
objects such as clothing).
- ?The virtual character functionality is implemented as a
JavaScript library?. Is IMPLEMENTED !!! This is a Generic Enabler
specification something like implementation or specific language
programming should not be here.
- ?The 3D-UI GE (which in turn uses the WebGL API)??. This
sentence is too long, I suggest to reword it. I do not understand the
concepts of Entity-Component-Attribute based scene model, the hierarchical
transformation graph and implementing the actual rendering if I read first
time this sentence. What is WebGL, it is not defined in Terms and
Definitions.
- ?This is not however required and the library can also function
in purely local mode.? Why not change it by work or run?
- ?An animatable 3D object, which may consist of one or more
triangle mesh parts? It seems that there is missing something in this
sentence.
- ?A lightweight description file utilizing JSON format, that
lists the assets (mesh parts, materials and animations) used for
instantiating a character (also referred to as an avatar) into the scene.?
Maybe you want to say ?? is used for instantiating ? ?.
- ?The file also specifies how the parts are connected.? mesh
parts?
- ?A dataset which describes the changes to individual bone
transforms over time to produce for example a walking animation.
Typically, this involves?.
- ?If two animations both try to control the same bone
simultaneously, the one with higher priority will ultimately take effect.?
What does it do the other?
- ?Animations can also be played back only in part of the bone
hierarchy, and the magnitude of their influence (i.e. blending weight)?
- ?This requires storing a larger amount of data, but can be
useful for animations where the desired result cannot?.
- ?This GE is implemented as a JavaScript library, which can be
divided into the following parts? Idem previously.
- ?Character description file parser.?
- ?Helper functions.?
?Real-Virtual Interaction refers to Augmented Reality setup that
additionally allow users to interact with real-world objects through
virtual proxies in the scene that monitor and visualize the state in the
real-world and that can use services to change the state of the real world
(e.g. switch lights on and off via a virtual button the 3D scene).?
Sentence is too long.
- ?A Scene refers to a collection of objects, which are be
identified by type (e.g. a 3D mesh object, a physics simulation rigid
body, or a script object.).?
- ?In the context of middleware, it refers to the ability?
?Synchronization is the act of transmitting over a network protocol the
changes in a scene to participants so that they share a common, real-time
perception of the scene. This is crucial to e.g. implementing multi-user
virtual worlds.?
- ?It contains data such as the name of a variable?
- ?that can be moved and animated and can represent a user's
presence?
API Specification
-----------------------
- This not follow the defined FIWARE document for APIs style, I
mean it was not generated through Fabre tool.
- It is not a Rest interface, just a function call description.
- Is there no operation related to Placeable or Mesh?
- The javascript methods does not return any value?
- Missing examples of use and definition of some variable types.
- I cannot see the relationship between Placeable, Mesh,
AnimationController and Avatar with this description.
- ?Animations are referred to with their string names.? I
assume/suppose that they are the ones defined in the character description
file under animations but it should be clarify. In the same line, I assume
that it is the value of parameter ?name?.
APIARY project
----------------------
- There is not apiary project. It was marked in Release R5 as
N/A, I do not have information to check if it is correct or not.
GIS Data Provider (Henar)
==============
Open Specification: It seems to be ok.
API Specification: It seems to be ok
Apiari project: There is not apiary project in the page, but I found
http://docs.gisdataprovider.apiary.io. Please update the page with the
link..
POI Data Provider (reviewed by Henar)
===============
Open Specification: It seems to be ok
API Specification: There is not api specification. Please, generate the
specification with Apiary Blueprints format, generate the HTML pages by
using Fabre tool and upload it to gh-pages branch.
Apiari project. It seems to be ok
InterfaceDesigner (reviewed by Alvaro)
================
- Link to chapter (Advanced Web-based User Interfaces) is broken.
- Links to owners are broken
- Link to "Scene and EC model? in section ?Overview? is broken
- Link to "Scene and EC model? in section ?Main Interactions? is broken
- Section "Detailed Specifications? doesn?t exist. If this not apply for
the GE, this should be pointed out.
CloudRendering (Alvaro)
=============
- Link to chapter (Advanced Web-based User Interfaces) is broken.
- Links to owners are broken
- Section "Detailed Specifications? is empty. If this not apply for the
GE, this should be pointed out.
Best Regards,
Kenneth Nagin
Ph: +972-4-8296227
Cell: 054-6976227
Fx: +972-4- 8296114
http://researcher.ibm.com/view.php?person=il-NAGIN
From: MIGUEL CARRILLO PACHECO <miguel.carrillopacheco at telefonica.com>
To: "fiware-chapter-leaders at lists.fiware.org"
<fiware-chapter-leaders at lists.fiware.org>
Cc: JOSE MANUEL CANTERA FONSECA
<josemanuel.canterafonseca at telefonica.com>,
"fiware-chapter-architects at lists.fiware.org"
<fiware-chapter-architects at lists.fiware.org>, JUAN JOSE HIERRO SUREDA
<juanjose.hierrosureda at telefonica.com>
Date: 19/08/2016 01:52 PM
Subject: [Fiware-chapter-leaders] R5 Open Specs: next steps
Sent by: fiware-chapter-leaders-bounces at lists.fiware.org
Dear all,
The Open Specs should be ready by now. We need to start the review cycle
as agreed in a coordination call. Note that:
Each chapter leader decides whether to distribute it internally or to do
it himself. No excuses: if someone is on holidays, he will have to assign
it to someone else or do it himself
This has 3 parts: Open Specification, API Specification and Apiari
project.
We agreed on having cross reviews so here we go. We will do this:
19/Aug - 26/Aug - cross chapter reviews . On 26/8 the review report should
be sent - with 3 parts per GE: Open Specification, API Specification and
Apiari project
26/Aug - 31/Aug - changes from GE owner after receiving the reviews
1/Sept - 7/Sept - review from the coordinator
Assignments: (to be completed as the chapters are ready)
WebUi reviews Cloud
Cloud reviews WebUI
Assignments pending: Security, Data, Apps, IoT , I2ND (we will do it as
they deliver)
Note that the GE template was broken (an unintentional edit from a wiki
user) and it was impossible to add the ApIary links. This is fixed now,
please those who have already delivered take a look and put the right
APIary links.
Note that this message is for the coordinators only, to allow you to
coordinate things internally in the way that you prefer.
Actions:
1) Fix the APIary links those who already provided the info of the
delivery
2) Organize internally in your chapters to do this
3) Those who have not delivered yet: please do so
Regards
Miguel
--
Please update your address book with my new e-mail address:
miguel.carrillopacheco at telefonica.com
----------------------------------------------------------------------
_/ _/_/ Miguel Carrillo Pacheco
_/ _/ _/ _/ Telefónica Distrito Telefónica
_/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 6
_/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N
_/ _/_/ 28050 Madrid (Spain)
Tel: (+34) 91 312 94 15
e-mail: miguel.carrillopacheco at telefonica.com
Follow FIWARE on the net
Website: http://www.fiware.org
Facebook: https://www.facebook.com/eu.fiware
Twitter: http://twitter.com/Fiware
LinkedIn: https://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
puede contener información privilegiada o confidencial y es para uso
exclusivo de la persona o entidad de destino. Si no es usted. el
destinatario indicado, queda notificado de que la lectura, utilización,
divulgación y/o copia sin autorización puede estar prohibida en virtud de
la legislación vigente. Si ha recibido este mensaje por error, le rogamos
que nos lo comunique inmediatamente por esta misma vía y proceda a su
destrucción.
The information contained in this transmission is privileged and
confidential information intended only for the use of the individual or
entity named above. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have received
this transmission in error, do not read it. Please immediately reply to
the sender that you have received this communication in error and then
delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário,
pode conter informação privilegiada ou confidencial e é para uso exclusivo
da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário
indicado, fica notificado de que a leitura, utilização, divulgação e/ou
cópia sem autorização pode estar proibida em virtude da legislação
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o
comunique imediatamente por esta mesma via e proceda a sua destruição
_______________________________________________
Fiware-chapter-leaders mailing list
Fiware-chapter-leaders at lists.fiware.org
https://lists.fiware.org/listinfo/fiware-chapter-leaders
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-cloud/attachments/20160907/2a2d25e5/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy