The Way We Work

Purpose

This document describes the operational working model used by the Smart Cities SIG.

The objective is to support:

  • lightweight governance,
  • practical collaboration,
  • transparent participation,
  • and execution-focused ecosystem coordination.

This document complements:

Working Model

The Smart Cities SIG operates as a lightweight and collaborative ecosystem initiative focused on:

  • interoperability,
  • reusable profiles,
  • semantic mappings,
  • validation approaches,
  • and practical Proof of Concept activities.

The initiative prioritizes:

  • practical progress,
  • ecosystem alignment,
  • reusable outputs,
  • and timely delivery of agreed objectives.

The SIG is not intended to operate as a heavyweight standards development process or a formal architecture design authority.

Meetings

Meetings are intended to support:

  • collaboration,
  • coordination,
  • ecosystem alignment,
  • and review of ongoing activities.

Meeting minutes serve as the primary operational record for the initiative and may include:

  • agenda items,
  • participants,
  • action items,
  • references,
  • presentation links,
  • and related collaboration material.

Meeting records are maintained under:

Program/meetings/minutes/

Discussions and collaboration activities should remain:

  • constructive,
  • practical,
  • and aligned with the agreed objectives of the initiative.

Lightweight Decision-Making

The Smart Cities SIG primarily operates through:

  • collaborative alignment,
  • practical consensus,
  • and execution-oriented discussions.

The initiative does not rely on formal voting procedures for normal operational activities unless explicitly required by the initiative leadership.

Where needed, initiative coordinators may facilitate discussions to support alignment and maintain initiative progress.

The initiative encourages:

  • practical discussion,
  • incremental progress,
  • and ecosystem alignment rather than heavyweight approval processes.

Coordination and Execution Focus

The initiative prioritizes:

  • timely delivery of agreed Proof of Concept outputs,
  • interoperability validation,
  • practical collaboration,
  • and execution discipline.

Participants are encouraged to remain aware of the current initiative roadmap and execution phase when introducing new ideas or proposals.

The initiative roadmap and execution planning are maintained under:

Program/roadmap/release-planning.md

As the initiative progresses toward validation and delivery phases, activities are expected to increasingly prioritize:

  • stabilization,
  • interoperability validation,
  • test activities,
  • and completion of agreed outputs.

Traceability and Transparency

The initiative emphasizes:

  • transparent collaboration,
  • reusable outputs,
  • and traceable discussions.

Meeting minutes, GitHub Issues, Pull Requests, and related repository activities serve as the primary traceability mechanisms for:

  • discussions,
  • action items,
  • decisions,
  • and collaboration activities.

Participants are encouraged to maintain discussions and collaboration activities within public repositories and collaboration channels whenever feasible.

Additional contribution guidance and repository practices are defined in:

CONTRIBUTING.md

Escalation and Coordination

Concerns regarding collaboration behavior or participation issues may be raised with the initiative coordinators or designated SIG leadership.

Concerns may be reviewed and addressed by the initiative coordinators, including the Chair and Vice-Chair(s).

The initiative coordinators may moderate discussions or participation activities when necessary to maintain productive and respectful collaboration.

Additional collaboration behavior expectations are defined in:

Governance/code-of-conduct.md

Evolution of the Working Model

The Smart Cities SIG is expected to evolve over time based on:

  • ecosystem participation,
  • interoperability findings,
  • Proof of Concept outcomes,
  • implementation feedback,
  • and future collaboration opportunities.

Repository structures, collaboration practices, and operational processes may evolve incrementally as the initiative matures.