instruction:
In this task, you are given a paper review. Based on the review, your job is to identify language and generate "en" if the review is in English or generate "es" if the review is in Spanish. Note that URLs in the text have been replaced with [Link].
question:
RESUMEN:  El trabajo se presenta y describa la aplicación de una red social para noticias (4x4News), donde las noticias más relevantes estarán presentes (entre otras características). Esta aplicación se caracteriza por una pantalla divida en una matriz de 16x16, donde cada celda  es una noticia.   EVALUACIÓN GENERAL:  El trabajo está bien escrito y sigue un formato (casi) completamente adecuado para INFONOR. La aplicación suena interesante y potencialmente útil como un add-on para redes sociales ya comúnmente usadas (ej. Facebook).  Hay varios puntos independientes que considero que son importantes de resolver:  1) Si bien es un trabajo de ingeniería interesante, no puedo ver cuál es el aporte/contribución desde el punto científico ¿Qué se puede re-utilizar de este trabajo para un futuro trabajo científico?  2) Dado que ustedes ofrecen una aplicación, creo que es fundamental un link para (com)probar esta aplicación.  3) En mi opinión, el sitio Web [Link] se aproxima a lo propuesto por este trabajo. Estó es así, porque terra permite registro de usuarios (perfiles), comentar noticias, valorar noticias, y configurar el sitio Web para mostrar las noticias que un usuario desea.  4) Este podría ser un detalle menor, pienso que el uso de redes sociales se podría usar para algo más que solamente mostrar la noticia más importante (ej. mostrar una especie de tracking (social) de una(s) noticia(s) similar).  DETALLES MENORES:  - Al final de la introducción, el uso de BOLD no es recomendado. - “Los titulares no realizan un buen análisis”. ¿Qué es un “buen” análisis?. Durante el trabajo, se observa varios adjetivos usados de manera ambiguas y que son innecesarios (ej. “complejo proceso” en la sección 2.1). - Dentro de la sección 2: “Desarrollo”, se encuentra el trabajo relacionado (sección 2.1). Esta sección debería ser re-estructurada. - Las citas del tipo “X, y otros, AÑO” (ej. sección 2.2 “Wilson, y otros, 2014”), creo que están incorrectas. Deberían usar “et al”. - Sección 2.2, ¿la coincidencia de palabras es suficiente para decir que dos noticias son similares? Creo que un análsis más profundo es un necesario. - Explicar un poco más el concepto “bundles”. - En las referencias se usan números [1], pero en el texto no usa números. Recomiendo seguir el formato de INFONOR.
answer:
es


question:
• Los títulos no van con “.” • Resumen   o“El objetivo de este documento es intentar recolectar…” --> sugiero quitar la palabra intentar •Abstract   oRevisar la gramática ya que se encuentran falta de artículos y algunas frases mal redactadas por ejemplo:    -	The images emerging technologies -->  the images technology emerging    -	such as machine vision systems and scanning --> such as the machine vision systems and the scanning…    -	…The objective of this paper is to try to collect… --> The objective of this paper is to try to collect    -	 the state of the art processing for 3d point cloud processing, going from the filters to the segmentation --> the state of the art of  processing the 3d point for the cloud processing going from the filters to the segmentation   oTexto en general revisar la falta de acentos y las palabras duplicadas, entre otros:    -Introducción: máquinas    -Trabajo realizado:       •	…que en general, que --> segundo que sobra       •	Trabajo realizado   oSimplificación de puntos, la segunda vez que pone la referencia [3] sobra    - La primera vez que aparecen unas siglas se deben incluir su significado RANSAC?       •	Segmentación   o...Muchas investigaciones --> cuáles? Incluir referencia de ese conjunto de muchas investigaciones   oExiste la palabra convolución? En la RAE no   oPresen-tan --> presentan       • Conclusiones   oFormato de las conclusiones       •	Referencias   oCompletar la referencias: 2,3,4,5,6,7 y 11       •	El artículo se queda en una recopilación de los trabajos enfocados en filtrado y documentación de la nube de puntos, recomiendo ir más allá, esto es hacer un mapeo de los trabajos que mencionas, el primero de los de simplificación y el segundo de los de segmentación basado en las características, alcance, debilidades y oportunidades de mejora identificadas, esto para que realmente hagas una aportación con tu artículo
answer:
es


question:
This paper describes interesting and ambitious work: the automated conversion of Universal Dependency grammar structures into [what the paper calls] semantic logical form representations.  In essence, each UD construct is assigned a target construction in logical form, and a procedure is defined to effect the conversion, working ‘inside-out’ using an intermediate form to ensure proper nesting of substructures into encapsulating ones.  Two evaluations are carried out: comparing the results to gold-standard lambda structures and measuring the effectiveness of the resulting lambda expressions in actually delivering the answers to questions from two QA sets.    It is impossible to describe all this adequately in the space provided.  The authors have taken some care to cover all principal parts, but there are still many missing details.  I would love to see a longer version of the paper!  Particularly the QA results are short-changed; it would have been nice to learn which types of question are not handled, and which are not answered correctly, and why not.  This information would have been useful to gaining better insight into the limitations of the logical form representations.    That leads to my main concern/objection.  This logical form representation is not in fact a ‘real’ semantic one.                          It is, essentially, a rather close rewrite of the dependency structure of the input, with some (good) steps toward ‘semanticization’, including the insertion of lambda operators, the explicit inclusion of dropped arguments (via the enhancement operation), and the introduction of appropriate types/units for such constructions as eventive adjectives and nouns like “running horse” and “president in 2009”.  But many (even simple) aspects of semantic are either not present (at least, not in the paper) and/or simply wrong.  Missing: quantification (as in “every” or “all”); numbers (as in “20” or “just over 1000”); various forms of reference (as in “he”, “that man”, “what I said before”); negation and modals, which change the semantics in interesting ways; inter-event relationships (as in the subevent relationship between the events in “the vacation was nice, but traveling was a pain”; etc. etc.  To add them one can easily cheat, by treating these items as if they were just unusual words and defining obvious and simple lambda formulas for them.  But they in fact require specific treatment; for example, a number requires the creation of a separate set object in the representation, with its own canonical variable (allowing later text to refer to “one of them” and bind the variable properly).  For another example, Person A’s model of an event may differ from Person B’s, so one needs two representation symbols for the event, plus a coupling and mapping between them.  For another example, one has to be able to handle time, even if simply by temporally indexing events and states.  None of this is here, and it is not immediately obvious how this would be added.  In some cases, as DRT shows, quantifier and referential scoping is not trivial.    It is easy to point to missing things, and unfair to the paper in some sense; you can’t be expected to do it all.  But you cannot be allowed to make obvious errors.  Very disturbing is the assignment of event relations strictly in parallel with the verb’s (or noun’s) syntactic roles.  No-one can claim seriously that “he broke the window” and “the window broke” has “he” and “the window” filling the same semantic role for “break”.  That’s simply not correct, and one cannot dismiss the problem, as the paper does, to some nebulous subsequent semantic processing.                          This really needs adequate treatment, even in this paper.  This is to my mind the principal shortcoming of this work; for me this is the make-or-break point as to whether I would fight to have the paper accepted in the conference.  (I would have been far happier if the authors had simply acknowledged that this aspect is wrong and will be worked on in future, with a sketch saying how: perhaps by reference to FrameNet and semantic filler requirements.)                            Independent of the representation, the notation conversion procedure is reasonably clear.  I like the facts that it is rather cleaner and simpler than its predecessor (based on Stanford dependencies), and also that the authors have the courage of submitting non-neural work to the ACL in these days of unbridled and giddy enthusiasm for anything neural.
answer:

en