You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do folks have a recommended technology for
a) Generating the JSON file from a basic input?
b) Connecting data files for upload and/or reference
c) Connecting analysis scripts
d) representing data provenance
For b & c, I think a URL is the way to go. I’m assuming we’re not
hosting data/scripts because there are a slew of other
services/options for that.
For d, probably a text description or link to documentation. The
provenance-related standards of which I’m aware tend to be highly
specialized, so I’m not sure it’s worth looking for a more structured
mode of representation.
On July 19, 2016 at 12:56:05 PM, Sean P. Goggins
([email protected]) wrote:
Do folks have a recommended technology for
a) Generating the JSON file from a basic input?
b) Connecting data files for upload and/or reference
c) Connecting analysis scripts
d) representing data provenance
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: #19 (comment)
Can start with Jeremy Dorn's JSON editor
The text was updated successfully, but these errors were encountered: