Daniele Romagnoli from Geosolution recently send us a document on Coverage I/O metadata. It sound like a very good draft to me. In the next bunch of emails, I'm going to comment some sections. I will send separated emails for different issues in order to create distinct threads.
For this email, I will just raise minor issues on class namings. AbstractSpatioTemporalCoverageReader (figure 3) ----------------------------------------------- If there is no SpatioTemporalCoverageReader, I would suggest to drop the "Abstract" prefix even if the class is abstract. This is a common practice in J2SE library: Reader, ImageReader, InputStream, Buffer, DataBuffer, RectangularShape, Rectangle2D, Ellipse2D and much much more are all abstract classes. Really, the "Abstract" prefix or "Default" prefix are just for distinguish a default base implementation from the interface it implements. ImageIOReader (figure 3) ------------------------ "IO" is usually for "Input/Output". It is strange to have the "Output" part in a Reader. I guess you are talking about the J2SE ImageReader? Figure 4 also have a "AbstractImageReader". I'm not sure if you are talking about the J2SE ImageReader or a new class. I guess that this is the J2SE one, in which case the "Abstract" prefix needs to be removed. Minor typos ----------- Page 17: "For our purposes we will to try to respect ...". There is one extra "to". Page 21 in the table: "stirng" should be "string". ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
