[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-957) Do we impose a format for SchemaVersion?
[ https://issues.oasis-open.org/browse/ODATA-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62857#comment-62857 ] Ralf Handl commented on ODATA-957: ---------------------------------- SAP OData V2 services use an annotation sap:schema-version whose value is a number, starting at 1. I wouldn't want to impose that format onto others, and I'd also like to continue using this format for SAP OData V4 services in the Core.SchemaVersion annotation. > Do we impose a format for SchemaVersion? > ---------------------------------------- > > Key: ODATA-957 > URL: https://issues.oasis-open.org/browse/ODATA-957 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: OData Protocol > Affects Versions: V4.01_WD01 > Reporter: Michael Pizzo > Fix For: V4.01_WD01 > > > Should we impose a format for the schema version? i.e., major.minor.errata? > Does Swagger impose any format for versioning? -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]