Re: [salud] New version of the ABNF-syntax

Dale,

I think there is the first proposal is OK. But the amount of changes depend
also on what you intend to do with the new identifier.

With the second proposal, we probably have to rewrite the draft. In this
case, I would give up.

But why do you need the components of an <alert-indication>?
Currently,  IMO they have no meaning and must be not managed as
individuals, only whole <alert-indicators> must be managed. This was a
decision of the WG at the beginning. If you want to change this we have to
throw avay what we have now an degin again were we were three or four years
ago.

And what is the open point you want to solve?  I thought with what we have
now we solved all issues. Or did I miss something here?

Thank you
Laura

2013/3/8 Dale R. Worley <worley@ariadne.com>

> [as an individual]
>
> The current syntax is:
>
>       alert-URN         = "urn:alert:" alert-identifier
>       alert-identifier  = alert-category ":" alert-indication
>       alert-category    = alert-name
>       alert-indication  = alert-name *(":" alert-name)
>       alert-name        = alert-label / private-name
>
> One source of difficulty I am having is that I would like a
> nonterminal that means "an <alert-name> that is part of an
> <alert-indication> (but not an <alert-category>".  I have been
> incorrectly using the term <alert-indication> for this nonterminal.
>
> There are alternative ways to provide this nonterminal.  We could
> introduce a new nonterminal:
>
>       alert-URN         = "urn:alert:" alert-identifier
>       alert-identifier  = alert-category ":" alert-indication
>       alert-category    = alert-name
>       alert-indication  = xxx *(":" xxx)
>       xxx               = alert-name
>       alert-name        = alert-label / private-name
>
> Or we could change the meaning of alert-indication:
>
>       alert-URN         = "urn:alert:" alert-identifier
>       alert-identifier  = alert-category ":" alert-indication *(":"
> alert-indication)
>       alert-category    = alert-name
>       alert-indication  = alert-name
>       alert-name        = alert-label / private-name
>
> But I do not know what change would cause the fewest problems with the
> rest of the draft text.
>
> What do you recommend?
>
> Dale
> _______________________________________________
> salud mailing list
> salud@ietf.org
> https://www.ietf.org/mailman/listinfo/salud
>