Prioritizing topics for TRAPI 1.5 by vote

[edeutsch]

This discussion thread will serve as the voting platform for prioritizing the topics to tackle for TRAPI 1.5 development. After everyone votes, we will address them roughly in order of acquired votes.

All regular team representatives/attendees of the TRAPI call are strongly requested to vote. All other Translator participants are welcome to vote.

You are NOT voting for a particular solution.
You ARE voting to prioritize the topics for future TRAPI calls to be discussed, resolved, and included for the TRAPI 1.5 release (or dismissed if that is the will of the people)

Voting Scheme:
+2 Highest (heart) - Must get this done for TRAPI 1.5
+1 High (thumb up) - Should try to get this done for TRAPI 1.5
0 Medium (none) - Meh, if there's extra time by the deadline, sure
-1 Low Priority (thumb down) - This should not be prioritized. Can take this up for TRAPI 1.6

Summary of the voting compiled on 2023-10-24:

• 9 - Design how to encode knowledge_level (knowledge_assertion, prediction, observation, etc.) and agent_type (eg. manual_agent, automated_agent, etc.) for Edges in TRAPI Update knowledge_level_agent_type_specification.md #459
• 7 - Go through all of TRAPI and tidy it up to formally make everything explicitly nullable or not to address OpenAPI thorns related to required/not and also address minItems for arrays not required not the same as nullable: true #458 and Tidy up schema to make null vs. empty list more intentional #438
• 7 - Add TRAPI support for collections: a node can represent a collection of concepts/CURIEs support for collections #396 and add support of collections #373
• 6 - 'Curification' of additional types of publication URLs 'Curification' of additional types of publication URLs #457
• 5 - Make Node.categories required and not nullable Make Node.categories required and not nullable #456
• 5 - Should MetaEdges with Qualifiers provide the union of all possibilities or individual allowed combinations? Should MetaEdges with Qualifiers provide the union of all possibilities or individual allowed combinations? #425
• 5 - Supporting data sources refinements in TRAPI schema Supporting data sources refinements in TRAPI schema #451
• 5 - Should we use the support graph infrastructure for subclass inference? Should we use the fancy supporting graph infrastructure for subclass inference? #414
• 4 - How to determine the specific type of a supporting publication How to determine the specific type of a supporting publication #410
• 3 - Add the sources field to MetaEdge so that infores identifiers are returned in the meta knowledge graph add sources field to MetaEdge so that infores identifiers are returne… #430
• 3 - Define intent and constraints on the Attribute.value_type_id field Define intent and constraints on the Attribute.value_type_id field #454
• 3 - Does a bad /asyncquery still require a job_id to be returned? Does a bad /asyncquery still require a job_id to be returned? #424
• 3 - What should Node descriptions look like? What should Node descriptions look like? #374
• 2 - Conventions for representing clinical trials supporting and Edge Conventions for representing clinical trials supporting and Edge #447
• 2 - Standardize how metadata supporting text mined results is represented Standardize how metadata supporting text mined results is represented #399
• 2 - Query context / intention Query context / intention #319
• 1 - Introduce formal support for negation in Edges in TRAPI Introduce a special property to make "negation" of edges more visible in a TRAPI message #407
• 1 - Should we disallow extra properties on QNode and QEdge Should we disallow extra properties on QNode and QEdge #321
• 0 - Set regex pattern for CURIE and add URL set regex pattern for CURIE and add URL, fixes #400 #406
• 0 - Extend TRAPI to capture QEdge.exclude Propose QEdge.exclude #306
• 0 - Consider defining a URL type Consider defining a URL type  #400
• 0 - Add QualifierConstraint.qualified_predicate property Add QualifierConstraint.qualified_predicate property  #368
• 0 - the refs to outside schema cause errors for BTE the refs to outside schema cause errors for BTE #301
• 0 - Streamline constraints Streamline constraints #297

[edeutsch]

Design how to encode knowledge_level (knowledge_assertion, prediction, observation, etc.) and agent_type (eg. manual_agent, automated_agent, etc.) for Edges in TRAPI #459

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Go through all of TRAPI and tidy it up to formally make everything explicitly nullable or not to address OpenAPI thorns related to required/not and also address minItems for arrays #458 and #438

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Make Node.categories required and not nullable #456

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Add the sources field to MetaEdge so that infores identifiers are returned in the meta knowledge graph #430

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Introduce formal support for negation in Edges in TRAPI #407

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Set regex pattern for CURIE and add URL #406

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Add TRAPI support for collections: a node can represent a collection of concepts/CURIEs #396 and #373

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Extend TRAPI to capture QEdge.exclude #306

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

'Curification' of additional types of publication URLs #457 #457

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Define intent and constraints on the Attribute.value_type_id field #454 #454

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Supporting data sources refinements in TRAPI schema #451 #451

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Conventions for representing clinical trials supporting and Edge #447 #447

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Should MetaEdges with Qualifiers provide the union of all possibilities or individual allowed combinations? #425 #425

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Does a bad /asyncquery still require a job_id to be returned? #424 #424

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Should we use the support graph infrastructure for subclass inference? #414 #414

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

How to determine the specific type of a supporting publication #410 #410

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Consider defining a URL type #400 #400

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Standardize how metadata supporting text mined results is represented #399 #399

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

What should Node descriptions look like? #374 #374

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Add QualifierConstraint.qualified_predicate property #368 #368

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Should we disallow extra properties on QNode and QEdge #321 #321

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Query context / intention #319 #319

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

the refs to outside schema cause errors for BTE #301 #301

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down

[edeutsch]

Streamline constraints #297 #297

Vote for this topic with an emoji: heart, thumbs up, nothing, thumbs down