(I'm moving this segment of the conversation to this "where can we put
it" thread ... to segregate it from the "what is an FO, or what should
it be" discussion ...) (01)
> [JSF] ... Yim has been doing
> a good job in hosting ontolog forum and the related web sites.
> Therefore, he should have the right of first refusal to host
> whatever this group develops. (02)
[ppy] Thank you John. ... only if I am capable, obviously, and, if
what I have to offer can do (at least) an equal or (hopefully) better
job than the alternatives. (03)
> [JP] the remaining question, it seems to me,
> would be whether Peter has the facilities to
> host a public SVN. I think he does in relation to
> some of his wiki work. (04)
[ppy] correct, Jack ... Yes, we do provide SVN (subversion
repository) hosting. For those who are familiar with the CODS [1]
offering, we have been hosting a SVN repository [2] for CODS since
late 2007. (05)
That said, though, version control and software configuration
management tools such as SVN (CVS, PVCS, Visual SourceSafe, and the
like) falls miserably short of being adequate for ontologies. For one,
they just aren't able to provide the necessary "diff's" in the case of
Ontologies, where one would obviously want to compare, say elements
within an ontology, that at a much finer granular level than that of
"the file." (Tim Redmond had mentioned some of that in one of our
earlier presentations on CODS before.) (06)
That shortcoming is among one of the drivers for the need for Ontology
Repositories ... and then came the OOR Initiative, OntologySummit2008,
... and ... please fast-forward to this Friday's OOR "developers"
session - http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2010_02_19 (07)
To those who are interested, please come join us in the discussion
this Friday (Feb-19) ... as well as the upcoming "content" and "use
cases" sessions (there even an "IPR" session being planned.) ... RSVP
(by emailing me offline), if you haven't already [4]. (08)
Thanks & regards. =ppy (09)
Ref.... (010)
[1] CODS - a joint Stanford-BMIR/CIM3 effort to provide a
Collaborative Ontology Development Service and Infrastructure to the
ontology community at large. see:
http://protege.cim3.net/cgi-bin/wiki.pl?CODS (011)
[2] CODS' subversion repository access - see:
http://protege.cim3.net/cgi-bin/wiki.pl?CODS/HostedServerConfiguration#nid9ZY (012)
[3] Ontolog session dated 11-Oct-2007 - see:
http://ontolog.cim3.net/cgi-bin/wiki.pl?ConferenceCall_2007_10_11
.... in particular, see TimRedmond's slide#6 (013)
[4] Your invitation -
http://ontolog.cim3.net/forum/ontolog-invitation/2010-02/msg00007.html
--- (014)
---------- Forwarded message ----------
From: Jack Park <jackpark@xxxxxxxxx>
Date: Wed, Feb 17, 2010 at 3:17 PM
Subject: Re: [ontolog-forum] Foundation ontology, CYC, and Mapping
To: "[ontolog-forum]" <ontolog-forum@xxxxxxxxxxxxxxxx> (015)
No objection raised for Peter to host the project; the remaining
question, it seems to me, would be whether Peter has the facilities to
host a public SVN. I think he does in relation to some of his wiki
work. (016)
Jack (017)
On Wed, Feb 17, 2010 at 2:49 PM, John F. Sowa <sowa@xxxxxxxxxxx> wrote:
> Jack,
>
> Thanks for the note of support.
>
> I believe that the only way to get this group to do anything is to
> start with something fairly good and build from there. OpenCyc is
> the most likely candidate, but the FO should give equal support to
> other reasonable ontologies. Therefore, it should be hosted on
> neutral grounds, rather than on a web site that is devoted to
> a specific ontology, such as OpenCyc.
>
> Re Google: That is a possibility, but Peter Yim has been doing
> a good job in hosting ontolog forum and the related web sites.
> Therefore, he should have the right of first refusal to host
> whatever this group develops.
>
> John
>
> -------- Original Message --------
> Subject: Re: [ontolog-forum] Foundation ontology, CYC, and Mapping
> Date: Wed, 17 Feb 2010 12:17:53 -0800
> From: Jack Park <jackpark@xxxxxxxxx>
> Reply-To: [ontolog-forum] <ontolog-forum@xxxxxxxxxxxxxxxx>
> To: [ontolog-forum] <ontolog-forum@xxxxxxxxxxxxxxxx>
>
> I would toss a +1 at this concept of starting somewhere and evolving
> from there. OpenCyc makes sense. What else makes sense might be a
> website for such a project, for instance, http://code.google.com/ ,
> which provides Subversion (and other) version control options, a wiki,
> download area, etc. Perhaps there are other options.
>
> Jack
>
> On Wed, Feb 17, 2010 at 8:41 AM, John F. Sowa <sowa@xxxxxxxxxxx> wrote:
> > Dear Matthew, Doug, and Pat C,
> >
> > Before getting to the details of your notes, I'd like to clarify the
> > term FO, which Pat introduced for a Foundation Ontology. I have no
> > objection to using the term FO, but I would apply it to the totality
> > of the theories (or microtheories) in an OOR. The Cyc example of an
> > upper ontology with many specialized microtheories would be an example.
> >
> > However, I would broaden the idea to support multiple theories at the
> > upper levels, which might be incompatible. For example, Matthew,
> > Chris P, and Pat H have strongly supported a 4D ontology for the upper
> > levels, but many other people prefer to use a 3D upper level. For
> > many of the lower level microtheories, the differences between a 3D
> > vs 4D foundation are irrelevant.
> >
> > Pat C wants to use primitives based on Longman's dictionaries, but
> > I objected that those terms are too vague, and an enormous amount
> > of work would be needed to make them precise. Therefore, I propose
> > the following approach:
> >
> > 1. OpenCyc is freely available as open source, but Pat objected
> > that it has very few axioms. However, Longman's terms have zero
> > axioms, and they have never been tested for their usefulness in
> > any ontology, certainly not in anything as large as Cyc.
> >
> > 2. Therefore, I recommend that we adopt the OpenCyc terms together
> > with the axioms available in OpenCyc as a "starter set" for
> > developing the Foundation Ontology.
> >
> > 3. But we would also welcome and encourage anybody with different
> > preferences to contribute more terms and theories to the FO.
> >
> > 4. When convenient, those new theories should adopt the same
> > spelling as the terms already in the starter set, but any
> > new terms (taken from Longman's or any other source anyone
> > might prefer) could also be used in those additional theories.
> >
> > 5. The complete hierarchy of theories for the FO would be
> > organized along the lines we've been discussing in these notes.
> >
> > 6. Pat's goal of finding a much smaller set of defining terms
> > (called primitives) could be done in parallel with the
> > development of the FO instead of delaying its development.
> >
> > 7. If and when a good set of primitives has been found useful,
> > a methodology based on them could be promoted for simplifying
> > further ontology development. However, older theories that
> > use the older terms would remain available as long as anyone
> > needs them.
> >
> > I'm suggesting this as a compromise that would begin with a large
> > tested set of terms already organized in a generalization/
> > specialization hierarchy. It would also accommodate new terms
> > that could be added as needed from any source. But if anyone
> > wants to do any immediate implementation today, the OpenCyc
> > terms can be used. Any work done with them would be guaranteed
> > to be supported by the full FO.
> >
> > MW> I think [the FO] is more than just a vocabulary, but I agree
> > > that great care would need to be taken not to introduce into what
> > > I am calling abstract theories axioms that did not contradict say
> > > the 3D and 4D axioms that would be introduced when they were
> > > combined with those theories.
> >
> > I agree. In fact, one advantage of OpenCyc is that it doesn't have
> > all the axioms (AKA old baggage) of full Cyc. That implies that it
> > is more general than Cyc and less likely to have unpleasant
> > "surprises" (AKA inconsistencies).
> >
> > MW> However, having such [abstract theories] would greatly simplify
> > > mapping between say 3D and 4D ontologies. These would I think need
> > > to be carefully designed rather than just picking something up,
> > > since it is casually almost certainly made some upper ontology
> > > assumptions.
> >
> > I agree. Many, if not most of those theories could be based on
> > terms that are already in OpenCyc. In fact, if you just adopt
> > the terms by themselves without any axioms, there is no possibility
> > of an inconsistency. Then any axiom that is added could be tested
> > for consistency with both the 3D and the 4D ontologies (along the
> > lines that I suggested in my previous note).
> >
> > DF> An ontology with a single theory would complicate the idea of
> > > a foundational ontology as an interlingua to which all external
> > > ontologies can be mapped.
> >
> > Yes. That is why I would prefer to use the name Foundation Ontology
> > for the full hierarchy of all the theories in the OOR.
> >
> > DF> Competing external theories could be incorporated by defining new
> > > concepts/relations for the relata of the competing theories (which
> > > map directly to the terms of the source ontology) and then adding
> > > rules relating them with the ostensible "sameAs" terms already in
> > > the foundational ontology.
> >
> > PC> Yes, but I would express the process as "logically specifying
> > > the terms of each extension ontology using only the terms in the
> > > FO" rather than "map directly" since that suggests that the
> > > entities in the extension ontology are already on the FO, which
> > > in general they will not be.
> >
> > I would expect the FO to be completely open-ended so that the
> > number of useful terms would increase indefinitely. There could
> > also be a small subset of recommended defining terms. (I wouldn't
> > even object to calling them "primitives".)
> >
> > But we do have to recognize that many "primitives" may be very
> > underspecified. For example, the term PointInTime should be neutral
> > with respect to a 3D or 4D ontology. For lower-level microtheories,
> > you might have a general theory called Hiking, which would use
> > PointInTime without any dependencies on 4D or 3D. But if there are
> > dependencies, one could have common specializations of Hiking with
> > either of the two upper-level theories to generate the subtheories
> > Hiking4D and Hiking3D.
> >
> > JFS> But if you think of [the FO] as a collection of theories organized
> > >> in a hierarchy, no single theory ever changes. Instead, each
> > >> innovation adds another theory to the hierarchy, which may be a
> > >> generalization, a specialization, a sibling, or a cousin of some
> > >> other theory. You can also compare and combine theories.
> >
> > DF> Agreed. This is part of the reasoning behind Cyc method of
> > > "microtheories" or contexts....
> >
> > PC> And that would be true for the FO and its extensions also. But there
> > > is an additional aspect to the FO as I have proposed it. The CYC
> > > BaseKB is part of every other more specialized microtheory, but it
> > > was not designed as, nor used as, an inventory of basic elements that
> > > is sufficient to specify (as combinations) the intended meanings of
> > > the symbols that are in all of the other linked microtheories. CYC
> > > didn't try that tactic, which could have been very informative. But
> > > a proper test would in any case require that a good number of separate
> > > groups with different applications and viewpoints try to use the same
> > > FO to describe their different domain ontologies.
> >
> > This comment mixes two different goals:
> >
> > 1. A large useful ontology that people can begin using ASAP.
> >
> > 2. A project to determine whether a small subset of terms (called
> > primitives) is sufficient to define everything else and would
> > thereby promote interoperability.
> >
> > Different people may have different priorities. My personal preference
> > is to emphasize #1. I have no objection to anyone who prefers #2, but
> > I would not want to tell people who have a day job that they have to
> > wait until #2 is finished. My recommendation is to start with #1 and
> > let anyone who wants #2 to *extract* some subset from #1 in order to
> > test that hypothesis. If that hypothesis seems to be justified, then
> > the results could be developed into a methodology for using, adapting,
> > and streamlining the much larger resources of #1.
> >
> > But I would never suggest that people who need an ontology today should
> > wait until project #2 is completed. The above proposal lets people
> > start new projects using OpenCyc and rest assured that the FO would
> > continue to support them in the future.
> >
> > JFS> You can think of context as some additional statements S that are
> > >> added to a theory T to specialize it for some particular application.
> >
> > DF> If the context referred to is what Cyc calls a DataMicrotheory,
> > > then the statements added are qualitatively different from those
> > > in the basic theory.
> > >
> > > A context might close T's open world assumption, such that T2 has
> > > a closed world assumption. T and T2, in such a case, would be
> > > different types of theory.
> >
> > That's a good point. It illustrates an important advantage of
> > starting with OpenCyc (or some subset of it). We can take advantage
> > of the 26 years of experience in developing Cyc. We don't have to
> > adopt every one of their decisions, but when we diverge, we should
> > have a good reason for doing so.
> >
> > DF> An FO would need to have a reasonably restrictive generalization
> > > of classes included in any microtheory that is to be mapped to it.
> > > Defining "reasonably restrictive" could be hard, but it seems to me
> > > that SUMO (with extensions) and Cyc both would currently meet this
> > > requirement. Including concepts from UMLS and GoodRelations would
> > > lower the rough lower edge of the directed acyclic graph of classes
> > > in several key areas.
> >
> > I'm all in favor of building on good work that has been done in other
> > systems. We should make sure that the licensing terms are compatible
> > and get explicit permission to use whatever is incorporated in the FO.
> >
> > DF> One question is on what basis should individuals should be included
> > > in an FO. Certainly units of measure should be. Currencies &
> > > countries surely. Cities and every instance in the GeoNames base?
> > > How should the selection of people to add be made? Organizations?
> > > Conceptual works (books, movies, songs, albums, paintings,
> > > constitutions, poems, ...)? Sports and games? Events (disasters,
> > > wars, elections, mergers, ...)? Etc.
> >
> > Those are excellent questions. I would prefer to err on the side of
> > being more inclusive. My suggestion would be to keep the axioms
> > relatively free of individual names, but to have an associated
> > database that would store as much as anyone might find useful.
> >
> > However, there will undoubtedly be many very useful specialized
> > theories, such as US IRS Tax Code for 2010. The most qualified
> > people to develop such a theory would be the IRS. But the FO
> > could maintain pointers to such theories stored and maintained
> > in compatible formats by other organizations.
> >
> > DF> The breadth of coverage of the proposed FO needs to clarified.
> > > Is it to be an ever-expanding set of all terms defined in any
> > > ontology? Should it include all individuals ever defined on
> > > the Semantic Web?
> >
> > Those are important policy decisions. Since the SW is expanding
> > very rapidly, we can't hope to incorporate it into the FO. But we
> > must have interfaces to it that would allow any application to
> > access it as needed. In fact, if we do a good job on the FO,
> > the SemWebbers might take notice and adapt their technology to
> > facilitate sharing in both directions.
> >
> > DF> Or could there be a basic, relatively fixed, FO to which an
> > > expanding number of contextually restricted, but still centralized,
> > > ontologies are related? I could see such for brand-name products,
> > > GeoNames, UMLS, IMDB, GeneBase, etc.
> >
> > PC> The FO itself should try to include all primitives that are used
> > > by more than a small set of specific domain ontologies, and only
> > > those non-primitive elements that are needed for ease of use and are
> > > non-controversial. Primitives required by domain ontologies should
> > > also be maintained, but as part of a domain extension.
> >
> > The goal of getting a useful FO ASAP implies that we should start
> > with a much larger set of terms than Pat has in mind. But that may
> > be an advantage. The goal of extracting a smaller number of defining
> > terms can be guided by usage patterns. Those terms that are most
> > widely used would be prime candidates. The other terms could be
> > redefined in terms of them.
> >
> > I would expect an FO committee to be similar (in some ways) to the
> > W3C. It would define formats, guidelines, policies, etc., and
> > encourage other groups to adopt them and make their work compatible.
> >
> > John (018)
On Sun, Feb 14, 2010 at 5:38 PM, Peter Yim <peter.yim@xxxxxxxxx> wrote:
> Thank you very much, John.
>
>
> YES, I agree! ... (rather than just talking about it) getting started
> is the key.
>
>> JG>> How do I find out what "an Ontology Repository that federates with
>> >> the OOR" means and how I can achieve it? (Has this been discussed
>> >> in one of the sessions, or is it a topic for discussion?)
>>
>> PPY> I guess some developer has to "create" it first ... and then
>> > administrators/stewards/users of "ontologies" will be able to
>> > leverage those capabilities.
>>
>> [JFS] I believe the subscribers to this list can begin that development
>> very soon with a modest amount of resources. In the initial stages,
>> it could be a *virtual* repository, which would contain metadata about
>> and pointers to various resources stored on other web sites.
>
> [ppy] Through the effort of the OOR team (which began in Jan-2008)
> members, and contributions from NCBO, Stanford, CIM3, BBN,
> Northeastern, Toronto and other members of that team, we are actually
> further along that some folks might realize. The exchange cited above
> between JG (John Graybeal of the MMI Project) and PPY (myself, Peter
> Yim) was actually in reference to the "federation" capability of an
> OOR.
>
> I waited a whole week to respond to you, John, because I hope I can
> have something specific to point everyone to ... (and they're just
> out)
>
> I would like to draw everyone's attention to the OOR-related
> announcement I just posted
> at: http://ontolog.cim3.net/forum/oor-forum/2010-02/msg00007.html
>
> ... please join us in testing out the OOR-sandbox, and come to the
> upcoming three panel sessions, to find out where things stand, and
> help influence how the OOR project will proceed.
>
>
>> [JFS] ... require a small amount of storage space, and it could be
>> started on the same web site used for ontolog forum. The initial
>> work would involve the development of the metadata for relating
>> ontologies to one another and to lexical resources that relate the
>> categories of an ontology to the terms in natural languages.
>>
>> We would also develop guidelines for reviewing ontologies and
>> case studies about how they have been used, including both
>> successes and failures. As time goes on, it could evolve from
>> a virtual repository to a physical repository with a full-time
>> staff, a larger budget, and systematic procedures for acquiring,
>> developing, and maintaining ontologies.
>
> [ppy] Recognizing that not all ontology formats are supported so far
> (e.g. Michael Gruninger and his team's work on COLORE and CL support
> is still at an early stage) ... therefore, John's suggestion of just
> registering the relevant metadata and documenting finding and insights
> on the wiki is a great idea (while software development work
> progresses in parallel.) I will be more than
>
> As for metadata that needs to be captured, a prime candidate for the
> OOR work (adoption to use and extend from) is the OMV (Ontology
> Metadata Vocabulary) which PeterHaase/Karlsruhe has authored (ref.
> http://ontolog.cim3.net/cgi-bin/wiki.pl?ConferenceCall_2008_04_10 &
> http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2008_Communique#nid1GWH
> ).
>
> Please continue this dialog on the list asynchronously, so we can have
> something to bring up for real-time discussion at the Thu 2010.03.25
> OOR "Content" panel session (especially on how we could make use of
> the OOR infrastructure that is becoming available.) ... Volunteers to
> provide their ontologies, concrete suggestions and candidate action
> plans welcome!
>
>
> Thanks again, John.
>
>
> Regards. =ppy
> --
>
>
> On Sun, Feb 7, 2010 at 8:03 AM, John F. Sowa <sowa@xxxxxxxxxxx> wrote:
>> Dear Matthew and Peter,
>>
>> I'd like to comment on some points that Matthew made in this thread and
>> Peter made in a different thread. And I'd like to combine my comments
>> with parts of two previous notes I sent to this thread (copies below).
>>
>> MW> It depends what you think an FO is, which seems to be one of the
>> > questions that need to be settled still. However, I don't think it
>> > reasonable to expect to develop a single ontology that everyone will
>> > sign up to.
>>
>> I agree. That is the goal of a proposal I outlined in the first note
>> copied below and elaborated in the second one.
>>
>> JG>> How do I find out what "an Ontology Repository that federates with
>> >> the OOR" means and how I can achieve it? (Has this been discussed
>> >> in one of the sessions, or is it a topic for discussion?)
>>
>> PPY> I guess some developer has to "create" it first ... and then
>> > administrators/stewards/users of "ontologies" will be able to
>> > leverage those capabilities.
>>
>> I believe the subscribers to this list can begin that development
>> very soon with a modest amount of resources. In the initial stages,
>> it could be a *virtual* repository, which would contain metadata about
>> and pointers to various resources stored on other web sites.
>>
>> That would require a small amount of storage space, and it could be
>> started on the same web site used for ontolog forum. The initial
>> work would involve the development of the metadata for relating
>> ontologies to one another and to lexical resources that relate the
>> categories of an ontology to the terms in natural languages.
>>
>> We would also develop guidelines for reviewing ontologies and
>> case studies about how they have been used, including both
>> successes and failures. As time goes on, it could evolve from
>> a virtual repository to a physical repository with a full-time
>> staff, a larger budget, and systematic procedures for acquiring,
>> developing, and maintaining ontologies.
>>
>> John
>
>
>> -------- Original Message --------
>> Subject: Re: [ontolog-forum] Foundation ontology, CYC, and Mapping
>> Date: Fri, 05 Feb 2010 02:00:51 -0500
>>
>> Before getting into the details of what I've been arguing against, I'll
>> summarize what I've been arguing for in many notes over the years:
>>
>> 1. A loosely axiomatized hierarchy of categories (predicates,
>> relations, functions, types, or whatever they're called in the
>> version of logic that is being used). Those categories may be
>> associated with lexical resources such as WordNet, Longman's
>> "primitives", Anna Wierzbicka's "primitives", Roget's Thesaurus,
>> or many other resources that have been or will be developed.
>>
>> 2. For any particular application, more detailed axioms are needed
>> to support precise reasoning. Those axioms are organized in
>> small, modular theories (or 'microtheories' in Cyc's sense).
>> Those theories can be related in a finite hierarchy (of which
>> the infinite lattice is the theoretical extension).
>>
>> 3. All the resources in #1 and #2 are stored in a repository,
>> with all the documentation, case studies, testimonials for
>> and against, stored with them. All the relations that Ali
>> proposed for COLORE and any others that anybody else might
>> find useful could also be stored with them.
>>
>> 4. Tools for using, analyzing, relating, combining, testing,
>> extending, and editing the term hierarchy and the hierarchy
>> of theories should also be developed and made available.
>>
>> 5. Further additions, extensions, and modifications that anyone
>> might invent or implement may be added as time goes by.
>>
>> I believe that this kind of system could serve the requirements
>> that Pat C. would like to achieve, it can accommodate formalized
>> versions of theories based on Longman's list, and anybody who
>> finds them useful could use them and write testimonials for or
>> against them along the lines of point #3 above. But it doesn't
>> require anyone to limit their choice to any predetermined set
>> of terms (whether primitive or not).
>>
>> For interoperability, anyone who has stories about successes
>> or failures can document them in the repository, and further
>> decisions can be based on the accumulated experience....
>>
>> John
>
>
>> -------- Original Message --------
>> Subject: Re: [ontolog-forum] Foundation ontology, CYC, and Mapping
>> Date: Fri, 05 Feb 2010 10:47:46 -0500
>>
>> Mike,
>>
>> I agree:
>>
>> MB> I think it would make sense to set up a structure as you describe
>> > and populate it with such terms as can be defined semantically from
>> > authoritative industry sources i.e. industry standards, along with
>> > annotation of the provenance of those semantics.
>>
>> The goal would be to "populate" it with any and all resources that
>> anyone might make available under a suitable license. SourceForge,
>> Wikipedia, and WordNet are three different examples of rich resources
>> that were developed with modest levels of funding. The W3C and ISO
>> are examples that require more funding, but have a more disciplined
>> organization. There are many other organizations and consortiums
>> that use various non-profit business models for maintaining resources,
>> free, low cost, or high cost.
>>
>> Instead of $30 million for a 3-year project, I would suggest a more
>> modest amount of funding to organize a long-term non-profit organization
>> that could accept contributions (of ontologies and funding), vet the
>> ontologies and related resources, organize them, and maintain them
>> according to guidelines along the lines we have been discussing.
>>
>> MB> A vital component of this would be change management, such that
>> > when the competent authority makes a change or an addition to
>> > their semantics, this can be picked up and propagated through the
>> > resource and any developments that have made use of this resource.
>> > A tall order perhaps, but not as tall as maintaining an isolated
>> > huge ontology.
>>
>> I agree. But we don't have to make it perfect on the first try.
>> Getting the resources together would be an important first step.
>>
>> MB> For the most part such terms would also be more relevant to how
>> > information is passed between computers, than something from the
>> > broader and fuzzier world of the human language dictionary, I would
>> > venture to suggest. They would certainly be simpler.
>>
>> The organization could include both formal ontologies and lexical
>> resources for mapping the formally defined theories to natural
>> languages. But it's important to distinguish the two. WordNet
>> is often called an ontology, but it's closer to a dictionary
>> than to a formal ontology. It's important to clarify the nature
>> of the various resources and their interrelationships.
>>
>> MB> I think a relevant point is that any "widely supported ontology"
>> > should be widely supported because it has emerged from industry
>> > specialists doing real work (like [Matthew's] work at Shell) and
>> > not because some group of clever ontologists have got some funding
>> > and gone off and done some ontology and then worked to get it widely
>> > supported. In other words, the semantics would be widely supported
>> > to begin with.
>>
>> My preference is to let the users "vote with their feet." All the
>> contributed ontologies would be organized in a hierarchy. Each one
>> would have statistics, documentation, and reviews about how it was
>> being used and the results obtained. Nothing would have to be thrown
>> away, all versions of all resources would always be available, and
>> users could view the collection according to various criteria:
>> popularity, reviews, success stories, application domain, etc.
>>
>> John
> (019)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx (020)
|