From OntologPSMW

Jump to: navigation, search
[ ]

OpenOntologyRepository: Project Team Member (regular planning & admin) Conference Call - Tue 2014_07_22     (1)

  • Session Co-chairs: KenBaclawski and TillMossakowski     (1B)

  • Dial-in:     (1C4)
    • Phone (US): +1 (425) 440-5100 ... {{{(long distance cost may apply)}}}     (1C4A)
    • Skype: join.conference (i.e. make a skype call to the contact with skypeID="join.conference") ... {{{(generally free-of-charge, when connecting from your computer ... ref.)}}}     (1C4B)
      • when prompted enter Conference ID: 843758#     (1C4B1)
      • Unfamiliar with how to do this on Skype? ...     (1C4B2)
        • Add the contact "join.conference" to your skype contact list first. To participate in the teleconference, make a skype call to "join.conference", then open the dial pad (see platform-specific instructions below) and enter the Conference ID: 843758# when prompted.     (1C4B2A)
        • you may connect to the user:"join.conference" even if the skype GUI shows that this user is offline!     (1C4B2B)
      • Can't find Skype Dial pad? ...     (1C4B3)
        • for Windows Skype users: Can't find Skype Dial pad? ... it's under the "Call" dropdown menu as "Show Dial pad"     (1C4B3A)
        • for Linux Skype users: if the dialpad button is not shown in the call window you need to press the "d" hotkey to enable it. ... {{{(ref.)}}}     (1C4B3B)
      • if you are using skype and the connection to "join.conference" is not holding up, try using (your favorite POTS or VoIP line, etc.) either your phone, skype-out or google-voice and call the US dial-in number: +1 (425) 440-5100 ... when prompted enter Conference ID: 843758#     (1C4B4)
  • Discussions and Q & A:     (1C5)
    • Nominally, when a presentation is in progress, the moderator will mute everyone, except for the speaker.     (1C5A)
    • To un-mute, press "*7" ... To mute, press "*6" (please mute your phone, especially if you are in a noisy surrounding, or if you are introducing noise, echoes, etc. into the conference line.)     (1C5B)
    • we will usually save all questions and discussions till after all presentations are through. You are encouraged to jot down questions onto the chat-area in the mean time (that way, they get documented; and you might even get some answers in the interim, through the chat.)     (1C5C)
    • During the Q&A / discussion segment (when everyone is muted), If you want to speak or have questions or remarks to make, please raise your hand (virtually) by clicking on the "hand button" (lower right) on the chat session page. You may speak when acknowledged by the session moderator (again, press "*7" on your phone to un-mute). Test your voice and introduce yourself first before proceeding with your remarks, please. (Please remember to click on the "hand button" again (to lower your hand) and press "*6" on your phone to mute yourself after you are done speaking.)     (1C5D)
    • instructions: once you got access to the page, click on the "settings" button, and identify yourself (by modifying the Name field from "anonymous" to your real name, like "JaneDoe").     (1C6A)
    • You can indicate that you want to ask a question verbally by clicking on the "hand" button, and wait for the moderator to call on you; or, type and send your question into the chat window at the bottom of the screen.     (1C6B)
    • thanks to the folks, one can now use a jabber/xmpp client (e.g. gtalk) to join this chatroom. Just add the room as a buddy - (in our case here) ... Handy for mobile devices!     (1C6C)
  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at: ... view-only password: "ontolog"     (1C7)
    • if you plan to be logging into this shared-screen option (which the speaker may be navigating), and you are not familiar with the process, please try to call in 5 minutes before the start of the session so that we can work out the connection logistics. Help on this will generally not be available once the presentation starts.     (1C7A)
    • people behind corporate firewalls may have difficulty accessing this. If that is the case, please download the [ slides above] (where applicable) and running them locally. The speaker(s) will prompt you to advance the slides during the talk.     (1C7B)
  • RSVP to appreciated, ... or simply just by adding yourself to the "Expected Attendee" list below (if you are a member of the team.)     (1C9)
  • Please note that this session may be recorded, and if so, the audio archive is expected to be made available as open content, along with the proceedings of the call to our community membership and the public at-large under our prevailing open IPR policy.     (1C11)

Attended:     (1C12)

Chat Transcript     (1D)

[07:19] Todd Schneider: Does the generated specification depend on the coding language?     (1D2)

[07:28] Todd Schneider: So a query is not treated as an object?     (1D3)

[07:30] Todd Schneider: The description of ontologysearch is not clear to me.     (1D4)

[07:31] Till Mossakowski: slide 13...     (1D5)

[07:34] Todd Schneider: What is the context of the APIs? Instances of ontohub (i.e., inter-ontohub)? End users? Both?     (1D6)

[07:36] Todd Schneider: Are 'accepts', 'registers with', 'informs' API commands?     (1D7)

[07:37] Todd Schneider: How does 'reliance' handle end-point or communication failures?     (1D8)

[07:41] Till Mossakowski: Todd: does the API cover authentification? Tim: yes, using an authorization token approach.     (1D9)

[07:42] Mike Bennett: This might be a naive question: can these API commands be executed from the command line? So that for instance a scheduling tool like Jenkins could invoke them?     (1D10)

[07:45] Till Mossakowski: Tim's answer: yes.     (1D11)

[07:46] Mike Bennett: Can you search on ontology imports i.e. get a result showing how ontologies import from one another?     (1D12)

[07:46] Till Mossakowski: Todd: Does the generated specification depend on the coding language? Tim: we use ruby, and the DSL will be based on ruby.     (1D13)

[07:51] Till Mossakowski: Tim: in the API, ontology-related queries use the IRI of the ontology, followed by a command. Other queries consist of just the command. In both cases, there may be additional parameters.     (1D14)

[07:51] Till Mossakowski: Todd: why constrain this prefixing approach just to ontologies?     (1D15)

[07:52] Till Mossakowski: Todd: the general approach to use a IRI as a prefix that gives the context to the subsequent command is interesting.     (1D16)

[07:53] Till Mossakowski: Todd: the prefix approach could be used for any resource (text files, image files, ...), not just ontologies.     (1D17)

[07:54] Todd Schneider: Can imports be considered as a 'type' of [ontology] mapping?     (1D18)

[07:55] Till Mossakowski: Mike: Can you search on ontology imports i.e. get a result showing how ontologies import from one another? Tim: this would be a textual representation of the ontology graph. Would be interesting to add this.     (1D19)

[07:57] Todd Schneider: Would it make sense to include a 'resource type' as part of the prefix?     (1D20)

[07:57] Till Mossakowski: Tim: until now, we compute all query answers on the fly, later on, caching will be needed.     (1D21)

[07:57] Till Mossakowski: Tim: imports are a kind of ontology mapping.     (1D22)

[07:58] Ravi Sharma: thanks for answering search during import on the fly.     (1D23)

[08:00] Mike Bennett: I have to drop off now     (1D24)

[08:01] Till Mossakowski: Todd: Would it make sense to include a 'resource type' as part of the prefix? Tim: yes, we should think about this, to prefix or postfix the IRI with the type, in order to ensure that the command is relevant in the given context.     (1D25)

[08:04] Todd Schneider: Thank you.     (1D26)

[08:04] Till Mossakowski: Agreement: in a few weeks, have will a follow-up meeting, with discussion of more details.     (1D27)

[08:04] Ravi Sharma: thanks     (1D28)

[08:05] Till Mossakowski: Next week: general OOR strategy discussion.     (1D29)

[08:05] Tim Reddehase: Thank you all for the suggestions and revealing questions.     (1D30)