Designing the FEA DRM for Information Sharing October
Designing the FEA DRM for Information Sharing October 9, 2004 Michael C. Daconta Metadata Program Manager
Agenda § Problem § Design Goals § Completeness § Consistency § Cohesiveness § Revised DRM Structure § Conclusion Michael C. Daconta October 9, 2004 2
Problem § Draft DRM structure will not achieve the goals of information sharing. § It does not follow modern principles of knowledge representation § Lacks necessary features § Will cause mass implementation confusion in its current form. Michael C. Daconta October 9, 2004 3
Design goals for DRM Revision § Completeness § The DRM must contain all the necessary features to cover 80% of federal data (80/20 rule). § Cannot exclude Unstructured resources, Security Context or Information Access (vice Exchange). § Consistency § Each axis of the DRM must be consistent with the others in its use of modeling constructs and metaphors. § Cohesiveness § The DRM whole must be greater than the sum of its parts. § Must satisfy “connecting the dots”. Michael C. Daconta October 9, 2004 4
Completeness § DRM uses a 3 -axes approach. § The approach is fine but the axes are inconsistent and underspecified. Information Context Subject Service Security Sharing Exchange Access Description Data Element Michael C. Daconta Resource October 9, 2004 5
Consistency § The modeling constructs in use must be consistent across all axes of the structure. § Example: Super-Type vice Data Object. § A more consistent strategy is an intuitive set of refinements to classic Entity-Relationship Modeling. Entity Relationship Topic (heterogeneous) Class (homogeneous) Property (intrinsic) Domain Association (extrinsic) Range Michael C. Daconta Instance (Object) October 9, 2004 6
Cohesiveness § Explicit Associations across and within levels § Standard Associations § i. e. Subclass-Of, Part-Of, Instance-Of Michael C. Daconta October 9, 2004 7
Revised DRM Structure Context Subject Context Service Context Subject Area Subject Class Association Who What When Service Class Input/Output Association Security Context Security Class Association Where Why Sharing Information Exchange Class Exchange Payload Association Description Structured Semi-Structured Unstructured Data Element Description Data Class Data Property Association Information Access Unique Identifiers Query Class Association Resource Description Resource Class Association Michael C. Daconta October 9, 2004 8
Conclusion § These modifications will achieve the goals of Information Sharing across the federal government. § These modifications achieve: § Completeness § Consistency § Cohesiveness § Questions? Michael C. Daconta October 9, 2004 9
- Slides: 10