OASIS Open Mailing List Archives  ·  All Lists  ·  csaf  ·  2023-10

csaf — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

API directions


Dear members, as the meeting was suddenly gone while I was trying to explain where I see current points of interest in the development of standardized API(s) for CSAF v2.1 I like to shortly summarize per mail: REST,  GraphQL, and OData to me are potentially all three sustainable as specs Call for action as which architectural forms of API would your organization be willing to operate wanting to consume The editors currently prefer in any case a separation of work products a.k.a. documents core spec (the format as successor of the v2.0 spec as it is today) schema files (as of now eventually a different number but linked per the title page of (3.a) new API spec OData / REST / GraphQL presumably in separate docs for themselves (1 to 3) There is a collecting issue - please feel free to comment there: https://github.com/oasis-tcs/csaf/issues/637 Thanks. All the best, stefan. --- Stefan Hagen, Emmetten, Nidwalden, Switzerland. read: https://stefan-hagen.website write: [email protected]

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]