From OntologPSMW

Jump to: navigation, search
[ ]


Ontology Summit 2014 session-14: Communique Draft Review - Thu 2014-04-17     (1)

  • Summit Theme: OntologySummit2014: "Big Data and Semantic Web Meet Applied Ontology"     (1A)

Reference:     (1D)

Abstract     (1M)

OntologySummit2014 Session-14: "OntologySummit2014_Communique: Finalization"     (1M1)

This is our 9th Ontology Summit, a joint initiative by Ontolog, NIST, NCOR, NCBO, IAOA & NCO_NITRD with the support of our co-sponsors.     (1M2)

Since the beginnings of the Semantic Web, ontologies have played key roles in the design and deployment of new semantic technologies. Yet over the years, the level of collaboration between the Semantic Web and Applied Ontology communities has been much less than expected. Within Big Data applications, ontologies appear to have had little impact.     (1M3)

This year's Ontology Summit is an opportunity for building bridges between the Semantic Web, Linked Data, Big Data, and Applied Ontology communities. On the one hand, the Semantic Web, Linked Data, and Big Data communities can bring a wide array of real problems (such as performance and scalability challenges and the variety problem in Big Data) and technologies (automated reasoning tools) that can make use of ontologies. On the other hand, the Applied Ontology community can bring a large body of common reusable content (ontologies) and ontological analysis techniques. Identifying and overcoming ontology engineering bottlenecks is critical for all communities.     (1M4)

Ontology Summit 2014 will pose and address the primary challenges in these areas of interaction among the different communities. The Summit activities will bring together insights and methods from these different communities, synthesize new insights, and disseminate knowledge across field boundaries.     (1M5)

At the Launch Event on 16 Jan 2014, the organizing team has provided an overview of the program, and how we will be framing the discourse - namely, to pursue that along four different content tracks that address different aspects of the issue at hand.     (1M6)

In today's session, our Lead Editors will be presenting an advanced draft of the Communique for review and discussion. We will attempt to finalize the document, so we can go into the OntologySummit2014_Symposium with the OntologySummit2014_Communique ready.     (1M7)

More details about this Ontology Summit is available at: OntologySummit2014 (homepage for this summit)     (1M8)

Agenda     (1N)

OntologySummit2014 - Community Discussion Session-14     (1N1)

  • Session Format: this is a virtual session conducted over an augmented conference call     (1N2)

Proceedings     (1O)

Please refer to the above     (1O1)

IM Chat Transcript captured during the session    (1O2)

see raw transcript here.     (1O2A)

(for better clarity, the version below is a re-organized and lightly edited chat-transcript.)     (1O2B)

Participants are welcome to make light edits to their own contributions as they see fit.     (1O2C)

-- begin in-session chat-transcript --     (1O2D)

Chat transcript from room: summit_20140417     (1O2E)

2014-04-17 GMT-08:00 [PDT]     (1O2F)

[8:59] Peter P. Yim: Welcome to the     (1O2G)

Ontology Summit 2014 session-14: Communique Draft Review - Thu 2014-04-17     (1O2H)

Summit Theme: Ontology Summit 2014: "Big Data and Semantic Web Meet Applied Ontology"     (1O2I)

Session Topic: Session Topic: OntologySummit2014_Communique Finalization     (1O2J)

Session Co-chairs & Communique Co-Lead Editors: Professor Michael Grüninger and Dr. Leo Obrst     (1O2K)

Logistics:     (1O2S)

  • (if you haven't already done so) please click on "settings" (top center) and morph from "anonymous" to your RealName; also please enable "Show timestamps" while there.     (1O2W)
  • Mute control (phone keypad): *7 to un-mute ... *6 to mute     (1O2X)

(i.e. even if it says it is "offline," you should still be able to connect to it.)     (1O2AA)

VoIP line, etc.) either your phone, skype-out or google-voice and call the US dial-in number: +1 (206) 402-0100     (1O2AC)

... when prompted enter Conference ID: 141184#     (1O2AD)

  • when posting in this Chat-room, kindly observe the following ...     (1O2AH)
    • whenever a name is used, please use the full WikiWord name format (every time you don't, some volunteer will have to make an edit afterwards)     (1O2AI1)
    • always provide context (like: "[ref. JaneDoe's slide#12], I think the point about context is great" ... rather than "that's great!"     (1O2AJ1)

as the latter would mean very little in the archives.)     (1O2AK)

the timestamp (in PST) of his/her post that you are responding to (e.g. "@JaneDoe [11:09] - I agree, but, ...")     (1O2AM)

    • use fully qualified url's (include http:// ) without symbols (like punctuations or parentheses, etc.) right before of after that URL     (1O2AN1)

Proceedings     (1O2AS)

[9:24] anonymous morphed into Jim Solderitsch     (1O2AT)

[9:34] anonymous morphed into Francesca Quattri     (1O2AU)

[9:35] anonymous morphed into Shahan Khatchadourian     (1O2AV)

[9:36] anonymous morphed into Dalia Varanka     (1O2AX)

[9:36] Peter P. Yim: == Michael Grüninger starts session on behalf of the co-chairs ... see prepared     (1O2AY)

[9:36] Michael Grüninger: Key Discussion Questions:     (1O2AAA)

1. General comments on content -- missing ideas, changes in emphasis, disagreements about content     (1O2AAB)

2. Editorial comments     (1O2AAC)

[9:38] anonymous morphed into Simon Spero     (1O2AAD)

[9:43] Amanda Vizedom: Reminder regarding making comments in the Google Doc: It helps the editors if     (1O2AAE)

comments are attributed to individuals, rather than anonymous, so that they can get clarification     (1O2AAF)

if needed. To make yourself non-anonymous in the Google Doc, go to the top right, to the left of     (1O2AAG)

the "Comments" button, you will see a square callout button. If you hover over this, it will say "join     (1O2AAH)

chat." Click this. It will open a chat window, which you can minimize. From this point, any comments     (1O2AAI)

you add will be attributed to you.     (1O2AAJ)

[9:45] ... Peter P. Yim: @MikeBennett ... I put you on mute (since your line was generating some noise),     (1O2AAK)

so please use *7 when you need to speak     (1O2AAL)

[9:46] Todd Schneider: In case I have to drop off, the description of 'semantic content' is section     (1O2AAM)

3, "Reuse of semantic content can be defined as the ability to include content from one source in     (1O2AAN)

another, or simply to be inspired by the content in a source., is too vague and does not constrain     (1O2AAO)

the interpretation 'semantic content'. What constitutes 'content'? Youtube videos? Also, there's a     (1O2AAP)

forward reference to 'semantic content'.     (1O2AAQ)

[9:48] Amanda Vizedom: Point I just raised re section 2: In addition to Expressivity and Scalability,     (1O2AAR)

we also heard multiple presentations call out the significance of Modularity. That might be worth     (1O2AAS)

calling out in its own subsection.     (1O2AAT)

[9:49] Todd Schneider: Why just equate 'semantic content' with ontology content?     (1O2AAU)

[9:51] Mike Bennett: @Todd [09:49] or "ontological content" - I think one possible angle was the     (1O2AAV)

existence of meaningful stuff in other than formally constituted FOL / OWL ontologies, I think.     (1O2AAW)

[9:54] Todd Schneider: Mike Bennett, That's fine. It just needs to be described. The opening paragraph     (1O2AAX)

of section 3 seems to be focused on 'ontology content'.     (1O2AAY)

[9:51] Ken Baclawski: I suggest that the use cases of all of the tracks be collected together in one     (1O2AAZ)

place on the wiki rather than being separated by tracks.     (1O2AAAA)

[9:52] Ken Baclawski: Then the communique should have a reference to this wiki page.     (1O2AAAB)

[10:16] Peter P. Yim: @ALL (especially track champions) ... re. Ken Baclawski [9:51] [9:52], Further to     (1O2AAAC)

Ken's suggestion on capturing use cases ... I've created the page where track champions can start     (1O2AAAD)

posting Use Cases, starting with those they have come across during their summit virtual panel     (1O2AAAE)

session - see:     (1O2AAAF)

[9:58] Simon Spero: AmandaVizdom mentioned the W3 convention of See [1].... / [1] url     (1O2AAAH)

[9:59] Amanda Vizedom: Thank you Simon, I hadn't identified that as a W3 convention, but that makes     (1O2AAAI)

sense as the source of the it. It seems to be the dominant citation mode in the SemWeb and Linked     (1O2AAAJ)

Data communities, unless my sample is very skewed.     (1O2AAAK)

[10:00] Leo Obrst: @AmandaVizdom, Simon Spero: yes, this is standard for many research paper formats.     (1O2AAAL)

[10:02] Amanda Vizedom: Documenting by prior comment, if it useful, I'm willing to go through and     (1O2AAAM)

make sure that anything cited in the communique is in the community library on zotero, and/or to     (1O2AAAN)

group them into citable subcollections, specific to particular points in the communique for which     (1O2AAAO)

the availability of multiple references via a single citation would be good.     (1O2AAAP)

[10:03] Amanda Vizedom: "Semantic Content" > "Semantic Resources"?     (1O2AAAQ)

[10:03] Amanda Vizedom: (for section 3)     (1O2AAAR)

[10:04] anonymous morphed into Lamar Henderson     (1O2AAAS)

[10:05] Mike Bennett: The sentence in Para 1 of Section 2 does seem to cover what we had in mind     (1O2AAAT)

for "semantic content" when speaking to its re-use in Section 3.     (1O2AAAU)

[10:08] Mike Bennett: @Amanda is what you are saying about "Semantic content" is that you interpret     (1O2AAAW)

the word "content" to refer to something at the instance level rather than the concepts in     (1O2AAAX)

ontologies?     (1O2AAAY)

[10:08] Todd Schneider: A resource may have 'content' which might be reused.     (1O2AAAZ)

[10:08] Andrea Westerinen: I think that "resource" is overloaded also.     (1O2AAAAA)

[10:09] Simon Spero: rdf:Resource     (1O2AAAAB)

[10:09] Simon Spero: That should cover every Thing!     (1O2AAAAC)

[10:09] Simon Spero: And "Thing!"     (1O2AAAAD)

[10:10] Todd Schneider: Andrea, 'Resource' can have a large space of interpretations, but use of it     (1O2AAAAE)

seems to meet the intent in the communique.     (1O2AAAAF)

[10:10] Amanda Vizedom: @MikeBennett [10:08], yes, that may be part of it. The information things to     (1O2AAAAG)

be enhanced or represented via ontologies, etc., rather than the ontologies, etc. themselves.     (1O2AAAAH)

[10:12] Mike Bennett: There is one thing missing in Section 3: See @Amanda note in the doc at hh:009     (1O2AAAAI)

[10:19] ... Peter P. Yim: @FrancescaQuattri ... I put you on mute (since your line was generating some     (1O2AAAAK)

noise), so please use *7 when you need to speak     (1O2AAAAL)

[10:20] ... Francesca Quattri: ok Peter, thanks     (1O2AAAAM)

[10:21] Mike Bennett: I think @Amanda sums up well the point I was driving at: (can't seem to     (1O2AAAAN)

copy-paste it)     (1O2AAAAO)

[10:27] Mike Bennett: Further to @MikeBennett [10:21] I have written a fresh comment against 3.1.1     (1O2AAAAP)

which I hope also captures this.     (1O2AAAAQ)

[10:22] ... Todd Schneider: Have to go. Cheers.     (1O2AAAAR)

[10:23] ... Peter P. Yim: @ChristophLange, @HensonGraves ... I put you on mute (since your line was     (1O2AAAAS)

generating some noise), so please use *7 when you need to speak     (1O2AAAAT)

[10:26] Terry Longstreth: Section 3 - should discuss Sharable content as a specific subsection.     (1O2AAAAU)

[10:28] Mike Bennett: It may also be worth calling out the distinction between re-use of ontologies     (1O2AAAAV)

intended as industry standards, and ontologies which were built for specific applications. That is,     (1O2AAAAW)

design for re-use versus opportunistic re-use.     (1O2AAAAX)

[10:35] Mike Bennett: I wonder if 3.1.4 and 3.1.5 are more about actually re-using as distinct     (1O2AAAAY)

from "why isn't there?"     (1O2AAAAZ)

[10:30] Ken Baclawski: Sections 1, 2 and 4 all end with questions, but Section 3 ends with a     (1O2AAAAAA)

subsection on advice. It might be better to put all recommendations in Section 5.     (1O2AAAAAB)

[10:32] ... Amanda Vizedom: Must leave early; apologies. Thanks, all.     (1O2AAAAAC)

[10:38] Andrea Westerinen: [action] Andrea will write up a new sub-section for Section 3 -     (1O2AAAAAD)

transitioning from problems to shareability and reuse, and then allowing a cleaner jump into best     (1O2AAAAAE)

practices. It will be emailed to the ontolog-summit mail list.     (1O2AAAAAF)

[10:46] Terry Longstreth: A question for Section 3: Are there examples of ontology usage that     (1O2AAAAAG)

illustrate the distinction between reuse and sharing of semantic content?     (1O2AAAAAH)

[10:50] Andrea Westerinen: @TerryLongstreth [10:46] Track A started with a bunch of questions.     (1O2AAAAAI)

Perhaps we should record these as well?     (1O2AAAAAJ)

[10:53] Mike Bennett: My response to Christoph's question about support, was that "design" was part     (1O2AAAAAK)

of the intended thing here. Or developing.     (1O2AAAAAL)

[10:55] Mike Bennett: Hackathons: The Re-use hackathon illustrates some of the points made elsewhere     (1O2AAAAAM)

in the document.     (1O2AAAAAN)

[10:55] ... Christoph Lange: Sorry, I had dropped off the call for 2-3 minutes, back now     (1O2AAAAAO)

[10:57] Peter P. Yim: == 4. Summary/wrap-up/announcements     (1O2AAAAAP)

[10:58] Shahan Khatchadourian: Thank you all. Very interesting discussion.     (1O2AAAAAQ)

[10:58] Francesca Quattri: all right. bye thanks.     (1O2AAAAAR)

[11:00] Peter P. Yim: [action] Michael Grüninger & Leo Obrst will make a post to the [ontology-summit]     (1O2AAAAAS)

list (after incorporating today's input) ... and will let people know that the deadline for comments     (1O2AAAAAT)

will be next Thursday Apr-24     (1O2AAAAAU)

[11:00] Peter P. Yim: @ALL: join us next Thursday, when we will, hopefully, be tackling "Final Symposium     (1O2AAAAAV)

preparation and logistics" - ref. developing details at:     (1O2AAAAAW)

[11:00] Peter P. Yim: @ALL: as announced earlier, by our Symposium co-chairs, Dr. Ram Sriram and     (1O2AAAAAZ)

Professor Tim Finin, our Apr 28~29 Symposium (at NSF in Greater Washington DC) registration in a few days.     (1O2AAAAAAA)

Please register yourself now, if you haven't already! - see:     (1O2AAAAAAB)

[11:00] Peter P. Yim: Michael Grüninger & Leo Obrst: Very productive session ... thank you ALL!     (1O2AAAAAAD)

[11:01] Peter P. Yim: -- session ended: 11:56 am PDT --     (1O2AAAAAAE)

-- end of in-session chat-transcript --     (1O2AAAAAAF)

Additional Resources     (1P)

For the record ...     (1P7)

How To Join (while the session is in progress)     (1Q)

  • Dial-in:     (1Q4D)
    • Phone (US): +1 (206) 402-0100 ... when prompted enter Conference ID: 141184# ... (long distance cost may apply)     (1Q4D1)
    • Skype: joinconference (i.e. make a skype call to the contact with skypeID="joinconference") ... (generally free-of-charge, when connecting from your computer ... ref.)     (1Q4D2)
      • when prompted enter Conference ID: 141184#     (1Q4D2A)
      • Unfamiliar with how to do this on Skype? ...     (1Q4D2B)
        • Add the contact "joinconference" to your skype contact list first. To participate in the teleconference, make a skype call to "joinconference", then open the dial pad (see platform-specific instructions below) and enter the Conference ID: 141184# when prompted.     (1Q4D2B1)
        • you may connect to (the skypeID) "joinconference" whether or not it indicates that it is online (i.e. even if it says it is "offline," you should still be able to connect to it.)     (1Q4D2B2)
      • Can't find Skype Dial pad? ...     (1Q4D2C)
        • for Windows Skype users: Can't find Skype Dial pad? ... it's under the "Call" dropdown menu as "Show Dial pad"     (1Q4D2C1)
        • for Linux Skype users: please note that the dial-pad is only available on v4.1 (or later; or on the earlier Skype versions 2.x,) if the dialpad button is not shown in the call window you need to press the "d" hotkey to enable it. ... (ref.)     (1Q4D2C2)
  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at: ... view-only password: "ontolog"     (1Q4E)
    • 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.     (1Q4E1)
    • 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.     (1Q4E2)
    • 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").     (1Q4F1)
    • 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.     (1Q4F2)
    • thanks to the folks, one can now use a jabber/xmpp client (e.g. Digsby or Adium) to join this chatroom. Just add the room as a buddy - (in our case here) ... Handy for mobile devices!     (1Q4F3)
  • Discussions and Q & A:     (1Q4G)
    • Nominally, when a presentation is in progress, the moderator will mute everyone, except for the speaker.     (1Q4G1)
    • 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.)     (1Q4G2)
    • 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.)     (1Q4G3)
    • 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.)     (1Q4G4)
  • RSVP to with your affiliation, ... or simply just by adding yourself to the "Expected Attendees" list below (if you are already a member of the community.)     (1Q4I)
  • 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.     (1Q4K)

Attendees     (1R)

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