> Perhaps the best place to start with this is to identify
>> a set of repository resources that are general enough to be applicable
>> to any language. Once we have a list of the resources we can design a
>> set of operations on these resource (i.e. the API). I think the
>> following is a starting point:
>>
>> 1) ontology
>> 2) module (not to be confused with a CL module)
>> 3) axiom
>> (01)
I guess I'd suggest 'specification' instead of axiom, to
go with the HetCASL notation. A specification may play
the role of an axiom, but it may want to have other
statuses. Some one might not want to call axioms.
Why not use the structuring that already exists? This
more or less includes CLIF as a sublanguage
already. (02)
John B. (03)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/oor-forum/
Subscribe: mailto:oor-forum-join@xxxxxxxxxxxxxxxx
Config/Unsubscribe: http://ontolog.cim3.net/mailman/listinfo/oor-forum/
Shared Files: http://ontolog.cim3.net/file/work/OOR/
Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository (04)
|