Recommendation Notes from Workshop

DIF -Workshop greate feedback for the new AD-I DIF:
DIF- good tool to discovery data
DIF AD - not to be used for single instances
DIF -AD - start with a conceptual model then develop the keywords
SensorML - use it to populate the ISO 19115 Marine Community Profile mandatory and core metadata (see Resulting Specification)
TML - Needs smooth handoff to sensorML
TML/SML - harmonize SensorML and TransducerML, document complementary usage and see if they can be a part of a single standard (see Question below)
MMI - should create a feature matrix standards
MMI - create a hosted/moderated registry
GENERAL - Need standard controlled vocabularies for Instrument and Sensor Types and variables (phenomenon dictionary), processes, units, values identifier types, role, interface
GENERAL - Transducer registry
GENERAL - Extensible descriptions for instrument policy
GENERAL - define requirements for global repository of instrument metadata (could drive implementation of TML/SML)
GENERAL - put static and dynamic metadata on internet in a place you can get to it
FGDC - need further cosnstraints (elements to support instruments descriptions) -e.g. location of in situ sensors
GENERAL - tracking provenance is a useful thing (must occur? must define what's mandatory and what is optional)
GENERAL - minimum fields for each standard must be documented (enforced or convention = Best Practices) -- note that minimal fields creates minimal interoperability and automatability, even if it does increase acceptance (how to find the sweet spot)
GENERAL - is there a provenance tracking issue with metadata? must have versioning and/or unique identifier to handle when metadata records change -- UUID or other unique identifier on metadata record (who provides that? at what point in the process? system receiving first record creation)
GENERAL - need mechanism to relate sensor descriptions to data generated from that sensor
GENERAL - define levels of interoperability to characterize what metadata is needed (note Sensor Workshop) -- possibly make this part of an instance so you know how to use it; level of interoperability could also be represented by a 'certification' from an organization
GENERAL - Adopt standards widely use elsewhere
GENERAL - Hybrid approach may work better than a single standard
GENERAL - ability to cross-reference metadata in other content standards from the one you have (e.g., from within ISO, FGDC, or DIF, refer to a content standard or component of same written in SensorML or TransducerML; can also go the other way); would need to decide whether this is a 'generic' (blob) link or 'understood' link); consider security issues and issues associated with the link going away

GENERAL - retarding the proliferation of standards
GENERAL - interoperability between computational models and realtime.
GENERAL - DIF, ISO and FGDC are more content descriptive - while SensorML and TML is more processable
GENERAL - Provide clear definitions of document model schema’s fields
GENERAL - Have manufacturers enter immutable metadata
GENERAL - Provide guidance on best standard for me: Feature matrix, standard selection matrix, wikipedia entry, pointers to additional documentation
GENERAL - Provide more documentation on standards: Dummy’s guide to…, Conceptual documents like UML views of schema, white papers, tutorials, examples of descriptions in specific domains (oceanography, ...), example use cases and application scenarios, User's experiences with the standards (e.g., comment boxes/bulletin boards (need promotion), FAQs)
GENERAL - collect existing reference information and make sure it's available
GENERAL - Constrain vocabularies in user community
GENERAL - Profiling to constrain content in schemas
GENERAL - Collaborative efforts to contribute information
GENERAL - Creation of moderators or authorities for vocabularies
GENERAL - GUI needs to be developed to make life easier
GENERAL - Voluntary help desk
MMI - Expert contact for different standards and their own help information
GENERAL - funding is a nice idea
GENERAL - Establish repository for instrument ML instances (ACT?)
GENERAL - Acknowledge that additional info will be added along the way (above problems/solutions apply)
GENERAL - Note metadata will be stored internally (puck), externally stored on the web, accompanying the instrument (physical media)

QUESTION: Does harmonization matter (e.g., between SensorML and TransducerML)?