Existing Data Exchange Methods/Systems

Data Interface - how JSON is presented
1. Tables
2. Sample Data
3. HTML
  1. HTML used to display selected data from the API, and structure the web page
    1. Creates text: uses tags like <h1> and <p> to display the API responses as text for users to read.
    2. Creates menu bar: uses tags like <div> to separate parts of the webpage into different parts, like a header at the top of the page.
4. CSS
  1. Used to style the different HTML elements to make the web app engaging and interesting for the users and user persona
    1. Can change colours: use "color" property to specify a predefine CSS colour, or use a HEX code.
      1. e.g. HEX Code: "#4b1394"
Data Structures - how JSON is structured from API
1. Keys
  1. "A string that identifies a 'key-value pair'". (Opentext, n.d.).
    1. Key-value pair: made of two elements ("a constant that defines the data set" and a value). (Adobe - Experience League, 2021).
    2. e.g. "name": "Alex Terry"
2. Values
  1. Data that can be manipulated or displayed, with a specific data type. (Launch Code Education, n.d.).
    1. JSON Value Types (W3Schools, n.d.).
      1. String (e.g. "Hello, world!")
      2. Number/integer (e.g. "4" or "25")
3. Arrays
  1. JSON Structure that can hold "zero, one, or more ordered elements". These are separated by a comma (,) and stored in square brackets ([]). (Opentext, n.d.).
    1. e.g. ["Hello", 2, 8, "Purple"]
Data Specifications - different data used in JSON
1. Data Types
  1. Boolean - only two options, used as a basis to determine if a condition is met or not.
    1. i.e. "true" or "false"
  2. Null - defines a cell/element that is empty
    1. i.e. "null"
  3. Text/varchar/string - any words or characters or general text
    1. e.g. "This is some text."
  4. Integer - numbers or digits
    1. e.g. "2", "64", "123"
2. Data Length
  1. Defines the number of characters in a data value
    1. E.g. 255 characters for Dad jokes (text/varchar/string)
    2. E.g. 4 characters for small ID codes (integer/number)
    3. E.g. 10 characters for phone numbers (integer/number)
3. Constraints/validation
  1. Constraint: defines any "individual requirements" applying to specific elements in JSON (Dennis, 2023).
    1. NOT NULL
    2. AUTO INCREMENT
    3. UNIQUE
    4. NULL
  2. Validation: checks for "proper syntax and structure", "identifies syntax errors" and can confirm if JSON meets the structural requirements (Janghu & Luthra, n.d.).
    1. Privacy - usernames, passwords and emails must be the designated data type when the user inputs them (e.g. strings with a certain data length), otherwise the database cannot accept them as values.
    2. E.g. Strings must be wrapped in double quotes (" ") not single quotes (' ') (Janghu & Luthra, n.d.).
    3. E.g. Arrays must be "denoted" by square brackets ([]) (Janghu & Luthra, n.d.).
Digital Methods of Exchanging Data - ways of exchanging data
1. Protocols
2. REST Principles
  1. A guideline with conditions for API, and manages complex network communication (Amazon Web Services, n.d.).
    1. Uniform Interface: a "standard format" so that there is enough information transferred for resource modification and processing (Amazon Web Services, 2024).
    2. Write the other four REST Principles
3. JSON + XML

Nächster

Existing Data Exchange Methods/Systems

Beschreibung

Zusammenfassung der Ressource

ähnlicher Inhalt

	Erstellt von Rebbecca Stanley vor fast 2 Jahre