BHyland added h3 in modeling section.
--- a/bp/index.html Thu Dec 19 14:12:11 2013 -0500
+++ b/bp/index.html Thu Dec 19 14:14:28 2013 -0500
@@ -356,6 +356,7 @@
The modeling process for Linked Data requires participants who represent a range of concerns including one or more people familiar with the existing data workflow and data policies. It is helpful to include a database administrator (DBA) and/or someone responsible for data collection. Ideally, a Linked Data subject matter expert will help facilitate the Linked Data modeling process. Their role is to help explain both the similarities, differences and benefits of a Linked Data approach.
</p>
+<h3>Data Relationships and Context</h3>
<p>
In general, data modeling requires an understanding of the category of database being used, for example relational or NoSQL. An <a href="http://www.w3.org/TR/ld-glossary/#rdf-database"> RDF database</a> is a type of NoSQL database and the only type based on an international family of standards.[[DWOOD2013]] Linked Data uses RDF as its data model because RDF is the international standard for representing data on the Web. RDF databases are built on well-established and widely deployed standards including <a href="http://www.w3.org/TR/ld-glossary/#http-uris">HTTP URIs</a>. Thus, one important difference between relational databases versus Linked Data is in the use of international standards for data interchange (e.g., <a href="http://www.w3.org/TR/ld-glossary/#rdfa">RDFa</a>, <a href="http://www.w3.org/TR/ld-glossary/#json-ld">, <a href="http://www.w3.org/TR/ld-glossary/#turtle">Turtle</a> and <a href="http://www.w3.org/TR/ld-glossary/#rdf-xml">RDF/XML</a>) and <a href="http://www.w3.org/TR/ld-glossary/#sparql">SPARQL</a> for query.
</p>