Re: [regrep] UK Government Registry Requirements

[Duane Nickull <dnickull@adobe.com>]

Peter:

I do not think it is that big of a problem.  I am familiar with their 
requirements and UDDI will not meet UK requirements so they cannot use 
it.  This especially relates to lifecycle management of user submitted 
artifacts to the registry.  You cannot put a data dictionary in a UDDI 
registry.

Duane

Peter Kacandes wrote:

> Hi All,
>
> I've just been reading a most disturing section of a draft document 
> called the UK e-GIF (e Government Interoperability Framework):
>
> "2.5    Departments which are connected to the GSI are to use the GSI 
> Notice 1/2003 Information GSI Directory Schema, except for WEB based 
> transactions over SOAP when UDDI is to be used
>
> 2.6     When Web services are used they shall to be based on SOAP, 
> UDDI and WSDL specifications."
>
> I think we as a TC need to make sure that ebXML Registry gets equal 
> billing with UDDI for these purposes.
>
> Paul, is there anyway you can put us in touch with appropriate 
> contacts to make sure that this gets modified in the next draft of 
> this document?
>
> Especially given that other parts of the document talk about the 
> importance of meta-data content management:
> "Content management metadata
> 2.19    The technical policies for content management metadata cover:
>
> The adoption and development of the e-GMS, based on the International 
> Dublin Core model, to meet government's information management and 
> retrieval needs
>
> The e-GMS is a 'superset' of metadata elements and refinements, and it 
> is unlikely that any single system will require all of them. 
> Organisations are therefore encouraged to develop sector and 
> system-specific standards, removing elements that are not required, 
> and adding local constraints
>
> 2.20    The development and maintenance of the GCL (Government 
> Category List)."
>
> Also in section 2.39 it says:
> "For example, ebXML uses the international address standard whereas 
> the UK has its own address standard."
> I'd like to understand what they mean by that.
>
> The full document can be found at:
> http://www.govtalk.gov.uk/schemasstandards/egif_document.asp?docnum=731
>
> regards
>
> pk
>
>
>
>
> -----Original Message-----
> From: Paul Spencer [mailto:paul.spencer@boynings.co.uk]
> Sent: Friday, January 09, 2004 10:29 AM
> To: regrep
> Subject: [regrep] UK Government Registry Requirements
>
>
> I hope people remember the discussions we had last year about this. We got
> as far as agreeing to put together a document based on the requirements of
> the UK MOD and wider requirements that others could contribute.
>
> Sorry about the delay (I have been tied up with the Election Markup
> Language), but I have now done a first draft of those parts of the 
> document
> that I said that I would do. It is at
> http://boynings.co.uk/mod/regrep-v0-2.pdf.
>
> The next stage is to add wider requirements and come up with a
> standards-based architecture to achieve these requirements. My goal is to
> create an architecture using OASIS standards that can be used to allow 
> these
> registries to interact, not only within government, but also, for example,
> with a UBL repository. Although I am talking about the registry (which 
> will
> obviously use ebXML standards since we are discussing it here) I believe
> there is a lot we need to decide in terms of how the registry is used and
> the client applications required. However, it is essential within 
> Government
> not to specify specific applications to be used.
>
> My hope is that people will read this document (it is a PDF, but I am 
> happy
> to do other formats on request) and we can discuss it at the telecon on
> Thursday.
>
> Regards
>
> Paul Spencer
> Director
> Boynings Consulting Ltd
> http://www.boynings.co.uk
>
>
> 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/regrep/members/leave_workgroup.php.
>

-- 
Senior Standards Strategist
Adobe Systems, Inc.
http://www.adobe.com