{"id":52,"date":"2005-01-22T02:04:03","date_gmt":"2005-01-22T02:04:03","guid":{"rendered":"http:\/\/lachy.id.au\/log\/2005\/01\/link-relationships-revisited-part-2"},"modified":"2006-04-30T23:48:52","modified_gmt":"2006-04-30T23:48:52","slug":"link-relationships-revisited-part-2","status":"publish","type":"post","link":"https:\/\/lachy.id.au\/log\/2005\/01\/link-relationships-revisited-part-2","title":{"rendered":"Link Relationships Revisited, Part 2"},"content":{"rendered":"<p>As I mentioned in <a href=\"http:\/\/lachy.id.au\/blogs\/log\/2005\/01\/link-relationships-revisited-part-1\">part\r\n\t\t1<\/a>, I plan to discuss major modification to my original\r\n\t    <a href=\"http:\/\/lachy.id.au\/blogs\/log\/2004\/08\/link-relationships\">link relationships\r\n\t    proposal<\/a> taking into account feedback and ideas received\r\n\tfrom a variety of sources. For this, I am currently writing, and will soon\r\n\t    publish, the first working draft for a link relationship profile called\r\n\t    \u201c<cite>Web Communication Link Relationships<\/cite>\u201d. The aim is to define\r\n\t    link relationships that will facilitate web communication through increased\r\n\t    linking semantics. This proposal, rather than focussing on rating systems,\r\n\t    focuses on the semantics of the links to be used by user agents in ways\r\n\t    that will most benefit the user.<\/p>\r\n<p>The criteria I will use to determine which relationships are appropriate and\r\n\tto make improvements includes:<\/p>\r\n<ul>\r\n\t<li>Link Relationships should express semantics to indicate at least one of:\r\n        <ul>\r\n        \t<li>The semantic relationship between resources.<\/li>\r\n        \t<li>The type of resource.<\/li>\r\n        \t<li>The purpose of the link<\/li>\r\n       \t<\/ul>\r\n\t<\/li>\r\n\t<li>Relationship semantics should make sense in the context of any\r\n        \t\tnumber of user agents.<\/li>\r\n\t<li>Relationship names should accurately represent the semantics of the relationship,\r\n\t\t\tand<\/li>\r\n\t<li>Relationship semantics should avoid expressing user-agent-implementation\r\n\t\t\tspecific functionality.<\/li>\r\n<\/ul>\r\n<p>From those criteria, I determined that the number and type of categories I\r\n\toriginally included (<a href=\"http:\/\/www.lachy.id.au\/blogs\/log\/2004\/08\/link-relationships#userfeedback\">user\r\n    feedback<\/a>, <a href=\"http:\/\/www.lachy.id.au\/blogs\/log\/2004\/08\/link-relationships#quality\">quality<\/a>, <a href=\"http:\/\/www.lachy.id.au\/blogs\/log\/2004\/08\/link-relationships#accuracy\">accuracy<\/a>, <a href=\"http:\/\/www.lachy.id.au\/blogs\/log\/2004\/08\/link-relationships#accessibility\">accessibility<\/a>, <a href=\"http:\/\/www.lachy.id.au\/blogs\/log\/2004\/08\/link-relationships#rating\">rating<\/a> and <a href=\"http:\/\/www.lachy.id.au\/blogs\/log\/2004\/08\/link-relationships#endorsement\">endorsement<\/a>)\r\n    were mostly very inappropriate. I decided that the categories: quality, accuracy,\r\n    accessibility and rating should be removed entirely because they don&#8217;t meet\r\n    the criteria, nor were they particularly useful. This left only the\r\n    values from user feedback and endorsement; however, user feedback\r\n    is being renamed to user contribution because a contribution may not necessarily\r\n    be the result of feedback, but rather the start of a new thread, for example.<\/p>\r\n<h5 id=\"user-contribution\">User Contribution<\/h5>\r\n<p>The user contribution category is designed to identify links which have been\r\n\tpublished as a result of user contribution. It is common for several different\r\n\tkinds of links to be published as a result of user contribution including user\r\n\tidentification (eg. User\u2019s homepage or e-mail address), the use of a referral\r\n\tmechanism (eg. Pingback or Trackback) or links contained within the user\u2019s contribution.\r\n\tAs a result, I have the following relationships defined for this category:<\/p>\r\n<ul>\r\n\t<li><code class=\"markup attribute-value\">user<\/code><\/li>\r\n\t<li><code class=\"markup attribute-value\">referral<\/code><\/li>\r\n\t<li><code class=\"markup attribute-value\">pingback<\/code><\/li>\r\n\t<li><code class=\"markup attribute-value\">trackback<\/code><\/li>\r\n\t<li><code class=\"markup attribute-value\">contribution<\/code><\/li>\r\n<\/ul>\r\n<p>Note: Both pingback and trackback are implementation specific referral mechanisms,\r\n\tbut are included because their mechanisms are so widespread and several interoperable\r\n\timplementations of each already exist. See the <a href=\"http:\/\/hixie.ch\/specs\/pingback\/pingback-1.0\">Pingback\r\n\t1.0<\/a> and <a href=\"http:\/\/www.movabletype.org\/trackback\/\">Trackback<\/a> specifications.<\/p>\r\n<h5 id=\"endorsement\">Endorsement<\/h5>\r\n<p>The original endorsement category is being included with the same relationships,\r\n\tthough their definitions are being revised. The relationships in this category\r\n\twill be:<\/p>\r\n<ul>\r\n\t<li><code class=\"markup attribute-value\">advert<\/code><\/li>\r\n\t<li><code class=\"markup attribute-value\">endorsed<\/code><\/li>\r\n\t<li><code class=\"markup attribute-value\">unendorsed<\/code><\/li>\r\n<\/ul>\r\n<h5 id=\"communication-tracking\">Communication Tracking<\/h5>\r\n<p>A few months ago, <a href=\"http:\/\/boxofchocolates.ca\/\">Derek Featherstone<\/a> had an interesting discussion about <a href=\"http:\/\/boxofchocolates.ca\/archives\/2004\/08\/26\/tracking-the-spread-of-ideas\">tracking\r\n\tthe spread of ideas<\/a>. In it, he discusses the common attribution method called\r\n\tthe \u201cvia\u201d link, used among web-logs (in particular, link-logs) and other similar\r\n\tsites for indicating where an interesting resource was found. The aim of which\r\n\tis to not only find out who is linking to a particular resource, but from whereabouts\r\n\tpeople have located it.<\/p>\r\n<p> This is an interesting concept because news travels\r\n\t\trather quickly around the blogosphere, but with little indication of\r\n\tthe communication paths. As a result, I am including the via link within this\r\n\tproposal, but I\u2019m also extending it slightly to address some other related issues\r\n\tincluding related links.<\/p>\r\n<p>In the article, Derek mentions that it is difficult to semantically associate\r\n\ta \u201cvia\u201d link with the resource and illustrates a possible solution using\r\n\tthe\r\n\t<code class=\"markup attribute-value\">for<\/code> attribute, yet notes that it is also invalid markup according to\r\n\tthe <abbr title=\"Hypertext Markup Language\">HTML<\/abbr> specification. To address this problem, I have decided that rather\r\n\tthan trying to explicitly associate the \u201cvia\u201d link with the resource, it\r\n\tmay be possible to implicitly do so. The full details of how will be discussed\r\n\tin the draft specification, but the relationships being included within this\r\n\tcategory include:<\/p>\r\n<ul>\r\n\t<li><code class=\"markup attribute-value\">resource<\/code><\/li>\r\n\t<li><code class=\"markup attribute-value\">related<\/code><\/li>\r\n\t<li><code class=\"markup attribute-value\">related-to<\/code><\/li>\r\n\t<li><code class=\"markup attribute-value\">via<\/code><\/li>\r\n<\/ul>\r\n<h5 id=\"resource-tracking\">Resource Tracking<\/h5>\r\n<p>The final category includes relationships for identifying and tracking resources\r\n\tcommonly used in web communication, such as web-logs and news sites. Usually,\r\n\teach article has permanent link associated with it and archival indexes\r\n\tare provided for the articles. Many sites also have facilities, and designate\r\n\tpages\/areas, for user contributions (comments). Finally most blogs, and increasingly\r\n\tnews sites, provide syndication feeds for their articles, link logs and occasionally\r\n\tcomments. For these purposes, I\u2019ve defined the following relationships:<\/p>\r\n<ul>\r\n\t<li><code class=\"markup attribute-value\">permalink<\/code><\/li>\r\n\t<li><code class=\"markup attribute-value\">comments<\/code><\/li>\r\n\t<li><code class=\"markup attribute-value\">archive<\/code><\/li>\r\n\t<li><code class=\"markup attribute-value\">feed<\/code><\/li>\r\n<\/ul>\r\n<h5 id=\"other-suggestions\">Other Suggestions<\/h5>\r\n<p>Several other relationships have been suggested and considered, but so far\r\n\trejected for various reasons including not meeting the criteria or their usefulness.\r\n\tSome of these include:<\/p>\r\n<dl>\r\n\t<dt><code class=\"markup attribute-value\">tag<\/code> <\/dt>\r\n\t<dd><a href=\"http:\/\/www.technorati.com\/tag\/\" title=\"Technorati Tags\">Technorati defines<\/a>, and uses, user-agent-implementation specific functionality\r\n\t\tand it seems to be inappropriately named.<\/dd>\r\n\t<dt><code class=\"markup attribute-value\">category<\/code><\/dt>\r\n\t<dd>Generic version of <code>tag<\/code>, but not sure how it could be defined and used more\r\n\t\tappropriately.<\/dd>\r\n\t<dt><code class=\"markup attribute-value\">external<\/code><\/dt>\r\n\t<dd>Suggested to indicate links to external sites, but not sure how useful it\r\n\t\tis.<\/dd>\r\n<\/dl>\r\n<p>Feedback is welcome and I will still incorporate suggestions and revisions\r\n\tinto the Web Communications Link Relationship working draft before I publish\r\n\tit in a few days.<\/p>\r\n","protected":false},"excerpt":{"rendered":"As I mentioned in part 1, I plan to discuss major modification to my original link relationships proposal taking into account feedback and ideas received from a variety of sources. For this, I am currently writing, and will soon publish, the first working draft for a link relationship profile called \u201cWeb Communication Link Relationships\u201d. The &hellip; <a href=\"https:\/\/lachy.id.au\/log\/2005\/01\/link-relationships-revisited-part-2\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Link Relationships Revisited, Part 2<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a>","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[9,10,2],"tags":[],"_links":{"self":[{"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/posts\/52"}],"collection":[{"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/comments?post=52"}],"version-history":[{"count":0,"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/posts\/52\/revisions"}],"wp:attachment":[{"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/media?parent=52"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/categories?post=52"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/tags?post=52"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}