<feed xmlns='http://www.w3.org/2005/Atom'>
<title>progmaweb/ops/schemastore, branch site/structured-data</title>
<subtitle>The site and account service of Progmasoft: a Next.js frontend and an ASP.NET Core API.</subtitle>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/'/>
<entry>
<title>Merge main into legal/patent-grant-notice</title>
<updated>2026-11-15T16:34:39+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T16:34:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=c0d96223e2240cc61af194737e3e5dc9faa2f1d2'/>
<id>c0d96223e2240cc61af194737e3e5dc9faa2f1d2</id>
<content type='text'>
The README takes main's sentence, which no longer names the former site,
with PATENTS.md; REUSE.toml keeps the CC0-1.0 annotation of the JSON
Schemas and names AGPL-3.0-or-later alone. The Nginx file of
schemastore.progmasoft.com, new on main, gets the same SPDX expression.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The README takes main's sentence, which no longer names the former site,
with PATENTS.md; REUSE.toml keeps the CC0-1.0 annotation of the JSON
Schemas and names AGPL-3.0-or-later alone. The Nginx file of
schemastore.progmasoft.com, new on main, gets the same SPDX expression.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Serve JSON Schemas on schemastore.progmasoft.com</title>
<updated>2026-11-15T12:28:13+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T12:28:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=30b799ffe9f67aac0abe9ce8426cec8b2d6163f8'/>
<id>30b799ffe9f67aac0abe9ce8426cec8b2d6163f8</id>
<content type='text'>
schemastore.progmasoft.com/json/ holds the JSON Schemas of Progmasoft's file
formats. The first is progmasoft-cpp-index.json, which describes the
index.json of each folder of guidelines in Progmasoft/progmasoft-cpp: the
language versions with exactly one default, and every document with its
chapter, path and versions.

- ops/schemastore/json: the schemas, under CC0-1.0 (REUSE.toml, the legal
  code in LICENSES/CC0-1.0.txt) so that projects and schema catalogs can copy
  them.
- ops/schemastore/nginx/schemastore.conf: static files from
  /srv/schemastore, GET only, readable from every origin for editors in the
  browser, an hour of caching; everything outside /json/ is 404.
- ops/README.md: the install steps, the SELinux label and the rule that a
  schema which would reject files it accepted before gets a new name.

Live on 91.151.88.130; the progmasoft.com certificate names the host.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
schemastore.progmasoft.com/json/ holds the JSON Schemas of Progmasoft's file
formats. The first is progmasoft-cpp-index.json, which describes the
index.json of each folder of guidelines in Progmasoft/progmasoft-cpp: the
language versions with exactly one default, and every document with its
chapter, path and versions.

- ops/schemastore/json: the schemas, under CC0-1.0 (REUSE.toml, the legal
  code in LICENSES/CC0-1.0.txt) so that projects and schema catalogs can copy
  them.
- ops/schemastore/nginx/schemastore.conf: static files from
  /srv/schemastore, GET only, readable from every origin for editors in the
  browser, an hour of caching; everything outside /json/ is 404.
- ops/README.md: the install steps, the SELinux label and the rule that a
  schema which would reject files it accepted before gets a new name.

Live on 91.151.88.130; the progmasoft.com certificate names the host.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
</feed>
