[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Maturing Businesses and Web Standards

• To: "Bullard, Claude L \(Len\)" <len.bullard@i...>, "Rex Brooks" <rexb@s...>
• Subject: RE: Maturing Businesses and Web Standards
• From: "Chiusano Joseph" <chiusano_joseph@b...>
• Date: Wed, 24 Aug 2005 13:02:42 -0400
• Cc: "XML Developers List" <xml-dev@l...>
• Thread-index: AcWovU2Wl9nX3me+Sga/DlSr1wFzHgAD2emg
• Thread-topic: Maturing Businesses and Web Standards

> -----Original Message-----
> From: Bullard, Claude L (Len) [mailto:len.bullard@i...] 
> Sent: Wednesday, August 24, 2005 11:05 AM
> To: Chiusano Joseph; Rex Brooks
> Cc: XML Developers List
> Subject: RE:  Maturing Businesses and Web Standards
> 
> "The developers envision that the FEA DRM will be used in 
> conjunction with the Global Justice XML Data Model and the 
> National Information Exchange Model. One of the NIEM Program 
> Goals is to leverage shared technology through implementation 
> of the FEA Data Reference Model (DRM)."
> 
> http://xml.coverpages.org/ni2005-06-20-a.html
> 
> How would this work in practice?  

I'm not the official authority on this topic (that would be Mike
Daconta), but I will take a confident and informed shot at it anyway as
Mike likes me to do (you've already stated much of this in your response
below): 

Vocabularies/models such as GJXDM and the NIEM (which are merging to
become NIEM 1.0, as you know) can be associated with all 3 of the FEA
DRM's primary standardization areas:

- Data Description: Each element/attribute/data type could be mapped to
entity/attribute-based representations, such as logical data models;

- Data Exchange: These vocabularies define on-the-wire messages, and can
therefore be mapped to Exchange Packages;

- Data Context: The entities that comprise the Exchange Packages can be
categorized according to taxonomies, which may be FEA reference models,
or other taxonomies that are agency-specific, community of interest
(COI)-specific, or cross-COI.

These associations can aid in multiple areas, the most pertinent one
here being harmonization (mapping 2 or more vocabularies with each other
through the common reference model). That is one of the multiple values
of the DRM.

Joe

Joseph Chiusano
Booz Allen Hamilton
O: 703-902-6923
C: 202-251-0731
Visit us online@ http://www.boozallen.comFrom 

> From the bottom, GJXML is a 
> rather large and somewhat obtuse description of data being 
> exchanged by justice agencies.  The description of the data 
> collected might be different, but GJXML is suitable as the 
> basis for exchange on the wire.  As I understand NIEMs, the 
> actual contract deliverable is an Information Exchange 
> Package (IEP) and this is what the service actually serves 
> up.  The products of the public safety vendor for say a 
> records management system are to work with the customer 
> agency to define, declare and serve the IEPs as derived from 
> GJXML plus any local entities/fields/reports as may be needed.
> 
> Where does the FEA DRM fit into that process?  What 
> deliverables are created by applying it?
> 
> The world is festering with meta-specs.  These become cost items. 
> FEA DRM can be a cost-saver or a cost-maker.   Unless we understand 
> this going in and work smartly, costs rise.  That is 
> doubtless, not the intent.
> 
> len
> 

• Prev by Date: Re: Names As Types
• Next by Date: RE: Names As Types
• Previous by thread: RE: Maturing Businesses and Web Standards
• Next by thread: : Create XML Data using PL/SQL
• Index(es):
  • Date
  • Thread