OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

egov-services message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: FW: Svar: [egov-services] eGov Service Subcommittee charter brainstorm1/31/02




-----Original Message-----
From: Lewis, Diane 
Sent: Monday, February 03, 2003 7:55 AM
To: 'Todd Harbour'; 'egov-services(a)lists.oasis-open.org'
Subject: RE: Svar: [egov-services] eGov Service Subcommittee charter
brainstorm 1/31/02


thanks Todd for your input.. i will re-read it along with all the other messages from Friday's dialogue and post a synopsis and draft charter for further review and comment by all members... 

i am hoping to arrange a teleconference as follow-up... in the coming days.. stay tuned diane

-----Original Message-----
From: Todd Harbour [mailto:toddh@fgm.com]
Sent: Sunday, February 02, 2003 7:02 PM
To: Lewis, Diane; 'egov-services(a)lists.oasis-open.org'
Subject: Re: Svar: [egov-services] eGov Service Subcommittee charter
brainstorm 1/31/02


Sorry I am late to this thread, but I only got back from Europe late last
night. While I think that the charter has a good start, I think that it is
important to separate a few concepts. Let me try and explain some of my
thinking with everyone.

First, I think that we need to "step up" a level of abstraction in our
definition. If we define things according to organizations, integrated
delivery, and services, we are likely going to run into numerous problems.
For example, what is the service that provides "health care" in any given
country? I think the answer is "it depends." If we are talking about
procurement of medicines, we may have one type of organization. However, if
we are talking about delivering other forms of health care, we may end up
with another.

Second, there seemed to be a hint of implementation in this thread. In
particular, I was noticing references to "fields" and "object." I think that
we need to steer clear of any kind of implementation in this specification.

Third, I think that the goals identified are a good start as well, though, I
have to confess that I do not think that I understand them entirely. There
may be others out there that feel as I do, so I suspect that they need to
have some additional work done to them.

Last, in an attempt to offer alternatives (not just problems :-), I have
tried rewriting some of the language below. Hopefully, this will get others
thinking and offering some other ideas for our mission statement.

Hope this helps.

*****

Purpose:

The purpose of the eGov Services subcommittee is to identify domains of
governmental activity and their associated vocabulary and transform that
vocabulary into a data specification that will allow governmental
organizations to share information within a single, national, jurisdiction
and where the political will exists, allow national authorities to share
that same information among nations and states.

Goals:

- Identify common needs regarding standardisation of information
objects and data element.

- Formulate a common methodology regarding analysis of form, documents
and processes (data needs)

- 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 (data definitions)>


=========================================
Todd Harbour                            571-276-2196 (Cell)
45245 Business Court              703-478-9881 (Talk)
Dulles, Virginia 20166              703-478-9883 (Fax)





On 1/31/03 2:32 PM, "Lewis, Diane" <Diane.Lewis@usdoj.gov> wrote:

> 
> 
> -----Original Message-----
> From: Lewis, Diane
> Sent: Friday, January 31, 2003 2:27 PM
> To: 'Michael Bang Kjeldgaard'; 'egov-services@lists.oasis-open.org'
> Subject: RE: Svar: [egov-services] eGov Service Subcommittee charter
> brainstorm 1/31/02
> 
> 
> OK..Michael
> 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)
> 


=========================================
Todd Harbour                            571-276-2196 (Cell)
45245 Business Court              703-478-9881 (Talk)
Dulles, Virginia 20166              703-478-9883 (Fax)




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC