We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This started in n3-class-metadata
The goal is to:
The current configuration is similar to this...
+----------------+ | ClassMetadata | | - icon | | - color | | - label | | - comment | | - searchPrio | +----------------------+ | sh:targetNode |--------->| :Person a rdfs:Class | +----------------+ +----------------------+
What is wrong with that approach:
First Try: Create an N3 rules for this and use the eye reasoner to add the information directly to the subjects.
{ ?s a <https://schema.org/Organization> } => { ?s <https://flux.described.at/searchPrio> 3 ; <https://flux.described.at/label> "Organization" ; <https://flux.described.at/comment> "" . <https://flux.described.at/icon> "fa-solid fa-building" ; <https://flux.described.at/colorIndex> "1" ; . } .
You can read the rule like { if } => { then } . Then use the rule to "reason" the Icon, Color, SearchPriority, and the "Class" Label.
{ if } => { then }
Findings after the implementation:
Second try:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This started in n3-class-metadata
The goal is to:
The current configuration is similar to this...
What is wrong with that approach:
First Try:
Create an N3 rules for this and use the eye reasoner to add the information directly to the subjects.
You can read the rule like
{ if } => { then }
.Then use the rule to "reason" the Icon, Color, SearchPriority, and the "Class" Label.
Findings after the implementation:
Second try:
The text was updated successfully, but these errors were encountered: