---
title: Case for Sharing Definitions & Specifications in the Public Community
description: IData Blog | The Case for Sharing Definitions and Specifications in the Public Community
---

[IData Insights Blog](https://blog.idatainc.com)

# [Case for Sharing Definitions & Specifications in the Public Community](https://blog.idatainc.com/the-case-for-sharing-definitions-and-specifications-in-the-public-community)

 Written by [Brenda Reeb](https://blog.idatainc.com/author/brenda-reeb) | Jan 17, 2017 1:37:21 PM

 

As you many know, IData [publishes](https://community.datacookbook.com/institutions) a number of publicly-available definitions and specifications for public consumption, including national data sets like [IPEDS](https://community.datacookbook.com/institutions/IPEDS) and [CDS](https://community.datacookbook.com/institutions/cds), state bodies like [SCHEV](https://community.datacookbook.com/institutions/schev) in Virginia, regional accreditors like [WASC](https://community.datacookbook.com/institutions/wascsenior), and professional accreditors like [AACSB](https://community.datacookbook.com/institutions/aacsb).

The public availability of this information helps IData clients and organizations such higher education institutions in general deal with the increasing complexity of data definitions. However, there remains an immense amount of private definitions that may help other organizations if made available in the public community.

Some institutions remain leery of sharing their data definitions and specifications with the larger community. Such hesitation is certainly understandable given data governance structures, and we readily acknowledge that some data should not be shared. Consider, though, the process that nearly all institutions who develop their own data dictionaries undergo: wrestling with the nuances of meaning, application to local understanding and culture, and vetting across multiple stakeholders. If there is a particular data point, say *ethnicity* for example, that is the culmination of combining many other definitions, vetting, and re-drafting, would it not hold value for others?

This is not to say that organizations should consider sharing some of their data merely an act of good will. Rather, sharing such information could help establish collaborative relationships between peer organizations, departments, or other organizations that may pay dividends in the future. The Data Cookbook Community efforts, then, could be more directed toward networking individuals and departments to peers who are actively solving the same or similar problems at their own organizations.  Feel free to check out the [Data Cookbook Community](https://community.datacookbook.com/) which is available at no cost to anyone.

If you would like to discuss the community with us or data governance (data intelligence), please feel free to .

(image credit StockSnap\_EB9B6BC1F6\_SharingDefsModernLibrary\_BP #1054)

[View full post](https://blog.idatainc.com/the-case-for-sharing-definitions-and-specifications-in-the-public-community)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Brenda Reeb"
  },
  "dateModified" : "2021-05-02T05:34:49.424Z",
  "datePublished" : "2017-01-17T13:37:21Z",
  "headline" : "Case for Sharing Definitions & Specifications in the Public Community",
  "image" : {
    "@type" : "ImageObject",
    "height" : 2848,
    "url" : "https://cdn2.hubspot.net/hubfs/4171032/IMG-Image/StockSnap_EB9B6BC1F6_SharingDefsModernLibrary_BP.jpg",
    "width" : 4288
  },
  "mainEntityOfPage" : "https://blog.idatainc.com/the-case-for-sharing-definitions-and-specifications-in-the-public-community",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60,
      "url" : "/hs/hsstatic/content_shared_assets/static-1.4092/img/default-amp-logo.png",
      "width" : 60
    },
    "name" : "IData Insights"
  }
}
```