{"id":2142,"date":"2014-06-09T18:38:13","date_gmt":"2014-06-09T18:38:13","guid":{"rendered":"https:\/\/notebooks.dataone.org\/?p=2142"},"modified":"2014-06-21T05:30:05","modified_gmt":"2014-06-21T05:30:05","slug":"week-2-update","status":"publish","type":"post","link":"https:\/\/notebooks.dataone.org\/prov-trace\/week-2-update\/","title":{"rendered":"Week 2 Update"},"content":{"rendered":"
In the past week, I\u2019ve coordinated with Patrick West and Tim Lebo to set up my development copy of the Prizms framework.\u00a0 As mentioned earlier, Prizms is a framework for publishing linked data that will aid in our management of OPeNDAP based provenance records.<\/p>\n
Additionally, based on a review of the OPeNDAP documentation, Patrick and I have discussed a set of structural requirements for OPeNDAP\u2019s provenance records.\u00a0 It has been determined that we will need provenance encodings for each of the following entities:<\/p>\n
Modules:<\/strong> the actual OPeNDAP modules. For each of these entities, we envision OPeNDAP consumers being able to look up corresponding information in a human-readable form.\u00a0 Therefore, one of our next steps will be to design website templates for each of these entity types.<\/p>\n","protected":false},"excerpt":{"rendered":" In the past week, I\u2019ve coordinated with Patrick West and Tim Lebo to set up my development copy of the Prizms framework.\u00a0 As mentioned earlier, Prizms is a framework for publishing linked data that will aid in our management of OPeNDAP based provenance records. Additionally, based on a review of Continue reading Week 2 Update<\/span>
\nVersions:<\/strong> specific versions of modules representing particular software versions.
\nOrganizations \/ Contributors:<\/strong> entities making changes to OPeNDAP software.<\/p>\n