RE: [egov] BCM and eprXML pilots

["Weiland, John R. NMIMC GS" <JRWeiland@US.MED.NAVY.MIL>]

Good Morning,

This seemed to be a recurring theme during our F2F last week.  I envisioned
a Registry/Repository a utility for programmer's use, not a broker for end
users.

r/ John Weiland

-----Original Message-----
From: Farrukh Najmi [mailto:Farrukh.Najmi@Sun.COM]
Sent: Monday, November 03, 2003 7:53 AM
To: Hans A. Aanesen
Cc: bcm@lists.oasis-open.org; egov@lists.oasis-open.org; Knut Lindelien
Subject: Re: [egov] BCM and eprXML pilots


Hans A. Aanesen wrote:

> Hi
>
>  
>
> Thank you for a very fruitful conference.(Specially our workshop) 
>
> It is obvious that eprXML will be a very nice "face" for BCM in 
> Governmental organized services in e-Gov SOA. Special interesting is 
> the broader audience in the e-Gov TC and that they need a more 
> governmental and not vendor controlled guidance.
>
>  
>
> One important topic here is the needed "single sign-on" PKI solutions 
> based on a national repository (UDDI?)
>
Why do you pre-suppose UDDI here Hans?

Were you aware that UDDI *DOES NOT* provide a repository at all?

I would think that ebXML Registry would be a much better fit for a 
standards-based national registry/repository. It *DOES* provide a 
feature rich repository.

I would be glad to explore this further with the team if needed. Thanks.

-- 
Farrukh


> built upon a _not vendor made_ specification of API Meta-models (Web 
> Services).It is crucial that it must be built upon Governmental terms 
> (as EPR).
>
> Such Meta models should be approved by Governments based 
> on recommended certificates from for instance OASIS e-Gov.
>
>   
>
> It would be nice if we could extend our eprXML pilots on a broader 
> international basis!
>
> We will also come back on sugestions on international pilots.
>
>  
>
> Best regards
>
> Hans A. Aanesen
>
> EPR-Forum Norway
>




To unsubscribe from this mailing list (and be removed from the roster of the
OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/egov/members/leave_workgroup.ph
p.