[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Svar: [egov-services] eGov Service Subcommittee charter brainstorm1/31/02
-----Original Message----- From: Lewis, Diane Sent: Friday, January 31, 2003 3:24 PM To: 'Michael Bang Kjeldgaard'; ''egov-services@usdoj.gov' Cc: 'SimonScott.Ashley@hq.navy.mil' Subject: RE: Svar: [egov-services] eGov Service Subcommittee charter brainstorm 1/31/02 Michael, i understand your point... .. each government entity federal, state, local will continously legislate rules, laws and procedures in a number of "service" areas.... this in turn will "create" data to be collected, viewed, processed according to laws, rules and procedures. if we first identify the common services, then the common data elements and then map them to existing international or national standards or standards underdevelopment... we have provided knowledge and links that all governmental bodies can use?? dl i also note for others Tom's note below as a reference. TT>These are at the process and procedure level once we have identified the white page of services. We must identify the identities before we can form relationships, and best practices. </TT> -----Original Message----- From: Michael Bang Kjeldgaard [mailto:mbk@itst.dk] Sent: Friday, January 31, 2003 3:18 PM To: Lewis, Diane; 'egov-services@usdoj.gov Cc: SimonScott.Ashley@hq.navy.mil Subject: RE: Svar: [egov-services] eGov Service Subcommittee charter brainstorm 1/31/02 Would this be an example that clarifies: Say we have en form regarding application of provision of some aid for a disabled person, eg. a wheel chair or something. What would you call the datafield whre you enter the type of aid wished for in the schema? "Aid", "product", "type" or whatever. This my be a local issue when developing af schema for such a form, which today in the paperworld may exist in a local environment (with no mandatory and common language). The question would be to calify: - is this need for at datadefinition covered by ebXML (or other) in part or in full - if not: is there a potential for new internartional work regarding this type of data? And who should lead this work? Is it of high or low priority? Michael >>> "Lewis, Diane" <Diane.Lewis@usdoj.gov> 31-01-2003 21:00:12 >>> your perspective Michael is from a conceptual view... can you give me an example mapping from the Danish Government point of view... where a government service and the resulting data would be "registered" in a "global" repository .. so if the US and Danish Government exchange information on lets say health care we share a common standard of data exchange... ? dl -----Original Message----- From: Michael Bang Kjeldgaard [mailto:mbk@itst.dk] Sent: Friday, January 31, 2003 2:56 PM To: Lewis, Diane; 'egov-services Subject: RE: Svar: [egov-services] eGov Service Subcommittee charter brainstorm 1/31/02 I have not expected us to actually provide a real yellow pages deliveable in the SC (that could be a rather costly project and would certainly demand a lot of work), but the TC could form another SC - or we could take it up later. But for the first phase I think our main objective must be the develop a sound base for "a new age" of standardisation in the public sector domain. As we all know ebXML is an important base for the private sector and to a certain extent for the public sector (at the moment we are workning very har in Denmark to adopt ebXML to Danish Goverment needs regaring both key-data in public registires and e-trade. But ebXML does not cover all the ground. It is a plan for covering more (or all) the ground not covered by ebXML we need to define and analyse. Michael >>> "Lewis, Diane" <Diane.Lewis@usdoj.gov> 31-01-2003 20:43:29 >>> would a white/yellow pages deliverable be a product of our goals.... ?? dl -----Original Message----- From: Michael Bang Kjeldgaard [mailto:mbk@itst.dk] Sent: Friday, January 31, 2003 2:43 PM To: Lewis, Diane; 'egov-services@lists.oasis-open.org' Subject: RE: Svar: [egov-services] eGov Service Subcommittee charter brainstorm 1/31/02 Well to me "Best practise" regards "recommandations" og "good stories" regarding how to make eGovernmetn, how to develop datamodels for interoperability purposes, how to make XML schema and how to develop webservices. Concerning the services group it seems to me, that some of the most important questions are: - how do we go about standardising across government agencies, across tiers of governemt and across nations? - how do we go about making "eGovernemt" standards in a way that not only coordinates with the needs of the private sector, but also improves both public and private administrative efficiency - which areas of administration/service should we give high priority - how can we define a common methodoly that allows a optimal and realitic level of coordination in order to avoid redundant data definitions - at what level can we agree on common standards (syntax or semantic - the latter being much more difficult) Michael >>> "Lewis, Diane" <Diane.Lewis@usdoj.gov> 31-01-2003 20:26:53 >>> OK.. how do your objectives for our committee differ from best practices??? dl -----Original Message----- From: Michael Bang Kjeldgaard [mailto:mbk@itst.dk] Sent: Friday, January 31, 2003 2:20 PM To: Lewis, Diane; 'egov-services@lists.oasis-open.org' Subject: Svar: [egov-services] eGov Service Subcommittee charter brainstorm 1/31/02 >>> "Lewis, Diane" <Diane.Lewis@usdoj.gov> 31-01-2003 20:09:32 >>> Statement of Purpose (review eGov TC charter) OASIS text: A forum for Governments internationally to voice their needs and requirements with respect to XML-based standards. where does our subcommittee work tie into the eGov TC charter.. <DL: work with other OASIS channels and other international standards bodies' channels (e.g. XML.org for schema registry and/or information portal), to act as a clearinghouse of information related to applicable specifications/standards as well as activities and projects being conducted by Governments in the adoption of XML-based systems and standards. > Goals of the Sub-TC (what do we want to accomplish?) <MBK: - Identify common needs regarding standardisation of informations objects and dataelement. - Formulate a common methodology regarding analysys of form, documents and processes (dataneeds) - Formulate a common methodology for defining priorities - Achieve a minimum level of consensus on priorities in order to coordinate work done in many different organisations in order to share knowledge as well as achievements (datadefinitions)> List of deliverables (purpose/content of each identified deliverable)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC