Content Knowledge Graph

Technical and other non-functional requirements

Must Have:

Initial Knowledge Graph Deployment:

• Deploy a scalable KG infrastructure capable of representing DeepFunding content that includes 
  • entities (data objects) such as documentation, proposers, proposals and milestones, voters and votes 
  • and labelled relationships between participants in the network.
• The KG should be designed with future ecosystem-wide content integration in mind, allowing for scalability (compatible with nested and interlinked subgraphs) and the handling of a growing volume of data types and sources.
• Reliable hosting solution for the KG for 1 year. Having a well-defined plan to host in a partner of SNET like Ocean or ICP would be a bonus. 

Data Ingestion Process:

• Ability to add/delete data to the KG in JSON-LD format, compatible with data from DeepFunding voting portal, and with flexibility to add new sources as required.
• Include data cleaning mechanisms to ensure the accuracy and quality of the data ingested into the KG. (to be tested with export data from the test round). 
• API to offer search functionality of the data in the KG. Report on the subset of GRAPHQL (https://spec.graphql.org/October2021) covered.

Good to Have:

• Semantic and Social Network data structure to understand what has been said (Semantic) and who said what (Social Network).
• Automated Data Pipelines for real-time data ingestion from a broader array of sources, ensuring data relevance by integrating live updates to the KG.
• Data Enrichment Tools: Integrate NLP and ML tools for semantic analysis, automated categorization, tagging, and enrichment to uncover hidden relationships and enhance metadata.
• Protected data and access management.

Nice to Have:

• MetaData entry for Reputation scores for each data object (trustability).
• MetaData entry for Flagging (3rd party application warnings on trustability).
• Auditable log of interactions with and modifications to the KG.

Non-Functional requirements:

Include aspects like documentation, maintenance, and compliance with standards.

Must Have:

Thorough Documentation:

• Provide comprehensive documentation detailing the KG's structure, functionality, data models, and interaction interfaces (APIs/UI), enabling effective collaboration and development by other teams.
• Include guidelines for data ingestion, querying practices, and interface customization.

Collaboration and Support:

• Collaboration process with Application teams to co-define the ontology (must contain elementary words) and to ensure that the ontology design aligns with the requirements of the user interface. This may involve discussing how entities and relationships will be presented and navigated within the Front-End(s).
  • Understand what the data presentation needs and ensure the ingested data is structured and labelled appropriately to support front-end functionalities such as querying and visualization.
  • Availability for at least 6 meetings (1 hour each) with the Applications teams and 8 hours for monitoring async communication channels during the Applications RFPs submission period and after with the selected teams to answer questions, coordinate requirements, and provide support. Any needs exceeding this amount should be budgeted by the Application teams.
    
    
• Maintenance plan for ongoing support and updates of the Knowledge Graph for 1 year.
  • Mattermost channels for customer support to Application teams (monitored weekly) and availability for at least 2 calls a month.
  • Fixing of any bugs or gaps in the technical functioning of the KG and APIs.
  • At least 30 hours of technical support available to expand the KG’s ontology and/or support the integration of new data sources. (available to Application teams on a first come first serve basis). The hourly rate for these hours is to be presented in the proposal for the KG RFP, however, the payment of said hours should not be budgeted in the KG proposal. The payment for said hours is to be budgeted in the Application RFP's proposal and paid to the selected KG team by the selected Application team(s).
    
    
• Integration with SingularityNET's AI platform as a 'knowledge node': 
  • A minimum of 10% of the budget is suggested to be reserved for this purpose.
  • The SingularityNET foundation team will provide guidance and support to the selected team.

Good to Have:

• Training materials for users and admins.
• Clear budget outlining the allocation for collaboration (coordination and support), build, and maintenance.

Nice to Have:

• Agile methodologies to coordinate tasks and collaborate with Application teams.
• Ontology that includes URIs, Images, Text Blocks, etc.