Mahfuza Humayra Mohona mhmohona

Outline for AITRIOS

Level 1	Level 2	Level 3	Level 4	Level 5	Reference
Quick Start	1. Welcome to AITRIOS
	2. Development Workflow Overview
	3. Account Setup and Management
	4. System Introduction

graph TD
A[Prepare test dataset] --> B[Configure V-pipe for wastewater analysis]
B --> C[Run V-pipe on wastewater samples]
C --> D[Examine key output files]
D --> E[Update tutorial text]
E --> F[Optionally create Google Colab notebook version]

A --> A1[Download representative samples from SRA/ENA]
A1 --> A2[Organize FASTQ files into V-pipe directory structure]

graph TD
    CLI("Command Line Interface") -->|User Input| Core("Core Module")
    Core -->|SPARQL Queries| Wikidata("Wikidata Query Service")
    Core -->|Data Processing| DataProcessing("Data Processing Module")
    DataProcessing -->|Formatted Data| Core
    Core -->|Scribe API Calls| ScribeApps("Scribe Applications")
    Wikidata -->|Query Results| DataProcessing

Running Hooks in the New System

Updating extension.json

To start using the new hook system, you need to update your extension's extension.json file. Define a handler class for your hooks by adding a new section called hookHandlers to the file:

{
    "name": "MyExtension",

Newly Created pages -

Page name	Wiki	Stats
Data Analysis : Curve Fitting	wiki	not reviewed
Data Analysis : Fourier Transform	wiki	not reviewed
CAS Computing	wiki	not reviewed
LaTeX Typesetting	wiki	not reviewed
Tools : FITS Metadata Editor	wiki	not reviewed

Story: Eve Helps Chan Fix His Spaceship

1. Info (Metadata about the API):

Think of this as the name tag on Chan's spaceship. It tells you the spaceship's name and which version it is (like if it's a newer or older model). In our API, the "info" section does something similar. It gives a title and version for the API, like a name tag so everyone knows what they're working with.

2. Channels (Communication channels in the API):

Imagine the spaceship has different radio stations for talking to different parts of space. Each station (or channel) is for talking about specific things. In our API, "channels" are like these radio stations. They're paths for sending specific types of messages. Each channel is for a different topic, just like how each radio station on Chan's spaceship talks to different planets or stars.

3. Components (Reusable parts of the API):

Module 3

Let's delve deeper into these components:

info: info section provides metadata about the API, such as its title and version
channels: channels section defines the communication channels used by the API. Each channel corresponds to a specific topic or queue in the message broker. The channels section includes the type of messages sent on each topic/queue
components: components section defines reusable components that can be referenced elsewhere in the API definition. This can include message definitions, schemas, parameters, and more. By defining these components in one place, you can maintain consistency across your API
tags: tags section allows you to categorize operations in your API. It can be useful for grouping related operations together, making the API easier to navigate and understand.
Operations: operations are defined within channels. For example, a send operation might be defined for a channel to specify that messages are sent by that channel.
Messages: Mess

PR	Reviewer	Tech Review Status	Editorial Review status	Remark
Adding channel	Sergio Moya	addressed	addressed	Marged
Dynamic channel	Sergio Moya	addressed	addressed	Marged
Extending Specification	Jonas Lagoni	addressed	addressed	Marged
Adding Messages	Fran Méndez	addressed	addressed	Marged
Reuse with traits	Lukasz Gornicki	addressed	addressed	Marged
Adding binding	Lukasz Gornicki	addressed	addressed	Marged

	Killercoda AsyncAPI Profile	Linux Foundation Interactive Content
Content Authoring	- Content creation using Killercoda's tools and templates. - Publishing content in various formats.	- Content authoring using various tools like text editors and authoring tools. - Collaboration features for authors and subject matter experts. - Course management through an integrated Learning Management System (LMS).
Reader Flow & Content Access	- Standalone platform with direct content access on Killercoda website. - Readers browse and access content on the platform.	- Dedicated learning platform or integrated LMS. - Users access content through the Linux Foundation Learning Platform website or LMS portal. - Account creation and direct access to learning paths and courses.
Technological Requirements	- Front-end: HTML5, CSS, JavaScript, React/Angular/Vue.js, UI libraries/frameworks.- Back-end: Python/Ruby/Node.js, Django/Ruby on Rails/Express.js, RDBMS.- Additiona

	asyncapi: 3.0.0
	info:
	title: Sending SIgnal to Eve
	version: 0.1.0
	channels:
	userSignedUp:
	address: Earth/letter
	messages:
	lettertoEarth:
	description: Communicating with Eve.