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

[Jim C. <jr...@an...>]

> > basically everything that does not fit in the main part of the
> > element itself...
>
>Sorry, but I don't follow your meaning...

neither do I most of the time...

What I was driving at is that there are a number of things in our esisting 
descriptions of  a HISPID element  that are already handled by the schema 
as attributes outside of the annotation/documentation/appinfo 
construct.  Such things as the name of the element, a short tag, a bried 
description, acceptable ranges, values, obligation, optionality, 
repeatability, etc.

These are the things I am suggesting that we may not need to repeat in the 
appinfo structured explanatory material.  We could, but it would be 
redundant and maybe get out of sync and lead to confusion.  The appinfo 
should be used to hold constraints, dependencies and explanation that we 
can not express in the working part foteh schema.  As we move into this new 
way of expressing HISPID, I think we need to shed the traditional HISPID as 
a book paradigm that we have grown used to...

Once we get this first pass finished and validated I would strongly 
recommend that we create an official repository as an on-line  database 
that allows shared access and on-line editing...

jim


~ Jim Croft ~ jr...@an... ~ 02-62465500 ~ www.anbg.gov.au/jrc/ ~