Hey all, I'm slogging through the various catalog specs: it's all hard going for little return so far (I'm in the abstract levels still). One question arises.
We know from the geoserver/geotools/udig experience that part of what we need to track is 'metadata about the data as we experience it' I'm calling this 'metainfo' simply to have a quick label for it. This stuff is inherently *not* something anyone else can provide for us. It ranges from info about our experience of the service such as responsiveness, throughput, error rates, correctness of the advertised capabilities, and 'last time of successful use' to info about our experience of the data such as 'real bounds of the data provided' or 'that data sucks, I'm never using it again.' So far, none of the specs mention this as a different body of metadata from that which can provided by a service. Can any of you comment about how and where the standards process has integrated this user need? Has this been studied and discarded? Is this under the radar screen since it is inherently not a *service* someone can provide (i.e. once it is shared it simply becomes metadata like any other)? I see this as a fundamental need for any data user and, indeed, figures in Jody's comments about the history of the various 'catalogs' batting around the geotools world but don't see it addressed so far in any spec. thanks for your thoughts and comments, --adrian ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
