<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Web Design&gt;Metadata</title>	<link>http://tc.eserver.org/dir/Articles/Web-Design/Metadata</link>
	<description>A listing of the most recently indexed works about Articles and Web Design and Metadata in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Articles&gt;Web Design&gt;Metadata</title>
		<link>http://tc.eserver.org/dir/Articles/Web-Design/Metadata</link>
	</image>
	<item>
		<title>Introduction to RDFa</title>
		<link>http://tc.eserver.org/34664.html</link>
		<guid>http://tc.eserver.org/34664.html</guid>
		<description>The web is designed to be consumed by humans, and much of the rich, useful information our websites contain, is inaccessible to machines. People can cope with all sorts of variations in layout, spelling, capitalization, color, position, and so on, and still absorb the intended meaning from the page. Machines, on the other hand, need some help.&#xD;&#xD;A new kind of web—a semantic web—would be made up of information marked up in such a way that software can also easily understand it. Before considering how we might achieve such a web, let’s look at what we might be able to do with it.</description>
	</item>
	<item>
		<title>Classifying Web Sites</title>
		<link>http://tc.eserver.org/34183.html</link>
		<guid>http://tc.eserver.org/34183.html</guid>
		<description>In this paper, we present a novel method for the classification of Web sites. This method exploits both structure and content of Web sites in order to discern their functionality. It allows for distinguishing between eight of the most relevant functional classes of Web sites. We show that a pre-classification of Web sites utilizing structural properties considerably improves a subsequent textual classification with standard techniques. We evaluate this approach on a dataset comprising more than 16,000 Web sites with about 20 million crawled and 100 million known Web pages. Our approach achieves an accuracy of 92% for the coarse-grained classification of these Web sites.</description>
	</item>
	<item>
		<title>XML Transformation and Metadata Repositories Enable Information Integration</title>
		<link>http://tc.eserver.org/33796.html</link>
		<guid>http://tc.eserver.org/33796.html</guid>
		<description>Among the popular emerging integration needs in the market today is information aggregation, normalization, and presentation from multiple back-end data sources to front-end applications. Termed Enterprise Information Integration by some vendors in the market, this type of solution relies on a centralized common object model to provide a data access interface to client applications. Applications can used this common interface to request data from one or more data sources in a single query, with the intricate details of resolving the query left to the integration tool. This session will explain the architecture of an enterprise information integration solution in general, highlight some of the vendors and their approaches in this market space, and explain the use of such as solution through a real-world example with a large financial services organization.</description>
	</item>
	<item>
		<title>The Atom API: Publishing Web Content with XML and HTTP</title>
		<link>http://tc.eserver.org/33801.html</link>
		<guid>http://tc.eserver.org/33801.html</guid>
		<description>The Atom API is an emerging interface for editing content. The interface is RESTful and uses XML and HTTP to define an editing scheme that&apos;s easy to implement and extend. History, basic operation, and applications to areas outside weblogs will be covered.</description>
	</item>
	<item>
		<title>Give Your Website a Location</title>
		<link>http://tc.eserver.org/33404.html</link>
		<guid>http://tc.eserver.org/33404.html</guid>
		<description>One of the critical-mass elements for location-based services to actually be useful is for online content to have a sense of geographic context. We&apos;re already seeing it to some extent with services such as Flickr allowing photographs to be tagged with GPS coordinates: camera-phones with built-in GPS can automatically tag each photo with the exact location at which it was taken, and that meta-data can then be used to search for photos of a particular area or place.</description>
	</item>
	<item>
		<title>Extended Faceted Taxonomies for Web Catalogs</title>
		<link>http://tc.eserver.org/33236.html</link>
		<guid>http://tc.eserver.org/33236.html</guid>
		<description>Which would be easier to remember: one thousand individual terms or three facets of ten terms each?</description>
	</item>
	<item>
		<title>Use of Faceted Classification</title>
		<link>http://tc.eserver.org/33239.html</link>
		<guid>http://tc.eserver.org/33239.html</guid>
		<description>Unlike a simple hierarchical scheme, faceted classification gives the users the ability to find items based on more than one dimension. For example, some users shopping for jewelry may be most interested in browsing by particular type of jewelry (earrings, necklaces), while others are more interested in browsing by a particular material (gold, silver). “Material” and “type” are examples of facets; earrings, necklaces, gold, silver are examples of facet values. </description>
	</item>
	<item>
		<title>Faceted Access: A Review of the Literature </title>
		<link>http://tc.eserver.org/33242.html</link>
		<guid>http://tc.eserver.org/33242.html</guid>
		<description>The purpose of this 1995 paper is to define what is meant by facet analysis, and to review briefly the history of facet analysis within the context of other types of subject analysis in libraries and within the context of information retrieval research.</description>
	</item>
	<item>
		<title>Death of a Meta Tag</title>
		<link>http://tc.eserver.org/33021.html</link>
		<guid>http://tc.eserver.org/33021.html</guid>
		<description>The value of adding meta keywords tags to pages seems little worth the time. In my opinion, the meta keywords tag is dead, dead, dead. Like Andrew, I say good riddance!</description>
	</item>
	<item>
		<title>It&apos;s Time To Get Serious About Metadata</title>
		<link>http://tc.eserver.org/33027.html</link>
		<guid>http://tc.eserver.org/33027.html</guid>
		<description>When it comes to the Web, there is nothing more misunderstood than metadata. Technical people search vainly for a way to automate its creation. Many editors and writers want nothing to do with it. And yet without quality metadata a website cannot properly achieve its objectives. It’s time to get serious about metadata.</description>
	</item>
	<item>
		<title>Metadata is Essential Web Writing Skill: Part 1</title>
		<link>http://tc.eserver.org/33032.html</link>
		<guid>http://tc.eserver.org/33032.html</guid>
		<description>Metadata is one of the most misunderstood aspects of content management and website design. Editors and writers tend to look at it as a technical issue. Technical people look for a software solution. Both are wrong. Metadata is a fundamental skill that web writers and editors must acquire.</description>
	</item>
	<item>
		<title>Metadata is Essential Web Writing Skill: Part 2</title>
		<link>http://tc.eserver.org/33033.html</link>
		<guid>http://tc.eserver.org/33033.html</guid>
		<description>Creating great metadata for your content begins with understanding who your reader is. What is the metadata they look for when they read a page of your content? What are the type of words they use when they search for your content? When scanning your classification, what are the &quot;trigger words&quot; that will make them want to go deeper into your website?</description>
	</item>
	<item>
		<title>Metadata: Seven Tips for Writing Better Keywords</title>
		<link>http://tc.eserver.org/33035.html</link>
		<guid>http://tc.eserver.org/33035.html</guid>
		<description>The shift in how search engines treat keywords is significant. They tend to ignore the keyword metatag and rather look for keywords in the actual page content. This means that you need to figure out your keywords before you write any content. Then, you include them throughout your content, particularly in headings and summaries.</description>
	</item>
	<item>
		<title>Accessible Folksonomies</title>
		<link>http://tc.eserver.org/32921.html</link>
		<guid>http://tc.eserver.org/32921.html</guid>
		<description>I’ve been thinking about one particular artifact of the folksonomy phenomenon — the folksonomy menu that serves as a sort of buzz index providing users with a quick visualization of the most popular tags (technically I think it’s called a weighted list). Popular tags are displayed in a larger font and it’s relatively easy to identify hot topics at a glance. This visual representation of the popularity of any given tag is undeniably cool. However, once the coolness factor wears off it becomes fairly obvious that these menus are also not very accessible.</description>
	</item>
	<item>
		<title>JavaScript Badges Powered by JSONP and Microformats</title>
		<link>http://tc.eserver.org/32525.html</link>
		<guid>http://tc.eserver.org/32525.html</guid>
		<description>Using a bit of JavaScript, a nifty way of making remote web service calls (JSONP) and a few microformats, I can display information from one service somewhere else, leaving me with only one place to update it. In this article you&apos;re going to create a JavaScript badge that can be added to any site and which will display relationship data from a service which exposes it</description>
	</item>
	<item>
		<title>Microformat Encoding and Visualization</title>
		<link>http://tc.eserver.org/32530.html</link>
		<guid>http://tc.eserver.org/32530.html</guid>
		<description>So you have heard about microformats, read the introductory articles, and even bought the book. But now you are probably thinking &quot;great - I have done my part to make the web a better place by adding microformats; what&apos;s next? What can people do with my data besides add it to their address book or calendar?&quot; The intent of this article is to get you to think about microformats in different ways, and to demonstrate some interesting visualizations and mash-ups of microformatted content.</description>
	</item>
	<item>
		<title>Location-Based Publishing and Services</title>
		<link>http://tc.eserver.org/32531.html</link>
		<guid>http://tc.eserver.org/32531.html</guid>
		<description>In this article, we&apos;ll look at ways that you can geocode your content, using data formats such as the location nanoformat, GPX and combinations of geocoded microformats in HTML.</description>
	</item>
	<item>
		<title>The HTML HEAD Element</title>
		<link>http://tc.eserver.org/32464.html</link>
		<guid>http://tc.eserver.org/32464.html</guid>
		<description>This article deals with a part of the HTML document that does not get the attention it deserves: the markup that goes inside the head element. By the end of this tutorial you’ll have learnt about the different parts of this section and what they all do, including the doctype, title element, keywords and description (which are handled by meta elements).</description>
	</item>
	<item>
		<title>Choosing the Right Doctype for Your HTML Documents</title>
		<link>http://tc.eserver.org/32465.html</link>
		<guid>http://tc.eserver.org/32465.html</guid>
		<description>In this article I will look at the doctype in a lot more detail, showing what it does and how it helps you validate your HTML, how to choose a doctype for your document, and the XML declaration, which you’ll rarely need, but will sometimes come across.</description>
	</item>
	<item>
		<title>Use of Collaborative Recommendations for Web Search: An Exploratory User Study</title>
		<link>http://tc.eserver.org/32327.html</link>
		<guid>http://tc.eserver.org/32327.html</guid>
		<description>This study investigated use of collaborative recommendations in web searching. An experimental system was designed. In the experimental system, recommendations were generated in a group report format, including items judged relevant by previous users, search queries and the URLs of documents. The study explored how users used these items, the effects of their use, and what factors contributed to this use. The results demonstrate that users preferred using queries and document sources (URLs), rather than relevance judgment (document ratings). The findings also show that using recommended items had a significant effect on the number of documents viewed, but not on precision or number of queries. Task difficulty and search skills had significant impact on the use. Possible reasons for the results are analyzed. Implications and future directions are discussed.</description>
	</item>
	<item>
		<title>The Folksonomy Tag Cloud: When is it Useful?</title>
		<link>http://tc.eserver.org/32276.html</link>
		<guid>http://tc.eserver.org/32276.html</guid>
		<description>The weighted list, known popularly as a `tag cloud&apos;, has appeared on many popular folksonomy-based web-sites. Flickr, Delicious, Technorati and many others have all featured a tag cloud at some point in their history. However, it is unclear whether the tag cloud is actually useful as an aid to finding information. We conducted an experiment, giving participants the option of using a tag cloud or a traditional search interface to answer various questions. We found that where the information-seeking task required specific information, participants preferred the search interface. Conversely, where the information-seeking task was more general, participants preferred the tag cloud. While the tag cloud is not without value, it is not sufficient as the sole means of navigation for a folksonomy-based dataset.</description>
	</item>
	<item>
		<title>Don&apos;t Forget A Strategy for Microcontent—Headlines, Decks, Buttons and Links—When You Redesign Your Site</title>
		<link>http://tc.eserver.org/31510.html</link>
		<guid>http://tc.eserver.org/31510.html</guid>
		<description>Little things mean a lot. Especially online. Microcontent—or the headlines, decks, subheads and other &apos;small&apos; pieces of web copy—actually do most of the communicating on your web site. Handled poorly, microcontent can confuse and frustrate web visitors. Here&apos;s how to write microcontent to communicate to—instead of discombobulate—your readers.</description>
	</item>
	<item>
		<title>Use Product and Service Names as Keywords on Your Web Pages</title>
		<link>http://tc.eserver.org/28145.html</link>
		<guid>http://tc.eserver.org/28145.html</guid>
		<description>I am quite surprised by what I have learned about the effectiveness of product names as organic search keywords.</description>
	</item>
	<item>
		<title>The Meta Description Tag</title>
		<link>http://tc.eserver.org/27519.html</link>
		<guid>http://tc.eserver.org/27519.html</guid>
		<description>The keywords and phrases you use in your Meta description tag don&apos;t affect your page&apos;s ranking in the search engines (for the most part), but this tag can still come in handy in your overall SEO campaigns.</description>
	</item>
	<item>
		<title>Two Kinds of Keywords</title>
		<link>http://tc.eserver.org/26136.html</link>
		<guid>http://tc.eserver.org/26136.html</guid>
		<description>I have long wondered why government web sites all over the world tend to use metadata of several different types jumbled together and overlapping. For example, pages with two description metatags or two or three title tags are common. I suspect that most of the replication and confusion has developed for historical reasons.</description>
	</item>
	<item>
		<title>The Semantic Web, Taking Form</title>
		<link>http://tc.eserver.org/21597.html</link>
		<guid>http://tc.eserver.org/21597.html</guid>
		<description>The Semantic Web is a conceptual information space in which the resources identified by URIs can be processed by machines. It operates on the principles of &apos;partial understanding&apos; and &apos;inference&apos; (being able to infer new knowledge of terms from data that you already understand), and hence evolution and transformation. Because the URIs are being used to represent the resources, systems can grow on a globally decentralized basis, similar to hypertext documentation systems on the early WWW.</description>
	</item>
	<item>
		<title>La Web Semántica, Hoy</title>
		<link>http://tc.eserver.org/21603.html</link>
		<guid>http://tc.eserver.org/21603.html</guid>
		<description>Hace casi tres años comentábamos que la promesa de la web semántica era convertir la red en &apos;un espacio auto-navegable y auto-comprensible.&apos; ¿Dónde estamos hoy en día?.</description>
	</item>
	<item>
		<title>Coloring Outside the Lines</title>
		<link>http://tc.eserver.org/21281.html</link>
		<guid>http://tc.eserver.org/21281.html</guid>
		<description>Once upon a time, we were curious and everything we encountered was new. We were excited about discovering new things and the world offered unlimited possibilities. Then we went to school and were taught to color inside the lines, that everything had its place and the world was ordered.</description>
	</item>
	<item>
		<title>Hypermedia and the Semantic Web: A Research Agenda</title>
		<link>http://tc.eserver.org/18977.html</link>
		<guid>http://tc.eserver.org/18977.html</guid>
		<description>Until recently, the Semantic Web was little more than a name for the next-generation Web infrastructure as envisioned by its inventor, Tim Berners-Lee. With the introduction of XML and RDF, and new developments such as RDF Schema and DAML+OIL, the Semantic Web is rapidly taking shape. This paper gives an overview of the state-of-the-art in Semantic Web technology, the key relationships with traditional hypermedia research, and a comprehensive reference list to various sets of literature (hypertext, Web and Semantic Web). A research agenda describes the open research issues in the development of the Semantic Web from the perspective of hypermedia research.</description>
	</item>
	<item>
		<title>A Metadata Framework Developed at the Tsinghua University Library to Aid in the Preservation of Digital Resources</title>
		<link>http://tc.eserver.org/18309.html</link>
		<guid>http://tc.eserver.org/18309.html</guid>
		<description>This article provides an overview of work completed at Tsinghua University Library in which a metadata framework was developed to aid in the preservation of digital resources. The metadata framework is used for the creation of metadata to describe resources, and includes an encoding standard used to store metadata and resource structures in information systems. The author points out that the Tsinghua University Library metadata framework provides a successful digital preservation solution that may be an appropriate solution for other organizations as well.</description>
	</item>
	<item>
		<title>Building the Semantic Web</title>
		<link>http://tc.eserver.org/14913.html</link>
		<guid>http://tc.eserver.org/14913.html</guid>
		<description>In the information age it is widely understood that there is now too much information. Some of this newly created information will most certainly be valuable, but despite marked improvement in search tools, finding the valuable information is a slow panhandle. Perhaps in light of this situation, the W3C under the direction of Berners-Lee has begun to build the foundation for the next phase of the web. This phase, called the Semantic Web, will make information stored with this technology much more processible by machines.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Web-Design/Metadata.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>