Abstract: A system allows translation across API models represented using different API description languages. The system stores model bindings from a common visualization model format to multiple API description languages. The model bindings map constructs of the API description language to and from modeling constructs of the common visualization model format. The system uses the model bindings to convert API models to and from representations based on API description languages to the common visualization model format. The system used the common visualization model format to generate visualizations of the API model that can be displayed via a user interface and also allow users to modify the API model.

Abstract: Techniques are disclosed relating to the serialization of data of a database. A computer system may maintain a database that stores data as a plurality of triples. A triple may include a first data entity that is connected to a second data entity via an edge, and triples of the plurality of triples may be connected to form graphs. The computer system may store metadata defining types of edges between data entities. An edge's type may indicate a procedure for serializing a target data entity connected to that edge's type. The computer system may receive a request to access a data entity associated with a plurality of descendant data entities connected to the data entity via edges. The computer system may generate an output having the data entity and one or more of the plurality of descendant data entities that are serialized according to the types of edges.

Abstract: Techniques are disclosed relating to the garbage collection of data of a database. A computer system may maintain a database that stores data as a plurality of triples. A given triple may include a first data entity that is connected to a second data entity via an edge, and triples of the plurality of triples may be connected to form a plurality of graphs. The computer system may store metadata that defines strengths of edges between graphs of the plurality of graphs. The computer system may receive a request to delete a particular triple or graph of the plurality of graphs. The particular graph may include a set of edges originating in the particular graph to other graphs of the plurality of graphs. The computer system may determine, based on the stored metadata, which graphs of the other graphs to delete in addition to the particular graph.

Abstract: Techniques for maintaining a data dictionary within a computing platform that provides a multitenant environment in which multiple tenants utilizing the multitenant environment share a single instance of a database. The data dictionary is maintained with referential integrity utilizing custom database objects to provide metadata corresponding to the data dictionary. The data dictionary tracks attributes for the custom database objects utilizing natively supported field attributes and the custom database objects maintain tenant-specific information. The custom database objects are automatically updated corresponding to the data dictionary. A notification to one or more users is generated for custom database objects that correspond to the data dictionary that cannot be updated automatically, if any.

Abstract: Data field lifecycle management mechanisms. Custom metadata about a database object is generated. The custom metadata includes at least a specified name for the custom metadata type, a specified one or more fields to contain configuration information for the custom metadata type, and specification of at least one relationship field having fields as its domain relating the custom metadata type to a column or field of the database object stored in a database. One or more objects of the custom metadata type are maintained with referential integrity to provide metadata corresponding to the database object. The custom metadata objects maintain tenant-specific information. The one or more objects of the custom metadata type are updated automatically. A notification to one or more users is generated for one or more objects of the custom metadata type that cannot be updated automatically, if any.

Abstract: Data field lifecycle management mechanisms. Custom metadata about a database object is generated. The custom metadata includes at least a specified name for the custom metadata type, a specified one or more fields to contain configuration information for the custom metadata type, and specification of at least one relationship field having fields as its domain relating the custom metadata type to a column or field of the database object stored in a database. One or more objects of the custom metadata type are maintained with referential integrity to provide metadata corresponding to the database object. The custom metadata objects maintain tenant-specific information. The one or more objects of the custom metadata type are updated automatically. A notification to one or more users is generated for one or more objects of the custom metadata type that cannot be updated automatically, if any.

Abstract: Techniques for maintaining a data dictionary within a computing platform that provides a multitenant environment in which multiple tenants utilizing the multitenant environment share a single instance of a database. The data dictionary is maintained with referential integrity utilizing custom database objects to provide metadata corresponding to the data dictionary. The data dictionary tracks attributes for the custom database objects utilizing natively supported field attributes and the custom database objects maintain tenant-specific information. The custom database objects are automatically updated corresponding to the data dictionary. A notification to one or more users is generated for custom database objects that correspond to the data dictionary that cannot be updated automatically, if any.

Abstract: Data field lifecycle management mechanisms. Custom metadata about a database object is generated. The custom metadata includes at least a specified name for the custom metadata type, a specified one or more fields to contain configuration information for the custom metadata type, and specification of at least one relationship field having fields as its domain relating the custom metadata type to a column or field of the database object stored in a database. One or more objects of the custom metadata type are maintained with referential integrity to provide metadata corresponding to the database object. The custom metadata objects maintain tenant-specific information. The one or more objects of the custom metadata type are updated automatically. A notification to one or more users is generated for one or more objects of the custom metadata type that cannot be updated automatically, if any.