Dear TC members,
On Fri, Jun 21, 2024, at 22:40, Przemyslaw Roguski wrote:
> Dear OpenEoX TC members,
>
>
> During the last meeting (2024-06-19), we discussed the JADN representation of the OpenEoX schema.
> This was proposed by the below pull requests:
>
> _https://github.com/oasis-tcs/openeox/pull/10_
>
> _https://github.com/oasis-tcs/openeox/pull/24_
>
>
> Meeting participants agreed that while there are benefits of using JADN to describe and validate the structure of the OpenEoX schema in JSON format, it may be better to focus right now on the OpenEoX schema definition and robust specification. We can continue to work with the traditional JSON format as examples of the OpenEoX data, allowing users to validate the format in their own way. We may get back to this JADN usage proposal in the future.
>
>
> I hereby submit the following motion as we agreed during the last meeting and request feedback, including no objections, before the 2024-06-26 23:00 UTC.
> No feedback will be considered as no objection. We will state the result via an mail to this list when the period has passed.
>
>
> My vote:
> Move to focus the current OpenEoX TC work to use the traditional JSON schema format vs JADN.
>
>
>
> Best regards,
>
> Rogue [...]
I, Stefan Hagen, hereby second the motion.
Cheers,
Stefan
---
Stefan Hagen, Emmetten, Nidwalden, Switzerland.
read:
https://stefan-hagen.websitewrite:
stefan@hagen.link
Original Message:
Sent: 6/21/2024 4:40:00 PM
From: Przemyslaw Roguski
Subject: Motion for OpenEoX to use the traditional JSON schema, not include JADN for now
Dear OpenEoX TC members,
During the last meeting (2024-06-19), we discussed the JADN representation of the OpenEoX schema.
This was proposed by the below pull requests:
https://github.com/oasis-tcs/openeox/pull/10
https://github.com/oasis-tcs/openeox/pull/24
Meeting participants agreed that while there are benefits of using JADN to describe and validate the structure of the OpenEoX schema in JSON format, it may be better to focus right now on the OpenEoX schema definition and robust specification. We can continue to work with the traditional JSON format as examples of the OpenEoX data, allowing users to validate the format in their own way. We may get back to this JADN usage proposal in the future.
I hereby submit the following motion as we agreed during the last meeting and request feedback, including no objections, before the 2024-06-26 23:00 UTC.
No feedback will be considered as no objection. We will state the result via an mail to this list when the period has passed.
My vote:
Move to focus the current OpenEoX TC work to use the traditional JSON schema format vs JADN.
Best regards,
Rogue