AmpersandTarski / Ampersand

Build database applications faster than anyone else, and keep your data pollution free as a bonus.
http://ampersandtarski.github.io/
GNU General Public License v3.0
40 stars 8 forks source link

Describe an agreed-upon semantics of the namespace stuff. #1509

Open hanjoosten opened 1 month ago

hanjoosten commented 1 month ago
          The problem is that we have no agreed-upon semantics of the namespace stuff. So how are we going to build it first-time-right?

Originally posted by @stefjoosten in https://github.com/AmpersandTarski/Ampersand/issues/1467#issuecomment-1950984951

hanjoosten commented 1 month ago

The groundwork for namespaces has been done. In the Haskell code, we have the Name type, that is used now all over the place. Semantically hardly anything has changed: There are some restrictions on names:

The last namepart of a name is called the localname. The casing of the first character of a localname is according of the casing of names that we are all used to (Uppercase for Concepts, Lowercase for Relations)

hanjoosten commented 1 month ago

Now it is time to add semantics for the namespace. There have been several discussions about this in the past. My gut feeling is that @stefjoosten and @Michiel-s have slightly different ideas. Regardless if these ideas differ or not, it is good to agree upon a well defined semantic, so I (or someone else 😃) can build this one-time-right.

So please, @stefjoosten and @Michiel-s , feel free to come up with your description