Re: [egov] Tactics on data alignment / standardization

[Thomas Lee <ytlee@cecid.hku.hk>]

Dear John, David, and Diane,

Thank you very much. I have forwarded your messages to the government 
team we are working with. We have found the suggestions very useful. 
Please help send us more information in this area from time to time.

Regards,

Thomas

Diane.Lewis@usdoj.gov wrote:

>Thanks for sharing this wonderful set of resources... 
>
>Context is what we are working on in the e-gov services subcommittee
>
>Citizen to government "services" performed, requested, required..
>the mandate of electronic government to provide information, perform activities based on statutes, laws, administer programs to accomplish the federal legislature's objectives in allocating federal funding to a "program".
>
>in my current work activity i am "extending" the ebXML business context templates i found in a book to study a set of data elements associated with enforcement of a public law.  this exercise along with my off hours spent on e-gov services meditation using the "fedex approach" model i have outlines in e-gov Services SC communication give me a better understanding of the challenge ahead and mechanisms 'to divide and conquer' (to create meaningful work products).  
>
>the 3 ebXML provided "context" Templates used in my grassroot study are:
>
>Content Mapping
>
>XML element
>content description
>standard
>version
>element/component name
>mapping/transformation
>note
>
>Application Data Exchange Collaboration
>
>Service Identifier
>Application Identifier
>Partner Types
>Authorized Roles
>Legal Steps/requriements
>Electornic consequences
>Initial/terminal events
>scope
>boundary
>constraints
>
>Application Data Exchange Transaction
>
>Identifier (form, application)
>Schema Identifier
>Description
>Pattern
>Business activities/associated authorized roles
>Constraints
>Requesting Partner Type
>Requesting Activity Role
>Requesting Activity Document
>Responding Partner Type
>Responding Activity Role
>Responding Activity Document
>
>cheers diane
>
>
>
>-----Original Message-----
>From: Gnosis_@compuserve.com [mailto:Gnosis_@compuserve.com]
>Sent: Friday, August 22, 2003 11:29 AM
>To: john.borras@e-envoy.gsi.gov.uk
>Cc: ytlee@cecid.hku.hk; egov@lists.oasis-open.org
>Subject: Re: [egov] Tactics on data alignment / standardization
>Importance: Low
>
>
>John,
>
>This whole problem space is one that the OASIS CAM templates
>are well equipped to help solve.
>
>Some quick bullet points on what is needed to bear down on the
>problem:
>
>1) means to tie local usage to general vocabulary
>2) means to drive adoption of common vocabulary and semantics
>3) means to automatically map across formats
>4) means to support local extensions to use and semantics
>5) but most important - means to capture and enable context driven
>     use of data elements.
>
>IMHO - understanding context is the next frontier here - for building
>agile information systems across the enterprise.
>
>For more on the work on business context - see the BCM PPT at
>
> http://dfas.info
>
>BCM / then Choice Pt presentation
>
>Hopefully this will save some of the "grind" here.
>
>Enjoy, DW.
>==========================================================
>Message text written by INTERNET:john.borras@e-envoy.gsi.gov.uk
>  
>
>>We have sent many hours in committee meetings debating the data elements 
>>    
>>
>and agreeing final standards.  These committees include representatives of 
>all government agencies and our process allows for escalation to senior 
>management of any unresolvable issues.  Clearly in this work there have to 
>be compromises and  for many agencies it can mean significant changes have 
>to be made, but the implementation of those changes has to be managed in a 
>pragmatic way. 
>
>Our initial focus has been on the common data elements that most agencies 
>use, eg names, addresses, dates, reference numbers etc.  It is essential 
>to get these agreed early on although they are probably some of the 
>hardest to deal with.
>
>So based on our experience I can say the task is not easy, there is no 
>quick solution, it is essential to involve all stakeholders, get their 
>early agreement on the strategic use of common data elements, then grind 
>your way through the individual elements trying to reach agreement.
>
><
>
>
>You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/egov/members/leave_workgroup.php
>
>  
>