Human Markup Language

Human Markup Language (also HumanML and, within the context of a HumanML document, huml) is an XML specification developed to contextually describe physical, kinesic, cultural, and social information about instances of human communication. Development by OASIS began in 2001,[1] and HumanML committee members released a Human Markup Language Primary Base Specification 1.0 in late 2002.[2]

Purpose

HumanML was proposed to "fundamentally enhance the human communications process, through the use of XML, with the purpose of ending human misunderstanding".[1] It addresses this purpose by standardizing the presentation of details relevant to communicative acts. Such details may be social, contextual, gestural, or psychological, and may pertain to an individual in an act of communication or to the context of that communication. For example, just as Internet users may use emoticons ("smileys") to convey emotional information relevant to their essentially textual communication, HumanML codes the emotional importance and intent of a signal in a series of markup tags. The standard aims to provide an arbitrarily detailed way to represent information pertinent to any act of communication.

gollark: > it seems like you're talking more about an API?Yes, I think the ability to do that might be more useful to (some) external services than having UI in Athens itself.> Dokuwiki does seem interesting thoughIt's a pretty good selfhosted wiki engine. It doesn't have knowledge-graph-y features because it was mostly made before that became a topic of interest, but does have... search, links, somewhat okay formatting, and many plugins. I currently run an instance because it seemed the best available stable thing when I was setting up things and it is quite hard to migrate now.
gollark: Sorry if I'm explaining this somewhat badly. I can probably clarify. I mean something like this (https://www.dokuwiki.org/plugin:struct) but without necessarily having to define a schema somewhere. I think this would be good for a few categories of thing, such as, say, exporting a list of cards (defined in notes) into a spaced repetition system. Possibly calendar events/reminders too, but you'd probably want a way to remove expired ones.
gollark: Regarding integration/plugins (I didn't see this being thought of here before or on github when I did a search, but my queries might have been bad): a nice/general way to integrate some types of external service without having to integrate per-service code could be to have a way to have blocks containing arbitrary machine-readable data (with a nice UI to edit it) and a type field, and an API to find all/all recent blocks with a given type.
gollark: It has fancy diagrams.
gollark: https://lhartikk.github.io is cool.

See also

References
  1. Thunga, Rajneeth Kumar & Karl Best. Call for Support.
  2. Brooks, Rex, ed. Human Markup Language Primary Base Specification 1.0.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.