Use of Standards

Use of Standards

This document explains the standards selected for the project, why they were chosen, and how they will be used in the system.

1. Schema.org with JSON-LD

Which standard did we select?

We selected the Schema.org vocabulary together with JSON-LD representation.

Why did we choose it?

Schema.org provides a common way to describe web data in a machine-readable form. JSON-LD allows us to represent that structured data in JSON format. This helps us describe important project entities in a standard and understandable way.

Which specific terms or structures are relevant?

• @context
• @type
• Person
• NewsArticle
• AskAction
• Place
• GeoCoordinates
• Common properties such as name, description, telephone, and datePublished

How do we plan to integrate it?

• User Profiles: Public profile information will be represented using the Person type.
• News and Announcements: Announcement pages will use the NewsArticle type.
• Help Requests: Help requests will be represented using AskAction.
• Location Information: Location-related data will use Place and GeoCoordinates.
• Implementation: The web frontend will add JSON-LD scripts to relevant pages, and the backend may provide matching structured fields in API responses where needed.

2. GeoJSON (RFC 7946)

Which standard did we select?

We selected GeoJSON.

Why did we choose it?

Our project uses geographic data for help requests, gathering areas, and user-related location information. GeoJSON is a standard JSON-based format for representing geographic data, and it is widely supported by map libraries and location-based tools.

Which specific terms or structures are relevant?

• Feature
• geometry
• Point
• coordinates
• properties

How do we plan to integrate it?

• API Responses: Endpoints that return map-related data will use the GeoJSON Feature structure.
• Coordinates: Locations will be represented as Point objects with [longitude, latitude] coordinates.
• Metadata: Additional information such as urgency or request type will be placed under properties.
• Implementation: The frontend map components will read this format directly when showing help requests or gathering areas.

Example:

{
  "type": "Feature",
  "geometry": {
    "type": "Point",
    "coordinates": [longitude, latitude]
  },
  "properties": {
    "needType": "medical",
    "urgency": "high"
  }
}

3. W3C WCAG 2.1 (Level AA)

Which standard did we select?

We selected the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.

Why did we choose it?

This project is intended for emergency use and should be usable by as many people as possible. WCAG 2.1 Level AA helps us design the system so that users with different accessibility needs can still use the platform effectively.

Which specific terms or structures are relevant?

• Sufficient color contrast
• Keyboard accessibility
• Alternative text for meaningful visuals
• Clear labels for form elements
• Visible focus indicators

How do we plan to integrate it?

• Frontend Development: We will use semantic HTML and accessible UI components.
• Interaction Design: Buttons, forms, and navigation elements will be usable with a keyboard.
• Accessibility Support: We will use ARIA labels only where necessary.
• Validation: We will use tools such as axe-core and also perform manual accessibility checks.

4. RFC 7519 (JSON Web Token - JWT)

Which standard did we select?

We selected JSON Web Token (JWT).

Why did we choose it?

The project needs a standard way to handle authentication across web and mobile clients. JWT is widely used for this purpose and supports stateless authentication between the client and the backend.

Which specific terms or structures are relevant?

• JWT token
• Claims
• Signature
• Authorization: Bearer <token> header

How do we plan to integrate it?

• Login: After a successful login, the backend will create a signed JWT.
• Authenticated Requests: The client will send this token in the Authorization header.
• Web Client: The token will be handled securely on the web side.
• Android Client: The token will be stored using secure Android storage mechanisms.