From OntologPSMW

Jump to: navigation, search
[ ]

Contents

Founding Members Meeting of the OpenOntologyRepository (OOR) Initiative - Wed 2008.01.23     (1)

This is the (first) Founding Members meeting (conference call) of the Open Ontology Repository (OOR) Initiative. Please refer also to the planning meeting* for this initiative, where the effort was materialized, along with its name and charter. (*ref. ConferenceCall_2008_01_03)     (1A)

Attendees     (1C)

Agenda Ideas     (1D)

... (please post your agenda ideas here; identify yourself for follow-up purposes)     (1D5)

Resources     (1F)

  • Charter of the Open Ontology Repository (OOR) Initiative     (1F1)
    • "To promote the global use and sharing of ontologies by: 1. establishing a hosted registry-repository; 2. enabling and facilitating open, federated, collaborative ontology repositories; 3. establishing best practices for expressing interoperable ontology and taxonomy work in registry-repositories."     (1F1A)
  • Open Ontology Repository initiative - Planning Meeting - Thu ConferenceCall_2008_01_03     (1F2)
  • LeoObrst's input on "definition: registry vs. repository; goals" - http://ontolog.cim3.net/forum/oor-forum/2008-01/msg00016.html     (1F3)

Agenda & Proceedings     (1G)

1. Meeting called to order:     (1G1)

2. Roll Call:     (1G5)

3. Status Review and Discussion:     (1G7)

  • Outstanding Issue review/update: (from last call)     (1G9)
    • consider requirement - think of scope and staging <-- to be discussed today     (1G9A)
    • create a wiki page and a mailing list - Peter (--partially done/ppy)     (1G9B)
    • will be subscribing all to [ontolog-forum] and the new [oor-forum] lists (--done/ppy)     (1G9C)
    • Adopting the following definition for the OOR initiative:     (1G12A)
      • a registry is defined to be a data structure where data, metadata, knowledge or semantic objects are listed as being available, along with who placed them there, and their conditions of use.     (1G12A1)
      • A repository is a data structure where data, metadata, knowledge or semantic objects and related artifacts are placed, and can be accessed from; typically repositories include management software.     (1G12A2)
        • for reference: A registry therefore can be considered a portion of a repository, a listing or table of contents for the repository, rather than the entire contents of the repository (which repository can be either centralized or distributed). A simple example of a registry is the Windows Registry, which is a listing or table of installed programs, rather than the entire set of programs themselves and their data.     (1G12A2A)
    • our (the OOR initiative) focus will be on the repository.     (1G13A)
    • Ravi: clarifying between registry and the registering process     (1G13B)
    • John: clarifying between register and registry     (1G13C)
    • Anders: there are also registry servcies and repository services     (1G13D)
    • Steve: ref. DavidWeinberger's "Everything is Miscellaneous" - repository is where we find the stuff, and registry contains information about that stuff     (1G13E)
    • we want: repository <-> storage ... registry <-> indices     (1G13F)
    • Steve: while separate notions, intelligent repositories will have a registry for performance reasons     (1G13G)
    • Ravi's suggestion:     (1G14A)
      • Repository is a database or datawarehouse where ontology information and artifacts including executables and software components and objects are stored.     (1G14A1)
      • Registry is both a mechanism to represent metadata about the contents of repository as well as a representation of public and private access and membership lists etc.     (1G14A2)
      • Both registries and repositories can be distributed and federated.     (1G14A3)
    • Steve's suggestion:     (1G15A)
      • A repository is a storage facility where ontology information and artifacts including executables and software components and objects can be found.     (1G15A1)
      • A registry is an index that organizes and directs the user to information stored in a repository.     (1G15A2)
  • Adopting: "An ontology repository is a facility where ontologies and related information artifacts can be stored, retrieved and managed."     (1G16)
    • not concluded ... fairly close already, we'll carry this on on the list     (1G16A)
  • organization     (1G18)
    • relationship to Ontolog? <-- deferred discussion to the next meeting     (1G18A)
    • Peter P. Yim: take inventory of what everyone is bringing to the table     (1G18B)
      • Peter will start a wiki page for that and let every know on the list     (1G18B1)
      • Everyone is encouraged to post to the list what they will be bringing to the table with links to the work (this will make initial content that could populate that page.)     (1G18B2)

5. New Issues:     (1G22)

6. Any Other Business:     (1G23)

7. Action items:     (1G24)

8. Schedule Next Meeting & Adjourn:     (1G25)

notes taken by: Peter P. Yim / 2008.01.23-10:39am PST     (1G29)

All participants, please review and edit to enhance accuracy and granularity of the documented proceedings.     (1G30)


Discussion Process     (1H)

  • Please mute your phone, by pressing "*2" on your phone keypad, when the talk is in progress. To un-mute, press "*3"     (1H1)
  • If you want to speak or have questions or remarks to make, please "raise your hand (virtually)" by pressing "11" on your phone keypad. You may speak when acknowledged by the speaker or the session moderator.     (1H2)
  • You can also type in your questions or comments through the browser based queue management chat tool by:     (1H3)
  • For those who have further questions or remarks on the topic, please post them to the [oor-forum] list so that everyone in the community can benefit from the discourse. (One needs to be subscribed to this archived mailing list first before posting. See subscription details here.)     (1H4)

Peter P. Yim: Welcome to: Founding Members Meeting of the OpenOntologyRepository (OOR) Initiative - Wed 2008.01.23     (1H6)

anonymous morphed into Lee Feigenbaum     (1H7)

Ravi Sharma: what is he broad agenda?     (1H8)

JohnGraybeal1: The assumption of a distributed system as the primary (?) solution merits further discussion,     (1H10)

but I don't think it affects the definition.     (1H11)

Ravi Sharma: location could be virtual and is only importnt for infrastructure and architecture such as     (1H12)

distributed for eficiency etc.     (1H13)

Ravi Sharma: Repository is a database or datawarehouse where ontology information and artifacts including     (1H14)

executables and software components and objects are stored.     (1H15)

Ravi Sharma: Registry is both a mechanism to represent metadata about the contents of repository as well as     (1H16)

a representation of public and private access and membership lists etc.     (1H17)

Ravi Sharma: Both registries and repositories can be distributed and federated.     (1H18)

anonymous morphed into Anders W. Tell     (1H19)

Steve Ray: How about: A repository is a storage facility where ontology information and artifacts     (1H20)

including executables and software components and objects can be found.     (1H21)

Steve Ray: Then, a registry is an index that organizes and directs the user to information stored in     (1H22)

a repository.     (1H23)

Ken Baclawski: Are registries and repositories separate notions or does a repository necessarily include     (1H24)

a registry?     (1H25)

John Graybeal: How critical are the words 'including executables and software components and objects"?     (1H26)

It raises a question for me about what they are doing in the registry.     (1H27)

Ravi Sharma: artifacts and information elements are ok     (1H28)

Ravi Sharma: services are ok     (1H29)

Steve Ray: A repository is a storage facility where information artifacts can be found.     (1H30)

Steve Ray: An ontology repository is a storage facility where ontologies and related information artifacts     (1H31)

can be stored, retrieved and managed.     (1H32)

Steve Ray: An ontology repository is a facility where ontologies and related information artifacts can be     (1H33)

stored, retrieved and managed.     (1H34)

Steve Ray: For the future: A registry is an index that organizes and directs the user to objects found in     (1H35)

a repository.     (1H36)

John Graybeal: To clarify for the minutes, let me introduce here (no comment needed at this time) the two     (1H37)

clarifying definitions I mentioned earlier. (I think these come from ISO 19135 but can't swear to that.)     (1H38)

John Graybeal: Register: database of the items being registered.     (1H39)

John Graybeal: Registry: information system on which a register is maintained; facilitates accessibility and     (1H41)

storage for the registry. (I assume this means the computer(s) and operating system(s).)     (1H42)

Ravi Sharma: The link provided by Anders is very relevant illustration from W3c and ebXML site.     (1H43)


This page has been migrated from the OntologWiki - Click here for original page     (1H44)