#axiomagic 검색 결과

#AxioMagic science app in client *or* service may fetch RDF as LDF, or as JSON-LD, SPARQL, #RdfJs linkeddatafragments.org/in-depth

Stu_B22's tweet image. #AxioMagic science app in client *or* service may fetch RDF as LDF, or as JSON-LD, SPARQL, #RdfJs linkeddatafragments.org/in-depth
Stu_B22's tweet image. #AxioMagic science app in client *or* service may fetch RDF as LDF, or as JSON-LD, SPARQL, #RdfJs linkeddatafragments.org/in-depth

#AxioMagic seeks to ease this mental challenge of cross referencing by addressing taxonomy, name-ref and alignment issues improving usability in "Organization" and "Tabulation" dimensions of #Tetrapod using E. Martin's points 3, 5, 7 as inspiration:


Discussing open web data apis for interactive science apps (like #AxioMagic), where "standard" has varying meaning, and some may prefer GraphQL, JsonLD...

Agree that strong-typed Java/Scala services on the backend are the way to go. But the API to that backend must be as standard and neutral as possible, using OpenAPI and JsonSchema. openapis.org Then presentation/GUI can be anything.



The primary deliverable of #AxioMagic is type specification for service boundary between math KB (server) and UI (client) components. This boundary is data-centric and technology-agnostic

#AxioMagic service boundary definition 1) UI lives on near side of protocol boundary(-s) 2) AI + storage both live on far side of protocol bounds 3) Messages crossing bounds describe/refer-to : Records having a) Field values, which inhabit types b) Metadata



#AxioMagic boundary API message-records ultimately contain FAIR references and copies from these open input knowledge sources, plus wikidata, arxiv, nCat-Lab, PLUS other special sauce mixed in for given use case

Presume such a cross-reference of multiple knowledge sources produces consolidated browsable snapshots, including aligned URI references for spaces like + Math Subject Classification (MSC2020) + Wikipedia + useful libraries of proofs in Lean, Isabelle, other + other named stuff



Hmm, "system" here might imply that #AxioMagic supports real apps, which isn't a priority goal at present. Rather we focus on exploring structure patterns that are helpful in interactive study of college+ material, as used by researchers who have evolving opinions.

We address the above use case with an intensional type system for a browsable math-concept reference KB, following the #TetrapodMathKnowledge paradigm:



study brk from intros at Stanford Encyclopedia of Phil, incl category theory = plato.stanford.edu/entries/catego… - note citations of J.C. Baez + section "5. cat theory and type theory" => types = plato.stanford.edu/entries/type-t… proofs may use Lean math lib = leanprover-community.github.io => #AxioMagic

이 트윗은 더 이상 사용할 수 없습니다.

#AxioMagic uses #AsciiMath = asciimath.org for math expressions whenever possible. Also supports other #MathJax eqn formatting, thus generally equivalent to #DokieLi math features. (Both rely on solidproject.org for auth+perm)

🎞️ dokie.li mathematics support: #MathML #LaTeX #ASCIIMath syntaxes via @MathJax from dokieli's authoring UI.



#AxioMagic boundary API message-records ultimately contain FAIR references and copies from these open input knowledge sources, plus wikidata, arxiv, nCat-Lab, PLUS other special sauce mixed in for given use case

Presume such a cross-reference of multiple knowledge sources produces consolidated browsable snapshots, including aligned URI references for spaces like + Math Subject Classification (MSC2020) + Wikipedia + useful libraries of proofs in Lean, Isabelle, other + other named stuff



The primary deliverable of #AxioMagic is type specification for service boundary between math KB (server) and UI (client) components. This boundary is data-centric and technology-agnostic

#AxioMagic service boundary definition 1) UI lives on near side of protocol boundary(-s) 2) AI + storage both live on far side of protocol bounds 3) Messages crossing bounds describe/refer-to : Records having a) Field values, which inhabit types b) Metadata



Hmm, "system" here might imply that #AxioMagic supports real apps, which isn't a priority goal at present. Rather we focus on exploring structure patterns that are helpful in interactive study of college+ material, as used by researchers who have evolving opinions.

We address the above use case with an intensional type system for a browsable math-concept reference KB, following the #TetrapodMathKnowledge paradigm:



#AxioMagic seeks to ease this mental challenge of cross referencing by addressing taxonomy, name-ref and alignment issues improving usability in "Organization" and "Tabulation" dimensions of #Tetrapod using E. Martin's points 3, 5, 7 as inspiration:


study brk from intros at Stanford Encyclopedia of Phil, incl category theory = plato.stanford.edu/entries/catego… - note citations of J.C. Baez + section "5. cat theory and type theory" => types = plato.stanford.edu/entries/type-t… proofs may use Lean math lib = leanprover-community.github.io => #AxioMagic

이 트윗은 더 이상 사용할 수 없습니다.

#AxioMagic uses #AsciiMath = asciimath.org for math expressions whenever possible. Also supports other #MathJax eqn formatting, thus generally equivalent to #DokieLi math features. (Both rely on solidproject.org for auth+perm)

🎞️ dokie.li mathematics support: #MathML #LaTeX #ASCIIMath syntaxes via @MathJax from dokieli's authoring UI.



#AxioMagic science app in client *or* service may fetch RDF as LDF, or as JSON-LD, SPARQL, #RdfJs linkeddatafragments.org/in-depth

Stu_B22's tweet image. #AxioMagic science app in client *or* service may fetch RDF as LDF, or as JSON-LD, SPARQL, #RdfJs linkeddatafragments.org/in-depth
Stu_B22's tweet image. #AxioMagic science app in client *or* service may fetch RDF as LDF, or as JSON-LD, SPARQL, #RdfJs linkeddatafragments.org/in-depth

Discussing open web data apis for interactive science apps (like #AxioMagic), where "standard" has varying meaning, and some may prefer GraphQL, JsonLD...

Agree that strong-typed Java/Scala services on the backend are the way to go. But the API to that backend must be as standard and neutral as possible, using OpenAPI and JsonSchema. openapis.org Then presentation/GUI can be anything.



#AxioMagic science app in client *or* service may fetch RDF as LDF, or as JSON-LD, SPARQL, #RdfJs linkeddatafragments.org/in-depth

Stu_B22's tweet image. #AxioMagic science app in client *or* service may fetch RDF as LDF, or as JSON-LD, SPARQL, #RdfJs linkeddatafragments.org/in-depth
Stu_B22's tweet image. #AxioMagic science app in client *or* service may fetch RDF as LDF, or as JSON-LD, SPARQL, #RdfJs linkeddatafragments.org/in-depth

Loading...

Something went wrong.


Something went wrong.


United States Trends