top of page
Respond.png

[ Sæyanæ ] - Request & Provide

it's ok to ask for something, it's splendid to give help

through out conversation, one can ask for things (like information) and provide as well

01:ReqRes

Request and Provide

We usually request or respond/provide, this can be used for information exchange, word building

Saeyanae.png
Request.png

[ Sæyanæ - Va - Ta ]

[ Sæ - Va - Ta ]

​[ SæVa ]

Request

Saeyanae.png
Respond.png

[ Sæyanæ - Va - Tæ ]

[ Sæ - Va - Tæ ]

[ SæVæ ]

Provide

Glyph Derivation

 

The Glyph for Sæva resembles a hand with it's palm facing upwards, requesting for something.

The Glyph for Sævæ resembles a hand with it's palm facing downwards, providing something

Pronunciation Derivation

Originally These 2 glphys or concept is meant for information echange

So there is a period where the pronunciation is influenced by "Kosra"

[ Kosra ] + [ KaxiTa ] → [ Koa ] + [ KaTa ] → [ KoaTa ]

[ Kosra ] + [ KaxiTæ ] → [ Koa ] + [ KaTæ ] → [ KoaTæ ]

 

Now the action of Request and Provide has ben generalized, and it is now a Verb

So now this falls under the Sæyanæ category

Sometimes we can omit the "Sæyanæ" glyph to simplify

Request.png

​[ SæVa ]

Request

Respond.png

[ SæVæ ]

Provide

02:WordStruct

Information Exchange

Information exchange is common through out conversations.

But simply asking for information is not enough, the information type or name is also required,

Saeyanae.png
Kosra.png

information name / type to request or provide

[ Sæva ]

or

[ Sævæ ]

03:InfoSpec

Examples

Here are some of the combination that can be translated into something that we can normally understand.

Saeyanae.png
Request.png
Kosra.png
Kaxi-thin.png

[ SæVaKoa - Ka ]

Where

Saeyanae.png
Request.png
Kosra.png
Event_Reason.png

[ SæVaKoa - SæTæ ]

Why

Saeyanae.png
Request.png
Kosra.png
Taxi-thin.png
Kaxi-thin.png

[ SæVaKoa - TaKa ]

Where

Saeyanae.png
Request.png
Kosra.png
Event_Process.png

[ SæVaKoa - SæTo ]

How

Saeyanae.png
Request.png
Kosra.png
Krosno.png

[ SæVaKoa - Ko ]

What

Saeyanae.png
Respond.png
Kosra.png
Event_Reason.png

[ SæVæKoa - SæTæ ]

Because

Saeyanae.png
Request.png
Kosra.png
Krosni.png

[ SæVaKoa - Koi ]

Who

Saeyanae.png
Kosra.png
Respond.png
Event_Result.png

[ SæVæKoa - SæTa ]

Therefore

Wait ... this has no Translations ...

 

Sometimes, you might end up with combinations that cannot be directly translated into a word

in English / Chinese  / Japanese etc. But sometimes they may make sense.

Keep in mind, these combinations are some of the possible combinations,

this does NOT mean that those are the only available combinations.

Examples

 

someone may request information about a person,

which one can use "SæVaKoa - Koi",

which can be translated to "who" in English.

In This case, the one who answers will need to use "SæVæKoa - Koi" as a reply (optional),

which does not has a direct translation to English or Chinese or Japanese etc

however it can be broken down into

"Information - Provide - Person"

Warning

 

In most languages, animals other than humans have been treated as lifeless objects (instead of "he" or "she", they get to have "it"), however, in Astralica, all animals get to have "KosraNi" or "KrosNi" or "Kri" or "Koi".

Information Segment

Sometimes we can attach information for an entity

such as length, size, duration, time, color, brightness, pitch, quantity, mass, adjectives and more.

To attach information to an entity,

we will attach an "information segment" behind the entity we want to describe.

an information segment is made up of 3 parts : open, trait list, close

Entity goes here

Saeyanae.png
Kosra.png
Respond.png

[ Sæyanæ - VæKosra ]

[ SæVæKoa ]

"start attaching information"

the opening particle

Trait List goes here

Saeyanae.png
Request.png
Kosra.png

[ Sæyanæ - VoKosra ]

[ SæVoKoa ]

"stop attaching information"

the closing particle

every trait item can be broken down into 2 parts :

Trait name and Trait value

Nested Information Segment

 

Sometimes it is possible to have items inside the trait list to attached with it's information segment.

The function of the opening particle and the closing particle can act as a mechanism to avoid ambiguity.

 

In theory of computation, Ambiguitity happens when a string can be generated by using different parse trees.

Astralica is built and designed based on Computer Science, therefore grammatic Ambiguity is one of the Design goals to fix.

Examples

 

"Koixonya SæVæKoa Kla la Litaraka rahanota Kaklana sklæri SæVoKoa"

let's disect this

"Koixonya" : "Cat"

"Koatæ" : "Start attach information"

"Kla" : "Quantity" ("Klari"), a type of trait

"la" : "number 7", a possible value

"Litaraka" : "color in HSV format", a type of trait

"rahanota" : "red, no saturation, bright", which is white, a possible value

"Kaklana" : "Size in 3D", which is just size, a type of trait

"sklæri" : "crank low, neutral", with the context of size, it means "small", a possible value

"Koato" : "Stop attaching information"

so the whole thing can be translated to

"seven small white kittens"

instead of attaching information, we can request information instead, at this point, we can change

"Koatæ" to "Koata", literally "start requesting for the following traits"

Entity goes here

Saeyanae.png
Request.png
Kosra.png

[ Sæyanæ - VaKosra ]

[ SæVaKoa ]

"start asking information"

the opening particle

Trait List goes here

Saeyanae.png
Respond.png
Kosra.png

[ Sæyanæ - VoKosra ]

[ SæVoKoa ]

"stop asking for information"

the closing particle

over here, every trait list item will be the trait name.

Examples

 

by reusing the previous example to turn

"Koixonya Koatæ Kla la Litaraka rahanota Kaklana sklæri Koato"

into an information hungry sentence or a question. We can have

"Koixonya Koata Kla Litaraka Kaklana Koato ?"

Sometimes, we want to ask for information about a certain noun by giving traits to narrow down the search space. Here we can attach the Information Providing Segment to the noun, followed by the Information requesting segment, or the other way around

Entity goes here

Saeyanae.png
Respond.png
Kosra.png

Trait List goes here

Saeyanae.png
Request.png
Kosra.png
Saeyanae.png
Request.png
Kosra.png

Trait List goes here

Respond.png
Saeyanae.png
Kosra.png

or

Entity goes here

Saeyanae.png
Request.png
Kosra.png

Trait List goes here

Saeyanae.png
Respond.png
Kosra.png
Saeyanae.png
Respond.png
Kosra.png

Trait List goes here

Saeyanae.png
Request.png
Kosra.png

Examples

"Koixonya SæVæKoa Kla la Litaraka rahanota Kaklana sklæri SæVoKoa SæVaKoa Ka SæVoKoa ?"

based on the previous examples, we can translate this to

"Cats, Start Describing, Quantity seven, color white, size small, Stop Describing , Start Asking , location Stop asking"

or in other words,

"Where are the seven little white kittens"

where we can have a perfect example of "Nesting information segments"

here just simple asking "SæVaKoa Ka SæVoKoa" might not be enough

is it in the past ? "Where were the kittens ?"

or right now ? "Where are the kittens ?"
or in the future "Where will be the kittens be ?"

so we can attach "now" to the requested trait "Ka"

and now we have :

"Koixonya SæVæKoa Kla la Litaraka rahanota Kaklana sklæri SæVoKoa SæVaKoa Ka SæVæKoa TaKo SæVoKoa SæVoKoa"

bottom of page