<br>I am putting together some Use Cases to describe the needs the community has of a metadata management tool, specifically the ability to "compose" metadata artefacts like ANZLIC data set descriptions, data product specifications (cf ISO 19131 and the EU INSPIRE methdology, and service profiles) from more reusable lower level artefacts, like reusable data access agreements, data quality statements, data access service descriptions.<br>
<br>We will be publishing a sample based on some real-world deployed data access services (time series water resources observations) at the end of the month.<br><br>In general, we should avoid making premature architectural decisions with some real world data access services as test cases, otherwise we risk building a tool to solve the wrong problem. We desperately need some "framework data set" examples, as well as "myBusinessData" examples for how a framework data set can be used to underpin a business application and its derived data sets.<br>
<br><br>Rob Atkinson<br>(wearing a SISS project hat)<br><br><div class="gmail_quote">On Mon, Jun 2, 2008 at 11:49 AM, <<a href="mailto:Bruce.Bannerman@dpi.vic.gov.au">Bruce.Bannerman@dpi.vic.gov.au</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><font face="sans-serif" size="2">IMO:</font>
<br>
<br>
<br><font face="sans-serif" size="2">I'd like to wrap this thread up soon
and put together a summary of the discussion into a proposal for a way
forward for GeoNetwork ANZLIC Profile.</font>
<br>
<br>
<br><font face="sans-serif" size="2">I'd like to start work on this summary
next week, starting 10th June.</font>
<br>
<br>
<br><font face="sans-serif" size="2">Where should this proposal go, once
it has been subject to our peer review?</font>
<br>
<br>
<br><font face="sans-serif" size="2">I suspect that it may be appropriate
to go to the ANZLIC Council for approval, however this needs debate.</font>
<br>
<br>
<br>
<br><font face="sans-serif" size="2">I have been contacted by several people
off line and understand that they have not been in a position to respond
due to work commitments. </font>
<br>
<br><font face="sans-serif" size="2">We have one more week for comments,
please take the time to do so if you are able.</font>
<br>
<br><font face="sans-serif" size="2">I'd like to read more from the ANZLIC
community. </font>
<br>
<br><font face="sans-serif" size="2">I also know that Ben and Jeroen would
like to add additional thoughts.</font>
<br>
<br><font face="sans-serif" size="2">Simon, I'd also appreciate reading your
additional thoughts on what would work.</font>
<br>
<br>
<br>
<br>
<br>
<br><font face="sans-serif" size="2">Bruce Bannerman<br>
</font>
<br>
<br><font face="sans-serif" size="2">__________________</font>
<br>
<br>
<br><font size="2"><tt>Finding an Open Source process that will work for
GeoNetwork - ANZLIC Profile will<br>
take a bit of trial and error to get right.<br>
</tt></font>
<br><font size="2"><tt>We may not be able to treat it as a traditional Open
Source Project as there is a<br>
need to support ANZLIC involvement in the process.<br>
</tt></font>
<br>
<br>
<br><font size="2"><tt>Many of the ideas here have come from Karl Fogel's
book "Producing Open Source Software,<br>
How to Run a Successful Free Software Project" ( <a href="http://producingoss.com/" target="_blank">http://producingoss.com/</a>
). This is an<br>
enlightening read if you have the time.<br>
</tt></font>
<br>
<br>
<br><font size="2"><tt>Below is a random collection of thoughts that needs
further work. <br>
We need your input and experience to flesh out these ideas.<br>
</tt></font>
<br>
<br>
<br><font size="2"><tt>_Working with the GeoNetwork Community_<br>
</tt></font>
<br><font size="2"><tt>We are not developing a project from scratch.<br>
</tt></font>
<br><font size="2"><tt>We are contributing to and customising an existing
OS Project, GeoNetwork.<br>
</tt></font>
<br><font size="2"><tt>Therefore, whatever we want to get into GeoNetwork
will have to be worked through<br>
the GeoNetwork community and GeoNetwork Project Steering Committee.<br>
</tt></font>
<br><font size="2"><tt>The GeoNetwork Community are not going to want to
include all of our changes at face value.<br>
To get them included will require a number of our developers to work *within*
the community,<br>
contribute to the project and over time *earn* credibility that they know
what they are<br>
talking about.<br>
</tt></font>
<br><font size="2"><tt>Simon and Byron have obviously been very successful
at doing this and we could learn from<br>
their examples.<br>
</tt></font>
<br><font size="2"><tt>We will also need to be sensitive to the GeoNetwork
community and by our actions make it<br>
clear to them that we are not trying to hijack their project, but act as
good community<br>
members.<br>
</tt></font>
<br>
<br><font size="2"><tt></tt></font>
<br>
<br><font size="2"><tt>_How can we get the work done?_<br>
</tt></font>
<br><font size="2"><tt>This will provide some challenges for government organisations,
where development work is<br>
typically project based with defined deliverables. Some initial ideas on
how we can engage<br>
with the community and get work done:<br>
</tt></font>
<br><font size="2"><tt>- Architects and Senior developers could start subscribing
to the GeoNetwork mailing lists<br>
( <a href="http://geonetwork-opensource.org/" target="_blank">http://geonetwork-opensource.org/</a> ) to observe how the community operates.
When they<br>
feel comfortable with the process they could start contributing to discussions.</tt></font>
<br>
<br><font size="2"><tt>- For some of our permanent developers, we could
start setting performance goals relating<br>
to GeoNetwork contributions and providing work time for this to occur.
These goals<br>
could possibly relate to a specific number of commits being accepted by
the community.<br>
The work may or may not be explicitly AP related.</tt></font>
<br>
<br><font size="2"><tt>- For those of us who do not have permanent developers,
we could explore Cameron's idea<br>
of engaging specialist consultancies to do some of this work for us. We
could treat<br>
this as *product support* with an appropriate annual fee. Over time these
consultancies<br>
would also need to build up the required rapport within the GeoNetwork
community and be<br>
available as a resource to use to get our future customisation done.</tt></font>
<br>
<br><font size="2"><tt>- I'm interested in other suggestions as well here.<br>
</tt></font>
<br>
<br>
<br><font size="2"><tt>_How do we prioritise AP work_<br>
</tt></font>
<br><font size="2"><tt>Ideally, we'd be able to come up with a list desired
improvements, assign a priority<br>
and work through them one by one.<br>
</tt></font>
<br><font size="2"><tt>In practice, some organisations will have an urgent
itch to scratch. If they have the<br>
resources to fund (and community accepted developers to undertake) that
work, they<br>
should be free to do so.<br>
</tt></font>
<br>
<br><font size="2"><tt>How do we establish the list of priorities, determine
if it is required and assign a<br>
priority?<br>
</tt></font>
<br><font size="2"><tt>We have a set of priorities in the September workshop
minutes last year<br>
( <a href="http://www.osdm.gov.au/Metadata/GeoNetwork/Committees/default.aspx" target="_blank">http://www.osdm.gov.au/Metadata/GeoNetwork/Committees/default.aspx</a> )
. Is this list<br>
being monitored and under active review?<br>
</tt></font>
<br><font size="2"><tt>What processes do we need to go through to coordinate,
review, monitor and accept<br>
additions to this list?<br>
</tt></font>
<br><font size="2"><tt>Who should be on this review panel and who has the
responsibility of liaising the<br>
requirements with the appropriate people in the GeoNetwork community.<br>
</tt></font>
<br><font size="2"><tt>What mailing lists should be used to coordinate this
work?<br>
</tt></font>
<br>
<br>
<br><font size="2"><tt></tt></font>
<br>
<br><font size="2"><tt>_How do we manage AP code development_<br>
</tt></font>
<br><font size="2"><tt>It appears that Jeroen Ticheler has been successful
in his proposal to allow sandpit<br>
development within the GeoNetwork subversion revision control environment
(is<br>
this correct Jeroen?).<br>
</tt></font>
<br><font size="2"><tt>This is the obvious place to do our development work,
feeding regular changes back<br>
into the main truck version when appropriate and accepted.<br>
</tt></font>
<br><font size="2"><tt>Do we need an AP developers list, or would the geonetwork-devel
list be more appropriate?<br>
</tt></font>
<br><font size="2"><tt>What do we do for bug tracking?<br>
</tt></font>
<br><font size="2"><tt>What do we do for packaging, automated testing and
functional testing?<br>
</tt></font>
<br><font size="2"><tt>How do we determine what goes into each release of
GeoNetwork ANZLIC Profile and<br>
enforce the practice of release early and release often?<br>
</tt></font>
<br>
<br>
<br><font size="2"><tt>I leave this here. Hopefully there is enough meat
to pick to pieces and then build on.<br>
</tt></font>
<br>
<br><font size="2"><tt>I look forward to hearing some more constructive comments.<br>
</tt></font>
<br>
<br>
<br><font size="2"><tt>Ben, do you have any comments from an ANZLIC perspective
that may need to constrain<br>
some of the ideas to come out of this?<br>
</tt></font>
<br>
<br><font size="2"><tt>Bruce Bannerman<br>
</tt></font>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br><font size="2"><tt>_______________________________________________<br>
Aust-NZ mailing list<br>
<a href="mailto:Aust-NZ@lists.osgeo.org" target="_blank">Aust-NZ@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/aust-nz" target="_blank">http://lists.osgeo.org/mailman/listinfo/aust-nz</a></tt></font>
<br>
<p><font face="Arial" size="2">Notice:</font><font style="background-color: rgb(255, 0, 0);"><br></font><font size="2"><font face="Arial">This
email and any attachments may contain information that is personal,
confidential,<br>legally privileged and/or copyright.</font> <font face="Arial">No
part of it should be reproduced, adapted or communicated </font><font face="Arial">without the prior written consent of the copyright owner.
</font></font></p>
<p><font size="2"><font face="Arial">It is the responsibility of the recipient to
check for and remove viruses.</font></font></p>
<p><font face="Arial" size="2">If you have received this email in error, please
notify the sender by return email, delete it from your system and destroy any
copies. You are not authorised to use, communicate or rely on the information
contained in this email.</font></p>
<p><font color="#008000" face="Arial" size="2">Please consider the environment before
printing this email.</font></p>
<p><font face="Arial" size="2"></font> </p>
<p> </p>
<p> </p>
</blockquote></div><br>