<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by Hong Sik  Kim</title>
    <link>http://www.boxesandarrows.com/person/24936</link>
    <pubDate>Wed, 07 Jan 2009 12:07:37 GMT</pubDate>
    <description>Comments by Hong Sik  Kim</description>
    <item>
      <description>&lt;p&gt;At the end of year 2007, I had proposed a different name, Enterprise Information Architecture, from Enterprise Architecture. Today I found exactly same term, &lt;span class="caps"&gt;EIA&lt;/span&gt; in your article. And core concepts look similiar with my idea. What I am saying is that &lt;span class="caps"&gt;EIA&lt;/span&gt; could be more suitable term in stead of Enterprise Architecture. With just the Enterprise Architecture, it is very difficult to imagine that it is related with information areas. Among Enterprise, Information and Architecture, the Information is the most important thing. Therefore Information should be never omitted. But current Enterprise Architecture community seem to cause some confusion between enterprise domain and information area by using Enterprise Architecture to represent the Information Architecture.  Now I am a little bit relieved from the &lt;span class="caps"&gt;EIA&lt;/span&gt;, which is more sound usage, in my opinion. If you want more of my definition of &lt;span class="caps"&gt;EIA&lt;/span&gt;, please let me know.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/enterprise#content_31506</link>
      <guid>http://www.boxesandarrows.com/view/enterprise#content_31506</guid>
      <pubDate>Wed, 07 Jan 2009 12:07:37 GMT</pubDate>
      <author>Hong Sik  Kim</author>
    </item>
  </channel>
</rss>

