BHyland added h3 in modeling section.
Thu, 19 Dec 2013 14:14:28 -0500
changeset 759 4a761a202663
parent 758 880e0d13b339
child 760 7f6ff5589f47
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.  
+<h3>Data Relationships and Context</h3> 
 In general, data modeling requires an understanding of the category of database being used, for example relational or NoSQL.  An <a href=""> 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 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="">RDFa</a>, <a href="">, <a href="">Turtle</a> and <a href="">RDF/XML</a>) and <a href="">SPARQL</a> for query.