[uf-discuss] Versioned Documents
timbarker at hotmail.co.uk
Mon Jan 30 11:57:05 PST 2006
Thanks for the idea Shawn - i think sse could be the answer but i ideally
there would be a microformat available i could use (i guess i'm just lazy!).
To clarify, if you think about Versioned-Documents, they will have a number
version number: 1.0, 1.1, 2.0 etc.
updated by: <person>
update date: <date>
status: draft, published, etc.
First version URI: The URI to the first document version
Previous version URI: The URI to the last document version
Version URI: where the document is
conceptually, the idea of a microformat to describe an individual document
version is very cool
----Original Message Follows----
From: Shawn Carnell <ShawnCarnell at aol.com>
Reply-To: Microformats Discuss <microformats-discuss at microformats.org>
To: Microformats Discuss <microformats-discuss at microformats.org>
Subject: Re: [uf-discuss] Versioned Documents
Date: Mon, 30 Jan 2006 08:40:31 -0500
Tim Barker wrote:
>Hi All - i'd appreciate your thought on how microformats can (or could) be
>applied to solving the problem i'm trying to tackle:
>A lot of corporations have internal document management systems which are
>used to apply change and version control for (mainly) documents.
>Ironically, a large company will have around 8 different internal document
>managements, each focusing on a different type of document or process.
>Seems to me that an RSS feed containg a microformat describing the document
>meta-data, version infomation and enclosed file would be the ideal way to
>distribute document meta-data and version information between different
>systems. I'm thinking that it would work in a similar way to hCard, with
>each document having its own meta data.
Would SSE <http://msdn.microsoft.com/xml/rss/sse/> handle the
versioning/sync issues? You'd still probably want a uf to describe the
document meta-data, 'course.
microformats-discuss mailing list
microformats-discuss at microformats.org
More information about the microformats-discuss