wrote stuff on object mapping

This commit is contained in:
2025-02-07 13:48:24 +01:00
parent edaee1db5a
commit 01a0a603d3
5 changed files with 59 additions and 25 deletions

View File

@@ -15,7 +15,8 @@
\acro{GUI}[GUI]{Graphical User Interface}
\acro{MASA}[MASA]{Medienagenten Secret Authority}
\acro{YAML}[YAML]{Yet Another Markup Language}
%\acroplural{CMS}[CMSe]{Content Management Systeme}
\acro{UUID}[UUID]{Universally Unique Identifier}
\acroplural{UUID}[UUIDs]{Universally Unique Identifiers}
%
%
\end{acronym}

View File

@@ -15,5 +15,17 @@
Eine arrivierte Container-Engine für Anwendungsentwicklung.
\item [Toolbox] \hfill \\
Eine Ansammlung an Werkzeugen, wie zum Beispiel Skripte.
\item [Öffentliche 1P-UUID] \hfill \\
Die 1P-UUID, die zu einem originalen Eintrag gehört, und nicht zu einer Referenz.
Externe Entwickler*innen haben also keinen direkten Zugriff auf einen solchen Eintrag, sondern müssen stattdessen eine Referenz auf diesen Eintrag verwenden.
Eine solche UUID kann beispielsweise in Ansible-Konfigurationdateien stehen
und von jedem*r Entwickler*in verwendet werden.
\item [Private 1P-UUID] \hfill \\
Die 1P-UUID, die zu einem Referenz-Eintrag gehört, und nicht zu einem originalen Eintrag. Diese Einträge sind emphemerisch und existieren ausschließlich
in den einzelnen Developer-Vaults und sind Entwickler*innen-spezifisch.
\item [Listenansicht / Listenaufruf] \hfill \\
Eine Anfrage, die eine Liste von Objekten oder Einträgen zurückgibt.
\item [Detailansicht / Detailaufruf] \hfill \\
Eine Anfrage, \emph{ein} Objekt oder \emph{einen} Eintrag zurückgibt oder manipuliert.
\end{description}

View File

@@ -2,29 +2,6 @@
# Note that authors are "and"-seperated. The comma is part of the name. Like in "Etienne, Leon".
# So if you have multiple authors, use "Peter and Werner and Mario and Johann"...
@article{bib:leossfc,
author = {Maral, Gérard and de Ridder, Jean-Jacques and Evans, Barry G. and Richharia, Madhavendra},
title = {Low earth orbit satellite systems for communications},
journal = {International Journal of Satellite Communications},
volume = {9},
number = {4},
pages = {209-225},
publisher = {Wiley Online Library},
doi = {https://doi.org/10.1002/sat.4600090403},
url = {https://onlinelibrary.wiley.com/doi/abs/10.1002/sat.4600090403},
eprint = {https://onlinelibrary.wiley.com/doi/pdf/10.1002/sat.4600090403},
abstract = {Abstract It may be that we are now entering the era of LEO constellation satellite communications after thirty years of domination by the GEO systems. This paper heralds the coming of the new era with a tutorial approach to the system design and trade-offs of LEO constellation system design. It discusses orbital configurations, network topologies and routeing considerations, multiple access schemes and link performance design. In so doing it brings out the major design parameters and how they interact with each other. Also considered are the service applications for the LEO constellation systems, and the important difference between real-time and delayed communication systems is highlighted. Examples of single and multi-beam (cellular) coverage system link designs are presented for L-Ka frequency bands. Future papers will consider aspects of the LEO spacecraft and launchers.},
year = {1991}
}
# Example Website
@misc{bib:typo3-frontpage,
author = {{TYPO3 Association}},
howpublished = "\url{https://typo3.org/}",
title = {{ TYPO3 — the Professional, Flexible Content Management System }},
year = {2024},
note = {Zugriff: Mai 2024}
}
@misc{bib:ansible,
author = {{Red Hat, Inc.}},
@@ -41,3 +18,11 @@
year = {2019},
note = {Zugriff: Januar 2025}
}
@misc{bib:1password-cli-caching,
author = {{1Password}},
howpublished = "\url{https://developer.1password.com/docs/cli/reference/#cache-item-and-vault-information}",
title = {{ Cache item and vault information }},
year = {2025},
note = {Zugriff: Februar 2025}
}