The document discusses how relational database management systems and relational modeling have dominated in the past but are declining with the rise of NoSQL databases. It argues that data modelers can save their careers by returning to focus on conceptual modeling rather than assuming relational modeling. Conceptual modeling involves communicating with users to understand entities, attributes, and relationships without implementation details. This will help data modelers choose the appropriate logical data model and adapt to changes in technologies.
Point of having a merged cell for physical: it’s all coming together – it’s increasingly difficult to distinguish the underlying physical model services…Here again, hypertext is not 1:1 with HTML – it’s beyond-the-basics hypertext as manifested, e.g., in Web publishing and collaboration-oriented systems/serversXQuery is not mainstream today, but it is exceptionally powerful and was co-developed in conjunction with XPath 2.0
Point of having a merged cell for physical: it’s all coming together – it’s increasingly difficult to distinguish the underlying physical model services…Here again, hypertext is not 1:1 with HTML – it’s beyond-the-basics hypertext as manifested, e.g., in Web publishing and collaboration-oriented systems/serversXQuery is not mainstream today, but it is exceptionally powerful and was co-developed in conjunction with XPath 2.0
Point of having a merged cell for physical: it’s all coming together – it’s increasingly difficult to distinguish the underlying physical model services…Here again, hypertext is not 1:1 with HTML – it’s beyond-the-basics hypertext as manifested, e.g., in Web publishing and collaboration-oriented systems/serversXQuery is not mainstream today, but it is exceptionally powerful and was co-developed in conjunction with XPath 2.0
Point of having a merged cell for physical: it’s all coming together – it’s increasingly difficult to distinguish the underlying physical model services…Here again, hypertext is not 1:1 with HTML – it’s beyond-the-basics hypertext as manifested, e.g., in Web publishing and collaboration-oriented systems/serversXQuery is not mainstream today, but it is exceptionally powerful and was co-developed in conjunction with XPath 2.0
Point of this slide: reinforce ability to discern major similarities/differences between two tools/services focused on similar domain, by comparing/contrasting model diagrams Non-technical people can easily learn how to read/use this type of model – not the case with most logical and physical model diagramming techniquesEvernote conceptual model fragment example from http://www.quepublishing.com/articles/article.aspx?p=1684320 Incomplete – a full conceptual model includes accompanying documentation, e.g., with entity definitions and examplesMicrosoft OneNote 2010 conceptual model fragment example from http://www.quepublishing.com/articles/article.aspx?p=1684320 Reason for including it: it provides an example, comparing it to the Evernote conceptual model fragment, of how easy it is to understand domains, when using conceptual models – e.g., the fact that OneNote has a more elaborate info item containment structure, and supports tags at the item/paragraph level, while Evernote tagging is at the note/page level. That’s not meant to be a judgment call; the extent to which Evernote or OneNote is more useful is a function of your info item/note-taking needs.
Point of this slide: reinforce ability to discern major similarities/differences between two tools/services focused on similar domain, by comparing/contrasting model diagrams Non-technical people can easily learn how to read/use this type of model – not the case with most logical and physical model diagramming techniquesEvernote conceptual model fragment example from http://www.quepublishing.com/articles/article.aspx?p=1684320 Incomplete – a full conceptual model includes accompanying documentation, e.g., with entity definitions and examplesMicrosoft OneNote 2010 conceptual model fragment example from http://www.quepublishing.com/articles/article.aspx?p=1684320 Reason for including it: it provides an example, comparing it to the Evernote conceptual model fragment, of how easy it is to understand domains, when using conceptual models – e.g., the fact that OneNote has a more elaborate info item containment structure, and supports tags at the item/paragraph level, while Evernote tagging is at the note/page level. That’s not meant to be a judgment call; the extent to which Evernote or OneNote is more useful is a function of your info item/note-taking needs.