h i g h l i g h t s Fuel potential was enhanced via hydrothermal carbonization and torrefaction. ... more h i g h l i g h t s Fuel potential was enhanced via hydrothermal carbonization and torrefaction. Hydrochar performed better than torrefied bamboo produced at the same temperature. Hydrophobicity was obtained at higher treating temperature. Removal of hemicellulose was the dominant reaction in hydrothermal carbonization. 260°C was determined to be suitable for hydrochar production.
... ONEKIN Research Group, University of the Basque Country, San Sebastián, Spain sandy-perez@ika... more ... ONEKIN Research Group, University of the Basque Country, San Sebastián, Spain [email protected], {oscar.diaz,inaki.paz}@ehu.es http://www.onekin.org Abstract. ... Raposo, J., ´Alvarez, M., Losada, J., Pan, A.: Maintaining web navigation flows for wrappers. ...
RESTful Web services have opened the door to clients to use Web sites in ways the original design... more RESTful Web services have opened the door to clients to use Web sites in ways the original designers never imagined giving rise to the mashup phenomenon. The main advantage of the model based approach in Web engineering is that the models specify sort of contract the Web application adheres to and promises to deliver. Similarly, in RESTful scenario, mashup components responsible for delivering composite functionalities out of RESTful components could benefit from such contracts in search, automatic mashup, and other scenarios. Such scenarios ground the need for taking RESTful Web services in existing Web methods. This paper proposes the Application Facade Component Model in existing Web methods to support RESTful, resource-oriented architectures generation. Amazon Simple Storage Service is used as the running example and proof of concept to show advantages of such approach.
2008 Eighth International Conference on Web Engineering, 2008
Traditionally, Web applications have had great limitations in the usability and interactivity of ... more Traditionally, Web applications have had great limitations in the usability and interactivity of their user interfaces. To overcome these limitations, a new type of Web applications called Rich Internet Applications (RIAs) has recently appeared providing richer and more efficient graphical components similar to desktop applications. However, RIAs are rather complex and their development requires the designing and implementation tasks which are time-consuming and error-prone. Moreover, RIA development is a new challenge for the Web engineering methodologies requiring their modification and the introduction of other concerns. In this context, we propose a new approach called OOH4RIA which proposes a modeldriven development process that extends OOH methodology. It introduces new structural and behavioural models in order to represent a complete RIA and to apply transformations that reduce the effort and accelerate its development. This RIA will be implemented on the promising Google Web Toolkit (GWT) framework.
Proceedings of the 16th international conference on World Wide Web, 2007
Portlets strive to play at the front end the same role that Web services currently enjoy at the b... more Portlets strive to play at the front end the same role that Web services currently enjoy at the back end, namely, enablers of application assembly through reusable services. However, it is wellknown in the component community that, the larger the component, the more reduced the reuse. Hence, the coarse-grained nature of portlets (they encapsulate also the presentation layer) can jeopardize this vision of portlets as reusable services. To avoid this situation, this work proposes a perspective shift in portlet development by introducing the notion of Consumer Profile. While the user profile characterizes the end user (e.g. age, name, etc), the Consumer Profile captures the idiosyncrasies of the organization through which the portlet is being delivered (e.g. the portal owner) as far as the portlet functionality is concerned. The user profile can be dynamic and hence, requires the portlet to be customized at runtime. By contrast, the Consumer Profile is known at registration time, and it is not always appropriate/possible to consider it at runtime. Rather, it is better to customize the code at development time, and produce an organization-specific portlet which built-in, custom functionality. In this scenario, we no longer have a portlet but a family of portlets, and the portlet provider becomes the "assembly line" of this family. This work promotes this vision by introducing an organization-aware, WSRP-compliant architecture that let portlet consumers registry and handle "family portlets" in the same way that "traditional portlets". In so doing, portlets are nearer to become truly reusable services.
A corporate portal supports a community of users on cohesively managing a shared set of resources... more A corporate portal supports a community of users on cohesively managing a shared set of resources. Such management should also include social tagging, i.e. the practice of collaboratively creating and managing tags to annotate and categorize content. This task involves to know both what to tag (hence, the rendering of the resource content) and how to tag (i.e. the tagging functionality itself). Traditionally both efforts are accomplished by the same application (Flickr is a case in point). However, portals decouple these endeavours. Tagging functionality is up to the portal, but content rendering can be outsourced to thirdparty applications: the portlets. Portlets are Web applications that transparently render their markup through a portal. The portal is a mere conduit for the portlet markup, being unaware of what this markup conveys. This work addresses how to make portlets tagging-aware, i.e. portlets that can be seamlessly plugged into the portal tagging infrastructure. The main challenge rests on consistency at both the back-end (i.e. use of a common structure for tagging data, e.g. a common set of tags), and the front-end (i.e. tagging interactions to be achieved seamlessly across the portal using similar rendering guidelines). Portlet events and RDFa annotations are used to meet this requirement. A running example in WebSynergy illustrates the feasibility of the approach.
h i g h l i g h t s Fuel potential was enhanced via hydrothermal carbonization and torrefaction. ... more h i g h l i g h t s Fuel potential was enhanced via hydrothermal carbonization and torrefaction. Hydrochar performed better than torrefied bamboo produced at the same temperature. Hydrophobicity was obtained at higher treating temperature. Removal of hemicellulose was the dominant reaction in hydrothermal carbonization. 260°C was determined to be suitable for hydrochar production.
... ONEKIN Research Group, University of the Basque Country, San Sebastián, Spain sandy-perez@ika... more ... ONEKIN Research Group, University of the Basque Country, San Sebastián, Spain [email protected], {oscar.diaz,inaki.paz}@ehu.es http://www.onekin.org Abstract. ... Raposo, J., ´Alvarez, M., Losada, J., Pan, A.: Maintaining web navigation flows for wrappers. ...
RESTful Web services have opened the door to clients to use Web sites in ways the original design... more RESTful Web services have opened the door to clients to use Web sites in ways the original designers never imagined giving rise to the mashup phenomenon. The main advantage of the model based approach in Web engineering is that the models specify sort of contract the Web application adheres to and promises to deliver. Similarly, in RESTful scenario, mashup components responsible for delivering composite functionalities out of RESTful components could benefit from such contracts in search, automatic mashup, and other scenarios. Such scenarios ground the need for taking RESTful Web services in existing Web methods. This paper proposes the Application Facade Component Model in existing Web methods to support RESTful, resource-oriented architectures generation. Amazon Simple Storage Service is used as the running example and proof of concept to show advantages of such approach.
2008 Eighth International Conference on Web Engineering, 2008
Traditionally, Web applications have had great limitations in the usability and interactivity of ... more Traditionally, Web applications have had great limitations in the usability and interactivity of their user interfaces. To overcome these limitations, a new type of Web applications called Rich Internet Applications (RIAs) has recently appeared providing richer and more efficient graphical components similar to desktop applications. However, RIAs are rather complex and their development requires the designing and implementation tasks which are time-consuming and error-prone. Moreover, RIA development is a new challenge for the Web engineering methodologies requiring their modification and the introduction of other concerns. In this context, we propose a new approach called OOH4RIA which proposes a modeldriven development process that extends OOH methodology. It introduces new structural and behavioural models in order to represent a complete RIA and to apply transformations that reduce the effort and accelerate its development. This RIA will be implemented on the promising Google Web Toolkit (GWT) framework.
Proceedings of the 16th international conference on World Wide Web, 2007
Portlets strive to play at the front end the same role that Web services currently enjoy at the b... more Portlets strive to play at the front end the same role that Web services currently enjoy at the back end, namely, enablers of application assembly through reusable services. However, it is wellknown in the component community that, the larger the component, the more reduced the reuse. Hence, the coarse-grained nature of portlets (they encapsulate also the presentation layer) can jeopardize this vision of portlets as reusable services. To avoid this situation, this work proposes a perspective shift in portlet development by introducing the notion of Consumer Profile. While the user profile characterizes the end user (e.g. age, name, etc), the Consumer Profile captures the idiosyncrasies of the organization through which the portlet is being delivered (e.g. the portal owner) as far as the portlet functionality is concerned. The user profile can be dynamic and hence, requires the portlet to be customized at runtime. By contrast, the Consumer Profile is known at registration time, and it is not always appropriate/possible to consider it at runtime. Rather, it is better to customize the code at development time, and produce an organization-specific portlet which built-in, custom functionality. In this scenario, we no longer have a portlet but a family of portlets, and the portlet provider becomes the "assembly line" of this family. This work promotes this vision by introducing an organization-aware, WSRP-compliant architecture that let portlet consumers registry and handle "family portlets" in the same way that "traditional portlets". In so doing, portlets are nearer to become truly reusable services.
A corporate portal supports a community of users on cohesively managing a shared set of resources... more A corporate portal supports a community of users on cohesively managing a shared set of resources. Such management should also include social tagging, i.e. the practice of collaboratively creating and managing tags to annotate and categorize content. This task involves to know both what to tag (hence, the rendering of the resource content) and how to tag (i.e. the tagging functionality itself). Traditionally both efforts are accomplished by the same application (Flickr is a case in point). However, portals decouple these endeavours. Tagging functionality is up to the portal, but content rendering can be outsourced to thirdparty applications: the portlets. Portlets are Web applications that transparently render their markup through a portal. The portal is a mere conduit for the portlet markup, being unaware of what this markup conveys. This work addresses how to make portlets tagging-aware, i.e. portlets that can be seamlessly plugged into the portal tagging infrastructure. The main challenge rests on consistency at both the back-end (i.e. use of a common structure for tagging data, e.g. a common set of tags), and the front-end (i.e. tagging interactions to be achieved seamlessly across the portal using similar rendering guidelines). Portlet events and RDFa annotations are used to meet this requirement. A running example in WebSynergy illustrates the feasibility of the approach.
Uploads
Papers by Sandy Perez