Automatic transformation of XML namespaces specification releases its first draft.
From the specification:
This is a preliminary rough draft. There may be errors, omissions, and logical inconsistency. There should be added more formal explanations (not just examples as now), more examples, and more explanation. The standard may change.
However, the first draft is released and it is a complete specification, which should be formal enough to write an implementation. (I am going to write an implementation in Ada.)
Note that for this to be practically useful, we need a robust sandbox (it is proposed for Linux).
My writer’s block for my XML-related standard went away.
I propose to classify XML namespaces into three distinct groups regarding “interaction” of elements (or attributes) of the same namespace.
Then we can transform between namespaces of the same precedences in such a way that in the case if elements interact, there remains only one namespace, thus not interacting elements of different namespaces.
I should write an exact specification for this idea, but the way is now open, I am past of my writer’s block.
I have several times said that this my project failed but it was salvaged again.
Now I again have a “writer block” concerning this project.
See this unsolved problem.
Today I have moved all my Web sites from an old VPS hosting to Digital Ocean VPS hosting.
Their prices start from unbelievable $5 per month for a server with 20GB SSD disk.
I myself use the 2GB RAM, 40GB SSD hosting for unbelievable price $20/month (not counting backup price).
Click this link to order the VPS hosting (clicking this link you also earn $10).
I recently bought an UPS by the Innova company.
On the box it was written “Linux”. I opened the box and got a CD disk. On the CD was the folder “linux”. In the folder was some old broken version of the program Upsilon and no driver. (The built-in driver coming with Debian Linux also didn’t work.)
I returned the UPS to the seller.
Shame to the Innova company.
I’ve copied my
/var/www, MySQL database, and
/etc from a sever to an other server.
After this I found that my MySQL does not work anymore.
The reason for the trouble was that
/etc/mysql/debian.cnf contains (twice) an auto-generated password for the database, and so after copying my old
/etc directory from my old server the password didn’t match the new password stored in my MySQL database.
The solution: Do not overwrite
/etc/mysql/debian.cnf file when copying
/etc directory, but leave it as it was autogenerated by the new server installation script.
Note: This is a about Debian Linux.