Deniz Aydemir: Difference between revisions
Tag: Undo |
|||
| Line 1: | Line 1: | ||
{{Participant | {{Participant | ||
|Table Assignment=Table 5}} | |||
|Table Assignment=Table 5 | |||
}} | |||
{{Workshop Submission | {{Workshop Submission | ||
|Interest=It is becoming increasingly important to create a standard for how knowledge graphs and ontologies can be made interoperable, and I propose solving this with what I am calling a "Discourse Protocol". More and more users are thinking about how best to structure their own research and writing using personal ontologies, and tools like Roam, Logseq, Obsidian, Notion, and now Tana (among others) are continuing to add more ways for users to create semantic relationships within their notes. We want a world where my knowledge graph can reference your knowledge graph, but I shouldn't have to understand your whole personal ontology in order to reference content you've published. We need to create some sort of standard protocol for knowledge content in order to make it possible for different users using different tools and their own personal ontologies to reference each other's work in a sensible way. There are existing ontologies that attempt to be globally applicable, but as a community we should be forming a well-supported and future-proof standard "Discourse Protocol" that both creates a general structure through which users can interface their personal knowledge graphs, and also creates a clear way for all these disparate note-taking applications to publish interoperable content. | |Interest=It is becoming increasingly important to create a standard for how knowledge graphs and ontologies can be made interoperable, and I propose solving this with what I am calling a "Discourse Protocol". More and more users are thinking about how best to structure their own research and writing using personal ontologies, and tools like Roam, Logseq, Obsidian, Notion, and now Tana (among others) are continuing to add more ways for users to create semantic relationships within their notes. We want a world where my knowledge graph can reference your knowledge graph, but I shouldn't have to understand your whole personal ontology in order to reference content you've published. We need to create some sort of standard protocol for knowledge content in order to make it possible for different users using different tools and their own personal ontologies to reference each other's work in a sensible way. There are existing ontologies that attempt to be globally applicable, but as a community we should be forming a well-supported and future-proof standard "Discourse Protocol" that both creates a general structure through which users can interface their personal knowledge graphs, and also creates a clear way for all these disparate note-taking applications to publish interoperable content. | ||
Latest revision as of 21:20, 26 October 2022
| Deniz Aydemir | |
|---|---|
| Timezone |
|
| Group(s) | Table 5, Computable Graphs |
| Table Assignment | Table 5
|
Discord
Page Schemas#Creating a new Schema Page schemas is mostly a handy way to generate boilerplate templates and link them to semantic properties. A Form (using Page Forms is something that is an interface for filling in values for a template.
For an example of how this shakes out, see Category:Participant Template:Participant Form:Participant
- go to a `Category:CategoryName` page, creating it if it doesn't already exist.
- Click "Create schema" in top right
- If you want a form, check the "Form" box. it is possible to make a schema without a form. The schema just defines what pages will be generated, and the generated pages can be further edited afterwards (note that this might make them inconsistent with the schema)
- Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.
- Add fields! Each field can have a corresponding form input (with a type, eg. a textbox, token input, date selector, etc.) and a semantic property.
- Once you're finished, save the schema
- Click "Generate pages" on the category page. Typically you want to uncheck any pages that are already bluelinks so you don't overwrite them. You might have to do the 'generate pages' step a few times, and it can take a few minutes, bc it's pretty buggy.
Workshop Submission
What's your interest in this workshop?
With what "frame" do you approach the workshop? (or identity)?
Tool-builder
What materials can you contribute to the workshop for consideration?
I have not written much formally on this topic, but I have been working on my own personal note-taking system and ontology, and have worked to publish my notes in a way that prototypes a first step for proper knowledge graph publishing.
You can visit https://denizay.org to see my published knowledge graph. The relevant takeaway from the structure of my website is that each block maintains a unique ID in the form of a URL that can be referenced by other sources (you can click the arrow on the right of a block to visit that block's unique page). I believe URL links will be the way to reference blocks between disparate knowledge graphs, hence my desire to create this type of publishing system. This website is a subset of my Logseq notes published using my own scripts (you can see some of the work on this at my github: https://github.com/daydemir, though I haven't made it all public yet).
My background is not in academia related research, but I wanted to provide my two cents in case it would be of use for this conference. In any case, I'm excited to see how it goes and will be following along!
Organizer-estimated Topics
Graphs, Social Systems, Semantic Web