Proposed update to OAL2.0

[Phyllis]

All,

We have neglected to update targetNamespace and xmlns:oal in each
piece of the schema to point to Groups URL (http://groups.google.com/
group/openastronomylog). I have changed my local copy and run it
through multiple validators with success.

An example comes from the first few lines of oal20.xsd:

<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema targetNamespace="http://groups.google.com/group/
openastronomylog" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:oal="http://groups.google.com/group/openastronomylog"
version="2.0">

Fortunately, this should break no one's code, but it makes validators
happy. Shall I check in a new zip file?

- Phyllis

[Tom]

Hi Phyllis,

Thanks for your suggestion. I accept it and don't think that it could
break existing code.

Meanwhile I have added hopefully clarifying commentson the fstOffset.
As you have already tested your version, would you please update the
oalBase.xsd for the observer's fstOffset:

<!-- New in V2.0: Personal offset to the "reference" correlation
between the sky quality -->
<!-- as it can be measured with an SQM and the estimated naked eye
limiting magnitude (fst) -->
<!-- The individual observer's offset depends mainly on the visual
acuity of the observer. -->
<!-- If the fstOffset is known, the sky quality may be derived from
faintestStar estimates -->
<!-- by this observer. -->
<!-- The "reference" correlation used to convert between sky
quality and fst was given by -->
<!-- Bradley Schaefer: fst = 5*(1.586-log(10^((21.568-BSB)/5)+1))
where BSB is the sky quality -->
<!-- (or background surface brightness) given in magnitudes per
square arcsecond -->
<xsd:element name="fstOffset" type="xsd:double" minOccurs="0"/>

I think we should then accept this version as the official OAL 2.0
release and discard all working drafts.

Best wishes,
Tom

[Dirk Lehmann]

Hi,

good suggestion, correcting the namespace.

I'll update the observation.sourceforge.net webpage in the next days,
so that only OM related stuff appears there and everything related to
COMAST or <OAL> will point to this
group.
My <OAL2.0> coding for OM 0.820 is done and I'll release a first beta
hopefuly this week.

So for me <OAL> 2.0 looks good and from my point of view we should
really consider calling it final.

Best regards

Dirk

[Phyllis]

All,

I uploaded a new zip file with the aforementioned URL changes and some
spelling corrections. It is OAL20_proposal_20090914.zip.

- Phyllis

[Dirk Lehmann]

Hi,

I'm fine with this proposal, too. I've added it to the first OM 0.820
release candidate.

I'm wondering how we organize the release process for OAL.
My proposal would be for releasing a new OAL version:
- All members who represent an application, compatible with OAL 2.0,
must sign off the new proposed version.
- All group members can optionally comment on the proposal.
- The proposed version gets released when all application
representatives agreed on it

My two cents

Regards

Dirk