Juniper Workspace Cloud: Register of members JSON
Register of members JSON for Juniper Workspace Cloud. The same 4 members plus the two cancelled certificates the CSV cannot hold, because a cancelled certificate has no current holding and would need a row with an empty share count. A reader that counts certificates from this file gets six; a reader that counts holdings gets four.
json
application/json
- Document Set
- corporate
- Industry
- software
- Source Kit
- saas-subscriptions
- Entity
- Juniper Workspace Cloud
- Synthetic
- true
- As Of
- 2026-09-08
Binary json: no in-browser preview. Download it above to open in a compatible application.
Specifications
- Document Set
- corporate
- Industry
- software
- Source Kit
- saas-subscriptions
- Entity
- Juniper Workspace Cloud
- Synthetic
- true
- As Of
- 2026-09-08
- Members
- 4
- Live Certificates
- 4
- Cancelled Certificates
- 2
Testing contract
Expected to pass- Scenario
- Count the certificates and the members separately.
- Expected result
- There are 4 members holding 600,000 shares under four live certificates, and a separate array of two cancelled certificates, SC-002 and SC-003, both cancelled on 2026-07-06 when the transfer was registered.
What is a .json file?
JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.
How to use this file
Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.
How to use this file for testing
“Juniper Workspace Cloud: Register of members JSON” is a deterministic Novus Examples fixture for Data import, JSON parsing. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.
Documented properties for this file: JSON · 2,388 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.
Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.
Code examples
import json
with open("register-of-members.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonJuniper Workspace Cloud: Annual return JSONAnnual return JSON for Juniper Workspace Cloud. The same five parts as a nested object with shareCapital, members, officers, personsWithSignificantControl and charges arrays. Numbers that are counts are JSON numbers and numbers that are money are strings with two decimals, so a reader that coerces everything to float loses the trailing zero on 6000.00 and on 14400.00.
- jsonJuniper Workspace Cloud: Corporate reconciliation identitiesCorporate reconciliation identities for Juniper Workspace Cloud. 6 named identities covering the issued and paid capital, the allotment split, the neutrality of the transfer, the resolution threshold and the trading figures the September minutes quote, with the numbers behind each. The deliberate defect and its 500 share shortfall are listed separately.
- jsonAlder Books Reconciliation: Banking reconciliation identitiesBanking reconciliation identities for Alder Books Reconciliation. 5 named identities covering the amortisation, the unfinanced arrangement fee, the covenant directions, the direct debit control sum and the two different chargeback totals, with the figures behind each. The deliberate defect and its measured 36.15 USD closing balance are listed separately.
- jsonAlder Books Reconciliation: Credit application JSONCredit application JSON for Alder Books Reconciliation. The same application as an object, with each financial summary row keeping the source string that names the file and column it came from. The connected facility is a nested object rather than a string, so a reader can tell that the existing borrowing belongs to a different entity.
- jsonAlder Table Bistro: Cost of goods sold documentCost of goods sold document for Alder Table Bistro. The same statement as JSON, listing all 24 purchase ids it consumed so the total can be checked against the shared purchases table by id. Totals: opening 1736.91, purchases 2834.82, closing 2996.92, cost of goods sold 1574.81 CAD.
- jsonAlder Table Bistro: Daily Z-read as structured dataDaily Z-read as structured data for Alder Table Bistro. The same Z-read as JSON: 4 item lines, a summary block, 3 tender lines that sum to the total collected, 2 voids, one comp, 1 refund traced to its sales id, and a cash drawer block whose expected figure less the counted figure equals the declared over/short of -0.35 CAD.
Generated by generation/industry_documents_two.py. Free for any use, no attribution required, license.