RE: [egov-registry] Registering schema components

["Paul Spencer" <paul.spencer@boynings.co.uk>]

Carl,

This was not quite the way I was thinking. My thoughts were (as options
rather than a sequence):

1. Full XML Schema document is registered as a 'Schema document' object and
stored in repository whole (as a blob). I had not thought of storing a URL,
but this seems a useful option. I think we should add it. I would then think
that the schema document object in the repository *or* the one referenced by
the URL in the repository is the master copy of that object.

2. Schema component is stored in the repository, with metadata in the
registry.

3. Schema component metadata is stored in the registry with nothing in the
repository. Component can be serialized as XSD Schema (or later as DTD,
RelaxNG, Schematron etc).

4. Schema components in the regrep can be referenced in other schema
components or in schema documents.

A sequence might then be (assuming there is no complete schema to match a
need):

1. Search registry for existing schema components that match parts of the
need.

2. Develop other schema components as required.

3. Submit the new components.

4. Use the regrep assembly function to build the required schema document(s)
from registered components.

5. Test this.

6. Submit the complete schema document(s) to the regrep.

Regards

Paul


> -----Original Message-----
> From: Carl Mattocks [mailto:carlmattocks@checkmi.com]
> Sent: 20 July 2004 15:47
> To: Egov-Registry
> Subject: RE: [egov-registry] Registering schema components
>
>
> Paul et al :
>
> Please consider if the following simplistic sequence for storing XML
> Schema  is aligned with your quest -
>
> (1) Full XML Schema is registered as a ' Schema' object and optionally
> (i)stored in repository whole (as a blob ).
> (ii) location of Schema is stored in repository as an URL
> (2) A schema component is registered as a ' Schema Component' object,
> associated with 'Full XML Schema' and stored in repository  .
>
> carl
>
>
> <quote who="Paul Spencer">
> > RE: [egov-registry] Registering schema componentsI had sort of
> taken this
> > as
> > a given. My only question is what about entering only metadata? If the
> > component is not serialized as XML Schema (or whatever) until *output*
> > from
> > the regrep, what goes into the repository? Anything? My understanding is
> > that something has to go there.
> >
> > Regards
> >
> > Paul
> >   -----Original Message-----
> >   From: Nikola Stojanovic [mailto:Nikola.Stojanovic@RosettaNet.org]
> >   Sent: 16 July 2004 22:29
> >   To: Egov-Registry
> >   Subject: RE: [egov-registry] Registering schema components
> >
> >
> >   <Carl>
> >   IMHO the RegRep should allow 'the component to into the
> repository' and
> >   the registry should contain the derived metadata.
> >   Assuming that, the RegRep interface will allow the 'user' (human or
> > their
> >   agent) to exploit both the metadata (at all levels of granularity) and
> > the
> >   artifact (as-in its original form).
> >   </Carl>
> >
> >   +1
> >
> >   Regards,
> >   Nikola
> >
>
>
> --
> Carl Mattocks
>
> co-Chair OASIS (ISO/TS 15000) ebXMLRegistry Semantic Content SC
> co-Chair OASIS Business Centric Methodology TC
> CEO CHECKMi
> v/f (usa) 908 322 8715
> www.CHECKMi.com
> Semantically Smart Compendiums
> (AOL) IM CarlCHECKMi