From OntologPSMW

Jump to: navigation, search
[ ]


SemanticWiki mini-series Session-5 - Thu 12-Feb-2009     (1)

  • Mini-series Title: Semantic Wikis: The Wiki Way to the Semantic Web     (1A)
  • Session-5 Topic: Semantic Wiki Applications & Use Cases (2): horizontal applications     (1B)
  • Session Chair: Dr. LiDing (RPI) & Dr. JieBao (RPI)     (1C)
  • Panel Presentations: [ slides & recording-segment ]     (1E)
    • (0) Dr. Li Ding & Dr. JieBao - opening - [ slides ] - [ 00:00~03:34 ]     (1E1)
    • (T1) Mr. YaronKoren - "External Data in Semantic MediaWiki" - [ slides ] - [ 03:36~19:31 ]     (1E2)
    • (T2) Mr. PhilippZaltenbach - "Expansion of MediaWiki search: The enhanced retrieval extension" - [ slides ] - [ 19:31~29:44 ]     (1E3)
    • (T3) Professor PeterDolog - "Tag Based Recommendations in KIWI" - [ slides ] - [ 29:45~42:40 ]     (1E4)
    • (T4) Mr. MikeAxelrod - "Shepherding the zoo, a lighthearted chat about fostering collaboration and wiki culture in a large corporate environment" - [ slides ] - [ 42:40~52:42 ]     (1E5)
    • (T5) Mr. MarcFeickert - "A Semantic Wiki for Your Grandmother" - [ slides ] - [ 52:42~63:14 ]     (1E6)
    • (T6) Mr. JoelNatividad - "Visualizing Semantic Inline Query Results with SRF-Ploticus" - [ slides ] - [ 63:14~79:14 ]     (1E7)
  • Lightning Talks: - [ Please note that: in order for the community to be exposed to the full range of technologies, an IPR policy waiver is applicable to this segment of the program. Therefore, technologies presented in these "Lightning Talks" do not necessarily fall into the "free and open" technology category. The presentation materials (slides, recording of the talks), however, are still licensed by all these speakers as open content, and our IPR Policy still applies in that regard. =ppy ]     (1F)
    • These are 1-slide, 3-min (max) talks open to anyone who has something relevant to present. To get a slot please email your talk title, a one-paragraph abstract, and your slide to the session co-chair and to <>. Titles and Slides has to be received by end-of-day Wed 11-Feb-2009 to be scheduled in.     (1F1)
    • (L1) Ms. JenniferVendetti - "The Stanford Protege Wiki" - [ slide ] - [ 79:14~82:20 ]     (1F2)
    • (L2) Mr. EnricoDaga - "ODP & Evaluation Wikiflow" - [ slide ] - [ 82:20~94:17 ]     (1F3)

  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at:     (1H5)
    • view-only password: "ontolog"     (1H5A)
    • 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.     (1H5B)
    • people behind corporate firewalls may have difficulty accessing this. If that is the case, please download the slides above and running them locally. The speaker(s) will prompt you to advance the slides during the talk.     (1H5C)
    • when there are a huge number of participants, the user experience may be better if you just run the slides from your desktop and advance the slides on the speaker's prompt.     (1H5D)
    • speaker(s) are encouraged to log into this shared-screen service, just so you can see what screen others are seeing (this will help avoid missing cues for slide advances.)     (1H5E)
  • Discussions and Q & A:     (1H6)
    • (Unless the conference host has already muted everyone) Please mute your phone, by pressing "*2" on your phone keypad, when a presentation is in progress. To un-mute, press "*3"     (1H6A)
    • You can type in your questions or comments through the browser based chat session by:     (1H6B)
      • instructions: once you got access to the page, click on the "settings" button, and identify yourself (by modifying the Name field). 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.     (1H6C1)
    • (when everyone is muted) If you want to speak or have questions or remarks to make, please "raise your hand (virtually)" by click on the "hand button" (lower right) on the chat session page. You may speak when acknowledged by the speaker or the session moderator (again, press "*3" on your phone to unmute). 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 "*2" on your phone to mute yourself after you are done speaking.)     (1H6D)
    • 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!     (1H6E)
  • Please note that this session will be recorded, and the audio archive is expected to be made available as open content to our community membership and the public at-large under our prevailing open IPR policy.     (1H11)

Attendees     (1J)

SemanticWiki mini-series Background     (1K)

The Semantic Wiki mini-series a 6-month mini-series comprising Talks, Panel Discussions and Online Discourse. The series is co-organized by FZI Karlsruhe, Mayo Clinic, Ontolog, RPI Tetherless World Constellation and Salzburg Research, Austria. This represents a collaborative effort between members from academia, research, software engineering, semantic web and ontology communities. The 6-month mini-series intends to bring together developers, administrators and users of semantic wikis, and provide a platform where they can conveniently share ideas and insights. Through a series of (mainly virtual) talks, panel discussions, online discourse and even face-to-face meetings, participants will survey the state-of-the-art in semantic wiki technology and get exposure to exemplary use cases and applications. Together, they will study trends, challenges and the outlook for semantic wikis, and explore opportunities for collaboration in the very promising technology, approach or philosophy which people has labeled "semantic wiki."     (1K1)

This series of virtual events will dovetail into the face-to-face workshop: "Social Semantic Web: Where Web 2.0 Meets Web 3.0" at the AAAI Spring Symposium (March 23-25, 2009 at Stanford, California, USA - see: ).     (1K2)

See: our SemanticWiki mini-series homepage and the developing program for the rest of the series.     (1K3)

Agenda & Proceedings     (1L)

  • Session Format: this is a virtual session conducted over an augmented conference call.     (1L1)
  • Agenda:     (1L2)
    • 1. Opening by the Session Chair     (1L2A)
    • 2. we'll go around with a self-introduction of participants - we will skip this if we have more than 20 participants (in which case, it will be best if members try to update their namesake pages on this wiki prior to the call so that everyone can get to know who's who more easily.) (All - total: ~15 minutes)     (1L2B)
    • 3. Panelists' Presentations - (10 min. each)     (1L2C)
    • 4. Lightning Talks - (3 min. max. each)     (1L2D)
    • 5. Q&A and Open Discussion - ALL (~15 min.)     (1L2E)
    • 6. Summary / Announcement / Conclusion - session chair     (1L2F)

Session Abstract: Semantic Wiki Applications & Use Cases (2): horizontal applications     (1M)

Session Abstract: by Li Ding & JieBao - [ slides ]     (1M1)

We will be focusing general purposed applications and use cases that can be applied across many domains. Our presenters at this session will take us through applications such as: Data oriented computing: privacy, protection, distributed data, inference (e.g., T1, T2); Supporting community and collaboration (e.g., T3, T4, T5, L1)��; Usability: visualization and user interaction (e.g., T6);�� and Methodology: design pattern and quality control (e.g. L2).     (1M2)

  • T1: YaronKoren - External Data in Semantic MediaWiki - [ slides ]     (1M3)
    • Abstract: A demonstration of how external data can be imported painlessly into an SMW wiki using the External Data extension.     (1M3A)
  • T2: PhilippZaltenbach - Expansion of MediaWiki search: The enhanced retrieval extension - [ slides ]     (1M4)
    • Abstract: The search mechanism of MW was often considered a weak spot of the MW engine. Meanwhile popular installations such as Wikipedia include a more sophisticated search engine - called MWSearch - based on Lucene. We will introduce our enhanced retrieval extension that is built on top of MWsearch. The major plus of this extension is the increase of recall by incorporating related terms and concepts, such as synonyms, broader and narrower terms.     (1M4A)
  • T3: PeterDolog - Tag Based Recommendations in KIWI - [ slides ]     (1M5)
    • Abstract: In this talk I will talk about how we utilized the flexible SOA architecture and widgets to extend the KIWI semantic wiki with tag based recommendations.     (1M5A)
  • T4: MikeAxelrod - Sheparding the zoo, a lighthearted chat about fostering collaboration and wiki culture in a large corporate environment. - [ slides ]     (1M6)
    • Abstract: This brief presentation will touch on a few of the challenges faced in developing a semantic wiki in a large organization. The focus will be on introducing semantic wiki concepts to people representing a wide range of concerns and technical abilities, and how we might bring them together in semantic wiki-space.     (1M6A)
  • T5: MarcFeickert - A Semantic Wiki for Your Grandmother - [ slides ]     (1M7)
    • Abstract: FamilySearch has produced a wiki to help the public a) learn how to perform genealogical research to find their ancestors and b) collaborate with genealogy experts of different areas to aid in research. We have decided to shift our wiki to a semantic architecture in order to take advantage of the rich tagging that will allow better browsing and searching of the wiki from multiple integrated tools at The challenge is to make such a wiki usable by our main focus group, which consists primarily of retired senior citizens with little to no knowledge of how to use a computer application. The SMW+ package offers the WYSIWYG features and integration of wiki tools that will allow us to accomplish our goal. In this presentation, I will talk more about the purpose of the wiki, our target audience and their needs, the design of our ontology, our use of Semantic Forms and other tools for easing the editing process. I will additionally talk about some specific challenges that we face, namely: incompatibility of SMW+ and current MediaWiki versions, how to convert existing pages to an SMW format, and how best to allow wiki contributors to effectively contribute to the ontology.     (1M7A)
  • T6: JoelNatividad - Visualizing Semantic Inline Query Results with SRF-Ploticus - [ slides ]     (1M8)
    • Abstract: Apart from SRF-GooglePie and SRF-GoogleBar, which themselves had data security limitations - there was no generic charting/plotting package to visualize Semantic Inline Query Results in Semantic MediaWiki. This talk is a quick overview and introduction of the new result printer which seeks to fill this gap - SRF-Ploticus. Leveraging Ploticus' flexibility, we will show how SRF-Ploticus can visualize inline query results - from simple pie and bar charts, to more specialized "semantic-friendly" formats like frequency distributions, scatter plots and heatmaps.     (1M8A)

Lightning Talks     (1M9)

Q & A and Open Discussion     (1N)

Questions and Discussion captured from the chat session     (1N2)

Transcript: (lightly edited for clarity only)     (1N2A)

Guoqian Jiang: @Yaron, for the input format, do you consider the RDF output from SMW itself as one of inputs for your extension?     (1N2B)

Michael Dale: and it gets really useful when you use it in templates : )     (1N2C)

EricRLindahl: This seems like a way for a single-step rewrite. What about rewrites in general? Using other ground terms within     (1N2D)

the page vs. URI resolution rewrite algorithms.     (1N2E)

EricRLindahl: (also per Jiang's SPARQL type question)     (1N2F)

Enrico Daga: data as wiki-page/csv... can be used as alternaive store for other extensions' data, flexible, I think...     (1N2G)

Mike Axelrod: I think there will be uses for this approach...     (1N2H)

Mike Bennett: What about Genericode - this is a way of maintaining selection lists of things like ISO country codes.     (1N2I)

Is that something that is supported by these mechanisms?     (1N2J)

Kei Cheung: nice presentation, Yaron. I just installed it for my wikineuron project. will let you know how it goes ...     (1N2K)

Peter Dolog: well, I guess quick integration of data from legacy web applications in enterprise environment could be     (1N2L)

an application for the external page data     (1N2M)

Yaron Koren: Guoqian - no, I haven't really considered supporting RDF - it's too complicated...     (1N2N)

Peter Dolog: Yaron, I might be interested in more details of your extensions     (1N2O)

Peter Dolog: we need something similar in KIWI, in one use case, so we might learn something from you     (1N2P)

Yaron Koren: Well, you can look at the source code, for one thing - it's really not that long.     (1N2R)

Yaron Koren: (Assuming you're talking about External Data.)     (1N2T)

Peter Dolog: well, external to the wiki     (1N2U)

Peter Dolog: but still intranet based in enterprise terminology     (1N2W)

Marc Feickert: Phillip, can you maintain your own list of synonyms with this extension?     (1N2X)

Guoqian Jiang: Yaron, RDF output has more explicit semantics. in some way, you may not need interpret them by yourself.     (1N2Y)

Yaron Koren: Well, if nothing else, I haven't seen a use case for supporting RDF yet.     (1N2Z)

Michael Dale: Yaron Koren: probably would be good to support Xpath via some xml lib integration     (1N2AA)

Michael Dale: in case you need fine grain access to xml attributes and what not     (1N2AB)

Michael Dale: for example the people.xml from gov track     (1N2AD)

Yaron Koren: Maybe... it would only really be necessary if the XML had two different tags or attributes of the same name.     (1N2AE)

Marc Feickert: if you are not in charge of writing the XML, it could     (1N2AF)

Michael Dale: it could also be a shorter expression / less logic to get at a given piece of data.     (1N2AG)

Yaron Koren: Sure. I'm just afraid XPath support would add a lot of complexity.     (1N2AH)

Marc Feickert: for you or for the user?     (1N2AI)

Yaron Koren: Marc - definitely for the programmer, probably for the user/admin as well.     (1N2AJ)

Marc Feickert: complexity for advanced users is sometimes okay, but I understand the reluctance if it adds too much effort on your end as well     (1N2AK)

Guoqian Jiang: Philipp, does autocompletion in searchbox support the query expansion e.g. synonym?     (1N2AL)

Philipp Zaltenbach: the autocomplete shows only tile of wiki pages. wiki pages are separated in regular article pages (instances),     (1N2AM)

category pages, property pages, template pages     (1N2AN)

Marc Feickert: and how can we expand the stemming dictionaries for multiple langauges?     (1N2AO)

Ravi Sharma: Philipp, How do you connect vocabularies or define related terms, are these a reasoning or inference engine sitting     (1N2AP)

behind the Tags or serach terms?     (1N2AQ)

Philipp Zaltenbach: no we are not using external vocabularies at the moment for the query expansion. the only external vocabulary     (1N2AR)

(for getting synonyms) is wordnet. but that is done by the MWsearch extension.     (1N2AS)

Marc Feickert: so by expanding the wordnet project, it would trickle down to expand this?     (1N2AT)

Marc Feickert: or would there be a way to import or tranform dictionaries?     (1N2AU)

Marc Feickert: actually, I need to talk to you in depth at another time. I'll email you to set something up     (1N2AV)

Guoqian Jiang: query expansion for an external vocabulary would be very useful     (1N2AW)

Marc Feickert: we intend to cover 20-30 languages     (1N2AY)

Philipp Zaltenbach: @marc: you can of course use different languages for annotating synoyms in your wiki. at the moment we     (1N2AZ)

simply do not care what a users specifies in the wiki as synonym. so you are free to use different languages.     (1N2AAA)

Philipp Zaltenbach: at mark, sure feel free to mail me     (1N2AAB)

Ravi Sharma: Peter Dolog, How is a single (?) Triplestoreservice related or delivered or choreographed with SOA Services in     (1N2AAC)

the upper architecture layer such as COntentItemService?     (1N2AAD)

Philipp Zaltenbach: the connecting of external vocabularies (even in different languages) is an issue we have on our radar,     (1N2AAE)

but as i said, we have not investigated further on how to realize that     (1N2AAF)

Guoqian Jiang: how do you represent the internal vocabularies in Halo?     (1N2AAG)

Guoqian Jiang: for external vocabulary, we mapped them to wiki pages     (1N2AAH)

Philipp Zaltenbach: internally we use the special relations such as "also known as" or "broader term". these pre-defined     (1N2AAI)

properties are actually mapped to SKOS properties.     (1N2AAJ)

Guoqian Jiang: I mean we may use the same mechanism for external voca as long as we observe the rule     (1N2AAK)

Marc Feickert: is it possible to use those properties to define synonyms for a single page? Like asking the contributor     (1N2AAL)

to input them into a semantic form?     (1N2AAM)

Philipp Zaltenbach: we didn't want to force the not-technical user to use properties such as "skos:altLabel" or "skosrefLabel".     (1N2AAN)

but when you export your ontology these skos properties will be serialized too     (1N2AAO)

Marc Feickert: And here I think also of text in the page that may need its own synonym separate of the page title     (1N2AAP)

Marc Feickert: You've hit on my professional area, Philipp     (1N2AAQ)

Guoqian Jiang: Is this query expansion a separate extension?     (1N2AAR)

Peter Dolog: ok, give me a second to recollect the thought and read your questions     (1N2AAS)

Philipp Zaltenbach: the synonyms actually relate to the source article where you put in your semantic annotations such as "also known as:blabla"     (1N2AAT)

Philipp Zaltenbach: marc, i have to leave soon, but i am looking forward to hear from you via email!     (1N2AAU)

Marc Feickert: I have asked Daniel Hansch for your contact info.     (1N2AAV)

Philipp Zaltenbach: the query expansion is just a "feature" of the enhanced retrieval extension which i highlighted     (1N2AAW)

Guoqian Jiang: Philipp, you mean enhanced retrieval extension could be separated from Halo?     (1N2AAX)

Marc Feickert: aber alles ist ausgezeichnet!     (1N2AAY)

Philipp Zaltenbach: yes, it will be available as a separate extension which you can plug in into an SMW (without having to use HALO extension)     (1N2AAZ)

Philipp Zaltenbach: ok, i have to leave guys, cu!     (1N2AAAB)

Peter Dolog: Ravi Sharma: any store has to be connected to the entitymanager, so there is always a bit of work to connect it     (1N2AAAE)

Peter Dolog: content item is an entity in the data model     (1N2AAAG)

Peter Dolog: accessible through hibernate like interface     (1N2AAAH)

Peter Dolog: that you can actually query it directly     (1N2AAAI)

Yaron Koren: Peter: are these tags editable by everyone, or are they user-specific?     (1N2AAAJ)

Peter Dolog: Yaron, which things?     (1N2AAAK)

Yaron Koren: The tags you were talking about.     (1N2AAAL)

Peter Dolog: Whether any person can add tags? Yes     (1N2AAAM)

Peter Dolog: Any user can tag     (1N2AAAN)

Yaron Koren: No, the question is, if one person adds a tag, can another person edit/remove it.     (1N2AAAO)

Peter Dolog: it depends how you set the rights control     (1N2AAAP)

Peter Dolog: in principle yes, if you want     (1N2AAAQ)

Peter Dolog: but you can restrict it     (1N2AAAR)

Peter Dolog: but if you look at the screenshot, I did not have any "-" symbol for me     (1N2AAAT)

Peter Dolog: so it was restricted     (1N2AAAU)

Peter Dolog: it was simple to make recommendations because the core datamodel is basically a triple (Content Item x Tags x Users)     (1N2AAAV)

Peter Dolog: similarly, access control is then simple     (1N2AAAW)

Peter Dolog: and then you can put a type system over it through semantic web annotations     (1N2AAAX)

Guoqian Jiang: we did meet many scenarios you described in your zoo     (1N2AAAAA)

Yaron Koren: Peter - is this (tagging) the semantic content of KIWI, or is it in addition to the semantic content?     (1N2AAAAB)

Peter Dolog: it is a bit tricky     (1N2AAAAC)

Peter Dolog: actually tag is a special kind of content item     (1N2AAAAD)

Peter Dolog: i.e. kind of a resource     (1N2AAAAE)

Peter Dolog: which link to another "media/text" based content item     (1N2AAAAF)

Peter Dolog: and it is cartesian     (1N2AAAAG)

Peter Dolog: i.e you can see the link bidirectionally     (1N2AAAAH)

Peter Dolog: I do not know if it answered your question     (1N2AAAAI)

Yaron Koren: Okay, I think I understand...     (1N2AAAAJ)

Yaron Koren: Basially, unlike SMW, KIWI doesn't store semantic data on the page - it's all separate "resources".     (1N2AAAAK)

Peter Dolog: also concepts in an ontology are currently separate content items     (1N2AAAAM)

Peter Dolog: and you can use them as labels for tags     (1N2AAAAN)

Peter Dolog: also user is a content item     (1N2AAAAP)

Peter Dolog: so content item is a base entity     (1N2AAAAQ)

Peter Dolog: and then you type it     (1N2AAAAR)

Peter Dolog: and link instances around     (1N2AAAAS)

Peter Dolog: actually to clarify     (1N2AAAAU)

Peter Dolog: we distinguish between rdf/owl annotations and tags     (1N2AAAAV)

Peter Dolog: and we can link them     (1N2AAAAX)

Marc Feickert: I'm out of breath...     (1N2AAAAY)

Yaron Koren: Peter: people type in RDF directly?     (1N2AAAAAA)

Peter Dolog: well, they can, if they have an editor in their configuration     (1N2AAAAAB)

Peter Dolog: but that is not what usually happen to normal user     (1N2AAAAAC)

Peter Dolog: this is why we actually introduced tagging in the KIWI project     (1N2AAAAAD)

Peter Dolog: I cannot imagine a project manager - one of the use cases we are targeting     (1N2AAAAAE)

Peter Dolog: who would write RDF     (1N2AAAAAF)

Peter Dolog: some people in the project are working on some simple editor for kind of rdf annotations     (1N2AAAAAH)

Peter Dolog: they are actually text analysis people     (1N2AAAAAI)

Peter Dolog: and are currently making some drag and drop highliting plugin     (1N2AAAAAJ)

Peter Dolog: to get those derived in writing directly     (1N2AAAAAK)

Peter Dolog: but user in fact does not see that it is RDF     (1N2AAAAAL)

Peter Dolog: but we would like to have a bit more than just tags     (1N2AAAAAM)

Peter Dolog: so we (meaning the whole project) are thinking how to support that     (1N2AAAAAN)

Yaron Koren: Right, interface is important.     (1N2AAAAAO)

Peter Dolog: But tagging seems to be acceptable     (1N2AAAAAP)

Peter Dolog: simple tagging is actually not semantic     (1N2AAAAAQ)

Peter Dolog: so one way to extend it is to somehow support editing of links between ontologies and tags     (1N2AAAAAR)

Marc Feickert: can Poticus work for a non-semantic wiki? We'd love to play with it now     (1N2AAAAAS)

Peter Dolog: Yaron, both architecture and some details on the whole KIWI data model is described     (1N2AAAAAT)

Peter Dolog: in case, you'd like to know more     (1N2AAAAAV)

Yaron Koren: Ploticus=awesome.     (1N2AAAAAX)

JoelNatividad: Thanks Yaron     (1N2AAAAAY)

Mike Bennett: @Joel: thanks for your kind mention of the EDM Council Semantics Repository     (1N2AAAAAZ)

JoelNatividad: It would not have been possible without all the help and feedback     (1N2AAAAAAA)

JoelNatividad: you gave during the dev process     (1N2AAAAAAB)

JoelNatividad: Hi Mike!     (1N2AAAAAAC)

Yaron Koren: Hey, I'm glad I did.     (1N2AAAAAAD)

JoelNatividad: So glad to see you here     (1N2AAAAAAE)

Mike Bennett: Hi Joel - good to see you also, the Ploticus stuff looks really exciting.     (1N2AAAAAAF)

Marc Feickert: I almost wet my pants     (1N2AAAAAAG)

Yaron Koren: I'm looking forward to the time-series stuff - animated graphs? Damn.     (1N2AAAAAAI)

Yaron Koren: Jennifer: that's too bad. That's the first I've heard of people not being able to find pages after they create them.     (1N2AAAAAAJ)

Yaron Koren: (Although maybe people just don't tell me about it.)     (1N2AAAAAAK)

Yaron Koren: ...created using forms, that is.     (1N2AAAAAAL)

Ravi Sharma: Joel: Excellent semantic plugin through Queries, it does have general value such as in BI OLAP Reports,     (1N2AAAAAAM)

my own opinion, you can probably offer to Excel or other databses this as a add-on similar to what     (1N2AAAAAAN)

financial analysts use as excel @risk, but very useful and is this likelty to be open source?     (1N2AAAAAAO)

JoelNatividad: @Ravi: it is open source and the good thing about CSV is that it opens in Excel without a problem     (1N2AAAAAAP)

JoelNatividad: @Ravi: perhaps, we can create Excel Bundles too in addition to the PDF Bundle     (1N2AAAAAAQ)

Jennifer Vendetti: Yaron: sorry - I was perhaps speaking too fast during my 3 minute talk. What I meant to say     (1N2AAAAAAR)

is that sometimes users enter something slightly incorrect in a form and then their plug-in     (1N2AAAAAAS)

is listed under an area that they didn't anticipate. The fix would be to correct the category     (1N2AAAAAAT)

or property that they entered, but they don't always seem to know what they have done wrong     (1N2AAAAAAU)

because they are unaware of the strict ontological structure in place for the plug-ins library.     (1N2AAAAAAV)

Yaron Koren: Oh, okay, that makes sense.     (1N2AAAAAAW)

Jennifer Vendetti: ... even though we have documented this.     (1N2AAAAAAX)

Yaron Koren: Jennifer: I think, having seen your forms to some extent, that there might be ways to make them a little more usable.     (1N2AAAAAAY)

Yaron Koren: Like, for instance, having a dropdown for the plugin name using the "values from category" parameter.     (1N2AAAAAAZ)

Jennifer Vendetti: Yaron: Great - I am very happy for your suggestions. I will look at this values from category parameter.     (1N2AAAAAAAA)

Sounds like it would be great for solving data entry problems.     (1N2AAAAAAAB)

Yaron Koren: You can also have the title of the new page be automatically-generated, if the name is meant to just fit a format based on the page's data.     (1N2AAAAAAAC)

Yaron Koren: These are both relatively new features.     (1N2AAAAAAAD)

Jennifer Vendetti: Oh - I didn't know about the auto-generation of new page names. Sounds like we should use this as well. Thank you for this suggestion!!     (1N2AAAAAAAE)

Ravi Sharma: to speakers: is there a uniform tagging and query standard emerging other than GRRDLE such as agreed Meta-tags etc?     (1N2AAAAAAAG)

Duane Searsmith: thanks!     (1N2AAAAAAAI)

Marc Feickert: thanks for all the fish     (1N2AAAAAAAJ)

Mike Bennett: Thanks all, great talks     (1N2AAAAAAAM)

Peter P. Yim: Thank you all for participating ... another great session!     (1N2AAAAAAAO)

JoelNatividad: thanks to ontolog for hosting the session!     (1N2AAAAAAAP)

Peter P. Yim: thanks to Jie Bao and Li Ding for putting this together ... and to all our wonderful speakers for sharing their insights with us!     (1N2AAAAAAAQ)

Peter P. Yim: bye! ... full proceedings, along with audio archives will be out shortly!     (1N2AAAAAAAR)

  • ... More Questions?     (1N2AAAAAAAS)
    • For those who have further questions or remarks on the topics, please email the authors directly, or, better still, post them to the [swikig] mailing list (ref. details here) so that everyone in the community can benefit from the discourse.     (1N2AAAAAAAS1)

Audio Recording of this Session     (1O)

  • suggestions:     (1O5)
    • its best that you listen to the session while having the respective presentations opened in front of you. You'll be prompted to advance slides by the speaker.     (1O5A)
    • Take a look, also, at the rich body of knowledge that this community has built together, over the years, by going through the archives of noteworthy past Ontolog events. (References on how to subscribe to our podcast can also be found there.)     (1O5B)

For the records ...     (1O6)

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

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