[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [egov] Tactics on data alignment / standardization
FYI to everyone - just sharing feedback here.
I think this looks useful in helping us define
our templates - and possible usage cases.
Once again - liaison with the eGov folks is
providing good feedback.
Thanks, DW.
-------------Forwarded Message-----------------
From: "Diane.Lewis@usdoj.gov", INTERNET:Diane.Lewis@usdoj.gov
To: "'john.borras@e-envoy.gsi.gov.uk'", INTERNET:john.borras@e-envoy.gsi.gov.uk
"'Gnosis_@compuserve.com'", Gnosis_
CC: "'egov@lists.oasis-open.org'", INTERNET:egov@lists.oasis-open.org
"'ytlee@cecid.hku.hk'", INTERNET:ytlee@cecid.hku.hk
Date: 8/22/2003 1:46 PM
RE: RE: [egov] Tactics on data alignment / standardization
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
----------------------- Internet Header --------------------------------
Sender: Diane.Lewis@usdoj.gov
Received: from wdcsun022.usdoj.gov (wdcsun3.usdoj.gov [149.101.1.103])
by siaag2ad.compuserve.com (8.12.9/8.12.7/SUN-2.7) with ESMTP id h7MH4Zpv015837
for <Gnosis_@compuserve.com>; Fri, 22 Aug 2003 13:04:35 -0400 (EDT)
Received: from wt2.usdoj.gov (localhost [127.0.0.1]) by
wdcsun022.usdoj.gov (Netscape Messaging Server 4.15) with ESMTP
id HK163I02.QTS; Fri, 22 Aug 2003 13:04:30 -0400
Received: (from x400@localhost)
by wt2.usdoj.gov (8.9.3 (PHNE_24419+JAGae58098)/8.9.3) id NAA03687;
Fri, 22 Aug 2003 13:04:29 -0400 (EDT)
Date: Fri, 22 Aug 2003 13:04:29 -0400 (EDT)
Autoforwarded: FALSE
Importance: Normal
Precedence: first-class
Received: by /C=US/A=_/P=USDOJ-JCON/ via NFT with NetJunction (6.0.2-p1); Fri, 22 Aug 2003 13:03:04 -0400
Received: by USDOJ; Fri, 22 Aug 2003 13:03:03 -0400
From: "Diane.Lewis@usdoj.gov" <Diane.Lewis@usdoj.gov>
Subject: RE: [egov] Tactics on data alignment / standardization
To: "'Gnosis_@compuserve.com'" <Gnosis_@compuserve.com>,
"'john.borras@e-envoy.gsi.gov.uk'" <john.borras@e-envoy.gsi.gov.uk>
Cc: "'ytlee@cecid.hku.hk'" <ytlee@cecid.hku.hk>,
"'egov@lists.oasis-open.org'" <egov@lists.oasis-open.org>
Message-Id: <"USAEOUSAML01-030822170134Z-35692*/PRMD=USDOJ/ADMD= /C=US/"@MHS>
Priority: Normal
X-Priority: 3 (Normal)
X-NJ-P1MID: [/P=USDOJ/A=_/C=US/;USAEOUSAML01-030822170134Z-35692]
X-MS-TNEF-Correlator: <"USAEOUSAML01-030822170134Z-35692*/PRMD=USDOJ/ADMD= /C=US/"@MHS>
Alternate-Recipient: Allowed
Disclose-Recipients: Prohibited
X400-Content-Return: Allowed
X-Implicit-Conv-Prohibited: FALSE
X-Mailer: NetJunction (NetJunction 6.0.2-p1)/MIME
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]