rel-home-issues: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
m (Reverted edits by Gowrvw (Talk) to last version by Tantek)
 
(9 intermediate revisions by 8 users not shown)
Line 4: Line 4:
The [http://www.w3.org/TR/html4/types.html#type-links HTML link Types document] does not explicitly list 'home' as a value, but it does list 'index'
The [http://www.w3.org/TR/html4/types.html#type-links HTML link Types document] does not explicitly list 'home' as a value, but it does list 'index'


INDEX is defined as: Refers to a document providing an index for the current document.
<blockquote>INDEX is defined as: Refers to a document providing an index for the current document.</blockquote>


Rel-Home has a slightly different semantics than INDEX, but sometime both are equivalent, in which case, should you use BOTH, or just INDEX?
Rel-Home has slightly different semantics than INDEX, but sometime both are equivalent, in which case, should you use BOTH, or just INDEX?


-Should "start" not be used instead?
-Should "start" not be used instead?
Line 14: Line 14:
The W3C has a document which is pre-HTML4.0, it is [http://www.w3.org/TR/relations.html Proposed REL values]. Home is in this list, but did NOT make it into the final specification. The only note on why is this:
The W3C has a document which is pre-HTML4.0, it is [http://www.w3.org/TR/relations.html Proposed REL values]. Home is in this list, but did NOT make it into the final specification. The only note on why is this:


HOME: RESERVED. Defined by the user (using the WWW_HOME environment variable). This relationship may not be overridden; HTML user agents should ignore any author-supplied REL=HOME setting.
<blockquote>HOME: RESERVED. Defined by the user (using the WWW_HOME environment variable). This relationship may not be overridden; HTML user agents should ignore any author-supplied REL=HOME setting.</blockquote>


I'm not sure how/is any implementation us or honor this, but it is something to be aware of. The W3C was going to add it to the spec, but thought against it for some reason.
I'm [''unsigned''] not sure how/is any implementation us or honor this, but it is something to be aware of. The W3C was going to add it to the spec, but thought against it for some reason.
 
== Absolute URLs ==
 
Why is it recommended that an absolute path is used? I [''unsigned''] had thought the current recommendation was to use relative pathnames to local documents?
 
== Template ==
 
{{issues-format}}
 
== See also ==
*[[rel-home]]
*[[issues]]

Latest revision as of 19:49, 25 August 2013

Rel-Home Issues

Rel-Home of Rel-Index

The HTML link Types document does not explicitly list 'home' as a value, but it does list 'index'

INDEX is defined as: Refers to a document providing an index for the current document.

Rel-Home has slightly different semantics than INDEX, but sometime both are equivalent, in which case, should you use BOTH, or just INDEX?

-Should "start" not be used instead?

un-recommended W3C home value

The W3C has a document which is pre-HTML4.0, it is Proposed REL values. Home is in this list, but did NOT make it into the final specification. The only note on why is this:

HOME: RESERVED. Defined by the user (using the WWW_HOME environment variable). This relationship may not be overridden; HTML user agents should ignore any author-supplied REL=HOME setting.

I'm [unsigned] not sure how/is any implementation us or honor this, but it is something to be aware of. The W3C was going to add it to the spec, but thought against it for some reason.

Absolute URLs

Why is it recommended that an absolute path is used? I [unsigned] had thought the current recommendation was to use relative pathnames to local documents?

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>

See also