Classification: For internal use only Bi-temporality is overkill for simple document version tracking.
Bi-temporality really helps if you have a data set that * Changes over time; * Refers to the future or past within the data set. With a data set like that, you sometimes get questions like "six months ago, what did we think would happen a year ahead, and how does that compare to what we now think will happen in six months". It's hard to answer that with just simple document versioning, but you can answer it with bi-temporality. Cheers, Tony. From: [email protected] [mailto:[email protected]] On Behalf Of Robert Del Toro Jr. Sent: 18 November 2015 15:18 To: MarkLogic Developer Discussion Subject: [MarkLogic Dev General] Bitemperal Documents vs Document Library Services What are the advantages and disadvantages of using either of these services for document version tracking? It seems that with Bitemperal docs, I simply get a record of the document state at a specific time and with DLS I can store a bit more info about the change, is that all there is to it? Why are bitemperal documents always described as being well-suited for financial, insurance, or other regulatory data? Couldn't the same thing be achieved with DLS? Robert --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy.
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
