tag:blogger.com,1999:blog-1367102802658603789.post7691860528184157344..comments2024-01-29T04:29:03.583-08:00Comments on David Clunie's Blog: Two (or More) Views of the World ...David Cluniehttp://www.blogger.com/profile/17331067317921452126noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-1367102802658603789.post-32900100031047726632012-05-29T22:04:08.053-07:002012-05-29T22:04:08.053-07:00David,
I am totally confused reading this. Just w...David,<br /><br />I am totally confused reading this. Just where are you heading down? Is this an extension of the Q/R models just like the relational queries, or is it something completely new and it gets us into the same discussions we were having last year that led to your framing the big stuff post. I thought you and the committee took a firm stance and the issue was resolved, and how the synthetic MF objects were accessed retrieved and stored were at the discretion of the implementation? If you include them, as exceptions, in the Q/R models you will get into implementation space and have to deal with issues, whether the synthetic MF images are real objects or they are just temporary representations of the genuine single and multi-frame objects that are part of the acquisition and post processing. I would think, if one choses an implementation that takes advantage of these objects, one would have a cache server where they get instantiated based on rules specific to the implementation and cached till the eviction policy kicks in. I am not in favor of changing the information model of the base standard because we allowed transient representations of the original objects. That would affect too many deployed implementations.<br /><br />Just my few pesos....and please take it with a few grains off the rim of the margarita glass, since I have not been keeping close watch on this subject. My goal was only to get it under the normal procedural control of the committee and let the group make intelligent decisions. This particular post gives me concerns.<br /><br />dee<br />;-Ddeehttps://www.blogger.com/profile/11925645227214733022noreply@blogger.com