Package Rename about livingmarkup

[hxtree]

Object-Oriented Markup Language (OOML).

PXP is a blueprint for objects construction and interactions. Objects are optional, an object not meeting a definition are left as is in the output. Object definition templates are the things that differ and assign the object. Consider writing an RFC on the subject. Then PXP would be packaged as OOML would be an implementation of the OOML standard.

The purpose is to encapsulate the message that is a web page. A web curator should be able to do more than use markup. They should be extended backend functionality. That same message should be able to be communicated to produce search engine results. That same page should be able to be built out on the server and delivered to the client as a rebust web page. Designers should be able to author and maintain light weight dynamic code. Curators should not be permitted to crash the site. Backend engineers should be able to create the feature but should not be responsible for its implemention. There should be a separation of responsibilties. And an underlying message that can be encoded snd decoded as approperiate to different audiences. That one underlying message, is not braket based templeting engine. By nature it cannot be. It must be fluid enough to enhance the language of the web, HTML, without deverging from it. The solution proposed is renaming PXP, OOML.

[hxtree]

BYOML. Build Your Own Markup Language?

[hxtree]

It certainly is a "markup language" and should contain that in its name.

"A markup language is a computer language that uses tags to define elements within a document. It is human-readable, meaning markup files contain standard words, rather than typical programming syntax. While several markup languages exist, the two most popular are HTML and XML." https://techterms.com/definition/markup_language

[hxtree]

It's actually not a new markup language, but is standard for embedded inside an existing markup language. Not even that, it's a standard for interpreting ML as objects.

[hxtree]

Markup Language followed by a word that is an abstraction of what PXP does or vice versa. Perhaps an animal. MarkupBeaver? DynamicMarkup? MarkupQueen? MarkupPlanner? MarkupMill? MarkupFactory? MarkupDirector?

[hxtree]

MDir? MarkupDir? Markdir? Marker? Dynamdir? Dirodynam? Dirdmu?

[hxtree]

HTML is a browser markup language, meaning is consumed by the browser.

PXP is a markup language that is meant to be the means in which a message is sent and stored to build a website.
This could be helpful
https://en.wikipedia.org/wiki/List_of_markup_languages

[hxtree]

Living Markup Language

Becoming a fan of this because it represents what PXP is about best.

[hxtree]

LivingMarkup would be a good name for the package and Living Hypertext Markup Language (LHTML) would be a good name for the type of markup it consumes, which is essentially HTML with parameters to construct object and argument and call methods.

[hxtree]

Refactored PXP to LivingMarkup commit 8cd5f47