Christian Hopps on Friday, March 15, 2024 20:10:
>> On Mar 15, 2024, at 13:26, mohamed.boucad...@orange.com wrote:
>>
>> Re-,
>> I’m not sure to agree with your last statement, Andy.
>> The reality is that the OLD reco is inducing many cycles and waste of time
>> for no obvious technical reason
> On Mar 15, 2024, at 13:26, mohamed.boucad...@orange.com wrote:
>
> Re-,
> I’m not sure to agree with your last statement, Andy.
> The reality is that the OLD reco is inducing many cycles and waste of time
> for no obvious technical reason: see an example
> herehttps://mailarchive.ietf.org
Re-,
I’m not sure to agree with your last statement, Andy.
The reality is that the OLD reco is inducing many cycles and waste of time for
no obvious technical reason: see an example here
https://mailarchive.ietf.org/arch/msg/teas/eknpfAZIb9gX7GvUN1UoByCf5e4/
Let’s save the authors time with a
On Fri, Mar 15, 2024 at 9:42 AM Jürgen Schönwälder
wrote:
> Yes, for long XPath expressions, one likes to have short prefixes, the
> shorter the better. In other contexts, such as type definitions, one
> may want to use longer prefixes providing more context. It seems you
> can't have both at the
Yes, for long XPath expressions, one likes to have short prefixes, the
shorter the better. In other contexts, such as type definitions, one
may want to use longer prefixes providing more context. It seems you
can't have both at the same time. Given this inherent conflict, I am
not sure that general
Andy, very good summary!
/jan
On 15 Mar 2024, at 16:22, Andy Bierman wrote:
On Fri, Mar 15, 2024 at 7:24 AM Jürgen Schönwälder
mailto:jschoenwaelder@constructor.university>>
wrote:
I wonder which problem we are solving with adding more little rules.
Perhaps a future version of YANG will do a
Chris,
> Right.. I don't understand the need for uniqueness even, since one
> specifies a prefix when importing other modules.
When importing, one should follow this part from 7550:
To
improve readability of YANG modules, the prefix defined by a module
SHOULD be used when the module is
Jürgen Schönwälder writes:
I wonder which problem we are solving with adding more little rules.
Perhaps a future version of YANG will do away with prefixes but until
this happens, I do not think we need to add more rules about how to
choose prefixes. The original intend was that they are short
On Fri, Mar 15, 2024 at 7:24 AM Jürgen Schönwälder
wrote:
> I wonder which problem we are solving with adding more little rules.
> Perhaps a future version of YANG will do away with prefixes but until
> this happens, I do not think we need to add more rules about how to
> choose prefixes. The ori
Hi Jürgen,
I agree this is marginal, but the proposed change is mainly to ensure some
consistency and to some extend avoid collision with other SDOs. In the
meantime, the initial reco is not technically justified :-)
Please note that the initial reco is not always followed in practice: for
ex
I wonder which problem we are solving with adding more little rules.
Perhaps a future version of YANG will do away with prefixes but until
this happens, I do not think we need to add more rules about how to
choose prefixes. The original intend was that they are short to keep
YANG snippets concise a
Hi Andy,
(changing the subject to ease tracking this)
The thread I was referring is:
https://mailarchive.ietf.org/arch/msg/netmod/6VkSrroaxwXHSI19Jj0j-tbFCjA/
I do personally think that it is a good guidance to prefix IETF modules with
“ietf-“ and IANA-maintained ones with “iana-‘. This is con
12 matches
Mail list logo
