00:10:34 Truman Esmond: I have one for this week 14th as well (one I know is old, but one I thought was “new”) 00:10:58 Sean Bohan (openIDL): Thanks Truman and David - I will track this down 00:12:25 Peter Antley: @David, we are postponing RRDMWG this Friday (Holiday for Good Friday). Not sure if you were at the Friday meeting. 00:13:44 David Reale: I was thank you 00:15:04 Jeff Braswell: The openIDL Adapter is a functional interface that would define and observe an interaction protocol for control and data communication, and would need to support standards for data definitions and formats 00:20:11 Jeff Braswell: How the interface is implemented would follow the clear specification of the interactions and data requirements. Communication of the data request and confirmation is a control-type of interaction; the extraction of data could be a subsequent interaction (e.g., if the data request was more ad hoc and needed to be confirmed ), or — if “pre-confirmed” due to known repetition — could follow the request with an asynchronous response. These are just various modalities of interaction that could be supported. 00:23:07 Jeff Braswell: @David, agree with the flexibility of how/when to keep the HDS “current”, but status dates pertaining to when data was updated would/should be part of the data standard (which is what I think I heard you say ) 00:24:57 Jeff Braswell: RIght, the “as-of” date of the data; the physical update date is another kind of date. 00:26:35 Jeff Braswell: Historical retrofit is generally difficult and not advisable 00:27:33 Jeff Braswell: Format/schema changes are one thing; adding historical content generally not feasible 00:28:26 Jeff Braswell: The concept of “levels” is a good one, and can be forward-compatible 00:31:16 Jeff Braswell: Modifications/extensions to the data standards would/should be done on regular, and fairly infrequent interval — formal versioning, in other words. 00:31:48 Satish Kasala: Satish from The Hartford joined. 00:39:34 Peter Antley: What about the validations? Right now we validate with NAIC data that becomes available 1 year after business happened. 00:42:47 Truman Esmond: It’s available quarterly, but finalized annually w/a quarter delay 00:43:22 Jeff Braswell: Wouldn’t it be possible to keep historical snapshots of prior years (for annual/end-of-year report datasets ) ? 01:02:22 Jeff Braswell: There are differences in business requirements that will affect different use cases, data standards, and interface/adapter interactions. 01:03:58 Truman Esmond: I have to drop at the top of the hour. 01:04:41 Jeff Braswell: The hash is perhaps then more of a response/request control communication response 01:04:47 Jeff Braswell: yes 01:04:52 Tsvetan Georgiev: yes 01:05:31 Truman Esmond: This event is on the mailing list events page the TSC should be on there too (and is on the google cal)