On Mon, Oct 28, 2013 at 11:53 AM, Christopher Sean Morrison <[email protected]> wrote: > > On Oct 28, 2013, at 6:53 AM, Tom Browder wrote: > >> (Note that I I think it is better not to mix >> time stamps with attributes.) > > Not sure I understand this. If you're saying that we should not time stamp > attributes themselves, > I agree.
Hm, I thought originally you thought that all attributes should get time stamps. > If you're saying we should not store time stamps as attributes, I might need > some convincing. I guess I need more on your implementation plan, to wit: 1. Are attributes to be time stamped? If so, and we use key=binaryattribute-timestamp, we get a lot of overhead space taken up with the keys. 2. If objects only are to be time stamped, will that be in the object body or in a separate object again with key=binaryattribute-timestamp (and more space overhead for keys). I guess I need more on your ideas for binary attribute implementation. . >> While on the subject of the database I was thinking that we need some >> kind of DB analysis and management program (I think such is in the > > This would be a great project for anyone interested in getting involved on a > more serious level. > It's an isolated feature. It's very low-level. Lots of design possibilities. Roger! > I don't see a need or value for providing them optionally considering the > implementation should have nominal disk and CPU implications. If it has > more, we probably haven't thought about it hard enough or implemented it well > enough. Agree. > We need some means to discuss and mark-up beyond comments in the xml. > Suggestions? The spec used to exist as a word doc with reviewer comments. > Docbook is rather limited in that capacity. For sure. I guess we could put it back into MS Word format, but looks-wise that would be a downgrade. Cheers! -Tom ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
