Dontopedia

Should have

From Dontopedia, the open, paraconsistent wiki. (Last updated 2026-06-07.)

Should have is Important tasks that should be completed if possible.

34 facts·13 predicates·6 sources·4 in dispute

Mostly:rdf:type(6), has member(6), has task(5)

Maturity scale raw canonical shape-checked rule-derived certified

Inbound mentions (42)

Other subjects in dontopedia point AT this entity as a value. These are inverse relationships — e.g. "X motherOf this subject" — and answer questions the forward facts can't. Grouped by predicate.

hasPriorityCategoryHas Priority Category(13)

belongsToManyCoWCategoryBelongs to Many Co W Category(6)

memberOfMember of(6)

moscowCategoryMoscow Category(3)

hasCategoryHas Category(2)

isTaskOfIs Task of(2)

consistsOfConsists of(1)

correspondsToCorresponds to(1)

hasExamplesHas Examples(1)

hasHigherPriorityThanHas Higher Priority Than(1)

hasLabelTypeHas Label Type(1)

hasPriorityHas Priority(1)

hasPriorityLevelHas Priority Level(1)

inverseMoscowCategoryInverse Moscow Category(1)

isPartOfIs Part of(1)

supersedesSupersedes(1)

Other facts (28)

The long tail: predicates that appear too rarely to warrant their own section. Filter or scroll to find a specific one. Each row links to its source.

28 facts
PredicateValueRef
Rdf:typeMo S Co W Category[1]
Rdf:typePriority Category[2]
Rdf:typePriority Level[3]
Rdf:typeMo S Co W Category[4]
Rdf:typePriority Level[5]
Rdf:typeMo S Co W Category[6]
Has MemberTask 6[6]
Has MemberTask 7[6]
Has MemberTask 8[6]
Has MemberTask 12[6]
Has MemberTask 13[6]
Has MemberTask 18[6]
Has TaskEvaluate Mongodb[2]
Has TaskEvaluate Cassandra[2]
Has TaskPrepare Presentation Materials[2]
Has TaskEvaluate Secondary Databases[3]
Has TaskPrepare Presentation Materials[3]
DescriptionImportant tasks that should be completed if possible[1]
DescriptionImportant tasks that should be completed if possible[4]
Corresponds to LabelShould Have Label[2]
Has Higher Priority ThanCould Have[2]
SupersedesCould Have[3]
Inverse Belongs toMoscow Method[4]
Qualifies AsImportant[4]
Implies RecommendationCompletion Advisable[4]
Member ofFour Categories[4]
Inverse ofMember of[6]
Member Count6[6]

Timeline

Timeline axis is valid_time — when each source says the fact was true in the world, not when Dontopedia learned about it. Retracted rows are kept for provenance; coloured stripes indicate the context kind.

typebeam/95897ce5-4de3-49c2-86f7-c0d0dcc34c3c
ex:MoSCoWCategory
labelbeam/95897ce5-4de3-49c2-86f7-c0d0dcc34c3c
Should have
descriptionbeam/95897ce5-4de3-49c2-86f7-c0d0dcc34c3c
Important tasks that should be completed if possible
typebeam/dc33286e-4cea-4307-be9b-b01c4f520ace
ex:PriorityCategory
hasTaskbeam/dc33286e-4cea-4307-be9b-b01c4f520ace
ex:evaluate-mongodb
hasTaskbeam/dc33286e-4cea-4307-be9b-b01c4f520ace
ex:evaluate-cassandra
hasTaskbeam/dc33286e-4cea-4307-be9b-b01c4f520ace
ex:prepare-presentation-materials
correspondsToLabelbeam/dc33286e-4cea-4307-be9b-b01c4f520ace
ex:should-have-label
labelbeam/dc33286e-4cea-4307-be9b-b01c4f520ace
Should Have
hasHigherPriorityThanbeam/dc33286e-4cea-4307-be9b-b01c4f520ace
ex:could-have
typebeam/0a605956-e0ef-4fcb-a467-3d5f0619cf80
ex:PriorityLevel
labelbeam/0a605956-e0ef-4fcb-a467-3d5f0619cf80
Should Have
hasTaskbeam/0a605956-e0ef-4fcb-a467-3d5f0619cf80
ex:evaluate-secondary-databases
hasTaskbeam/0a605956-e0ef-4fcb-a467-3d5f0619cf80
ex:prepare-presentation-materials
supersedesbeam/0a605956-e0ef-4fcb-a467-3d5f0619cf80
ex:could-have
typebeam/cf4d2438-c322-4bbc-b6d0-dca657766c49
ex:MoSCoWCategory
descriptionbeam/cf4d2438-c322-4bbc-b6d0-dca657766c49
Important tasks that should be completed if possible
inverseBelongsTobeam/cf4d2438-c322-4bbc-b6d0-dca657766c49
ex:moscow-method
labelbeam/cf4d2438-c322-4bbc-b6d0-dca657766c49
Should have
qualifiesAsbeam/cf4d2438-c322-4bbc-b6d0-dca657766c49
ex:important
impliesRecommendationbeam/cf4d2438-c322-4bbc-b6d0-dca657766c49
ex:completion-advisable
memberOfbeam/cf4d2438-c322-4bbc-b6d0-dca657766c49
ex:four-categories
typebeam/b33c2772-cdf9-4ac9-b77b-d6813b2e6bf7
ex:PriorityLevel
labelbeam/b33c2772-cdf9-4ac9-b77b-d6813b2e6bf7
Should Have
typebeam/411bbe2e-f7e6-4e1d-82f6-ad1e0e76379c
ex:MoSCoWCategory
hasMemberbeam/411bbe2e-f7e6-4e1d-82f6-ad1e0e76379c
ex:task-6
hasMemberbeam/411bbe2e-f7e6-4e1d-82f6-ad1e0e76379c
ex:task-7
hasMemberbeam/411bbe2e-f7e6-4e1d-82f6-ad1e0e76379c
ex:task-8
hasMemberbeam/411bbe2e-f7e6-4e1d-82f6-ad1e0e76379c
ex:task-12
hasMemberbeam/411bbe2e-f7e6-4e1d-82f6-ad1e0e76379c
ex:task-13
hasMemberbeam/411bbe2e-f7e6-4e1d-82f6-ad1e0e76379c
ex:task-18
labelbeam/411bbe2e-f7e6-4e1d-82f6-ad1e0e76379c
Should have
inverseOfbeam/411bbe2e-f7e6-4e1d-82f6-ad1e0e76379c
ex:memberOf
memberCountbeam/411bbe2e-f7e6-4e1d-82f6-ad1e0e76379c
6

References (6)

6 references
  1. ctx:claims/beam/95897ce5-4de3-49c2-86f7-c0d0dcc34c3c
    • full textbeam-chunk
      text/plain1 KBdoc:beam/95897ce5-4de3-49c2-86f7-c0d0dcc34c3c
      Show excerpt
      Task 1 - 2 hours Task 2 - 3 hours Task 3 - 1 hours ... Number of sprints: 1.00 ``` ### Using Jira for Task Management 1. **Create a Jira Project**: - Go to Jira and create a new project. - Choose the Scrum or Kanban board based on y
  2. ctx:claims/beam/dc33286e-4cea-4307-be9b-b01c4f520ace
    • full textbeam-chunk
      text/plain1 KBdoc:beam/dc33286e-4cea-4307-be9b-b01c4f520ace
      Show excerpt
      - **Sprint Backlog**: - Must Have: - Evaluate PostgreSQL (5 points) - Evaluate MySQL (5 points) - Document findings (3 points) - Should Have: - Evaluate MongoDB (3 points) - Evaluate Cassandra (3 points) - Prepar
  3. ctx:claims/beam/0a605956-e0ef-4fcb-a467-3d5f0619cf80
  4. ctx:claims/beam/cf4d2438-c322-4bbc-b6d0-dca657766c49
    • full textbeam-chunk
      text/plain1 KBdoc:beam/cf4d2438-c322-4bbc-b6d0-dca657766c49
      Show excerpt
      [Turn 4484] User: I'm using Jira 9.5.0 to manage my agile project, and I've logged 20 tasks for metadata workflows. I'm aiming to complete 80% of the sprint, but I'm not sure how to prioritize my tasks effectively. Can you help me with some
  5. ctx:claims/beam/b33c2772-cdf9-4ac9-b77b-d6813b2e6bf7
    • full textbeam-chunk
      text/plain1 KBdoc:beam/b33c2772-cdf9-4ac9-b77b-d6813b2e6bf7
      Show excerpt
      ### Applying MoSCoW in Jira Here are the steps to apply the MoSCoW method in Jira 9.5.0: 1. **Identify Tasks**: List all the tasks you have logged in Jira for the sprint. 2. **Categorize Tasks**: Categorize each task into one of the MoSCo
  6. ctx:claims/beam/411bbe2e-f7e6-4e1d-82f6-ad1e0e76379c
    • full textbeam-chunk
      text/plain1 KBdoc:beam/411bbe2e-f7e6-4e1d-82f6-ad1e0e76379c
      Show excerpt
      - Task 13: Implement metadata normalization. - Task 14: Integrate with security framework. - Task 15: Implement metadata indexing. - Task 16: Test metadata extraction with edge cases. - Task 17: Implement metadata validation rules. - Task 1

See also

Keep researching

Missing something or suspicious of what's here? Kick off a research session — a Claude agent will investigate, cite its sources, and file new facts into a dedicated context you can review before accepting into the shared view.