Use these definitions as a working vocabulary. A corporate agreement should add owner, context and version if a term can be interpreted in different ways.
Government language
| Term | Meaning at the workshop | Useful distinction |
|---|---|---|
| Data governance | Authority, decisions and monitoring of data use | Management implements decisions |
| Data owner / owner | Responds for a domain and its use decisions | It doesn't mean I have to manage the base. |
| Data steward | Watch out for definitions, rules and incident resolution | Do not replace owner at risk acceptance |
| Custodian | Implement and operate technical controls | The administrative permission does not confer authority over all aims |
| Data product | Data with purpose, consumers, owner and conditions of service | A standalone table does not express all these agreements |
| Data contract | Extent agreement on structure, meaning, quality, access and changes | It's bigger than the technical scheme. |
| PII | Information that identifies or can be linked to a person | Treatment depends on the applicable context, combination and policy |
| Purpose | authorized and defined use for a data | A reading permission does not allow any use |
| Consent | Registration of an election for an aim and duration | It isn't summed up as a universal brand for all relationship with a client |
| Maestro datus | Shared representation of a business entity | The transactions describe events of these entities |
| Reference datum | Controlled values that classify other data | Example: states contract valid |
| Golden record | Consolidated representation by correspondence and survival | It doesn't mean choosing all the fields from the most recent row |
| The quality rule | Measurable and contextual aptitude condition | "Cleaner" with no metric or threshold cannot be decided |
| SLA / SLO | Service commitment / measurable service target | In this case they are fictitious agreements, and they are not guarantees of a product. |
The examples and definitions are original synthesis for this workshop.
Section 3
| Term | Meaning at the workshop | Useful distinction |
|---|---|---|
| Oracle AI Data Platform | AI data and asset engineering | Platform that combines engineering and AI assets with access controls |
| Oracle Autonomous AI Lakehouse | Oracle Autonomous AI Database modality with analytic data and AI | His role is explained by his capacity, not as a substitute for every source system. |
| Catalog | Organization of assets and their metadata | Each product has its own scope and interface |
| Glossary | Business definitions with context and accountability | A list of tables isn't a corporate glossary |
| Methate | Information describing data, structures, uses or operations | Can be entrepreneurial, technical or operational |
| Lineage | Provenance and processing relations | Section of entity and figure of a column answer different questions |
| Impact analysis | Identification of units affected by a change | The cover depends on what's been captured by tools |
| Ontology | Model concepts, relationships and restrictions of a domain | It does not amount to renaming columns or a catalogue of services |
| Semantic model | Definitions that link data with concepts and indicators | Requires business validation, even if suggested by a AI |
| RBAC | Role-based access | The inherited privileges also count at effective access |
| CDC | Capture of changes from a source | Reducing latency does not validate quality or permissions |
| Federation | Logic access to sources with configured connections | It doesn't mean copying anything or automatically spreading identities. |
| Iceberg REST catalogg | Catalogue interface for tables Apache Iceberg | Managing metadata does not eliminate control of storage |
| Delta Sharing | Data-sharing protocol with authorized recipients | That doesn't mean giving access to all the files of a workspace. |
| Mocking / drafting | Retirement of copies and concealment of values at consultations, as required by the mechanism | Review persistence and scope Do not exchange their names without explaining the effect |
| RAG | Recovery of information to underpin a generative response | Recovery of a fragment does not confirm authorisation or accuracy response |
| Quarantine | Separation of registries that have failed to meet criteria | It should preserve motif, owner and resolution path |
| Custom Control | Regulation implemented using SQL, code or workflow | Linkages owner's decision with its execution, result and review |
The applications of each product and its official documentation are met at the capacity matrix. Use that matrix as we discuss Inclusive case.