[ ] LookupValue and LookupDisplayName Enforcement - Standard LookupValue items were added to the Data Dictionary 1.7 reference sheet to provide a specification for those using OData Edm.EnumType enumerations. These items have been carried over to the Data Dictionary 2.0 reference sheet as well. Systems will be checked using a number of techniques, including edit distance matching, to ensure that they're using the standard values, when appropriate. For those using Edm.String values with the Lookup resource, the LookupDisplayName will be checked as well. (In Progress)
[ ] Resource and Field Name Enforcement - Similarity metrics and other heuristics will also be used to ensure that standard names are being used for resources and fields as well.
[ ] Data Validation Against Server Metadata - The Data Dictionary 1.7 Specification didn't include strict checking of data available on a given server against its advertised metadata. In Data Dictionary 2.0, these two items MUST match. This means that providers will fail testing if resources, fields, or enumerations appear in the data set that weren't advertised on the server. Similar is true in cases where fields, such as Edm.String, exceed their advertised data length, or any other similar data anomalies. See #94.
[ ] Reference Spreadsheet Structure - Previously there were individual sheets for each resource. They have been merged into a single sheet called "Fields," which also matches the format of the new Field metadata resource. The resource that each field belongs to will be indicated in the Field entry. Enumerations will be in a separate Lookups sheet.
Add support for Data Dictionary 2.0.
This issue consists of the following tasks:
[ ]
LookupValueandLookupDisplayNameEnforcement - StandardLookupValueitems were added to the Data Dictionary 1.7 reference sheet to provide a specification for those using ODataEdm.EnumTypeenumerations. These items have been carried over to the Data Dictionary 2.0 reference sheet as well. Systems will be checked using a number of techniques, including edit distance matching, to ensure that they're using the standard values, when appropriate. For those usingEdm.Stringvalues with the Lookup resource, theLookupDisplayNamewill be checked as well. (In Progress)[ ] Resource and Field Name Enforcement - Similarity metrics and other heuristics will also be used to ensure that standard names are being used for resources and fields as well.
[ ] Data Validation Against Server Metadata - The Data Dictionary 1.7 Specification didn't include strict checking of data available on a given server against its advertised metadata. In Data Dictionary 2.0, these two items MUST match. This means that providers will fail testing if resources, fields, or enumerations appear in the data set that weren't advertised on the server. Similar is true in cases where fields, such as
Edm.String, exceed their advertised data length, or any other similar data anomalies. See #94.[ ] Reference Spreadsheet Structure - Previously there were individual sheets for each resource. They have been merged into a single sheet called "Fields," which also matches the format of the new Field metadata resource. The resource that each field belongs to will be indicated in the Field entry. Enumerations will be in a separate Lookups sheet.