Next in thread → Next in month →

[OASIS Issue Tracker] (ODATA-957) Do we impose a format for SchemaVersion?

From
OASIS Issues Tracker <>
Date
2016-07-07T06:27:15+00:00
ID
Thread
[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:all-tabpanel ]

Michael Pizzo updated ODATA-957:
--------------------------------

    Environment: [Proposed]
       Proposal: We should not mandate the format of the version string. Swagger recommends semantic versioning but does not require it; any string can be used as the version.

> 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
>         Environment: [Proposed]
>            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)
Next in thread → Next in month →