<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="https://www.stress-free.co.nz"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>stressfree - caadria</title>
 <link>https://www.stress-free.co.nz/tech/caadria</link>
 <description></description>
 <language>en</language>
<item>
 <title>What is Web 2.0 again?</title>
 <link>https://www.stress-free.co.nz/what_is_web_2_0_again</link>
 <description>
  &lt;div class=&quot;field-body&quot;&gt;
      &lt;p&gt;There is a lot of talk about Web 2.0, my paper to CAADRIA even mentioned it in the title. Whether its a fad or the next big thing is fairly uncertain but it does provide a nice general purpose container for a bunch of different read/write Web concepts like blogging, tagging, and RSS. Certainly there is a lot of hype around the whole thing but as a general theme for a bunch of technologies it is pretty strong. &lt;/p&gt;  &lt;p&gt;What I do think it is achieving is the evolution of a far more conceptually and technologically richer Web space. The Web is no longer about hugely expensive and flashy billboards, tightly controlled portals or online stores with weird names. Sure all these things still exist but they are now taking second place to far more dynamic sites with their background and identity rooted firmly in the Web rather than being simply the extension of a conventional organisation&#039;s operations. Web 2.0 seems also to be more about empowering the individual to be able to do things like get their own &#039;stuff&#039; online and track/search the Web in ways that make sense to them. &lt;a href=&quot;http://www.myspace.com/&quot;&gt;MySpace&lt;/a&gt;, &lt;a href=&quot;http://www.blogger.com&quot;&gt;Blogger.com&lt;/a&gt;, &lt;a href=&quot;http://www.technorati.com/&quot;&gt;Technorati&lt;/a&gt; and &lt;a href=&quot;http://www.flickr.com&quot;&gt;Flickr&lt;/a&gt; are all successful Web 2.0 sites that have these fundamental ideas at their core. Recently Apple announced iWeb which is the first &#039;traditional&#039; application that attempts to blur the lines between &lt;a href=&quot;http://www.apple.com/ilife/iweb/&quot;&gt;the computer, the Web and your life&lt;/a&gt;.    &lt;br /&gt;&lt;/p&gt;  &lt;p&gt;Personally I agree with Jonathan Boutelle, &lt;a href=&quot;http://www.jonathanboutelle.com/mt/archives/2005/07/ajax_web_20.html&quot;&gt;AJAX is not part of Web 2.0&lt;/a&gt;. If you do not know already AJAX (or to use the proper terminology &lt;a href=&quot;http://en.wikipedia.org/wiki/AJAX&quot;&gt;Asynchronous JavaScript And XML&lt;/a&gt;) is a technique for updating a page without the user having to navigate to a different screen through a HTTP POST/GET request. The HTTP POST/GET requests still occur but in the background, usually tied to certain events on a page. AJAX provides a level of application richness that has been lacking from conventional HTML/Javascript but has always been a part of traditional programs. Consequently with its emergence we are seeing more Web applications that are mirroring the functionality of their traditional bretherin. Applications like GMail and Writely are beginning to replace Outlook and Word but this is merely a transition from an operating system based application silo to the more generic but still silo driven Web application space. &lt;/p&gt;  &lt;p&gt;Tim O&#039;Reilly has talked about the subject a lot in a couple of articles:&lt;/p&gt;  &lt;ul&gt;&lt;li&gt;&lt;a href=&quot;http://www.oreillynet.com/pub/a/oreilly/tim/news/2005/09/30/what-is-web-20.html&quot;&gt;What is Web 2.0&lt;/a&gt; &lt;/li&gt;    &lt;li&gt;&lt;a href=&quot;http://radar.oreilly.com/archives/2005/08/not_20.html&quot;&gt;Not 2.0?&lt;/a&gt;      &lt;br /&gt;&lt;/li&gt;    &lt;li&gt;&lt;a href=&quot;http://www.readwriteweb.com/archives/tim_oreilly_int.php&quot;&gt;Tim O&#039;Reilly interview about Web 2.0&lt;/a&gt;      &lt;br /&gt;&lt;/li&gt;  &lt;/ul&gt;&lt;p&gt;Plus his company helped organise a Web 2.0 Conference and many of the &lt;a href=&quot;http://www.itconversations.com/series/web2.0-2004.html&quot;&gt;presentations can be listened to on IT Conversations&lt;/a&gt;.    &lt;br /&gt;&lt;/p&gt;   &lt;/div&gt;

&lt;ul class=&quot;field-taxonomy-vocabulary-1&quot;&gt;

      &lt;li&gt;
      &lt;a href=&quot;/thesis&quot;&gt;thesis&lt;/a&gt;    &lt;/li&gt;
      &lt;li&gt;
      &lt;a href=&quot;/tech/web_2_0&quot;&gt;web 2.0&lt;/a&gt;    &lt;/li&gt;
      &lt;li&gt;
      &lt;a href=&quot;/tech/ajax&quot;&gt;ajax&lt;/a&gt;    &lt;/li&gt;
      &lt;li&gt;
      &lt;a href=&quot;/tech/caadria&quot;&gt;caadria&lt;/a&gt;    &lt;/li&gt;
  
&lt;/ul&gt;
</description>
 <pubDate>Thu, 26 Jan 2006 01:35:50 +0000</pubDate>
 <dc:creator>David</dc:creator>
 <guid isPermaLink="false">225 at https://www.stress-free.co.nz</guid>
</item>
<item>
 <title>CAADRIA 2006 Abstract Accepted</title>
 <link>https://www.stress-free.co.nz/caadria_2006_abstract_accepted</link>
 <description>
  &lt;div class=&quot;field-body&quot;&gt;
    &lt;p&gt;Recently I submitted an abstract for the &lt;a href=&quot;http://www.caadria2006.org/&quot;&gt;CAADRIA 2006 &#039;Rhythm and Harmony in the Bit-Sphere&#039;&lt;/a&gt; conference in Kumamoto, Japan. I am pleased to say the abstract was accepted so now I have the arduous task of completing a paper for submission January 21st 2006. The comments that came back were very good (compared to others I have received) and these are included below the abstract.      &lt;br /&gt;&lt;/p&gt;&lt;h2&gt;USING WEB 2.0 TECHNOLOGIES TO PRESERVE DESIGN HISTORY AND IMPROVE COLLABORATION &lt;/h2&gt;  &lt;p&gt;&lt;span style=&quot;font-weight: bold; font-style: italic&quot;&gt;Abstract.&lt;/span&gt; This paper describes ongoing research into how emerging Internet concepts used in conjunction with existing Information Technologies (IT) can improve inter-project communication and understanding. The emphasis of the research is to use technology as an enabler to share personal thoughts and enhance the conversation that takes place within a development team. It stems from the observation that the emphasis of many new Architecture, Engineering and Construction (AEC) technologies is to minimise and diffuse project conversation with highly complex, machine interpretable building information models.&lt;/p&gt;  &lt;p&gt;Conversation and collaboration play a crucial role within the Architecture, Engineering and Construction (AEC) industry. No matter the technology employed, without effective communication or understanding of design issues as conveyed by the client the chances of successfully meeting project objectives are severely handicapped (Barrett, Hudson and Stanley, 1996). Currently there is no simple, transparent way of documenting, reviewing and searching this conversation throughout the lifecycle of a project. Consequently information about design decisions and issues are lost as development responsibilities shift between groups who maintain different objectives within a project.&lt;/p&gt;  &lt;p&gt;Although the AEC industry has proven slow to adopt new process enhancing technologies it has been very swift in accepting email as a means of communication (Swee-Lean and Nga Na, 2004). More complex collaboration technologies ranging from the Building Information Model to project Intranets have struggled to gain the same level of acceptance even though research by Arayici and Aouad (2004) and Al-Reshaid (1999) has shown many benefits in their respective adoption. A factor identified by Anumba (1998) for this slow adoption is the limited time and financial resources available within AEC organizations to retrain staff and change internal and external collaboration processes.&lt;/p&gt;  &lt;p&gt;Project teams are usually brought together for a relatively short but intense period of time. Following project completion these unique teams are dissolved just as quickly and often are never formed again. As a consequence it is difficult to justify the investment in time and resources required to implement complex IT-based collaboration solutions. A further barrier to adoption is the differential application of IT skills across the AEC industry. Therefore in order for a new technology to gain broad acceptance and be most beneficial it must be applicable to the broadest audience with the minimum investment required from all parties.&lt;/p&gt;  &lt;p&gt;Web 2.0 is the name given to a series of new technology concepts that are profoundly affecting the way users are experiencing the Internet (Hammersley, 2005). Web 2.0 technologies like Really Simple Syndication (RSS), ‘blogging’ and ‘tagging’ focus on the creation of social networks and place an emphasis on actively sharing data. A key reason these technologies are being adopted very quickly is because just like email they are simple to understand and implement (Bosworth, 2004). This paper proposes a distributed Web 2.0 technology framework that works with the email and Internet tools already available to store, track and search for design decisions and communication. Through the reutilization of existing tools a user familiarity is maintained and the cost of entry for participants in this conversation is significantly reduced.&lt;/p&gt;  &lt;p&gt;The primary objective of this research is to preserve the rich design history of a project from conception to completion. Submitted information can be intelligently searched using the meta-data sourced from syndicated data feeds about team members, project timelines, work diaries and email communication. Once indexed users can tag documents and messages in order to provide a further, far richer layer of meta-data to assist in searching, identification of issues and semantic identification. This strategy of defining AEC semantics through social interaction differs greatly from that of more complex, computer interpretable solutions such as Industry Foundation Classes (Wix and Liebich, 2001). Rather than abstracting information to suit a generic yet highly intelligent building model, the emphasis is on preserving the participant’s own thoughts and conversation about decisions and issues in order to create a forum for intelligent conversation as the design evolves. &lt;/p&gt;  &lt;h4&gt;References&lt;/h4&gt;  &lt;p&gt;Al-Reshaid K., Kartam, N.: 1999, Improving Construction Communication: The Impact of the On-Line Technology, W78: Information Technology in Construction, Vancouver, Canada.    &lt;br /&gt;Anumba, C.J.: 1998, Industry Uptake of Construction Innovations – Key Elements of a Proactive Strategy, W78: The Life-Cycle of Construction IT Innovations, Stockholm, Sweden.    &lt;br /&gt;Arayici Y., Aouad G.: 2004, Requirements Engineering Process in the CIC Development: The Divercity Project Case Study, proceedings from the 1st International SCRI Symposium, Salford, United Kingdom. Pp 169-181.    &lt;br /&gt;Barrett, P.S., Hudson, J., Stanley, C.: Is Briefing Innovation? Proceedings of CIB W65 Symposium. Glasgow, United Kingdom.    &lt;br /&gt;Bosworth, A.: 2004, transcript of presentation, International Conference on Service Oriented Computing, New York, USA. &lt;a href=&quot;http://www.adambosworth.net/archives/000031.html&quot;&gt;http://www.adambosworth.net/archives/000031.html&lt;/a&gt;    &lt;br /&gt;Hammersley, B.: 2005, Developing Feeds with RSS and Atom, O’Reilly Media, California, USA. Pp 5.    &lt;br /&gt;Swee-Lean, C., Nga-Na, L.: 2004, State-of-the-Art Internet Technology in Singapore’s Construction Industry: The Impact of the On-Line Technology, CIB: Construction IT Bridging the Distance, Auckland, New Zealand. Pp 378-386.    &lt;br /&gt;Wix J. &amp;amp; Liebich T.: 2001. Industry Foundation Classes Ifc 2x,    &lt;br /&gt;&lt;a href=&quot;http://www.iai-international.org/Model/documentation/IFC_2x_Technical_Guide.pdf&quot;&gt;http://www.iai-international.org/Model/documentation/IFC_2x_Technical_Guide.pdf&lt;/a&gt;    &lt;br /&gt;&lt;br /&gt;&lt;/p&gt;  &lt;h2&gt;Reviewer Comments&lt;/h2&gt;  &lt;p&gt;Good idea seemingly well thought out. Broadly applicable. What it needs, however, is an example or case study - not as the end or goal of the paper - but as an illustration of the efficacy of the process(es) described.    &lt;br /&gt;&lt;/p&gt;  &lt;hr style=&quot;width: 100%; height: 2px&quot; /&gt;&lt;p&gt; &lt;/p&gt;  &lt;p&gt;This is well presented perspective about limitations on the technology for collaborative work. It justifies the authors&#039; efforts, although the abstract isn&#039;t entirely clear about the essential advantages of the authors approach nor does it provide any metrics to evaluate their findings. Will they really overcome the inherent in-practice limitations to such collaborative systems reducing time and cost and providing greater ease for handling the complex management of information? Have past models failed to grasp the nature of the communications needed? Can some abstract meta-data model capture this effectively? Hasn&#039;t this been the objective of such efforts to date? Perhaps these are issues to be more fully addressed in a final revision of the paper, the premise of which looks quite reasonable.    &lt;br /&gt;&lt;/p&gt;  &lt;hr style=&quot;width: 100%; height: 2px&quot; /&gt;&lt;p&gt; &lt;/p&gt;  &lt;p&gt;The research correctly identifies limited time and financial resources in hampering the acquistion of process enhancing technologies. It makes sense to use Web 2 technologies in this context, however, many of the examples cited in paragraph four of the abstract are quite generic. It will help if this presentation is illustrated with a technology demonstrator or nomenclatures showing the specific ways in which Web 2 technologies can be used by AEC industry.    &lt;br /&gt;&lt;/p&gt;  &lt;p&gt; &lt;/p&gt;   &lt;/div&gt;

&lt;ul class=&quot;field-taxonomy-vocabulary-1&quot;&gt;

      &lt;li&gt;
      &lt;a href=&quot;/thesis&quot;&gt;thesis&lt;/a&gt;    &lt;/li&gt;
      &lt;li&gt;
      &lt;a href=&quot;/tech/web_2_0&quot;&gt;web 2.0&lt;/a&gt;    &lt;/li&gt;
      &lt;li&gt;
      &lt;a href=&quot;/tech/caadria&quot;&gt;caadria&lt;/a&gt;    &lt;/li&gt;
      &lt;li&gt;
      &lt;a href=&quot;/tech/concept&quot;&gt;concept&lt;/a&gt;    &lt;/li&gt;
      &lt;li&gt;
      &lt;a href=&quot;/tech/abstract&quot;&gt;abstract&lt;/a&gt;    &lt;/li&gt;
  
&lt;/ul&gt;
</description>
 <pubDate>Mon, 12 Dec 2005 08:27:57 +0000</pubDate>
 <dc:creator>David</dc:creator>
 <guid isPermaLink="false">180 at https://www.stress-free.co.nz</guid>
</item>
</channel>
</rss>
