<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>lll3's blog</title>
	<atom:link href="http://blogs.njit.edu/lll3/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.njit.edu/lll3</link>
	<description>Just another blogs.njit.edu weblog</description>
	<lastBuildDate>Sat, 01 May 2010 01:20:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Effective Use of Active Space on Web Pages</title>
		<link>http://blogs.njit.edu/lll3/2010/04/29/effective-use-of-active-space-on-web-pages/</link>
		<comments>http://blogs.njit.edu/lll3/2010/04/29/effective-use-of-active-space-on-web-pages/#comments</comments>
		<pubDate>Fri, 30 Apr 2010 02:03:30 +0000</pubDate>
		<dc:creator>lll3</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.njit.edu/lll3/2010/04/29/effective-use-of-active-space-on-web-pages/</guid>
		<description><![CDATA[How do you feel when you open a web site and it’s a mass of clutter, or as Ginny Redish would say, a “wall of words” (Redish, 107)? I know I just want to close it and go on to one that has a cleaner look &#8211; one where I [...]]]></description>
			<content:encoded><![CDATA[<p>How do you feel when you open a web site and it’s a mass of clutter, or as Ginny Redish would say, a “wall of words” (Redish, 107)? I know I just want to close it and go on to one that has a cleaner look &#8211; one where I can easily find the information I want quickly and efficiently.  In many cases, this is a response to a design that does not utilize space well.</p>
<p>Redish offers guidelines in her book, <em>Letting Go of the Words: Writing Web Content that Works</em> that help web designers create web sites that are not only aesthetically appealing, but also usable. She writes, “When people come to a web page, they form an impression of the page before they read anything. They react first to the appearance (layout, fonts, colors, and so on)” (127). “Creating that appearance (designing the web page) is about more than aesthetics. It’s about usability. The design of your web pages can help people find what they need and understand what they find. It can also hinder them” (128).</p>
<p>So let’s look at some of the guidelines Redish writes about; specifically those that help us to make effective use of space.</p>
<p><strong>Use Patterns and Alignment</strong></p>
<p>Her first guideline is to use patterns and alignment to make page elements obvious. Cluttered, busy web sites usually do not have the elements (such as content, search, and navigation) aligned well. People are pattern-oriented and expect to see these elements in consistent places where they are instantly obvious. One of the best ways to form these patterns on the web page is through alignment of the elements whereby text and boxes start at only a few places (129 – 130).  And the best way to achieve consistent placement across your web site is to use templates (137). For example, the Godiva web site maintains consistent patterns and alignment across its pages. Notice how the banner is consistent and the galleries of products are aligned in a similar fashion.</p>
<p><a href="http://blogs.njit.edu/lll3/files/2010/04/godiva-1.jpg" title="godiva-1.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/04/godiva-1.jpg" alt="godiva-1.jpg" width="523" height="356" /></a><br />
Godiva Chocolate Collections and Treats page – Retrieved from http://www.godiva.com/Catalog/category.aspx?id=131</p>
<p><a href="http://blogs.njit.edu/lll3/files/2010/04/godiva-2.jpg" title="godiva-2.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/04/godiva-2.jpg" alt="godiva-2.jpg" width="523" height="354" /></a><br />
Godiva Bakery Shop &#8211; Retrieved from http://www.godiva.com/Catalog/category.aspx?id=139</p>
<p><strong>Keep Active Space in Your Content</strong><br />
Another guideline is to “keep active space in your content” (137). What is active space? How is it different from passive space? As shown in the image of a draft page from Redish’s book, active space is space inside the content area (such as space between paragraphs and list items), while passive space is space outside the content area (like the margins).</p>
<p><a href="http://blogs.njit.edu/lll3/files/2010/04/space.jpg" title="space.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/04/space.jpg" alt="space.jpg" width="416" height="515" /></a><br />
Draft book page with active and passive space labeled (138).</p>
<p>Both active and passive space work together to help visitors skim, scan, find and read information on the web page. For the web, we want to minimize passive space and focus on active space. Active space separates and groups content.</p>
<p>How do we achieve effective use of active space (137 – 139)? Redish points out several ways:<br />
•    Break the text up into small chunks<br />
•    Use lots of headings<br />
•    Keep paragraphs short and space them<br />
•    Use visuals like lists and tables rather than paragraphs<br />
•    Set off images and graphics with space around them</p>
<p><strong>Break the text up into small chunks</strong>, and separate those chunks with active space.</p>
<p>We can break the content down in various ways, such as provide the steps to accomplish a task in a list, or present directions to perform a task on its own page (like online help manuals). In the examples below, which set of directions to set a phone alarm clock would you prefer to follow? Of course the second set – the content is broken into small chunks and surrounded by active space; the first illustration is one long paragraph – a “wall of words”.</p>
<p><a href="http://blogs.njit.edu/lll3/files/2010/04/nokia-1.jpg" title="nokia-1.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/04/nokia-1.jpg" alt="nokia-1.jpg" width="461" height="431" /></a><br />
Nokia phone instructions to set the alarm clock in one paragraph &#8211; Retrieved from http://www.nokiausa.com/search?page=1&amp;cat=support&amp;qt=alarm+clock&amp;np=services&amp;cnt=1&amp;fullcontent=true</p>
<p><a href="http://blogs.njit.edu/lll3/files/2010/04/nokia21.jpg" title="nokia21.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/04/nokia21.jpg" alt="nokia21.jpg" width="382" height="364" /></a><br />
Nokia instructions to set the alarm clock broken into small chunks (72).</p>
<p><strong>Use lots of headings</strong> to help communicate content and to separate sections of information.</p>
<p>By putting spaces between headings and paragraphs, we make the information seem less dense and more readable. For example, when we compare the blood pressure information on two web sites, iVillage and FamilyDoctor, we find that headings and active space make a big difference in readability. The iVillage page lacks headings and active space; it appears as “a wall of words”.  On the other hand, the FamilyDoctor page appears less dense and more readable because of its effective use of headings and active space.</p>
<p><a href="http://blogs.njit.edu/lll3/files/2010/04/ivillage.jpg" title="ivillage.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/04/ivillage.jpg" alt="ivillage.jpg" width="473" height="376" /></a><br />
iVillage web page on checking your blood pressure – Retrieved from http://www.ivillage.co.uk/health/agestage/30and40/articles/0,,181165_183082,00.html</p>
<p><a href="http://blogs.njit.edu/lll3/files/2010/04/family-doctor.jpg" title="family-doctor.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/04/family-doctor.jpg" alt="family-doctor.jpg" width="468" height="400" /></a></p>
<p>familydoctor web page on high blood pressure – Retrieved from http://familydoctor.org/online/famdocen/home/common/heartdisease/risk/092.html</p>
<p><strong>Keep paragraphs short and space them</strong>.</p>
<p>In fact, Redish writes that on the web, a one-sentence or two-sentence paragraph is fine (191).  And space them … as on this web page:</p>
<p><a href="http://blogs.njit.edu/lll3/files/2010/04/espn.jpg" title="espn.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/04/espn.jpg" alt="espn.jpg" width="464" height="367" /></a></p>
<p>Short paragraphs on this ESPN page works well. Retrieved from http://soccernet.espn.go.com/news/story?id=344149&amp;cc=5901</p>
<p><strong>Use visuals like lists and tables rather than paragraphs</strong>.</p>
<p>According to Redish, “a great way to let go of the words without losing essential meaning is to use lists and tables” (205).  For example, visitors know to click on colored underlined words – in the following illustration, the sentence with links to visit the zoo is improved by converting it to a list (which has lots more active space).<br />
<a href="http://blogs.njit.edu/lll3/files/2010/04/zoo.jpg" title="zoo.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/04/zoo.jpg" alt="zoo.jpg" width="304" height="176" /></a><br />
<strong> </strong></p>
<p>Example of sentence and list (187)</p>
<p><strong>Set off images and graphics with space around them</strong> as are the images on The American School of Ballet Overview page.</p>
<p><a href="http://blogs.njit.edu/lll3/files/2010/04/school-of-american-ballet.jpg" title="school-of-american-ballet.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/04/school-of-american-ballet.jpg" alt="school-of-american-ballet.jpg" width="425" height="628" /></a></p>
<p>The American School of Ballet Overview page – Retrieved from http://www.sab.org/school/overview.php</p>
<p><strong>But Beware of Floating Headings and False Bottoms</strong></p>
<p>Mismanaged space can hinder visitors from effectively using your web site. So, beware and heed these two guidelines –</p>
<p><strong>don’t let headings float </strong>and</p>
<p><strong>don’t create false bottoms</strong>.</p>
<p>What do these mean?</p>
<p>Headings float in space when there is the same amount of active space before them as after them; in essence, a visitor cannot tell what content goes with what heading. To avoid this problem, be sure you leave more active space <em>above</em> the heading than below it (141 – 142).</p>
<p>A false bottom is created when a horizontal line or large block of space is placed across the page. They tend to stop people; people think they have reached the end of the page, they tend not to scroll down. For example, visitors to the Franklin Institute web site may be misled because the search box is all the way on the bottom of the page below several horizontals (140 – 141).</p>
<p><a href="http://blogs.njit.edu/lll3/files/2010/04/franklin-institute.jpg" title="franklin-institute.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/04/franklin-institute.jpg" alt="franklin-institute.jpg" width="427" height="891" /></a></p>
<p>The Franklin Institute home page – Retrieved from http://www2.fi.edu/</p>
<p>Effective use of active space is just one element in a series of several that Redish covers in her book. Stay tuned for more ways to let go of the words…</p>
<p>Works Cited<br />
American Academy of Family Physicians. FamilyDoctor.org. http://familydoctor.org. Web. 28 April 2010.<br />
ESPN Internet Ventures. ESPN soccernet Europe US. http://soccernet.espn.go.com. Web. 28 April 2010.<br />
The Franklin Institute. http://www2.fi.edu/. Web. 28 April 2010.<br />
Godiva Chocolatier, Inc. Godiva Chocolatier. http://www.godiva.com. Web. 28 April 2010.<br />
iVillage Ltd. iVillage.co.uk. http://www.ivillage.co.uk.  Web. 28 April 2010.<br />
Nokia Corp. Nokia Connecting People. http://www.nokiausa.com. Web. 28 April 2010.<br />
Redish, Janice (Ginny). Letting Go of the Words: Writing Web Content that Works. Canada: Elsevier, 2007. Print.<br />
School of American Ballet. The School of American Ballet at Lincoln Center. http://www.sab.org. Web. 28 April 2010.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.njit.edu/lll3/2010/04/29/effective-use-of-active-space-on-web-pages/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Writing for How People Read on the Web: Audience and Web Site Structure</title>
		<link>http://blogs.njit.edu/lll3/2010/03/31/writing-for-how-people-read-on-the-web-audience-and-web-site-structure/</link>
		<comments>http://blogs.njit.edu/lll3/2010/03/31/writing-for-how-people-read-on-the-web-audience-and-web-site-structure/#comments</comments>
		<pubDate>Thu, 01 Apr 2010 03:10:52 +0000</pubDate>
		<dc:creator>lll3</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.njit.edu/lll3/2010/03/31/writing-for-how-people-read-on-the-web-audience-and-web-site-structure/</guid>
		<description><![CDATA[How do you read on the web? I know I don’t read long paragraphs of text… Ginny Redish describes reading on the web as “skim and scan” (2). We go to the web to do a task or to get information, not to read for pleasure as we would a [...]]]></description>
			<content:encoded><![CDATA[<p>How do you read on the web? I know I don’t read long paragraphs of text…</p>
<p>Ginny Redish describes reading on the web as “skim and scan” (2). We go to the web to do a task or to get information, not to read for pleasure as we would a book.  If we don’t find what we want, we move on.</p>
<p><a href="http://blogs.njit.edu/lll3/files/2010/03/scan1-small.jpg" title="scan1-small.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/03/scan1-small.jpg" alt="scan1-small.jpg" /></a></p>
<p>Two typical web users. Image from Redish p. 2.</p>
<p>So if you’re writing for the web, what constitutes good web writing? Ginny Redish answers this question in her book, <em>Letting Go of the Words: Writing Web Content that Works</em>. Her book is comprehensive with lots of examples, yet an easy read.</p>
<p>She says, “Good web writing</p>
<ul>
<li>is like a conversation</li>
<li>answers people’s questions</li>
<li>lets people grab and go” (4)</li>
</ul>
<p>But, before we begin writing that content we need to understand our audience and the structure of websites …</p>
<p>In terms of our audience, we need to understand who will come to our site, and what tasks they will want to do or what information they will want to find.  And we need to write our content using their words.  To get this information it is best to actually watch, talk to and listen to our audience.   For example, we can watch and listen in your physical place of business, through a questionnaire, or interviews. We can also talk with other groups in our organization that are in contact with our audience like Marketing or Customer Service.  Other considerations about audience are their level of expertise, what technology they have available, what their state of mind is when they visit our site and what’s important to them.  As we gather this information it is helpful to create personas and scenarios that we can refer to throughout the website development or enhancement process (11 – 27).</p>
<p>Now for the structure; Redish identifies three types of web pages &#8211; home pages, pathway pages and information pages.</p>
<p><a href="http://blogs.njit.edu/lll3/files/2010/03/scan2.jpg" title="scan2.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/03/scan2.jpg" alt="scan2.jpg" /></a></p>
<p>“Information-rich web sites set up pathways to the information through the home page and one or more layers of pathway (menu) pages.” Image from Redish p. 29.</p>
<p>First, home pages – in general, people read very little on the home page, “they want to grab the information they need and move on” (30).  But home pages serve very important functions. According to Redish, they identify who we are (via our logo, name and tag line) and what our site is about (for example, what business we’re in); they portray the site’s personality through visual design; they direct visitors to the information they seek (via short descriptions and links to that information); and if appropriate, they provide ways to start the task right away (for example, they provide a form). So home pages must be content-rich, but concise; they must live up to the title of the book by <em>letting go of the words</em> (29 – 41).</p>
<p>Second, pathway pages – they too must live up to the title of the book.  “Busy site visitors are trying to get to the ‘good stuff’ – to whatever they are looking for – as quickly as possible. They don’t want to stop and read along the way. They are still navigating. They aren’t ‘there’ yet&#8221; (53).  The best pathway pages are like a table of contents, with short descriptions if appropriate.  They provide links.  It’s important that the pathway be quick and smooth, eliminating the need to think along the way. Many people will choose the first plausible link, so it’s also important that key information is on top (53 – 66).</p>
<p>And third, information pages &#8211; “[m]ost people come to the web for information, not for a complete document. They don’t want the user manual; they want instructions for the task they are doing. They don’t want the handbook; they want the answer to specific questions. They want usable, manageable pieces” (69).  To satisfy these needs, we need to break documents down into topics and subtopics, and provide premium navigation and search functionality. When deciding how much information to actually place on a page we need to think about our visitors; for example, how much do they need, will they print it, and how long will it take to download. Then we need to think about our message – even on information pages – visitors initially “skim and scan” – to determine if they’re in the right place.  So we must trim our message down, then trim down again, and perhaps again, to what is absolutely necessary. We need to write in “inverted pyramid style”; place the most essential information first, followed by less and less important information.  And then we need to break that information up into short paragraphs set off with headings, and incorporate bulleted lists where appropriate (93 – 107).</p>
<p>Now that we understand how to evaluate our audience and the structure of websites, we can begin writing content ‘that works’.  That’s a subject I will take up in future blogs.</p>
<p align="center">Works Cited</p>
<p>Redish, Janice (Ginny). <em>Letting Go of the Words: Writing Web Content that Works. </em>Canada: Elsevier, 2007. Print.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.njit.edu/lll3/2010/03/31/writing-for-how-people-read-on-the-web-audience-and-web-site-structure/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Collaboration: Clarity and Politeness</title>
		<link>http://blogs.njit.edu/lll3/2010/02/25/collaboration-clarity-and-politeness/</link>
		<comments>http://blogs.njit.edu/lll3/2010/02/25/collaboration-clarity-and-politeness/#comments</comments>
		<pubDate>Thu, 25 Feb 2010 18:44:16 +0000</pubDate>
		<dc:creator>lll3</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.njit.edu/lll3/2010/02/25/collaboration-clarity-and-politeness/</guid>
		<description><![CDATA[Now that we are working on our wiki, collaboration is on our minds.  Our text by Rude states that “[r]elationships succeed for three reasons: good writing and editing, good management, and collaborative partnerships.  Because editing involves evaluation and emendation of a writer’s work, the relationship between editor and writer can [...]]]></description>
			<content:encoded><![CDATA[<p>Now that we are working on our wiki, collaboration is on our minds.  Our text by Rude states that “[r]elationships succeed for three reasons: good writing and editing, good management, and collaborative partnerships.  Because editing involves evaluation and emendation of a writer’s work, the relationship between editor and writer can become adversarial.  Relationships fail for three reasons: poor writing and editing, poor management and oversized egos.” Rude (p. 36)  “The words you choose, your non-verbal expressions, and the way you listen all affect how well a writer receives your messages.  Your language can communicate a sense of collaboration, or it can communicate power and arrogance.” Rude (p. 444)</p>
<p>An article Rude (p. 44) lists for ‘Further Reading’, “The technical editor as diplomat: Linguistic strategies for balancing clarity and politeness” by Jo Mackiewicz and Kathryn Riley provides guidance for communicating with “a sense of collaboration”.  The authors of the article state, “[e}ditors must carry out two tasks at once.  They must <em>be clear</em> in conveying how a document should be changed, but they must also <em>be polite</em> to maintain good working relationships with writers. . . .  Managing these two needs – clarity and politeness – means managing the <strong>directness</strong> with which an editor states a writer’s obligation to change a document in some way.”  Three levels of directness are described: <strong>Direct strategies</strong> use clear and unambiguous language (the writer must carry out the action); <strong>Conventionally indirect strategies</strong> use less clear and ambiguous language (the writer must carry out the action or the writer has the option to carry out the action); and <strong>Nonconventionally indirect strategies </strong>(or <strong>hints</strong>) use the least clear and most ambiguous language (the writer may interpret the obligation to carry out the action in many ways). See table 2.  Furthermore, the directness of the language for any of these strategies can be mitigated by <strong>downgraders</strong>.  Downgraders suggested by the authors include words and phrases like <em>I think</em>, <em>maybe</em>, <em>possibly</em>, <em>OK?</em>, <em>you know,</em> and <em>just </em>as well as compliments and payoff statements (statements that express benefits).<em> </em>Downgraders have a cumulative effect; the more downgraders used, the more mitigated the directive. <em> </em>See table 3.<u> </u></p>
<p><a href="http://blogs.njit.edu/lll3/files/2010/02/table-2-small.jpg" title="table-2-small.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/02/table-2-small.jpg" alt="table-2-small.jpg" /></a></p>
<p><a href="http://blogs.njit.edu/lll3/files/2010/02/table-3-small.jpg" title="table-3-small.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/02/table-3-small.jpg" alt="table-3-small.jpg" /></a></p>
<p><strong>Direct strategies </strong></p>
<p>Direct strategies,<strong> </strong>are further divided into bald-on-record, locution-derivable (active and passive) and opinion.  Bald-on-record directives are imperative and unmitigated; therefore, they are explicit: <em>Include a table in this section</em>.  The authors suggest that bald-on-record language not be used unless either it is mitigated with downgraders, including compliments and payoff statements, or the writer does not understand the mitigated directive.  Locution-derivable directives use <strong>high-value modal verbs</strong> such as <em>should</em>, <em>will</em>, or <em>ought: You should include a table in this section</em>.  Both the active and passive voice may be used.   Although passive voice is considered more polite, the authors suggest that it should be avoided because it is not comprehended as easily as active voice.   They also suggest that locution-derivable directives not be used unless they are mitigated with downgraders, including compliments and payoff statements.  Opinion directives, although direct, are stated from the speaker’s point of view: <em>I would use a table in this section</em>.   The authors suggest that opinion directives should be used because they are both clear and polite.</p>
<p><strong>Conventionally indirect strategies</strong></p>
<p><strong>Conventionally indirect strategies</strong> include preparatory (active and passive) and interrogative.  Preparatory directives are less clear than those given with direct strategies because they introduce possibility through <strong>low-value modal verbs</strong> such as <em>can</em> and <em>could: You could include a table in this section</em>.  The authors suggest that the passive voice not be used for the same reasons given for passive locution-derivable directives.  They also suggest using this strategy only when possibility is truly an option.  Interrogative strategy uses either high-modal verbs or low-modal verbs in question form: <em>Should you include a table in this section?</em> or <em>Could you include a table in this section?</em>  It is less direct than preparatory strategy because it places the decision on whether the directive will be carried out on the writer.  The authors suggest using this strategy only when queries are truly required.</p>
<p><strong>Nonconventionally indirect strategies </strong>(or <strong>hints</strong>) may be strong or weak.  Both forms change the semantics of the directive so that the directive, <em>Include a table in this section</em>, is no longer explicit: <em>This section has a lot of numerical data in it</em>.  Because it is ambiguous, the hint can be interpreted in a variety of ways.  Strong hints do not include a directive, they merely consist of an observation.  Weak hints  express a general rule about writing: <em>Graphic aids can help the reader understand data.</em>  The authors suggest that hints, especially strong hints, be avoided because several studies show that they are considered less polite than conventional indirect strategies.</p>
<p>The authors provide a summary of the strategies discussed and their recommendations for achieving clear and polite communications in the following table.  See table 7.  They suggest using opinion, derivable (active) and bald-on-record strategies with downgraders when obligation is required; and preparatory strategy (active) when obligation is possible.  Interrogative strategy should be used for queries only.  Passive derivable and preparatory strategies as well as hints should be avoided.</p>
<p><a href="http://blogs.njit.edu/lll3/files/2010/02/table-7-small.jpg" title="table-7-small.jpg"><img src="http://blogs.njit.edu/lll3/files/2010/02/table-7-small.jpg" alt="table-7-small.jpg" /></a></p>
<p align="center">Works Cited</p>
<p>Mackiewicz, Jo, and Kathryn Riley. “The Technical Editor as Diplomat: Linguistic Strategies for Balancing Clarity and Politeness.”  <u>Technical Communication</u> 50.1 (2003): 83-94. Print.</p>
<p>Rude, Carolyn D., David Dayton, and Bruce Maylath. <em>Technical Editing</em>. 4<sup>th</sup> ed. Pearson Education, 2006. Print</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.njit.edu/lll3/2010/02/25/collaboration-clarity-and-politeness/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Keywords and Tags … Folksonomies</title>
		<link>http://blogs.njit.edu/lll3/2010/01/28/keywords-and-tags-%e2%80%a6-folksonomies/</link>
		<comments>http://blogs.njit.edu/lll3/2010/01/28/keywords-and-tags-%e2%80%a6-folksonomies/#comments</comments>
		<pubDate>Fri, 29 Jan 2010 02:50:59 +0000</pubDate>
		<dc:creator>lll3</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.njit.edu/lll3/2010/01/28/keywords-and-tags-%e2%80%a6-folksonomies/</guid>
		<description><![CDATA[I was thinking about keywords, especially in relation to finding relevant sites such as blogs or other items of interest on the internet when I came across an article by Adam Mathes.  Mathes’ article ‘Folksonomies – Cooperative Classification and Communication Through Shared Metadata’ talks about ‘user-created metadata’ on two sites, [...]]]></description>
			<content:encoded><![CDATA[<p>I was thinking about keywords, especially in relation to finding relevant sites such as blogs or other items of interest on the internet when I came across an article by Adam Mathes.  Mathes’ article ‘Folksonomies – Cooperative Classification and Communication Through Shared Metadata’ talks about ‘user-created metadata’ on two sites, Del.icio.us and Flickr.   Both sites allow users to create their own keywords or tags to describe their content, whether bookmarks for sites (as on Del.icio.us) or photos (as on Flickr).  Previously tags were created via one of the following approaches: dedicated professionally created metadata, author created metadata, and user created metadata.  The new approach described as an “organic system of organization” (Mathes 4) found on sites such as Del.icio.us and Flickr was called “folksonomy” by Thomas Vander Wal.   Folksonomy consists of terms that have no formal hierarchy; they “are simply the set of terms that a group of users tagged content with, they are not a predetermined set of classification terms or labels.” (Mathes 4)</p>
<p>Mathes points to problems with folksonomy such as ambiguity and synonyms.  Ambiguity arises when different users create the same tag to describe different entities – “completely separate domains and ideas are mixed together in the same tag.” (Mathes 6)  Lack of control over synonyms leads “to tags that seemingly have similar intended meanings”. (Mathes 6)</p>
<p>Folksonomy does have strengths which Mathes attributes to its “appeal and utility”. (Mathes 6)  Included as strengths are ‘Browsing vs Finding’ and ‘Desire Lines’.  Mathes describes ‘Browsing vs Finding’ as “serendipity”; “browsing the system and its interlinked related tag sets is wonderful for finding things unexpectedly in a general area.” (Mathes 6)  Mathes describes ‘Desire Lines’ as “the most important strength of a folksonomy” (Mathes 7) because “it directly reflects the vocabulary of the users.” (Mathes 7)  “It directly reflects their choices in diction, terminology, and precision.” (Mathes 7)</p>
<p>Mathes points out that folksonomies work because the of the low cost of time and effort on the part of users as well as a way to communicate with others, share information and organize personal entities.  “The near instant feedback in these systems leads to a communicative nature of tag use.” (Mathes <img src='http://blogs.njit.edu/lll3/wp-includes/images/smilies/icon_cool.gif' alt='8)' class='wp-smiley' /> </p>
<p>In conclusion, Mathes states that “folksonomy represents simultaneously some of the best and worst in the organization of information”. (Mathes 12)  “Systems employing free-form tagging that are encouraging users to organize information in their own ways are supremely responsive to user needs and vocabularies, and involve the users of information actively in the organizational system.” (Mathes 12)  I think the enthusiasm for internet use is in part due to folksonomy.  I think we will see systems incorporate it more frequently and in more creative ways in the future.</p>
<p align="center">Works Cited</p>
<p>Mathes, Adam. “Folksonomies – Cooperative Classification and Communication Through Shared</p>
<p>Metadata.” Computer Mediated Communication (Dec. 2004): 1-13.</p>
<p>&lt;http://www.adammathes.com/academic/computer-mediated-</p>
<p>communication/folksonomies.html&gt;.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.njit.edu/lll3/2010/01/28/keywords-and-tags-%e2%80%a6-folksonomies/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hello world!</title>
		<link>http://blogs.njit.edu/lll3/2010/01/27/hello-world/</link>
		<comments>http://blogs.njit.edu/lll3/2010/01/27/hello-world/#comments</comments>
		<pubDate>Thu, 28 Jan 2010 03:05:23 +0000</pubDate>
		<dc:creator>lll3</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[This blog is part of my coursework for PTC 624 Professional and Technical Editing.  Through this blog I will explore the various areas of editing as the course unfolds.]]></description>
			<content:encoded><![CDATA[<p>This blog is part of my coursework for PTC 624 Professional and Technical Editing.  Through this blog I will explore the various areas of editing as the course unfolds.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.njit.edu/lll3/2010/01/27/hello-world/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
