As a long term participant in OGC, I think it is capable of providing A computational view of a reference architecture.<br><br>We may want to support parallel views - for example a registry can easily support CSW. ebXML, Z39.50, SPARL, OAI etc interfaces from the same content.<br>
<br>This "profiling pattern" is possibly within the OGC purview, but its not handled well at the moment IMHO because its something that affects deployers, not technology developers: the need to maintain a consistent _information architecture_. OGC is a technology vendor association primarily.<br>
<br>GSDI could own a SDI reference architecture - but doesnt seem geared up for it. <br><br>OSGEO should at least consider the commonality between its projects, out of business sense. If databases and services and clients and registries dont handle common metadata, the pieces dont fit together well. Every time I get asked to advise someone on building tools I have to warn them they have a huge job gluing the pieces together into a coherent whole, and there will huge amounts of redundant information scattered across the configurations of each component that will make it all expensive to build, test and maintain. <br>
<br>Proprietary systems do tend to be better at this, since inter-component interoperation is often the key to marketing success. Peopele want an application - and they buy all the components with the expectation the application will work. IMHO OSGEO could significantly improve its offerings by having a common information architecture (without necessarily mandating all projects use it).<br>
<br>2c, but with inflation $64million :-)<br><br>Rob<br><br><br><br><br><div class="gmail_quote">On Wed, May 21, 2008 at 9:55 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">Thanks for the comments Rob,</font>
<br>
<br><font face="sans-serif" size="2">(Can all people please ensure that the
OSGeo-AustNZ list is included in replies, I'd like to keep the list as
the archive record for this thread?)<br>
<br>
</font>
<br><font face="sans-serif" size="2">Agreed, a branch is not ideal for the
medium to long term.</font>
<br>
<br><font face="sans-serif" size="2">Ideally from these discussions we'll
get the momentum to establish the mechanism whereby metadata profiles can
be configured as 'plugins' to the stable GeoNetwork version that is current
at that point in time.</font>
<br>
<br>
<br><font face="sans-serif" size="2">Until this occurs, we have to find a
better way of collaborating to ensuring a consistent, quality approach.
What we are doing now is not working and resulting in duplicated effort.
Therefore, I'd like to see all proposals explored and a preferred way forward
agreed on. </font>
<br>
<br>
<br>
<br><font face="sans-serif" size="2">wrt 'Reference Architecture', I can't
speak for others, however:</font>
<br>
<br><font face="sans-serif" size="2">- I don't think that this is a space
that OSGeo would want to get into.</font>
<br>
<br><font face="sans-serif" size="2">- I wouldn't want to be prescriptive
on what the projects can and can't do. We are talking about projects that
thrive on innovation.</font>
<br>
<br><font face="sans-serif" size="2">- I think that this is a role that is
more appropriately handled by the OGC, in this instance with the CSW standard.
As I understand it, GeoNetwork already supports CSW (excluding support
for ebRIM functionality).</font>
<br>
<br>
<br>
<br><font face="sans-serif" size="2">Jeroen may wish to comment further on
the GeoNetwork communities thoughts and intentions here.</font>
<br>
<br>
<br>
<br>
<br><font face="sans-serif" size="2">Bruce Bannerman</font>
<br>
<br><font face="sans-serif" size="2"><br>
</font>
<br>
<br>
<br>
<table width="100%">
<tbody><tr valign="top">
<td width="40%"><font face="sans-serif" size="1"><b>"Rob Atkinson"
<<a href="mailto:robatkinson101@gmail.com" target="_blank">robatkinson101@gmail.com</a>></b> </font>
<p><font face="sans-serif" size="1">21/05/2008 09:14 AM</font>
</p></td><td width="59%">
<table width="100%">
<tbody><tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">To</font></div>
</td><td><div class="Ih2E3d"><font face="sans-serif" size="1"><a href="mailto:Bruce.Bannerman@dpi.vic.gov.au" target="_blank">Bruce.Bannerman@dpi.vic.gov.au</a></font>
</div></td></tr><tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">cc</font></div>
</td><td><font face="sans-serif" size="1"><a href="mailto:ozmeta-l@erin.gov.au" target="_blank">ozmeta-l@erin.gov.au</a>, <a href="mailto:asdi-l@lists.anzlic.org.au" target="_blank">asdi-l@lists.anzlic.org.au</a>,
<a href="mailto:info@osdm.gov.au" target="_blank">info@osdm.gov.au</a></font>
</td></tr><tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">Subject</font></div>
</td><td><font face="sans-serif" size="1">Re: Fw: [Aust-NZ] Finding a way forward
- GeoNetwork as platform to support ANZLIC Profile of ISO 19115/19139</font></td></tr></tbody></table>
<br>
<table>
<tbody><tr valign="top">
<td>
</td><td></td></tr></tbody></table>
<br></td></tr></tbody></table><div><div></div><div class="Wj3C7c">
<br>
<br>
<br><font size="3"><br>
We should not be looking at a branch - there is nothing wierd about the
ANZLIC profile.<br>
<br>
Geonetwork needs to be capable of being configured with a profile of a
baseline standard it supports (ISO 19115 in this case) - this is _THE_
basic metadata implementation pattern. Putting the key piece of core configuration
capability required onto a branch is rather non-sensical.<br>
<br>
<br>
in fact, all tiers of an OS SDI reference implementatiuon (tools and architecture)
need to follow the pattern - this is the goal of the SISS project.<br>
<br>
FYI. I'm currently drawing up some architecture ideas for this, on behalf
of the SISS project. This is a somewhat slow process as I have a day a
week assigned to this and i'm doing a little geoserver effort support at
the same time. <br>
<br>
The broader challenge of how we effectively share architectural patterns
is also a concern - we design by starting from scratch, or "clone
and modify" from existing designs, and wonder why we have difficulty
joining the bits back together once built. Is there a role for a "reference
architecture" for OSGEO?<br>
<br>
<br>
Regards<br>
Rob Atkinson<br>
</font>
<br><font size="3">On Tue, May 20, 2008 at 8:34 PM, <</font><a href="mailto:Bruce.Bannerman@dpi.vic.gov.au" target="_blank"><font color="blue" size="3"><u>Bruce.Bannerman@dpi.vic.gov.au</u></font></a><font size="3">>
wrote:</font>
<br><font face="sans-serif" size="2"><br>
<br>
IMO:</font><font size="3"> <br>
</font><font face="sans-serif" size="2"><br>
<br>
This is a resend for people who are not following the thread on the OSGeo-AustNZ
list.</font><font size="3"> <br>
<br>
</font><font face="sans-serif" size="2"><br>
<br>
Bruce Bannerman</font><font size="3"> </font><font face="sans-serif" size="2"><br>
</font><font size="3"><br>
<br>
</font><font face="sans-serif" size="2"><br>
</font><font size="3"><br>
</font><font color="#800080" face="sans-serif" size="1"><br>
----- Forwarded by Bruce Bannerman/DPI/VICGOV1 on 20/05/08 08:21 PM -----</font><font size="3">
</font>
<table width="100%">
<tbody><tr valign="top">
<td width="30%"><font face="sans-serif" size="1"><b>Bruce Bannerman <</b></font><a href="mailto:bruce@bannerman.id.au" target="_blank"><font color="blue" face="sans-serif" size="1"><b><u>bruce@bannerman.id.au</u></b></font></a><font face="sans-serif" size="1"><b>></b>
<br>
Sent by: </font><a href="mailto:aust-nz-bounces@lists.osgeo.org" target="_blank"><font color="blue" face="sans-serif" size="1"><u>aust-nz-bounces@lists.osgeo.org</u></font></a><font size="3">
</font>
<p><font face="sans-serif" size="1">20/05/08 08:19 PM</font><font size="3">
</font>
</p></td><td width="69%">
<br>
<table width="100%">
<tbody><tr valign="top">
<td width="13%">
<div align="right"><font face="sans-serif" size="1">To</font></div>
</td><td width="86%"><a href="mailto:aust-nz@lists.osgeo.org" target="_blank"><font color="blue" face="sans-serif" size="1"><u>aust-nz@lists.osgeo.org</u></font></a><font face="sans-serif" size="1">,
</font><a href="mailto:anzlicmet-l@listserv.its.utas.edu.au" target="_blank"><font color="blue" face="sans-serif" size="1"><u>anzlicmet-l@listserv.its.utas.edu.au</u></font></a><font size="3">
</font>
</td></tr><tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">cc</font></div>
</td><td>
</td></tr><tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">Subject</font></div>
</td><td><font face="sans-serif" size="1">Re: [Aust-NZ] Finding a way forward
- GeoNetwork as platform to support ANZLIC Profile
of ISO 19115/19139</font></td></tr></tbody></table>
<br>
<br>
<table width="100%">
<tbody><tr valign="top">
<td width="50%">
</td><td width="50%"></td></tr></tbody></table>
<br></td></tr></tbody></table>
<br><font size="3"><br>
<br>
</font><font size="2"><tt><br>
Thank you to all who have responded so far.<br>
<br>
We're starting to get a snapshot of open source spatial work that is<br>
going on around Australia and New Zealand. It is certainly starting to<br>
take off.<br>
<br>
<br>
Please keep the comments coming, so that we as a community get a better<br>
understanding of the issues involved. <br>
<br>
<br>
I would like to reiterate that this email thread is not intended as a<br>
criticism of any group or individual.<br>
<br>
<br>
While I had originally wondered what we, as a community, could do to<br>
support Simon with the GeoNetwork ANZLIC Profile work, I can see that it<br>
is rapidly turning into:<br>
<br>
<br>
How can we support Simon, Byron, Cameron, Robert and a number of other<br>
organisations in their GeoNetwork ANZLIC Profile work?<br>
<br>
<br>
<br>
We have the beginnings of an open source community. Where to from here?<br>
<br>
<br>
What we eventually put in place could have potential for other<br>
Australian and New Zealand specific open source spatial work in the<br>
future.<br>
<br>
<br>
I'd also like to hear some thoughts from some of our more experienced<br>
open source developers. <br>
<br>
<br>
To kick things off:<br>
<br>
I've had an off line email from Jeroen Ticheler from the GeoNetwork<br>
community. Jeroen is keen to help us where he can.<br>
<br>
He has suggested that if it is required, it may be possible establish a<br>
branch with ANZLIC support on the Geonetwork SubVersion.<br>
<br>
<br>
<br>
Please keep the comments coming. This is very informative.</tt></font>
<br><font size="2"><tt><br>
<br>
<br>
<br>
Bruce Bannerman<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Aust-NZ mailing list</tt></font><font color="blue" size="2"><tt><u><br>
</u></tt></font><a href="mailto:Aust-NZ@lists.osgeo.org" target="_blank"><font color="blue" size="2"><tt><u>Aust-NZ@lists.osgeo.org</u></tt></font></a><font color="blue" size="2"><tt><u><br>
</u></tt></font><a href="http://lists.osgeo.org/mailman/listinfo/aust-nz" target="_blank"><font color="blue" size="2"><tt><u>http://lists.osgeo.org/mailman/listinfo/aust-nz</u></tt></font></a>
<p><font face="Arial" size="2">Notice:<br>
This email and any attachments may contain information that is personal,
confidential,<br>
legally privileged and/or copyright.</font><font size="2"> </font><font face="Arial" size="2">No
part of it should be reproduced, adapted or communicated without the prior
written consent of the copyright owner. </font>
</p><p><font face="Arial" size="2">It is the responsibility of the recipient
to check for and remove viruses.</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 size="3"> </font>
</p><p><font size="3"> </font>
</p><p><font size="3"> </font>
</p><p>
</p><p></p></div></div></blockquote></div><br>