Confused about tags inside property values in db version

Questions & Help
1

I am testing the new db version of Logseq and I came to an issue. I have a property named keywords that is set to Text for the Property type. According to schema.org standard, it is used for keywords or tags and it must be DefinedTerm or Text or URL.

When I write a name of a tag with a # and I finish manually typing it, it stays on the left close to the property name. But when I start typing and choose a tag from the suggestion popup to complete the name of the tag automatically, it goes to the right of the line that holds the values for the property.

Properties-Tags
Properties-Tags970×109 5.16 KB

Since they are part of a property’s value, one would expect them to appear next to the property as any other value.

Is this expected?

Questions about Tag properties in db version
2

When you want a tag to stay inline, you use the CMD + ENTER instead of ENTER after typing the tag name.

But there is another way to solve this, if I understood your objective.

  1. Create a Tag called `#keywords
  2. Set the keywords property as a type node, and set its node tag as #keywords
  3. Create a new tag called #network and apply the tag #keywords ; you can also create new keywords tag from the property

This would give you the a list of keywords only to choose from, and they will be tags.

3

The second way looks too complicated and prone to mistakes. The first one, with the CMD+ENTER, is much simpler. But is there any functional difference?

Anyway, how I want to use this keywords property is like in the old Logseq md properties with the double colon :: for holding the Tags like: tags:: #Tag1 #Tag2 #Tag3.

The reason why the keywords property is set to Text type is because I use this starter edn template: GitHub - C0ntr0lledCha0s/logseq-template-graph: This is a starter for 10 for anyone who wants to add structure to their Logseq DB. that is suggested in the documentation of the new Logseq db: docs/db-version.md at master · logseq/docs · GitHub . It is based on the https://schema.org/ for structured data. With the imminent release of the new Logseq db, I saw it as an opportunity to better organize my Graphs, using the https://schema.org/ guidelines, because the previous are a bit messy.

But now I wonder if this is useful in a program like Logseq. So my new question is: What is the appropriate place to put the tags that describe the content of the node so that it can be linked in the graph with other related nodes? Where does the new Logseq db want to see the Tags?