• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Stop wasting time looking for files and revisions. Connect your Gmail, DriveDropbox, and Slack accounts and in less than 2 minutes, Dokkio will automatically organize all your file attachments. Learn more and claim your free account.



Page history last edited by Silona Bonewald 10 years, 6 months ago

Since Drupal is a CMS we can make sure that is always creates URLs that point to the "current" version.  That way web site visitors NEVER see the ugly URLs. 


It can also add in the backend Microformat style anchor tags and hash tags within the document.  Enabling a verifiable version system to be implemented properly on the external archive servers.


Automatically publish all changes to the archive servers listed in the DNS.


We could also create a pretty module like the one in Adrian's presentation that pops up when you hover and suggests a permalink.  It can also publish the permalink automatically to the majority of social media sites like facebook, twitter and digg. 


We estimate this would not take very long to implement perhaps a month?


David's notes on Drupal integration


Drupal has hooks to support trapping content update events. A module can use these hooks to automatically push document updates to a Citability server by "pinging" the appropriate Citability server URL. A module like this would take very little time to write.


Deeper integration could include:


  • Informing the Citability server of deletion and location changes so the Citability archive can better track documents.
  • Pulling versioning metadata for the current document from the Citability server to provide a quick way to browse the archive.
  • Sending authorship and Drupal revision log data to the Citability server.
  • Offering permalinks in the form of Citability server URLs.
  • Integrating good anchor tags in the document.
  • Offering the Citability server a "clean" document version with navigation and other ephemera stripped.

Comments (4)

susan.turnbull@gsa.gov said

at 12:28 pm on May 15, 2009

I use a Collaborative Work Environment from www.cim3.com that supports permalinks (called node ids or purple numbers in this setting). They're automatically generated in all wiki content and discussion forum archives. This really matters for effective use of content, sharing, and comment reconciliation. Open source code extensions for this capability are now available for mediawiki and perhaps readily extensible to your space.

Silona Bonewald said

at 12:04 pm on Aug 19, 2009

yes we are talking of purple numbers for paragraphs in websites not just wikis (So I would like to expand it :-)) We also want something simpler for legal notation. Please see the work at http://citability.pbworks.com/Citable-Documents-Specification for more details. And thanks so much for visiting!

Ori Pekelman said

at 9:38 am on Aug 25, 2009

Basically Drupal supports both versioning and permalinks (either nice ones based on pathauto, or ugly ones based on the node number) revisions would usually not modify the url. But this is more a choice issue for the creators of specific websites. I don't think this is something a framework should impose. In Drupal 7 (code freeze in less then a week, expect an alpha real soon) will probably have some very deep RDFa integration. This might very well be the correct layer in which to implement this (a revision that changes a url having some kinf of relation defined to the earlier one).

As for the module I am not sure I understood, but there are a bunch of modules that support publishing to many different platforms. there is also an implementation of BlogAPI, not counting the services module that can help in implementing "pings" on URL changes. Could you clarify what this module should do?

On a general note: the problem you are addressing is real, but I am not sure how much the solution proposed is a good one. URLs are already supposed to do exactly this. We have paths and anchors, most importantly it requires too many people to modify their web architecture in order for this to provide usefullness. The better approach would probably either to add some meta data dublin core style where a new revision always points to the old one, just a rel micro tag, or do it outside of the document (xlink style with reversed links). The main question for me in resolving these issues is: how can we propose a solution that already works with the existing stuff and requires minimal technical change while providing maximum immediate value.

So yes solutions in paltforms like Drupal provide great market penetration very quickly, but it will still only cover "new" sites and only those in the platforms that implement this in a traversal manner (and in a way by forcing this on users...)

Silona Bonewald said

at 1:43 pm on Aug 25, 2009

you are misunderstanding some of both implementation and purpose so it's kinda hard on where to start...


I will ask that David strauss be more specific about the Drupal implementation. But just to reiterate... drupal is NOT the only implementation. The more important aspect is the abstraction of the archive server that works directly with drupal and creates the actual citable links. NORMAL permalinks are NOT citable as the underlying information is allowed to change.

If you read the http://citability.pbworks.com/QuickFix and http://citability.pbworks.com/ArchiveServers I think you will understand more. To see this is NOT a drupal specific solution and it actually target to sit on top of old crusty systems. But drupal could implement this quickly and cleanly.

You don't have permission to comment on this page.