Implementor Guide #1038
rufuspollock
started this conversation in
Ideas
Replies: 2 comments
-
we have an implementors guide here http://specs.frictionlessdata.io/implementation/ |
Beta Was this translation helpful? Give feedback.
0 replies
-
@pwalsh yes and I read it before I wrote this issue 😉 - this issue reflects the things I think are missing from that implementors guide. I could be mistaken on this so please comment against the items in the description 😄 (and add items). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is an epic for creating a detailed guide for implementors of the specs. The guide would be the main place for implementors to understand the nuances of the specs and how best to proceed.
User Stories
As a Developer creating and implementation I want a guide in one place on implementation to complement the bare specs so that I understand the nuances of the specs and how best to proceed.
As a Developer looking to create an implementation I want to know what the interface of my library should look like so that I can design it well and consistently with libraries in other languages
As a Developer looking to use one of the existing Data Package libraries i want to get up and running as quickly as possible so that I can be very productive
Acceptance criteria
Tasks
fmt:
support #436Analysis
Existing Work on a Guide
Stack reference - https://github.com/frictionlessdata/stack#frictionless-data-stack
For implementors - http://specs.frictionlessdata.io/implementation/
Neither of these provide simple examples.
Backwards Compatibility
There is an implementer note about
resource.url
support inTable Resource
spec. So I suppose the same we could do forTable Schema: date/time/datetime
andfmt:
- I suppose temporal format is the most often mistakes I saw. And implementations better to support prev version too.FAQs
Interface design and code walkthrough
Walkthrough - simple elegant code for each of these (could do as one big code block or as separate ones -- maybe easier together as you can reuse earlier pages)
We recommend library implementors support an interface similar to the following:
Python
JavaScript
Beta Was this translation helpful? Give feedback.
All reactions