<?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: NPTech Metatag Feed &#8212; why it&#8217;s broken and how to fix it</title>
	<atom:link href="http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it/feed" rel="self" type="application/rss+xml" />
	<link>http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=nptech-metatag-feed-why-its-broken-and-how-to-fix-it</link>
	<description>Confessions of a Non-Profit Executive Director</description>
	<lastBuildDate>Sun, 05 Sep 2010 19:51:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: abenamer</title>
		<link>http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it/comment-page-1#comment-679</link>
		<dc:creator>abenamer</dc:creator>
		<pubDate>Sat, 18 Nov 2006 14:58:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it#comment-679</guid>
		<description>Thanks for continuing the discussion about the stream. What I mean by silos are the disparate areas where the tag is coming from, each social bookmarking site is a silo of data. That&#039;s by design of course as each site needs to have that in order to create value for its members. I don&#039;t really have a problem with it except of course when it comes to the lack of tagging that gfitz points out. Frankly, it drives me nuts to look at links on the nptech metastream where I don&#039;t understand the intent of the tagger. And worse, there&#039;s no way for someone else to go in there and retag the link. At THAT point, the siloing is bad because you have to figure out a way to find out where the link came from in the first place but none of the current social bookmarking sites have that capability to go in and retag someone or to create what Google CSE calls &quot;refinements&quot;.

Google Marker and manseo allows for this because of the unique technology behind Google Co-op. People are used to social bookmarking sites and I like them too but I was always wary of them because I felt that people can be sloppy and there was no inherent way to implement a second-tier of checking on the initial tags. Google CSEs have that built-in. It&#039;s social bookmarking 2.0 in that sense.

Google CSE makes a great point in its documentation. Do NOT tag by keyword. Keyword searches are already handled well by Google&#039;s search algorithms. However, search by audience (which implies intent and a level of human-only utility) is how I created the site. Also, unique sites that are difficult to pick out via keyword search are also in the list of refinements.

The first search in any Google CSE is against the entire list of URLs in the CSE&#039;s database. The second search limits itself to a subset of the original set of URLs that are tagged by each refinement. This is not a silo because there&#039;s no friction between the superset and subsets of data. Also, if you want to see other people&#039;s tags on CSE, you see the tags set up by other collaborators on the CSE. My suspicion is that Google is going to put a lot of great engineers on CSE and ultimately, because of Google search technology and numerous APIs, will overtake the usefulness of old-school social bookmarking sites.</description>
		<content:encoded><![CDATA[<p>Thanks for continuing the discussion about the stream. What I mean by silos are the disparate areas where the tag is coming from, each social bookmarking site is a silo of data. That&#8217;s by design of course as each site needs to have that in order to create value for its members. I don&#8217;t really have a problem with it except of course when it comes to the lack of tagging that gfitz points out. Frankly, it drives me nuts to look at links on the nptech metastream where I don&#8217;t understand the intent of the tagger. And worse, there&#8217;s no way for someone else to go in there and retag the link. At THAT point, the siloing is bad because you have to figure out a way to find out where the link came from in the first place but none of the current social bookmarking sites have that capability to go in and retag someone or to create what Google CSE calls &#8220;refinements&#8221;.</p>
<p>Google Marker and manseo allows for this because of the unique technology behind Google Co-op. People are used to social bookmarking sites and I like them too but I was always wary of them because I felt that people can be sloppy and there was no inherent way to implement a second-tier of checking on the initial tags. Google CSEs have that built-in. It&#8217;s social bookmarking 2.0 in that sense.</p>
<p>Google CSE makes a great point in its documentation. Do NOT tag by keyword. Keyword searches are already handled well by Google&#8217;s search algorithms. However, search by audience (which implies intent and a level of human-only utility) is how I created the site. Also, unique sites that are difficult to pick out via keyword search are also in the list of refinements.</p>
<p>The first search in any Google CSE is against the entire list of URLs in the CSE&#8217;s database. The second search limits itself to a subset of the original set of URLs that are tagged by each refinement. This is not a silo because there&#8217;s no friction between the superset and subsets of data. Also, if you want to see other people&#8217;s tags on CSE, you see the tags set up by other collaborators on the CSE. My suspicion is that Google is going to put a lot of great engineers on CSE and ultimately, because of Google search technology and numerous APIs, will overtake the usefulness of old-school social bookmarking sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kanter</title>
		<link>http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it/comment-page-1#comment-676</link>
		<dc:creator>kanter</dc:creator>
		<pubDate>Sat, 18 Nov 2006 03:47:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it#comment-676</guid>
		<description>Okay, I played with Manseo.  It is cool.  

But, I personally wouldn&#039;t use it as the *only* source to find material when researching or to keep up to date. 

It is good for retrieval to find stuff you&#039;ve come across.  Although, I find that if I retag and annotate resources from the volumes of stuff I read into my social bookmarking account, that I can easily retrieve what I need via my own account.  

Is that your definition of silos?

Well, if your bookmarks are in a social bookmarking system, you have access to other people&#039;s bookmarks via the tag.  I actually find a lot of valuable resources browsing by tag and particular people&#039;s tag collections in social bookmarking services.  For example, Robin Good, makes his links public.  He&#039;s topic expert on online collaboration technology. I find precisely what I need from his collection because I have access to it because we use the same service and connect via the tag.

The drawback is that not all users are identified in places like delicious.  Some of the other services, like magnolia, have groups where you know the people. 
 
I&#039;m curious.  Have you done all the tagging by point of view, &quot;for techies&quot; &quot;for marketers&quot; etc.? Right?   Does it have the ability for  the group to do this versus one person?

I played with some searches and one thing that struck me is that it could be a different type of silo - field that doesn&#039;t cross disciplines.</description>
		<content:encoded><![CDATA[<p>Okay, I played with Manseo.  It is cool.  </p>
<p>But, I personally wouldn&#8217;t use it as the *only* source to find material when researching or to keep up to date. </p>
<p>It is good for retrieval to find stuff you&#8217;ve come across.  Although, I find that if I retag and annotate resources from the volumes of stuff I read into my social bookmarking account, that I can easily retrieve what I need via my own account.  </p>
<p>Is that your definition of silos?</p>
<p>Well, if your bookmarks are in a social bookmarking system, you have access to other people&#8217;s bookmarks via the tag.  I actually find a lot of valuable resources browsing by tag and particular people&#8217;s tag collections in social bookmarking services.  For example, Robin Good, makes his links public.  He&#8217;s topic expert on online collaboration technology. I find precisely what I need from his collection because I have access to it because we use the same service and connect via the tag.</p>
<p>The drawback is that not all users are identified in places like delicious.  Some of the other services, like magnolia, have groups where you know the people. </p>
<p>I&#8217;m curious.  Have you done all the tagging by point of view, &#8220;for techies&#8221; &#8220;for marketers&#8221; etc.? Right?   Does it have the ability for  the group to do this versus one person?</p>
<p>I played with some searches and one thing that struck me is that it could be a different type of silo &#8211; field that doesn&#8217;t cross disciplines.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gfitz</title>
		<link>http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it/comment-page-1#comment-674</link>
		<dc:creator>gfitz</dc:creator>
		<pubDate>Thu, 16 Nov 2006 19:34:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it#comment-674</guid>
		<description>Maybe I am thinking too old school here but I just wish people used the notes field more often when tagging something. I am not sure what the reluctance is ... maybe people just dont feel like they have time ... but when people write a little narrative in that space it actually gives us a glimpse into their intent.</description>
		<content:encoded><![CDATA[<p>Maybe I am thinking too old school here but I just wish people used the notes field more often when tagging something. I am not sure what the reluctance is &#8230; maybe people just dont feel like they have time &#8230; but when people write a little narrative in that space it actually gives us a glimpse into their intent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: abenamer</title>
		<link>http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it/comment-page-1#comment-666</link>
		<dc:creator>abenamer</dc:creator>
		<pubDate>Wed, 15 Nov 2006 23:20:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it#comment-666</guid>
		<description>You&#039;ll see that Google CSE is a far better paradigm for collaboration than del.icio.us or other social bookmarking sites. You didn&#039;t answer the real point -- all that lost work due to siloed data. There&#039;s no equivalent at Feedburner or Feedjumbler to deal with the archival issue so it&#039;s not even a matter of whether people have the patience to mine the stream. They simply can&#039;t even if they wanted to. 

With a Google CSE, you&#039;re basically taking the incoming stream, reorganizing it, archiving it and then (in the future) creating yet another stream out of it. It&#039;s a far more sophisticated feedback loop than the ones created by current social bookmarking sites. Those are JUST for tagging, there&#039;s no way to get in there and help to reorganize it. I don&#039;t think an nptech taxonomy is actually needed as that would be decided within the internal confines of the collaboration space of a CSE. Both the tagging AND the vocabularies are subject to a collaborative approach. With the CSE, there are NO artificial distinctions between a taxonomy and a folksonomy. It&#039;s radically more decentralized than del.icio.us. Really. I mean it. Try it out.</description>
		<content:encoded><![CDATA[<p>You&#8217;ll see that Google CSE is a far better paradigm for collaboration than del.icio.us or other social bookmarking sites. You didn&#8217;t answer the real point &#8212; all that lost work due to siloed data. There&#8217;s no equivalent at Feedburner or Feedjumbler to deal with the archival issue so it&#8217;s not even a matter of whether people have the patience to mine the stream. They simply can&#8217;t even if they wanted to. </p>
<p>With a Google CSE, you&#8217;re basically taking the incoming stream, reorganizing it, archiving it and then (in the future) creating yet another stream out of it. It&#8217;s a far more sophisticated feedback loop than the ones created by current social bookmarking sites. Those are JUST for tagging, there&#8217;s no way to get in there and help to reorganize it. I don&#8217;t think an nptech taxonomy is actually needed as that would be decided within the internal confines of the collaboration space of a CSE. Both the tagging AND the vocabularies are subject to a collaborative approach. With the CSE, there are NO artificial distinctions between a taxonomy and a folksonomy. It&#8217;s radically more decentralized than del.icio.us. Really. I mean it. Try it out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: abenamer</title>
		<link>http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it/comment-page-1#comment-665</link>
		<dc:creator>abenamer</dc:creator>
		<pubDate>Wed, 15 Nov 2006 23:10:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it#comment-665</guid>
		<description>My guess is that the stream and CSE will merge in usage. Basically, future iterations of the CSE API will allow for both an incoming stream of tags and an outgoing stream of notifications. The current nptech tag stream actually creates a problem -- nothing is ever tagged with a refined tag and this is because the tagging engine is fairly rudimentary in this aspect.

The current version of Google marker actually allows nptech-like definitions at the URL level or the site level. Your argument really needs more refinement because the publisher and tagger in a CSE environment are one and the same person. It wouldn&#039;t be hard for a tagger to create a new refinement to the tag and then start tagging sites to that site. Clearly, this suggests that Google CSE allows you to have your cake and eat it too. I think you need to really take a look at Google&#039;s new search technologies and the APIs they&#039;re developing. They&#039;re going to make del.icio.us and other tagging sites look oh so 2004 ;)</description>
		<content:encoded><![CDATA[<p>My guess is that the stream and CSE will merge in usage. Basically, future iterations of the CSE API will allow for both an incoming stream of tags and an outgoing stream of notifications. The current nptech tag stream actually creates a problem &#8212; nothing is ever tagged with a refined tag and this is because the tagging engine is fairly rudimentary in this aspect.</p>
<p>The current version of Google marker actually allows nptech-like definitions at the URL level or the site level. Your argument really needs more refinement because the publisher and tagger in a CSE environment are one and the same person. It wouldn&#8217;t be hard for a tagger to create a new refinement to the tag and then start tagging sites to that site. Clearly, this suggests that Google CSE allows you to have your cake and eat it too. I think you need to really take a look at Google&#8217;s new search technologies and the APIs they&#8217;re developing. They&#8217;re going to make del.icio.us and other tagging sites look oh so 2004 <img src='http://www.nonprofittechblog.org/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kanter</title>
		<link>http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it/comment-page-1#comment-664</link>
		<dc:creator>kanter</dc:creator>
		<pubDate>Wed, 15 Nov 2006 18:41:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it#comment-664</guid>
		<description>Allan,

Good points.  

What you are describing are the pros/cons and differences between taxonomies and folksonomies, centralized versus decentralized, controlled vocabularies versus tags versus search.

I think that the mega tag stream is very broad and is like hose sometimes and many people probably don&#039;t have the time or patient to mine it -- hence the concept of an information curator or reference librarian - a human who has the content expertise to make meaning out of these distributed and aggregated resources.

I have to do a lot of web resource as part of work - developing curriculum, writing, etc - and I find that searching nptech + (other tag) in a socialbookmarking site to turn up much better and useful resources than a keyword search.   However, I use both ... it isn&#039;t an either or.

and, if you were build the nptech taxonomy (which was drafted as part of techfinder at some point I seem to recall) - you&#039;d probably start with an analysis of the tag terms used for nptech as a first step.</description>
		<content:encoded><![CDATA[<p>Allan,</p>
<p>Good points.  </p>
<p>What you are describing are the pros/cons and differences between taxonomies and folksonomies, centralized versus decentralized, controlled vocabularies versus tags versus search.</p>
<p>I think that the mega tag stream is very broad and is like hose sometimes and many people probably don&#8217;t have the time or patient to mine it &#8212; hence the concept of an information curator or reference librarian &#8211; a human who has the content expertise to make meaning out of these distributed and aggregated resources.</p>
<p>I have to do a lot of web resource as part of work &#8211; developing curriculum, writing, etc &#8211; and I find that searching nptech + (other tag) in a socialbookmarking site to turn up much better and useful resources than a keyword search.   However, I use both &#8230; it isn&#8217;t an either or.</p>
<p>and, if you were build the nptech taxonomy (which was drafted as part of techfinder at some point I seem to recall) &#8211; you&#8217;d probably start with an analysis of the tag terms used for nptech as a first step.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: geilhufe</title>
		<link>http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it/comment-page-1#comment-662</link>
		<dc:creator>geilhufe</dc:creator>
		<pubDate>Wed, 15 Nov 2006 15:54:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/nptech-metatag-feed-why-its-broken-and-how-to-fix-it#comment-662</guid>
		<description>Two different problems, two different solutions. nptech allows humans to define the nptech space at a very ganular level (link, photo, post, etc.). CSE defines it at the publisher level. I doubt all of a single publisher&#039;s work will cleanly fit into nonprofit tech alone.

I think the real use of nptech is not consuming the nptech stream which is a really big content space, but consuming nptech + &quot;relevant tag&quot; streams.

So choosing between consuming an nptech stream and using CSE, obviously the search engine. When monitoring a specific topic nptech+cms, for example, I&#039;ll stick with nptech.</description>
		<content:encoded><![CDATA[<p>Two different problems, two different solutions. nptech allows humans to define the nptech space at a very ganular level (link, photo, post, etc.). CSE defines it at the publisher level. I doubt all of a single publisher&#8217;s work will cleanly fit into nonprofit tech alone.</p>
<p>I think the real use of nptech is not consuming the nptech stream which is a really big content space, but consuming nptech + &#8220;relevant tag&#8221; streams.</p>
<p>So choosing between consuming an nptech stream and using CSE, obviously the search engine. When monitoring a specific topic nptech+cms, for example, I&#8217;ll stick with nptech.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
