directory-proposal

hDirectory Proposal

This proposal is premature and fails to follow the microformats process.

Please see and use existing microformats, e.g. rel-directory, hListing (the combination of which appears to completely handle the use cases), before making new proposals.

Tantek 20:58, 25 September 2009 (UTC)

hDirectory is a proposal for an open, distributed directory (UK English: link directory; classifieds) format suitable for embedding in (X)HTML. hDirectory is based on hListing and would be one of several microformats open standards.

Draft Proposal 2008-11-20

Editor

• Yuval Ararat, Yuval Ararat

Introduction

Will be adding the details soon currentlly its on my website as a post. hDirectory Microformat Idea

The Problem

While there are dozens of formats used on thousands of web directories, there is no single standardised format for presentation of web directory listings. Having a standardised directory listing format will significantly benefit readers, aggregators, search engines, automations and researchers alike.

Thoughts on a Microformat for News

I found substantial base of attributes and fields with hListing, and simplified an initial effort at a data format for directory listing using fields already in hListing, the focus of this format is to add the required fields enabling you to create a meaningful Web Directory format.

The difference from the hListing is the purpose of the implementation and the core difference in the item properties and purpose, a Directory listing is an item with no associated price nor an expiry date, the ability to get the summery of the item in a condense format is one of the key parts of the listing.

The fields selected are a combination of the common fields from many of the Web Directory formats currently in use, and the introduction of new fields, TBD.

Common Directory Listing Fields

TBD.

Issues

Please add new issues to the bottom of the Open Issues section by copy and pasting the Template. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

Issues Template

Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.

Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.

<div class="hentry">
{{OpenIssue}} 
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2
</div>
</div>

Current Issues

TBD.