Replies: 1 comment
-
Valuable documentation for this feature: https://angular.dev/guide/forms/dynamic-forms |
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
-
The DWNs where we store data is very flexible and can store any type of data. Our "Data as a Service", or "Data" feature for short, will allow users to create, manage and curate their own sets of data, that can be used for personal use, public use, free or paid access.
We need to develop a highly dynamic forms editor, that will render a UI based upon either users own inputs, or from a known schema from a schema catalog.
The schema catalog will ensure a common set of data structures so they don't diverge too much.
For example schema for "Person".
https://schema.org/ has a lot of these schemas, but often they might not fit our needs. For example, a person should always have a single name field that can contain fairly long data. Names should not be divided up in First, Middle and Lastname. This is because everyone is different in many different cultures. See this Person schema as an example: https://schema.org/Person
Another example is "TVEpisode", if someone wants to curate a data list (we should decide naming convention on these things as we develop Ariton) it would be advisable to rely on this schema and not come up with custom annotations with different field names. It ensures potential import and exports to various other tools and services.
https://schema.org/TVEpisode
schema
is a field on data written to DWN, and should be a uri to a specific schema.This is a very big task, so I'm starting this as a discussion instead of issue, so we can discuss some ideas before nailing the specific tasks to be added as issues.
Beta Was this translation helpful? Give feedback.
All reactions