I am working on a prototype to convert RDF to an HTML form.
I am interested in other initiatives and thoughts of Solid enthusiasts.
In the readme you can read what the main idea is.
I want it to work with all the mainly used Ontologies. It has a plugin system so that you can add your own Ontologies.
It should have al the basic field types and for specific predicates it can have specific widgets.
nice. Yes the order may be a problem. I have also looked at streams. I thought for having a form, streams may be not needed. Streams may also complicate order.
I have read the article. I will investigate shapes. The article has interesting links in it. For example the UI ontology. https://www.w3.org/ns/ui maybe that can help and shacl.
While Forms could be rendered directly from the ShEx shape, the use of Form Models gives the form designer more control over the labeling/layout/ordering of the Form.
While thinking about that, a form builder would possible more interesting.
A visual builder that generates the forms along with a form renderer.
While using ShEx or forms.
create a form definition in turtle, publish it on the internet. (this can be attached to the ontology of the thing…)
create html: ‘’ with a couple of attributes.
Enjoy the form to edit or create things
For now I have stayed away from shex… I think it is really complex and doubt a web developer would like to create a form with that. I think it could be attached in the validation phase.
If anyone has feedback or observations I am looking forward to hear.
The ui:form does not have all the properties I needed for complex forms.
I have however started with those properties.
One other thing is that you could have an address field, or a geo location picker. These two examples both have multiple bindings, (postal code, country, house number etc and latitude and longitude).
At this moment nested forms are not possible. But that is one thing that I would like to add, nested forms with certain rules. Min or max values of the nested object etc.
One other difference is that I would like to make it so that conforms to general usage of forms.
I think one submit button is a general UI pattern and should be used as opposed to multiple save buttons or simply always saving via ajax. It could also be that multiple strategies would be okay to build in.
I build this for myself and for a big product I am experimenting for. We have a lot of reuse of forms in that application and a situation were we would like to join data from multiple data sources.
Hi @danielbeeke
Nice we components
the two ‘translation’ button disappear when we click on it, so it is fixed for two lang by the dev of the form ? Or could we add another lang?
That may be because I have not yet done any cross browser checks etc.
What versions are you using?
I also installed sentry now. So upcoming failures will be logged to my sentry dashboard.