RE: Fwd: Re: [Big-devel] big bad mother schema (was RE: RE: appinfo stuff)

[Ben R. <be...@ca...>]

> -----Original Message-----
> From: big...@li...
> [mailto:big...@li...]On Behalf Of Jim Croft

> >In order to enable our namespace properly, we really need a permanent
> >URL on the chah.gov.au web site to use for HISPID schemas along the
> >lines of the W3C for its schemas.
>
> I had not thought about this...  yes we need a stable place for the
> namespace...
> I guess CHAH is the most appropriate place for this
> activity...  I do not
> think DIGIR and ABCD have thought this far ahead...
>
> >Is there an area on chah.gov.au that we could set aside for
> publishing
> >our official schemas?  How about this for HISPID5:
> >http://www.chah.gov.au/2002/hispid5
> >we could then use other similar URLs for newer releases:
> >http://www.chah.gov.au/2004/hispid6
>
> this would work... do we need the year?

Probably not (it doesn't really matter, I'm just trying to think ahead),
so long as we continue the broad version numbering.  Otherwise we could
use:

a) http://www.chah.gov.au/2002/hispid

b) http://www.chah.gov.au/2004/hispid

The point being that each of these would ALWAYS point to the expected
version, and implicit in this is that forever afterwards, this URL would
provide an answer.

I guess my initial examples will be easiest to implement given the
current file name, "hispid5.xsd".

Also, on that web site, you might need to separate the schema documents
a bit more from other stuff hosted there:

a2) http://www.chah.gov.au/HISPID/hispid5

or whatever..

future versions could then be

b2) http://www.chah.gov.au/HISPID/hispid51

etc.

Given all the possible needs of the staff on the chah.gov.au web site, I
favour example a2, above.

Cheers,
Ben