xfolk-brainstorming: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 1: | Line 1: | ||
= xFolk Brainstorming = | = xFolk Brainstorming = | ||
xFolk is a bare bones microformat for describing and tagging | xFolk is a bare bones microformat for describing and tagging things represented by a URL. This definition, although simple, is pretty broad. xFolk brainstorming is a set of fairly free-flowing ideas about the future directions of xFolk. Are there functional issues you feel xFolk should address? Other issues or ideas? Put them here. | ||
== Authors == | == Authors == | ||
Line 11: | Line 11: | ||
* We will be adding the ability to tag any visible element that has an href attribute. This includes <img> and <object> elements. It is likely that there will be more specialized, domain-specific microformats for some of these items in the future. | * We will be adding the ability to tag any visible element that has an href attribute. This includes <img> and <object> elements. It is likely that there will be more specialized, domain-specific microformats for some of these items in the future. | ||
== Attribute Value Naming == | |||
* Should we change the name of taggedlink, used to represent the item to be tagged to a more neutral name such as tagged or taggedresource? | |||
The editor's current thinking is that taggedlink represents well the fact that people are identifying things represented by a URL. However, as some discussants have pointed out, the name may be too narrow. The editor is waiting to collect further data and use cases. |
Revision as of 16:20, 11 July 2005
xFolk Brainstorming
xFolk is a bare bones microformat for describing and tagging things represented by a URL. This definition, although simple, is pretty broad. xFolk brainstorming is a set of fairly free-flowing ideas about the future directions of xFolk. Are there functional issues you feel xFolk should address? Other issues or ideas? Put them here.
Authors
Add your name to the end of the list if you contribute an idea.
Functional Extensions
- We will be adding the ability to tag any visible element that has an href attribute. This includes <img> and <object> elements. It is likely that there will be more specialized, domain-specific microformats for some of these items in the future.
Attribute Value Naming
- Should we change the name of taggedlink, used to represent the item to be tagged to a more neutral name such as tagged or taggedresource?
The editor's current thinking is that taggedlink represents well the fact that people are identifying things represented by a URL. However, as some discussants have pointed out, the name may be too narrow. The editor is waiting to collect further data and use cases.