Final One

Final One

1. Data Interface

   • Tables
     • Row
       • A row refers to a horizontal arrangement of data in a table
     • Column
       • A column refers to a vertical arrangement of data in a table
     • Cell
       • A cell refers to a single piece of data located anywhere in a table
     • Headings
       • A heading refers to the title of a column or rows
   • Sample Data
     • XML
     • JSON
   • HTML
   • CSS

2. Data Structures

   • JSON
     • Value
       • A Value can be a number, string, or an array etc.
     • Array
       • An array are orderd lists of values enclosed within square brackets
     • Objects
       • Objects are enclosed within curly brackets and consist of key-value pairs. Keys are strings, and values can be any valid JSON data type
   • XML
     • Attributes
       • Attributes provide additional information about an element. They are specified within the start tag of an elemnt and consist of a name-value pair. Attributes are handy for providing metadata or additional details about an element
     • Comments
       • Comments allow you to include context and annotations within an XML document. They are enclosed within <!-- and --> delimiters
     • Namespaces
       • Namespaces allow elements and attributes to be identified uniquely in XML documents. They help avoid naming conflicts in XML documents
     • Elements
       • Elements are the fundamental building blocks of an XML document. They are enclosed within start and end tags, and can contain other elements, text, or attributes

3. Data Specification

   • Data Types
     • Time
     • Date
     • Boolean
     • Integer
     • Null
     • Array
     • Object
   • Data Length
     • 255
   • Constraints/validation
     • JSON and XML do not have built-in tools to verify the format, content, or structure of the data; this makes it difficult to debug the data
     • JSON
       • Schema
         • Allows users to describe the structure, format, and constraints of JSON data. It provides a way to define schemas that can be used to validate JSON documents
       • External Methods
         • Database Constraints: if the JSON data is stored in a database, users can utilize database constraints to enforce data validation rules
         • Custom Code: Users can write custom codes or use programming languages with built-in validation capabilities such as Python. By parsing the JSON data and writing custom validation logic, users can check for specific condition, types, ranges, or other constraints
     • XML
       • Schema
         • XML schema is a way to define the structure and constraints of an XML document. It provides a set of validation rules and allows users to define data types, element relationships, uniqueness constraints, and more
       • External Methods
         • Document Type Definition (DTD) is a simple way to define the structure and constraints of an XML document. It specifies the elements, attributes, and entity declarations allowed in the XML document. By defining a DTD, users can enforce constraints on the XML data, such as element order, data types, and cardinality.
         • Schematron is a rule-based validation language for XML. It allows users to define validation users using XPath expressions. It focuses on business and application-specific contraints that may be difficult to express using DTD or XML Schema alone

4. Digital Methods of Exchanging Data

   • Protocols
     • Transmission control protocol
       • TCP is connection-oriented protocol that establishes a connection between two devices and breaks the transmitting data into segments that are reassembled at the receiving end. This ensures that reliable data transfers can occur between devices
     • User datagram Protocol
       • UDP is a connectionless protocol that provides fast transmission such as video streaming. However, it does not provide error checking or reliability guarantees
     • Hypertext transfer protocol
       • HTTP is mainly used for webpages of the internet; it ensures that webpages are displayed correctly on the browsers and defines how webpages and servers should connect with each other
     • Hypertext transfer protocol secure
       • HTTPS is an extended version of HTTP; it is widely used on the internet for secure communication over a computer network. The communication protocol is encrypted using Transport Layer Security
     • File transfer Protocol
       • FTP provides a standardized way for devices to exchange secure encryption. It is used between devices on a network
     • Simple Mail Transfer Protocol
       • SMTP is used to send and receive emails over a network. It ensures that emails are delivered correctly
     • Domain Name System
       • DNS is used for translating a domain name into an IP address. It takes a language that humans can read and translate into an IP address that a computer can understand
   • REST Principles
     • Pros
       • REST services are stateless, meaning each request contains all the neccecary information making them scalable and highly cacheable
       • REST allows for a wide range of data formats and supports various protocols
       • REST is a straight forward and easy to understand service, making it easier to develop and matain APIs
     • Cons
       • REST APIs might require multiple round trips to the server to accomplish a task, leading to higher network overhead
       • REST is primarily used for CRUD applications and may not prvide built-in features for advancedd functionalities like transaction and security
       • REST does not have a strict standard like SOAP, which can lead to inconsistencies in how APIs are designed
   • JSON
     • Pros
       • JSON comprises smaller file sizes and faster data transmission compared to XML
       • JSON is simple and concise, meaning that it is easier to code
       • JSON is better for data transfers due to it storing data in arrays
       • JSON is quite easy to parse, especially in programming languages that have built in support such as JavaScript
     • Cons
       • JSON lacks some advanced features compared to XML such as namespaces and attributes
       • JSON does not have built in tool to verify the format, content, or structure of the data; this makes it difficult to debug the data
       • JSON has limited data type options; this prevents it from representing certain types of data such as binary
   • XML
     • Pros
       • XML supports namespaces meaning that data can be easily combined without name conflicts
       • XML is extendable, meaning that new modifications can be made to the structure without disrupting existing functionalities
       • XML supports complex data types such as timestamps and binary data
     • Cons
       • XML is less flexible since it has a more ridged data structure compared to JSON, making it more difficult to change without breaking the document
       • XML structures are harder to read and write since they are more complex
       • The file sizes of XML are larger than JSON
   • SOAP Principles
     • Pros
       • SOAP provides a standardized way of handling errors and exceptions
       • SOAP supports advanced features like security transactions, reliability, and message-level integrity
       • SOAP has a well-defined standard and protocol for building web sevices
     • Cons
       • SOAPs popularity has decreased due to users favouring REST for public-facing APIs
       • SOAP primarily uses SML for data reqpresentation, limiting the options for data formats
       • SOAP is more complex than REST, requiring addition layers of protocols

Imagens e arquivos do mapa