1. JSON namespaces can be accessed immediately after receiving data.
2. JSON namespaces can be accessed after parsing data.
3. JSON doesn't have namespaces. Though every object is inherently a namespace.
JSON doesn't have namespaces. Though every object is inherently a namespace.
1. A lightweight data-encoding framework. Java Omnipresent Notation.
2. A lightweight data-interchange format. JavaScript Object Notation.
3. A lightweight data-interchange format. Java Objective Notion.
4. A lightweight database framework. JavaScript Object Notation.
A lightweight data-interchange format. JavaScript Object Notation.
1. True
2. False
True
1. Error in Script
2. '20'30
3. 2030
4. 50
50
1. Primitive
2. Reference types
3. All of the above
4. None of the above
All of the above
1. for
2. while
3. forwhich
4. dowhile
while
1. JavaScript Object Nomenclature
2. JavaScript Objective Notation
3. JavaScript Object Notation
4. JavaScript Orientated Nomenclature
JavaScript Object Notation
1. JSON is more forgiving of poor formatting
2. JSON has less markup requirements and therefore is lighter than XML
3. JSON can be written poorly and still be parsed
4. JSON does not need to be stored in a file to be sent remotely
JSON has less markup requirements and therefore is lighter than XML
1. to style HTML pages
2. to execute Queries related to databases on a server
3. to add interactivity to html pages
4. All of the above
All of the above
1. Pass marks are 35
2. 35
3. Pass marks are35
4. Exception
Pass marks are35