Tantek: stub to capture some background, reasoning, for an explicit renaming of a well established property name

2013-06-05T19:50:39Z

stub to capture some background, reasoning, for an explicit renaming of a well established property name

New page

{{stub}}

This page is for documenting background / reasoning for using "p-job-title" in [[h-card]] instead of "title" from [[hCard]]/[[vCard]]. Any such renaming should be an exception and not a regular occurence. Thus we must document the background (problems, prior art) for deciding to do so.

== Problems with title ==
* 'title' is overloaded and ambiguous
* 'title' is mostly presentational, when there are other more semantic terms that can and are used.
** E.g. 'name' is often more accurate/precise/semantic, e.g.
*** song names - iTunes has "Name" as the header, not "Title"
*** blog posts - [[h-entry]] has "p-name" since that's what it really is, the name of an article or blog post.

== Prior art for job-title ==
* The [[hcard-input-formats#Microsoft_VCARD_NAME|Microsoft vCard object model]] uses "JobTitle" - camelcased per JS/DOM conventions, microformats [[naming]] equivalent is "job-title"
* Explicit consideration and adoption of "jobTitle" (camelcasing for similar reasons) in [https://wiki.mozilla.org/WebAPI/ContactsAPI#ContactProperties ContactsAPI ContactProperties interface]

== See Also ==
* [[naming]]
* [[hCard]]
* [[h-card]]
* [[h-entry]]

job-title - Revision history

Tantek: stub to capture some background, reasoning, for an explicit renaming of a well established property name