search

jakartaee / jakartaee-schemas

Other
7 stars 20 forks source link

Is this only for XML schemas? #4

Closed keilw closed 2 years ago

keilw commented 4 years ago

I know especially for Jakarta EE 9 it is mostly XML schemas to refactor into the new namespace, but could this repository also hold other schemas especially JSON schemas in future versions? There the $id property for a top-level schema should be an absolute-URI, with a domain that you control. For example, "jakarta.ee".

ivargrimstad commented 4 years ago

If there are any future platform level JSON schemas, this would be the place for it I guess. Schemas related to component specifications should be maintained in repositories under that particular specification project.

keilw commented 4 years ago

I think it remains to be seen, if JSON schemas would apply mostly to JSON-P or JSON-B (the most likely candidates) or something applies to the platform along the lines of configuration or deployment definitions etc. Are the versions planned to be in a folder structure like "jakartaee9" as it currently is? Then adding a new folder won't be a problem.

ivargrimstad commented 4 years ago

I think we should probably look over the folder structure a bit. It does not make sense to have a separate folder per version. That could be handled better with releases and tags.

I think you got your question answered, so this issue could be closed...?