Rel4tion-Wiki/projects/razom.mdwn

<div class="infobox">
<h2>Links</h2>

<ul>
<li> [[News]]
<li> [[Releases]]
<li> [[Forum]]
<li> [[Tickets]]
</ul>
</div>

[[!toc]]

# Introduction

**Razom** aims to be a complete set of software tools, frameworks and
interfaces for handling of semantically organized information. It will provide
tools for definition (a.k.a specification), management and sharing of
information based on a general-purpose information model.

Razom servers as the system side of the [[/projects/Rel4tion]] platform. The
user side is provided by various applications and environments which run on top
of Razom.

The information sharing component doesn't exist yet, and will possibly be
external to Razom as well. It hasn't been decided yet.

# Freedom

Razom is dedicated to freedom and sharing, in particular of software and
digital information. See [[/freedom]].

# Components

Razom's releases coordinate development and release of several components. Work
is planned according to the [[Rel4tion roadmap|/projects/rel4tion/roadmap]].

+ Expression
  - [[Smaoin]] - information model
+ Representation
  - [[Kort]]
  - [[language-kort]]
  - [[Idan]]
  - [[language-idan]]
+ Querying
  - [[Naya]] - query model
  - [[QueryLang]]
  - [[language-querylang]]
+ Storage
  - [[Saugus]] - semantic datastore
+ Access
  - [[razom-basic-store]] - API for basic data access

Uncategorized pages:

+ Razom [[architecture]] - system design overview
+ [[Verkosto]] - web service architecture and framework
+ [[API]]
+ [[Ideas]]
+ [[Proposals]]
+ [[developer-workflow]]
+ [[tool-reuse]]
+ [[from-idan-doc-repo]]

Useful information:

+ [[Related work|related-work]]

Aspects and components to consider moving out of Razom:

+ [[User interface design|user-interface-design]]

Some notes to move elsewhere:

There are entities in the world. Ideas. Things. Concepts. We can use labels to
refer to them. This is what Uids do. But some some things, there are reasons to
use other representations. This is fine, because they're just representations.
For example, for numbers we use representations like `-4.3$-5` (in text) and
standard floating-point numbers (in binary). The alternative would be some
scheme for defining an infinite number of Uids, and a way to convert from Uid
to number and vice versa. Much less readable, and doesn't do any good.

In some cases the representation may be there just for convenience. For
example, there's a finite number of Unicode characters. We could make them
resources with Uids, and define the Unicode code-points by storing them in
direct binary form and represent as Data in text, i.e. short Base64 chunks.

# Documentation

This is a place for Razom-general and cross-component docs which aren't
specific to any of its components. Tutorials, overviews, technical manuals,
various specs and so on.

- [[Information languages|info-lang]] - computer languages for expressing
  information under the [[Smaoin]] data model

Developer notes and documents:

- [[parsing-notes]]

# Community

See [[/community]] page.

# Bugs, Ideas, Tasks and Decisions

See these:

- [[tickets]]
- [[decisions]]