February 7, 2017

0 0
Read Time:1 Minute, 0 Second

Data Modeling and Normalization

I’m continuing the work I started last week, focused on normalizing my and Joshua’s combined data by splitting each CIDOC entity class into its own sheet (which will be the basis of a MySQL table eventually)

As I work on the data in Google Sheets, I am creating an ER Diagram in MySQL Workbench to keep track of what data is in what sheet/table:

Linked Data Encoding

Hooland, S. v., & Verborgh, R. (2014), p. 29 mentions the Open Graph protocol:

http://ogp.me/

Hooland, S. v., & Verborgh, R. (2014) touch on the virtues of XML vs. JSON for encoding linked data. Joshua opted for JSON encoding in his work, and Prof. Pattuelli seems to prefer it as well.

According to Hooland and Verborgh, p. 42-43, data exchange on the internet occurs mostly in JSON, and JSON has an inherently hierarchical structure.

Regardless of whether JSON or XML is used to encode linked data, outside users have no idea what elements mean without the existence of a namespace.

Hooland and Verborgh are in favor of Turtle as an encoding syntax (p. 47)

Hooland, S. v., & Verborgh, R. (2014), p. 52

Happy
Happy
0 %
Sad
Sad
0 %
Excited
Excited
0 %
Sleepy
Sleepy
0 %
Angry
Angry
0 %
Surprise
Surprise
0 %