Schema One or more schemas describe the entity model exposed by an OData service. The schema acts as a namespace for elements of the entity model such as entity types, complex types, enumerations and terms. A schema is identified by a . Schema namespaces MUST be unique within the document, and SHOULD be globally unique. A schema cannot span more than one document. The schema’s namespace is combined with the name of elements in the schema to create unique , so identifiers that are used to name types MUST be unique within a namespace to prevent ambiguity. See for more details. The namespace MUST NOT be one of the reserved values Edm, odata, System, or Transient. Schema Object A schema is represented as a member of the document object name is the schema namespace. Its value is an object that MUST contain a member and MAY contain a member . The schema object MAY contain members representing , , , , , , , and an . The schema object MAY also contain that apply to the schema itself. Alias A schema an alias which MUST be a . he alias used . Aliases are document-global, so all schemas defined within or included into a document MUST have different aliases. Aliases defined by a schema can be used throughout the containing document and are not restricted to the schema that defines them. The alias MUST NOT be one of the reserved values Edm, odata, System, or Transient. $Alias The value of $Alias is a string containing the alias for the schema. Example : document defining a schema org.example with an alias and a description for the schema { "$Version": "4.01", "org.example": { "$Alias": "self", "@Core.Description": "Example schema", … }, … } Annotations with External Targeting $Annotations The value of $Annotations is an object with one member per . The member name is a path identifying the , the member value is an object containing for that target. Example 7: annotations targeting the Person type with qualifier Tablet "org.example": {
Schema One or more schemas describe the entity model exposed by an OData service. The schema acts as a namespace for elements of the entity model such as entity types, complex types, enumerations and terms. A schema is identified by a . Schema namespaces MUST be unique within the document, and SHOULD be globally unique. A schema cannot span more than one document. The schema’s namespace is combined with the name of elements in the schema to create unique , so identifiers that are used to name types MUST be unique within a namespace to prevent ambiguity. See for more details. The namespace MUST NOT be one of the reserved values Edm, odata, System, or Transient. Schema Object A schema is represented as a member of the document object name is the schema namespace. Its value is an object that MUST contain a member and MAY contain a member . The schema object MAY contain members representing , , , , , , , and an . The schema object MAY also contain that apply to the schema itself. Alias A schema an alias which MUST be a . he alias used . Aliases are document-global, so all schemas defined within or included into a document MUST have different aliases. Aliases defined by a schema can be used throughout the containing document and are not restricted to the schema that defines them. The alias MUST NOT be one of the reserved values Edm, odata, System, or Transient. $Alias The value of $Alias is a string containing the alias for the schema. Example : document defining a schema org.example with an alias and a description for the schema { "$Version": "4.01", "org.example": { "$Alias": "self", "@Core.Description": "Example schema", … }, … } Annotations with External Targeting $Annotations The value of $Annotations is an object with one member per . The member name is a path identifying the , the member value is an object containing for that target. Example 7: annotations targeting the Person type with qualifier Tablet "org.example": {
odata-csdl-json-v4.01-wd01-2017-03-10.docx