# Demonstration of Gemini Specification Syntax This subsection includes examples of specification syntax * Im a bullet point => gemini://icebreaker.space project-uri-for-author ``` my comment for the block IM A BLOCK'S CONTENT ``` > This is a quote # Hello World Example This is a legal Gemini document. However, because of the ability for TXR to recognise TXR syntax it appears that .gmi files can be called within the Lisp dialect. Below is a 'Hello World' example. In it the content is different between the 'raw' and 'interpreted' GemTexts ``` demonstration Hello World! ``` That is naturally something basic. However, TXR has both a pattern matching language and also a Lisp - which can be hugely powerful, given its FFI capabilities. => https://www.nongnu.org/txr/ TXR homepage Its worth providing an overview of the differences between the two GemText files: ``` sh command compiling 'raw' GemText file into 'interpreted' GemText file - influenced by specifics surrounding TXR and TXR content in the document. $ txr rq_the-trouble-with-glichen.gmi > uw_the-trouble-with-glichen.gmi ``` The diff provides an aperture regarding how this marriage of TXR and Gemini can be fruitful or a point of concern re Day-0 abuses: ``` $ diff uw_the-trouble-with-glichen.gmi rq_the-trouble-with-glichen.gmi ``` This patch effectively isolates the existence of TXR syntax and its impact on GemText content. It could be feasible for a GemText documents being treated as application meshes or for people to inject TXR capabilities into existing content to generate outcomes not planned for by the original author(s). Naturally, this raises important questions regarding: * The limitations of TXR's extensibility with respect to GemText * Whether this unexpected pairing creates a wide range of security threats