XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Designing XML instances around concepts?

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

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS