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-1044) Require aliases for schemas and require alias-qualified names


    [ https://issues.oasis-open.org/browse/ODATA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65470#comment-65470 ] 

Michael Pizzo commented on ODATA-1044:
--------------------------------------

We can address the predictability of how a name is qualified by saying that an alias, if present, must be used.

Then we can suggest, but not require, the use of aliases.

> Require aliases for schemas and require alias-qualified names
> -------------------------------------------------------------
>
>                 Key: ODATA-1044
>                 URL: https://issues.oasis-open.org/browse/ODATA-1044
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: CSDL JSON 
>    Affects Versions: V4.01_WD01
>         Environment: Proposed
>            Reporter: Ralf Handl
>             Fix For: V4.01_WD01
>
>
> To simplify lookup of qualified names the CSDL JSON representation initially required namespace-qualified names. This got some pushback as namespaces are typically long to be unique and alias-qualified names are more readable, so aliases were re-introduced.
> Why not require aliases and alias-qualified names in CSDL JSON documents to further increase readability by avoiding the arbitrary mix of namespace- and alias-qualified names.



--
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]