[GeoNetwork-devel] Your ideal GeoNetwork

GeoNetwork GeoNetwork Developer
1

Hi Andrea,

I am about to have a meeting next Tuesday to discuss such things. Once the
documentation is written I will circulate it to this list. The wish list to
be discussed is:

- Xlink (are there any tools that actually implement Xlink?) Does anyone know
of any?,

- reusable components (how to do this if Xlink doesn't work),

- what to do if an element is changed (eg. indiviualName) in an Xlinked item
(Eg. CI_ResponsibleParty),

- different scenarios for changing reusable components,

- modularity so that different components can be used with/by other software,

- ebRIM (the good, the bad and the ugly ;--)),

- management of and interaction with code lists,

- WMC, WFC, WCC and Catalogue Service. How can the redundancy be eliminated,

- user interface design (can we make the complex ISO 19115 easier for users),

- the best XML technologies to implement OGC/ISO19100 standards and
specifications,

- the difference between inheritance between metadata records, use of
reusable components, different profiles and templates to get metadata records
started, and ...

- others that I can't think of at the moment.

This meeting is *not* for GeoNetwork. It is for a theoretical best solution
generic architecture that could be implemented by many tools. I really do
hope that GeoNetwork could use the content of the document but your
development may be down a different path.

I'll let you know how it goes.

Thanks.

John

-----Original Message-----
From: geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] On
Behalf Of Andrea Carboni
Sent: Tuesday, 23 January 2007 3:52 AM
To: geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] Your ideal GeoNetwork

Hi all,

as you know, we are designing geonetwork 3. The main issues
here are to
understand the real needs of the users and to address these
issues we need
some feedback from you.

The purpose of this email is to get your idea of your ideal
geonetwork. How
it should designed, what features it should have and so on. I
would like to
subdivide the requirements in 2 classes:

- those closely related to the metadata format itself (stuff
like the use of xlink
  for contacts, use of metadata hierarchies, ISO services etc...)

- general requirements (features, user interface, modules, protocols)

While it is easy for us to address the second class we have
some problems
with the first one. I would like to receive a lot of feedback
from you here,
exspecially from those of you (like John Hockaday) who have a
deep understanding
of the metadata formats like the ISO one. The question is:
how would you
design your geonetwork to face your needs?

Many thanks in advance,
Andrea

--------------------------------------------------------------
-----------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge

&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork