Vertical search on a Semantic web

What is Vertical Search?

Vertical search engines
A vertical search engine differentiates from a regular search engine due to it’s focus on a given subject or content type.

Topic focused vertical search engine
A great example of topic based search is Trip Advisor, a website with great information for people who are looking to travel.

Content focused vertical search engine
Media Type search can be found on sites such as Youtube, Vimeo, Flickr and others, where you search within specific media file types.
For example when I’m looking to fix CSS bugs my basic instinct makes me search on Google but if the first page doesn’t return the best answer for my problem I use Delicious, for books I use Amazon, etc.

The advantage of using a vertical search engine is that it will narrow the amount of information indexed which will result in more relevant search results.

What is Semantic Web

Semantic Web Experience
Semantic web can be interpreted as an intelligent, self-learning web. The future of semantic web will belong to services that will understand the user and deliver them the best answers for it’s need.

While it’s not perfectly clear for users, semantics have been implemented on several websites for a while now. Amazon was, as far as I know, the first site to implement a semantic user experience when it started suggesting further products based on users preferences. When a user bought a book, Amazon’s software would recommend other books based on purchases made by users who have bought that very same book. The result was a massive increase of sales and profit.
Google also is improving it’s search engine by reordering search results based on user navigation history.

So it’s fair to say a semantic web, or Web 3.0 as some call it, is each more a reality and not a trend. This brings me to this posts topic:

Can Vertical Search Engines coexist in a semantic web?

Personally I see vertical search engines as a the first step into the semantic web concept. I believe some people will say there completely separate things and I’d love to hear a different opinion on the subject.
If I want to find a needle inside a huge barn and know the needle is inside a haystack, I’ll search only inside the haystack. The haystack is my vertical search engine.

Using the same metaphor with semantic web once I’m inside the barn I’ll get a suggestion the needle is probably on the haystack, along with a picture of how the needle might look like and also where in the haystack it will probably be.
Eventually, once I find the needle, related subjects such as strings, other kinds of needles, groups, etc would be suggested as a complement to my interest on the needle.

Being the first time I searched for something I would also get suggestions related to hay and the haystack but if I show no interest in that, further similar searches would not retrieve those suggestions.

What do you think about the future of vertical search? How can it grow in order to survive on a Web 3.0 environment?

WordPress Theme CSS Reset

WordPress, like any CMS has a default structure with it’s how template hierarchy, template tags and default CSS classes that are obligatory on every WordPress theme in order for WordPress to work correctly.

Download WordPress Theme CSS Reset

Eric Meyer’s CSS Reset

A CSS reset will set all default values of HTML elements to zero. This will improve cross-browser CSS compatibility as different browsers will set different values for HTML / XHTML elements.

Eric Meyer’s CSS reset it a wonderful CSS reset for default HTML styles but when it comes to WordPress you need to contemplate WordPress default CSS styles.

WordPress default styles

As I mentioned before WordPress, as a CMS, creates some default CSS classes that applies to HTML elements and that you must include in your Theme style.css file in order for the Visual Editor (WYSIWYG Editor) to work correctly:

.alignleft {
   float: left;
}

.alignright {
   float: right;
}

.wp-caption {
   border: 1px solid #ddd;
   text-align: center;
   background-color: #f3f3f3;
   padding-top: 4px;
   margin: 10px;
   /* optional rounded corners for browsers that support it */
   -moz-border-radius: 3px;
   -khtml-border-radius: 3px;
   -webkit-border-radius: 3px;
   border-radius: 3px;
}

.wp-caption img {
   margin: 0;
   padding: 0;
   border: 0 none;
}

.wp-caption p.wp-caption-text {
   font-size: 11px;
   line-height: 17px;
   padding: 0 4px 5px;
   margin: 0;
}

Beyond these classes there are others to take in consideration. These classes are applied when showing categories, specific pages, widgets, links and so on. I’ll leave them blank so you can personalize as you wish. All the elements where the following classes applied have been reseted by Meyer’s CSS Reset.

When you put all of the CSS together you will get a complete CSS Reset for WordPress themes. Ready to go, ready to use on your own themes.
You can download the WordPress Theme CSS Reset by clicking on the link or just copy / paste the following code on to your style.css theme file:

/* WordPress WYSIWYG default syles */
.alignleft {
   float: left;
}

.alignright {
   float: right;
}

.wp-caption {
   border: 1px solid #ddd;
   text-align: center;
   background-color: #f3f3f3;
   padding-top: 4px;
   margin: 10px;
   /* optional rounded corners for browsers that support it */
   -moz-border-radius: 3px;
   -khtml-border-radius: 3px;
   -webkit-border-radius: 3px;
   border-radius: 3px;
}

.wp-caption img {
   margin: 0;
   padding: 0;
   border: 0 none;
}

.wp-caption p.wp-caption-text {
   font-size: 11px;
   line-height: 17px;
   padding: 0 4px 5px;
   margin: 0;
}

.aligncenter, div.aligncenter {
   display: block;
   margin-left: auto;
   margin-right: auto;
}

/* WordPress template default classes */

.categories {}
.cat-item {}
.current-cat {}
.current-cat-parent {}
.children {}
.pagenav {}
.page_item {}
.current_page_item {}
.current_page_parent {}
.current_page_ancestor {}
.widget {}
.widget_text {}
.blogroll {}
.linkcat{}

/* Eric Meyer's CSS Reset v1.0 | 20080212 */

html, body, div, span, applet, object, iframe,
h1, h2, h3, h4, h5, h6, p, blockquote, pre,
a, abbr, acronym, address, big, cite, code,
del, dfn, em, font, img, ins, kbd, q, s, samp,
small, strike, strong, sub, sup, tt, var,
b, u, i, center,
dl, dt, dd, ol, ul, li,
fieldset, form, label, legend,
table, caption, tbody, tfoot, thead, tr, th, td {
	margin: 0;
	padding: 0;
	border: 0;
	outline: 0;
	font-size: 100%;
	vertical-align: baseline;
	background: transparent;
}
body {
	line-height: 1;
}
ol, ul {
	list-style: none;
}
blockquote, q {
	quotes: none;
}
blockquote:before, blockquote:after,
q:before, q:after {
	content: '';
	content: none;
}

/* remember to define focus styles! */
:focus {
	outline: 0;
}

/* remember to highlight inserts somehow! */
ins {
	text-decoration: none;
}
del {
	text-decoration: line-through;
}

/* tables still need 'cellspacing="0"' in the markup */
table {
	border-collapse: collapse;
	border-spacing: 0;
}

Related links:

Justinmind Prototyper

It was build to help create interactive prototyping tools and allows you to define actions simply by selecting the object and applying an action to it. You also have the ability to create variables which can be interesting for development point of view.
Two key features that made me use this software more than once is the ruler with pixel units and the grid which are fundamental for anyone wireframing a website or application and some simply don’t understand the importance of pixel units. Even tough on JustinMind Prototyper the ruler only shows units from 50 to 50 pixels (0, 50, 100, 150, etc).

If you are looking to take your project beyond wireframing you might like to create fluxograms with the Scenario tool, comment on your project and define the requirements which help creating the project documentation.

It’s a very complete, useful and functional tool but there are too aspects I must refer to and hopefully JustinMind Prototyper developers will implement this in the future:

  1. Importing new widgets or stencils. One thing that makes OmniGraffle so grate is the possibility to use stencils created by others. This can make the difference for very boring wireframes to sexy wireframes. For what I’ve tested you can create your own widgets as long as they are in image format. In wireframes presentation is 80% of captivating your client.
  2. Fluid workspace. I am forced to work on the reduced canvas area while wireframing. I should be able to put that window on a different monitor.

Link: Justinmind Prototyper

The Gutenberg Diagram in Web Design

The Gutenberg rule points out a user behavior called reading gravity which is the western habit of reading left-to-right, top-to-bottom. It can be represented as a simple diagram that splits a page in four quadrants:

Gutenberg Diagram

  1. A Primary Optical Area
  2. a strong follow area
  3. a weak follow area
  4. and a Terminal Area

The higher left portion of the page is the user primary focus, it’s where the eyes will automatically focus regardless if the user is searching for something, wanting to read or just doing a quick scan on the page.

The second stage of the reading habit is moving to the higher right portion of the page, you can think of it as a follow up from the left portion but less important. It’s not a good idea to break the reader’s experience created from the starting point. Meaning that if you have a call to action the user will stop at this point and act.

The lower left portion is the blind portion of the Gutenberg diagram, although readable the user will not give much importance to content in this area of the page.

When the user reaches the lower right portion of the page there is a break in the reading / page scan process and the user will need to take an action. This is the perfect spot to insert call-2-action such as buttons, links, forms, video, etc.

By understanding the reading patterns of the users who visit your website you are able to place the most important content in the areas where they will be most effective.

If you’ve read about web users reading patterns you probably read Jacob Nielsen’s report on the F-Shaped Pattern that shows the lower right area as the less important area. I wouldn’t say this theory is wrong but consider the F-Shaped pattern for users that are scanning the page and the Gutenberg Diagram for user that are reading or genuinely interested in the content.

F-Shaped Pattern

For example, a user is searching for information about the Gutenberg Diagram and reaches this article. The user will look at the diagram image and read the lines above the image starting an inverted Gutenberg Diagram.
If the user is looking to buy a product on E-bay I believe the primary pattern on the product listing pages will be a typical Gutenberg Diagram.

On the other hand when a user is searching for information on a search engine and finds multiple articles about it, the user will engage an F-shaped pattern when visiting those pages trying to find quick and concrete references to it’s search.

Complementary readings:

Nikon Virtual Touch

The future of technology is augmented reality. Nikon decided to take Digital Cameras to the next level with their Coolpix series and have recently introduced the Nikon CoolPix S70 with touch screen allowing users to get more interactive with their cameras and reducing the camera size.
Apart from the camera itself Nikon also released a place where you can see navigate pictures using a webcam and gestures removing the need to touch or click.

Visit Nikon’s CoolPix website and try their augmented reality experience using your webcam and basic gestures to navigate and zoom their gallery.