Next in thread → Next in month →

[OASIS Issue Tracker] (ODATA-887) Should we allow multi-part namespace alias names?

From
OASIS Issues Tracker <>
Date
2016-12-19T10:40:46+00:00
ID
Thread
[OASIS Issue Tracker] (ODATA-887) Should we allow multi-part namespace alias names?
[ https://issues.oasis-open.org/browse/ODATA-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-887:
-----------------------------

    Environment: Closed without Action  (was: [Proposed])

> Should we allow multi-part namespace alias names?
> -------------------------------------------------
>
>                 Key: ODATA-887
>                 URL: https://issues.oasis-open.org/browse/ODATA-887
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData CSDL
>    Affects Versions: V4.0_ERRATA02
>         Environment: Closed without Action
>            Reporter: Michael Pizzo
>             Fix For: V4.01_WD01
>
>
> Currently namespace aliases are defined as simple identifiers, while namespaces can (but are not required to) be multi-part.
> Unclear why there is this distinction; it's not possible to tell from a single-part name whether the name references a namespace or an alias, so why prohibit multi-part names (i.e., names containing a dot (".")) in aliases?
> There are scenarios where a namespace is long that an application may want to use a shorter name but still represent some level of hierarchy in the naming scheme. 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
Next in thread → Next in month →