These are the current active projects of the JSON Schema form organisation, these include organisational and development-related projects for all the ports that cooperate within it.

If you are interested in collaborating as a part of this fantastic project, you are very welcome to do so, please tell us in the discussions:

Lead: David Jensen
Maintainers: Nicklas Börjesson, Marcel Bennett
Discussion: #json-schema-form-projects

It is proposed that a standard is created, a common json-schema-form-format under the umbrella of the json-schema-form organisation.

The standard should include only the non-platform/framework dependent parts of the ASF form format. Broadly speaking, this means the current ASF format minus the styling and initialisation parameters. Those are highly likely to differ on other platforms, and can therefore be considered to be out of scope of a portable input form definition.

Having a common standard makes it far easier to port the format to different platforms (it adds a known scope to the project). It can also move json-schema-form closer to being a common format for defining data formats and inputs that can be used over several platforms and over an entire organization. And multiple organizations.

It is proposed that jsonform is contacted to see if they are interested in participating.

Lead: Nicklas Börjesson
Member: Vicary Archangel
Discussion: #json-schema-form-projects

It is proposed that the companies that have actual vested interest in json-schema-form, like Optimal BPM and Textalk, create a loose consortium (no legal ties, no money) to officially show support and to perhaps handle minor expenses. As an example of level of involvement, Optimal BPM hereby donate the 20 bucks it paid for the jsonschemaform.org - domain.

A consortium is a way to lend the combined weight of the companies involved to the project. It tells the onlooker that these actual companies believe in the project. Also it is FOSS goodwill for the companies and good branding (and another incoming link for those in need).

It is also a way for companies to find other companies to cooperate with on common interests. Arguably, the project needs to become a little bit more pompous and pretentious as well, a consortium may help with that.

Lead: Nicklas Börjesson
Maintainers:
Discussion: #json-schema-form-projects

It is proposed that a repository(or many?) is created that serves as a repository for common schema/form-combinations. The purpose is to significantly speed up development of json-schema-form projects. It is also likely that some forms will be identical everywhere, like those implementing structures dictated by laws and regulatory standards.

A template, or whatever that should be called, could then contain the following:

• a schema defining structure and validation
• a form defining the input layout
• a file containing example data
• a README.md that describes the template as a whole

Possibly, some kind of namespace structure should be used. The schema.org hierarchy could be glanced upon: https://schema.org/docs/full.html

Lead: Nicklas Börjesson
Contributors: Pontus Espe , David Jensen, Adam Buckley
Discussion: #json-schema-form-projects

It is proposed that a documentation is created, aimed at introducing would-be contributors to the ASF code base. It should describe ASFs:

• concepts
• architectures
• conventions

Is is also proposed that this as it is more general and won't be as version-specific as the user documentation, it would probably fit better in the repository wiki, than in an .md. It would make it far easier to contribute, collaborate, and wouldn't have to pollute the regular flow of development with copious amounts of PRs to some development.md-file.

Lead: Nicklas Börjesson
Members:
Discussion: #json-schema-form-projects

With regards to how the main readme.md of ASF in general looks, it is proposed that it needs some restructuring. It should be modeled more to anticipate the needs of the visitor.

As an idea, in angular-schema-form-angular-select, it is laid out like this:

• A short presentation (new visitors)
• Tree of features (interested new visitors)
• A link and description to the example(more interested new visitors)
• A "HELP"-section where it is listed what to do when you have different kinds of problems. ("I don't understand the documentation", "I have a question", "I have found a bug", "I have a feature request", "I want to discuss..")

And then whatever else one would want to have there.

With that structure, the users are immediately guided to the right place, they do not have to guess on what link to click.
Of course, there is lot of room for improvement, but it is proposed that the main github page of ASF should be more like that.

Lead: Pontus Espe
Members: Nicklas Börjesson
Discussion: #json-schema-form-projects

A donation account for donations from grateful users has been proposed. Also as a tool for the lead/contributors to collect a yearly money budget. For expenditures as DNS, domains etc.

Lead: Lukas Eipert
Members: ?
Discussion: #angular-schema-form-projects

It has been proposed that ASF uses PR templates https://github.com/blog/2111-issue-and-pull-request-templates which "force" the users to upload their schemas to gists/whatever?

Lead: Chase Sterling
Members: David Jensen
Discussion: #angular-schema-form-projects

The oneOf, anyOf and allOf schema concepts needs to be implemented in ASF.

The in-progress stuff is still here, and partially works:

• https://github.com/json-schema-form/angular-schema-form/tree/gazpachoking-oneOf
• https://github.com/json-schema-form/angular-schema-form-bootstrap/tree/feature/anyof-or-bust

A discussion (though the actual code on that PR is older than linked branches) here. some discussion here.

Lead: Marcel Bennett
Members:
Discussion: #angular-schema-form-projects

Local JSON Schema refs needs to be implemented for ASF, and this project aims to provide that.

Lead: Marcel Bennett
Member: David Jensen
Discussion: #angular-schema-form-projects

There should be an official code style settled for ASF. Perhaps something like the jscs file in the in the bootstrap Material repo, as it is following the style guide in: https://github.com/johnpapa/angular-styleguide

Lead: ?
Member: ?
Discussion: #angular-schema-form-projects

Users have requested a compatibility chart for Angular schema form. It is proposed that this is placed in the wiki, see issue 19 for details: json-schema-form/angular-schema-form#19

Lead: Nicklas Börjesson
Members: David Jensen
Discussion: #angular-schema-form-projects

ASF already has support for some module loaders, however, there are some issues that may not be resolved, a project is therefore proposed that fully implements that so that all module frameworks (RequireJS, Browserify and SystemJS/JSPM) can easily use ASF. Also ASF needs to be properly registered in JSPM.

Lead: David Jensen
Members: Marcel J Bennett, Steve Hu, Raphael Owino, Nicklas Börjesson
Discussion: #angular-schema-form-projects

It is proposed that the core functionality of ASF is broken out into its own repository and into a plain vanilla ES6 modules to not be dependent on any frameworks. This would make it far easier to port ASF to other frameworks and other versions of frameworks, like Angular 2.

More thoughts on the project is on the ASF wiki: https://github.com/json-schema-form/angular-schema-form/wiki/Schema-Form-Core

Lead: Nicklas Börjesson
Members: David Jensen, Adam Buckley Discussion: #json-schema-form-projects

It is proposed to create a common documentation with regards to those parts of the documentation that aren’t specific to any implementation, basically that which pertains to the standard. Possibly this could be done by simply breaking out the relevant part of the ASF documentation. There is a tentative start posted at: https://github.com/json-schema-form/standard/wiki/Documentation

Lead: Marcel Bennett
Members:
Discussion: #angular-schema-form-projects

To enable the schema for builder and other workflows to dynamically change the decorator, they will need to be dynamically changeable.

Lead: Marcel Bennett
Members:
Discussion: #angular-schema-form-projects

Currently, the handling of validation results is TV4-specific and in need of an overhaul to allow for other validators to be used.

Lead: Nicklas Börjesson
Members:
Discussion: #angular-schema-form-projects

To be able to smoothly use all aspects of ASF in a typescript application, there has been requests of a Typescript definition: https://github.com/json-schema-form/angular-schema-form/issues/648

Lead: David Jensen
Members:
Discussion: #angular-schema-form-projects

Currently, an ASF implementation may still use an internal decorator. This should not be possible in 1.0