Look for unique ID pattern which easy indexed by search engines

Question

Like from Microsoft - \"KB2756872\" or from National Vulnerability Database - \"CVE-2010-1428\" or from Red Hat - \"RHSA-2010:0376\" or from OIDs -

Answer 1

You can use year and number based article identifier just like CVE identifiers. Since you need revisions as well, you can append dot after the identifier to clarify the version. For example, for an AWesome Blog Service, AWBS-2012-1.0 would refer to original document, AWBS-2012-1.1 would refer to first revision etc.

However, you need to make sure that AWBSs are unique before you use them. CVEs are assigned manually from the pool. You would probably need some kind of service that assigns AWBS from pool. It could be a simple database query.

Answer 2

You could use Tag URIs, as defined by RFC 4151.

They are globally unique, and everyone who owned a domain name or an email address for at least a day can mint them.

Note that these URIs only identify, they don’t locate. So a Tag URI doesn’t say anything about where something is published.

Let’s say your site’s domain is "example.com". If you create a blog post, you could create the following Tag URI:

tag:example.com,2012-12:cute-cat

Note that the date in this URI is not a publication date! It must be a (past) date on which you owned the domain (resp. email address). If you registered your domain in 2003, you could always use Tag URIs starting with tag:example.com,2004: (not "2003", because "2003" would mean "2003-01-01", which might be a time where you didn’t own the domain yet), followed by a (unique) string under your control. However, if you like you could always use the publication date, of course. But don’t use future dates.