Source material and SharePoint

Evidence intake is separate from group discussion. An active group uses a separate SharePoint source-intake site with one private organisation folder per approved company domain; the Team-connected Shared Documents library is not the controlled intake boundary.

How the intake area works

The Team roster identifies approved participants.
An approved company-domain account may be placed in its organisation's contributor group.
The participant can browse the intake index and open only the organisation folder they are permitted to use.
Other participating organisations cannot view that folder or its contents.
Contributors may organise their own folder, but cannot change permissions or make material public.

A generic-provider account may take part in Teams but does not receive a provider-wide SharePoint folder. Ask OPDA to add an authorised company-domain contributor instead.

Make every submission understandable

Maintain a README at the top of the organisation area containing:

an index of submitted files and folders;
the source organisation, owner or steward;
version, date and the period for which the material applies;
the relevant working-group context and what the material demonstrates;
whether it is authoritative, informative, illustrative or disputed; and
licence, confidentiality, retention, reuse and interpretation restrictions.

Useful material

Type	Examples	What it can show
Standards and interfaces	JSON Schema, OpenAPI, AsyncAPI, GraphQL and XML Schema	Existing exchange requirements and implementation constraints.
Data structures	Data dictionaries, field lists, ER diagrams and non-production DDL	Terms, cardinalities, identifiers and dependencies.
Business material	Policies, guidance, blank forms, contracts and handbooks	Definitions, rules, obligations and exceptions.
Semantic material	RDF, OWL, SKOS, SHACL, JSON-LD and mappings	Reuse candidates, vocabularies, validation and lineage.
Examples	Anonymised scenarios, valid/invalid samples, diagrams and screenshots	Competency questions, edge cases and test expectations.
Meeting evidence	Authorised transcripts with date, speakers and context	Rationale, disagreement, corrections and open questions.

Do not submit

Personal, customer or live property-transaction data.
Passwords, API keys, credentials, private keys, connection details or other secrets.
Material restricted by confidentiality, contract, licence or NDA.
Executables, active scripts, macros, encrypted files, password-protected files or archives.
Links to websites, cloud drives, shared folders or online documents in place of the source file.

Audio and video files are not accepted through the current intake. Supply a permitted transcript with its date, speakers and context. Upload only material your organisation is authorised to share with OPDA for this work.

What happens after submission

OPDA preserves the original and screens file type, rights, sensitivity and suitability.
Approved information is registered with provenance and the relevant context.
Facilitators may use it to frame questions or model candidates.
People review any proposition before it advances beyond candidate status.

A submission is not automatically public and is not automatically shared with other participants. If SharePoint is blocked, email fallback is available only when the sender's organisation resolves from an approved company-domain identity and live SharePoint membership. Permitted, allowlisted attachments of at most 50 MiB may be accepted at smartdata@openpropdata.org.uk. Larger or unknown files require manual review; links are not followed, and the same screening and isolated organisation boundary still apply.