[uf-discuss] Versioned Documents

[Tim Barker]

Thanks Tantek & James for your thoughts. I appreciate it.

James - following on from your suggestion of using Atom. If Atom can handle 
this structure then great. So, I could use this is stream-out the version 
history of a document.

This leads me onto another related question. If you think about it, 
'is_versioned' is a characteristic (or aspect, if you prefer) that could 
apply to many different types of document, each type of document could have 
different meta-data. So, 'contracts' has an date-signed, parties and contact 
amount for example.

The question is, what's the approach to take: Would 'contract' be a candiate 
as a hMicroformat, is there an 'is_versioned' set of attributes and values 
that would be embedded in an Atom feed, or something else.

Something to think about!



----Original Message Follows----
From: James M Snell <jasnell at gmail.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 12:16:32 -0800

I've been playing around with this for Atom and there is no reason to think 
it wouldn't also work with hAtom.

Example:

<feed>
   ...
   <entry>
     <id>tag:example.org,2006:some_doc</id>
     <title>My Document</title>
     <link href="http://.../word.doc?rev=3" />
     <link rel="http://.../diff" href="http://.../word.doc?diff" />
     <link rel="http://.../replaces" href="http://.../word.doc?rev=2" />
     <link rel="http://.../history" href="http://.../word.doc?history" />
     <updated>2006-01-30T12:12:12Z</updated>
     <author><name>James</name></author>
     <x:revision>3</x:revision>
     <x:status>published</xs:status>
   </entry>
   <entry>
     <id>tag:example.org,2006:some_doc</id>
     <title>My Document</title>
     <link href="http://.../word.doc?rev=2" />
     <link rel="http://.../diff" href="http://.../word.doc?diff" />
     <link rel="http://.../replaces" href="http://.../word.doc?rev=1" />
     <link rel="http://.../history" href="http://.../word.doc?history" />
     <updated>2006-01-30T12:11:12Z</updated>
     <author><name>James</name></author>
     <x:revision>2</x:revision>
     <x:status>draft</xs:status>
   </entry>
   <entry>
     <id>tag:example.org,2006:some_doc</id>
     <title>My Document</title>
     <link href="http://.../word.doc?rev=1" />
     <link rel="http://.../history" href="http://.../word.doc?history" />
     <updated>2006-01-30T12:10:12Z</updated>
     <author><name>James</name></author>
     <x:revision>1</x:revision>
     <x:status>draft</xs:status>
   </entry>
</feed>

- James

Tim Barker wrote:
>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 
>of characteristics:
>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.
>
>Shawn
>
>
>_______________________________________________
>microformats-discuss mailing list
>microformats-discuss at microformats.org
>http://microformats.org/mailman/listinfo/microformats-discuss
>
>
>_______________________________________________
>microformats-discuss mailing list
>microformats-discuss at microformats.org
>http://microformats.org/mailman/listinfo/microformats-discuss
>
_______________________________________________
microformats-discuss mailing list
microformats-discuss at microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss