[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: plant DB - distributed nodes
- To: permaculture <permaculture@franklin.oit.unc.edu>
- Subject: Re: plant DB - distributed nodes
- From: John Schinnerer <eco_living@yahoo.com>
- Date: Mon, 12 Nov 2001 00:20:50 -0800 (PST)
- In-reply-to: <LISTMANAGER-137576-27289-2001.11.11-11.43.33--eco_living#yahoo.com@franklin.oit.unc.edu>
- Newsgroups: permaculture
Aloha,
> It seems to me that at lease some of the hyperlinking tools would
> need to be common to the various websites participating,
> i.e. database features, html tags, server side includes. Website A's
> database with info on eleagnus would need to be acccessable to fields
> in website B's database with info on nitrogen-fixing, drought
> tolerance, fruit bearing, medicinal value.
This seems most easily solved with an object-oriented DB. If the DBs
are object-based and the objects present a consistent set of methods
(ways of communicating, basically) to the "outside world," it doesn't
matter what the internal implementations of the objects are on any
particular system or what presentation methods are used to display data
obtained from them.
For example, as long as any system can ask any other something like:
get.hardiness('vitis vinifera','F')
...and know that the queried system will return hardiness data in
degrees Farenheit for vitis vinifera (or a standardized "no data"
result), the data acquired can be dealt with however the querying site
chooses to.
=====
John Schinnerer, MA
--------------------
- Eco-Living -
Cultural & Ecological Designing
Food - Shelter - Community
john@eco-living.net
http://eco-living.net
__________________________________________________
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.com