-
Notifications
You must be signed in to change notification settings - Fork 110
Sneak peek at the new draft metadata schema! [Work in Progress] #273
Comments
@okamanda Should we bump the version up to 2.0.0 based on semantic versioning? |
@apyle yeah that's a good call. |
Is this correct: "required":[ Should it be license.URL or some other JSON schema construct? I'm not familiar with JSON schema. |
Question: Is |
Thanks @apyle That's a good question. costSavings field is anticipated to be the agency's measurement of costsavings across all known (internal) instances. |
@okamanda --
Another minor clarification question is: are the |
@IanLee1521 I would expect the license to use a SPDX Short Identifier. |
@styfle that seems reasonable to me, but I didn't notice that vein explicitly stated.. perhaps I missed it though? |
Hi folks,
As we build an updated version of the metadata schema, we want to give you the opportunity to share your feedback. We've started incorporating comments from the previous metadata schema thread: #250 .This draft is an early iteration of both the metadata schema and the sample code.json file. You'll note a number of syntactical changes in the newer draft, and we've provided a diff file below to show changes, but we specifically want to draw your attention to two new fields
costSavings
andopenSourceMeasureType
.costSavings How should we measure the impact of Code.gov? The
costSavings
field could provide a meaningful and flexible metric for agencies to demonstrate how much money has been saved by creating or using each repo. But we know this isn't the only way to show value. Some other alternatives to consider arelaborHours
,value
,cost
. Which of these, if any, make most sense to you and what are the arguments for using them instead ofcostSavings
?openSourceMeasureType The Federal Source Code Policy requires that 20% of an agency's code inventory be made available as open-source. In order to do so, agencies must (1) identify a method for measuring the 20% metric and (2) apply the measurement method to the total enterprise code inventory to establish a baseline. We've added a field for this to the updated version of the draft metadata schema. Agencies can use a few different methods for measuring their source code inventories as described here, which include:
You can take a look at the changes to the sample code.json and the draft of version 1.0.2 metadata schema below.
Changes to Sample Code.json in Version 1.0.2.
Draft Metadata Schema in Version 1.0.2.
The text was updated successfully, but these errors were encountered: