<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Everything Is Miscellaneous</title>
	<atom:link href="http://craigrandall.net/archives/2007/09/everything-is-miscellaneous/feed/" rel="self" type="application/rss+xml" />
	<link>http://craigrandall.net/archives/2007/09/everything-is-miscellaneous/</link>
	<description>Thoughts about software architecture, books and life</description>
	<lastBuildDate>Sat, 27 Feb 2010 19:04:38 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Adobe LiveCycle ES2 &#124; Craig's Musings</title>
		<link>http://craigrandall.net/archives/2007/09/everything-is-miscellaneous/comment-page-1/#comment-20826</link>
		<dc:creator>Adobe LiveCycle ES2 &#124; Craig's Musings</dc:creator>
		<pubDate>Mon, 05 Oct 2009 21:21:35 +0000</pubDate>
		<guid isPermaLink="false">http://craigrandall.net/archives/2007/09/everything-is-miscellaneous/#comment-20826</guid>
		<description>[...] pivoting. The task (goal) at hand is more richly represented at all times, allowing the user to pivot more effectively and efficiently and leading to better outcomes more [...]</description>
		<content:encoded><![CDATA[<p>[...] pivoting. The task (goal) at hand is more richly represented at all times, allowing the user to pivot more effectively and efficiently and leading to better outcomes more [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Document collaboration - questions</title>
		<link>http://craigrandall.net/archives/2007/09/everything-is-miscellaneous/comment-page-1/#comment-20496</link>
		<dc:creator>Document collaboration - questions</dc:creator>
		<pubDate>Wed, 13 Feb 2008 01:51:31 +0000</pubDate>
		<guid isPermaLink="false">http://craigrandall.net/archives/2007/09/everything-is-miscellaneous/#comment-20496</guid>
		<description>[...] RSS &#8592; Everything Is Miscellaneous [...]</description>
		<content:encoded><![CDATA[<p>[...] RSS &larr; Everything Is Miscellaneous [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alexandra</title>
		<link>http://craigrandall.net/archives/2007/09/everything-is-miscellaneous/comment-page-1/#comment-20361</link>
		<dc:creator>alexandra</dc:creator>
		<pubDate>Mon, 17 Sep 2007 00:30:44 +0000</pubDate>
		<guid isPermaLink="false">http://craigrandall.net/archives/2007/09/everything-is-miscellaneous/#comment-20361</guid>
		<description>Fuzzy categorization...looking forward to that. I believe there are several aspects of the problem.

First there is a need to find an easy way to manage references of how pieces of content are used together to create new content. Something like the way iLife works on Mac OS X. You are writing a text document in Pages, bring up the media browser, drag-&amp;-drop a photo and the use of it in that particular document is stored globally. That way it is easy to see in what documents (and in essence context) this image is being used.

The second part is the need be able to tag all content with metadata in different forms. I don&#039;t actually think there is a contradiction between managed taxanomies and folksonomies. The must successful way is probably to have them interact. Just as only a part of our content can be manually tagged (for the rest we have to settle for  some automatic measure) a managed taxonomy can only be that big. A folksonomy however, does not have that limitation. However, the managed taxonomy can regularly be updated based on developments in the folksonomy. Possibly content can have taxonomy tags, public folksonomy tags and even private folksonomy tags they don&#039;t like to share (like Siderean does I believe)

Thirdly is the need to sometimes find a way to create a discrete and unambiguous classification of words in a text. The reason for that is that it allows for a fixed context for that particular word. Also it makes automatic reasoning with advanced queries possible. If I had a text saying &quot;There is a Volvo, a Saab, a Ford and a Toyota on the parking lot&quot; I can ask how many cars there are on the parking lot without the word &quot;car&quot; being mentioned. Also it means that I can ask how many Swedish cars there are since the ontology that is being used contains that information.

Success in the general audience is of course a good way to make things happen fast but do we need to wait for that when there is a need for these technologies already. Possibly the people needing it don&#039;t yet know they need it, but they definitely do know that they have increasing troubles of handling vast amount of information effectively.

Also, &quot;semantic object-referenced word processing&quot; is probably not needed all the time but it could be an interesting alternative to custom database applications to store objects and there relations like used in most law enforcement agencies.</description>
		<content:encoded><![CDATA[<p>Fuzzy categorization&#8230;looking forward to that. I believe there are several aspects of the problem.</p>
<p>First there is a need to find an easy way to manage references of how pieces of content are used together to create new content. Something like the way iLife works on Mac OS X. You are writing a text document in Pages, bring up the media browser, drag-&amp;-drop a photo and the use of it in that particular document is stored globally. That way it is easy to see in what documents (and in essence context) this image is being used.</p>
<p>The second part is the need be able to tag all content with metadata in different forms. I don&#8217;t actually think there is a contradiction between managed taxanomies and folksonomies. The must successful way is probably to have them interact. Just as only a part of our content can be manually tagged (for the rest we have to settle for  some automatic measure) a managed taxonomy can only be that big. A folksonomy however, does not have that limitation. However, the managed taxonomy can regularly be updated based on developments in the folksonomy. Possibly content can have taxonomy tags, public folksonomy tags and even private folksonomy tags they don&#8217;t like to share (like Siderean does I believe)</p>
<p>Thirdly is the need to sometimes find a way to create a discrete and unambiguous classification of words in a text. The reason for that is that it allows for a fixed context for that particular word. Also it makes automatic reasoning with advanced queries possible. If I had a text saying &#8220;There is a Volvo, a Saab, a Ford and a Toyota on the parking lot&#8221; I can ask how many cars there are on the parking lot without the word &#8220;car&#8221; being mentioned. Also it means that I can ask how many Swedish cars there are since the ontology that is being used contains that information.</p>
<p>Success in the general audience is of course a good way to make things happen fast but do we need to wait for that when there is a need for these technologies already. Possibly the people needing it don&#8217;t yet know they need it, but they definitely do know that they have increasing troubles of handling vast amount of information effectively.</p>
<p>Also, &#8220;semantic object-referenced word processing&#8221; is probably not needed all the time but it could be an interesting alternative to custom database applications to store objects and there relations like used in most law enforcement agencies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Randall</title>
		<link>http://craigrandall.net/archives/2007/09/everything-is-miscellaneous/comment-page-1/#comment-20360</link>
		<dc:creator>Craig Randall</dc:creator>
		<pubDate>Sun, 16 Sep 2007 23:18:27 +0000</pubDate>
		<guid isPermaLink="false">http://craigrandall.net/archives/2007/09/everything-is-miscellaneous/#comment-20360</guid>
		<description>One of my follow-up posts is planned to be along the lines of &quot;fuzzy categorization.&quot; For example, can Semantic Web efforts be successful (in the way the Internet itself has defined success) as long as RDF triples are foundational? Are taxonomies good for anything more than jump-starting enterprise tagging? For example, is &quot;taxonomy&quot; the same as &quot;initial folksonomy&quot;? This all goes to participation versus control and contribution versus credentials. Cheers...</description>
		<content:encoded><![CDATA[<p>One of my follow-up posts is planned to be along the lines of &#8220;fuzzy categorization.&#8221; For example, can Semantic Web efforts be successful (in the way the Internet itself has defined success) as long as RDF triples are foundational? Are taxonomies good for anything more than jump-starting enterprise tagging? For example, is &#8220;taxonomy&#8221; the same as &#8220;initial folksonomy&#8221;? This all goes to participation versus control and contribution versus credentials. Cheers&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alexandra</title>
		<link>http://craigrandall.net/archives/2007/09/everything-is-miscellaneous/comment-page-1/#comment-20359</link>
		<dc:creator>alexandra</dc:creator>
		<pubDate>Sun, 16 Sep 2007 23:05:11 +0000</pubDate>
		<guid isPermaLink="false">http://craigrandall.net/archives/2007/09/everything-is-miscellaneous/#comment-20359</guid>
		<description>Interesting thoughts. I have always thought it is important to reflect on where and how (what format) we actually store and handle information since it affects what we can do with it later. Maybe the document is the equivalent to the album in your iTunes example. I always wanted to break down a text document in smaller discrete objects and look upon the document as merely a collection of those objects. Some examples of this thoughts can be seen in XML-based publishing concepts for brochures where both images and content can be different depending on geographic areas and  target groups. 

To me it would be interesting to bring that concept to a wider market for example people doing analysis work were paragraphs or even people, locations and things can be combined or at least described/referenced as objects but still looking like a text in a Word document.

I think the development of semantic technologies and OWL/RDF provides some promise in this area but there is still a lack of easy-to-use commercial applications where the content INSIDE the documents can be referenced and tagged. I would love to see Documentum to provide these technologies in the repository. Then we only need a client--in essence a new kind of Office application--to do the actual tagging/combining/writing. Maybe the easiest way is to leverage OpenOffice for a development project like this.</description>
		<content:encoded><![CDATA[<p>Interesting thoughts. I have always thought it is important to reflect on where and how (what format) we actually store and handle information since it affects what we can do with it later. Maybe the document is the equivalent to the album in your iTunes example. I always wanted to break down a text document in smaller discrete objects and look upon the document as merely a collection of those objects. Some examples of this thoughts can be seen in XML-based publishing concepts for brochures where both images and content can be different depending on geographic areas and  target groups. </p>
<p>To me it would be interesting to bring that concept to a wider market for example people doing analysis work were paragraphs or even people, locations and things can be combined or at least described/referenced as objects but still looking like a text in a Word document.</p>
<p>I think the development of semantic technologies and OWL/RDF provides some promise in this area but there is still a lack of easy-to-use commercial applications where the content INSIDE the documents can be referenced and tagged. I would love to see Documentum to provide these technologies in the repository. Then we only need a client&#8211;in essence a new kind of Office application&#8211;to do the actual tagging/combining/writing. Maybe the easiest way is to leverage OpenOffice for a development project like this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
