#magic terms

witchroleic

A roleic term for a system member whose role, status, or experience as a system member involves witches or being a witch in some way. This could involve: -having a magic-related origin or role -comparing your role to being a witch -being an introject of a witch character However, it could involve anything

Manitouwabi (Muh-nih-too-wuhbee)

-- Spirit

Geebawug (jee-buh-wugg)

-- Spirits

maji-manidoo (muh-jhee-muhnih-doo)

 --  an evil spirit, a devil

maji-manidoowaadizi (muh-jhee-muhnih-doo-wah-dizzy)

--  s/he is evil, is possessed by an evil spirit

manidoowi (muh-nih-doo-way)

--  s/he is or becomes a manitou, a spirit, god

maji-mashkiki (muh-jhee-muh-shkih-kih)

-- poison; bad medicine: a remedy or spell having or intended to have negative results

Neegoniwabungigaywin (knee-gonni-wuh-bung-igg-uhyy-win)

magicroleic

A roleic term for a system member who considers magic to be part of their role or status as a system member, without it inherently being the role itself. This may involve a system member who: -originated through magic -has a system role that involves performing magic -is an introject from something or has a timeline involving magic -uses magic for anything that involves the system However, it can involve anything.

wizardroleic

A roleic term for a system member whose role, status, or experience as a system member involves wizards or being a wizard in some way. This could involve: -having a magic-related origin or role -comparing your role to being a wizard -being an introject of a wizard character However, it could involve anything

Just a brief note on using magic terms v Linked Data, an organization can still define camera-aerial, it just would be as a URI rather than that exact phrase that you'd have to look up in a document. e.g. it would be https://somestandard.org/camera-aerial. This has several advantages:

it's obvious where to find the definition: at https://somestandard.org/camera-aerial. If you have Content-Type: application/xml it's not obvious where Content-Type or application/xml are defined, you have to go look them up somewhere. Obviously too late to change that decision though!

it can be gracefully shortened using QNames, e.g. standard:camera-aerial

if I need to define something that's not envisioned by the standard, I don't have to do x-my-thing

if two different organizations define camera-aerial, there's zero chance of a naming conflict

if two different organizations define camera-aerial, it's fairly straight forward to define mappings between the usages

it really isn't that wordy!

Tim Berners-Lee likes it!