Ladislav Lhotka wrote:
>
> > On 24 May 2016, at 16:33, Dale R. Worley wrote:
> >
> > (I've not received some of the discussion e-mails, so I am just now
> > responding.)
> >
> > Ladislav Lhotka writes:
> >> This follows from the fact that YANG doesn't support mixed content:
> >> there is no w
Thank you very much Dean.
Yours,
Joel
On 5/24/16 11:42 AM, Dean Bogdanovic wrote:
WG,
Joel and I had an offline discussion and in order to make it more clear, a text
clarification should be added to the document in which is stated that this
document proposes initial elements for a taxonomy, r
WG,
Joel and I had an offline discussion and in order to make it more clear, a text
clarification should be added to the document in which is stated that this
document proposes initial elements for a taxonomy, rather than an initial
taxonomy.
Dean
> On May 24, 2016, at 11:09 AM, Joel M. Halp
Jason,
> On Apr 29, 2016, at 3:33 PM, Sterne, Jason (Nokia - CA)
> wrote:
>
> Hi guys,
>
> I agree that we may want to consider other metadata items and also agree they
> will tend to be more implementation-specific. But rather than hold up this
> base ACL model for metadata why don't we t
> On 24 May 2016, at 16:33, Dale R. Worley wrote:
>
> (I've not received some of the discussion e-mails, so I am just now
> responding.)
>
> Ladislav Lhotka writes:
>> This follows from the fact that YANG doesn't support mixed content:
>> there is no way how this whitespace can be made signifi
I had real trouble mapping the taxonomy to the models I am familair with.
ODL uses YANG models to define the persistent data and interface APIs to
any and all of its internal services. These include controlling
anything and everything the controller does. But the results of the
YANG operatio
Joel,
> On Apr 24, 2016, at 9:31 PM, Joel M. Halpern wrote:
>
> What is the relationship between this taxonomy and the many models that do
> not fit its cateogrization?
>
> Three examples:
> Models used in ODL to generate results which may be neither network services
> nor network elements.
(I've not received some of the discussion e-mails, so I am just now
responding.)
Ladislav Lhotka writes:
> This follows from the fact that YANG doesn't support mixed content:
> there is no way how this whitespace can be made significant.
It seems to me that this is the restriction that should be
> On 24 May 2016, at 15:20, Martin Bjorklund wrote:
>
> Ladislav Lhotka wrote:
>>
>>> On 24 May 2016, at 14:52, Martin Bjorklund wrote:
>>>
>>> Ladislav Lhotka wrote:
Martin Bjorklund writes:
> Ladislav Lhotka wrote:
>>
>>> On 23 May 2016, at 14:30, Lou Berger wro
Martin Bjorklund writes:
>>
>>if-feature-expr = "(" if-feature-expr ")" /
>> if-feature-expr sep boolean-operator sep
>>if-feature-expr /
>> not-keyword sep if-feature-expr /
>> identif
Ladislav Lhotka wrote:
>
> > On 24 May 2016, at 14:52, Martin Bjorklund wrote:
> >
> > Ladislav Lhotka wrote:
> >> Martin Bjorklund writes:
> >>
> >>> Ladislav Lhotka wrote:
>
> > On 23 May 2016, at 14:30, Lou Berger wrote:
> >
> > Hi Lada,
> > I looks like no one
> On 24 May 2016, at 14:52, Martin Bjorklund wrote:
>
> Ladislav Lhotka wrote:
>> Martin Bjorklund writes:
>>
>>> Ladislav Lhotka wrote:
> On 23 May 2016, at 14:30, Lou Berger wrote:
>
> Hi Lada,
> I looks like no one really jumped on this one -- so better late than
Ladislav Lhotka wrote:
> Martin Bjorklund writes:
>
> > Ladislav Lhotka wrote:
> >>
> >> > On 23 May 2016, at 14:30, Lou Berger wrote:
> >> >
> >> > Hi Lada,
> >> >I looks like no one really jumped on this one -- so better late than
> >> > never ...
> >> >
> >> > When looking at the que
Martin Bjorklund writes:
> Ladislav Lhotka wrote:
>>
>> > On 23 May 2016, at 14:30, Lou Berger wrote:
>> >
>> > Hi Lada,
>> >I looks like no one really jumped on this one -- so better late than
>> > never ...
>> >
>> > When looking at the question below, we should consider the uses cases
Ladislav Lhotka wrote:
>
> > On 24 May 2016, at 12:04, Martin Bjorklund wrote:
> >
> > Ladislav Lhotka wrote:
> >>
> >>> On 24 May 2016, at 10:33, Martin Bjorklund wrote:
> >>>
> >>> Juergen Schoenwaelder wrote:
> On Mon, May 23, 2016 at 05:29:42PM +0200, Ladislav Lhotka wrote:
>
> On 24 May 2016, at 12:04, Martin Bjorklund wrote:
>
> Ladislav Lhotka wrote:
>>
>>> On 24 May 2016, at 10:33, Martin Bjorklund wrote:
>>>
>>> Juergen Schoenwaelder wrote:
On Mon, May 23, 2016 at 05:29:42PM +0200, Ladislav Lhotka wrote:
[...]
> This mixes up paths
Ladislav Lhotka wrote:
>
> > On 23 May 2016, at 14:30, Lou Berger wrote:
> >
> > Hi Lada,
> >I looks like no one really jumped on this one -- so better late than
> > never ...
> >
> > When looking at the question below, we should consider the uses cases.
> > I'm particularity interested (a
The proposed new text looks fine to me.
Rob
On 23/05/2016 15:08, Martin Bjorklund wrote:
Hi,
This comment from the Gen-ART review deserves it's own thread.
gen-art> - section 7.6.4
gen-art>
gen-art>The default value MUST NOT be marked with an "if-feature" statement.
gen-art>
[...]
gen-a
On Tue, May 24, 2016 at 12:13:04PM +0200, Martin Bjorklund wrote:
> Juergen Schoenwaelder wrote:
> > On Tue, May 24, 2016 at 10:33:29AM +0200, Martin Bjorklund wrote:
> > > Juergen Schoenwaelder wrote:
> > > > On Mon, May 23, 2016 at 05:29:42PM +0200, Ladislav Lhotka wrote:
> > > >
> > > > [...]
Juergen Schoenwaelder wrote:
> On Tue, May 24, 2016 at 10:33:29AM +0200, Martin Bjorklund wrote:
> > Juergen Schoenwaelder wrote:
> > > On Mon, May 23, 2016 at 05:29:42PM +0200, Ladislav Lhotka wrote:
> > >
> > > [...]
> > >
> > > > This mixes up paths in the data tree with those in the schema
Ladislav Lhotka wrote:
>
> > On 24 May 2016, at 10:33, Martin Bjorklund wrote:
> >
> > Juergen Schoenwaelder wrote:
> >> On Mon, May 23, 2016 at 05:29:42PM +0200, Ladislav Lhotka wrote:
> >>
> >> [...]
> >>
> >>> This mixes up paths in the data tree with those in the schema
> >>> tree. The X
On Tue, May 24, 2016 at 10:33:29AM +0200, Martin Bjorklund wrote:
> Juergen Schoenwaelder wrote:
> > On Mon, May 23, 2016 at 05:29:42PM +0200, Ladislav Lhotka wrote:
> >
> > [...]
> >
> > > This mixes up paths in the data tree with those in the schema tree. The
> > > XPath expression in the "p
> On 24 May 2016, at 10:33, Martin Bjorklund wrote:
>
> Juergen Schoenwaelder wrote:
>> On Mon, May 23, 2016 at 05:29:42PM +0200, Ladislav Lhotka wrote:
>>
>> [...]
>>
>>> This mixes up paths in the data tree with those in the schema tree. The
>>> XPath expression in the "path" statement is
Juergen Schoenwaelder wrote:
> On Mon, May 23, 2016 at 05:29:42PM +0200, Ladislav Lhotka wrote:
>
> [...]
>
> > This mixes up paths in the data tree with those in the schema tree. The
> > XPath expression in the "path" statement is evaluated in the context of a
> > data tree, but if the resul
On Mon, May 23, 2016 at 05:29:42PM +0200, Ladislav Lhotka wrote:
[...]
> This mixes up paths in the data tree with those in the schema tree. The XPath
> expression in the "path" statement is evaluated in the context of a data
> tree, but if the result is an empty node set, then "this leaf node
25 matches
Mail list logo
