Open cristianvasquez opened 1 year ago
Hi! Cool project. It reminds me I need to add schema:name to the real-world script
I'd like to know what the RDF looks like. Could I see an example?
Sure. docs.ttl.txt. You can also create this output with the example instructions. You don't need to have logseq installed
There are some similarities and differences between your example and this example script:
is a ::
which we don't have yet. url
to see other properties that have the same structure. I did it this way to encode all the information in the graph/vault and try to make it user friendly.Closing as I've answered. Happy to reopen if you want to chat more about this
Sure, I still need to find the time to analyze the links you posted adequately.
Regarding the production of RDF, a series of use cases could help shed some light.
Simple things, such as:
I understand this repo belongs to a specific scripting lib. Do you know a place where the PKM communities discuss interoperability between tools?
Do you know a place where the PKM communities discuss interoperability between tools?
I don't know if there's much of a community around this yet. I imagine David at https://samepage.network/ would know as his product is largely focused on this
There is some discussions in r/PKMS https://www.reddit.com/r/PKMS/
I'm looking into the RDF data, https://s.zazuko.com/3BjGKjB (with https://sketch.zazuko.com/) I can see the data produced is has types, some sort of taxonomy. Is this the triplification of https://docs.logseq.com itself? how do you handle relations?
I'm thinking of adopting the name 'Block' in the markdown triplifier, are blocks called 'blocks' in all outliner applications?
Is this the triplification of https://docs.logseq.com/ itself? how do you handle relations?
It's a triplification of a subset of the graph, not the whole graph. The script defaults to each node in a rdf triple corresponding to a logseq page but this is configurable by four queries. The configurability aims to make it easy for others to come up with different approaches to triplification. For example, one could write queries to triplify all blocks with properties. Personally I don't do that because Logseq's blocks aren't user friendly enough e.g. autocompletion isn't as good and blocks don't have names like pages do. By relations I think you mean rdfs properties. If so, they are just logseq property pages e.g. the linked refs in https://docs.logseq.com/#/page/Property
I'm thinking of adopting the name 'Block' in the markdown triplifier, are blocks called 'blocks' in all outliner applications?
I don't know. Some outliner apps also call them nodes
Hi! I'm happy about Logseq producing Linked data.
I'd like to know what the RDF looks like. Could I see an example?
I'm an Obsidian User, and I'm producing RDF from notes as well here: https://github.com/cristianvasquez/vault-triplifier
Perhaps they are similar models?