OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [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 ]

Michael Pizzo updated ODATA-887:

    Proposal: don't allow multi-part alias names as it would break atom and likely not be supported in programming languages.  (was: Allow multi-part namespace alias names.)

> 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: [Proposed]
>            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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]