Hi Folks,

A concept is something you need to understand to work effectively with a system.

Examples:

• To use Twitter, you need to understand tweets, hashtags and the concept of one user following another.
• To use Facebook, you need to understand posts, tags and friends.
• To use Adobe Photoshop, you need to understand pixels, layers and masks (and channels, profiles and so on).

Some concepts, such as tweets, are simple and easy to grasp; some, such as tags, are more complicated. Some systems, such as Twitter, have only a few concepts; others, such as Photoshop, have many.

Do you design your XML instances around a set of concepts? What are some concepts that users of your XML instances must understand?

The above examples and definitions come from a neat article about designing systems and applications around concepts: https://groups.csail.mit.edu/sdg/pubs/2015/concept-essay.pdf

/Roger