From: Tom <tomz@freedommail•ch>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Requesting BIP assignment; Flexible Transactions.
Date: Fri, 23 Sep 2016 15:13:10 +0200 [thread overview]
Message-ID: <2344192.PKYylsbkSL@kiwi> (raw)
In-Reply-To: <20160923115550.GB17871@nex>
On Friday, 23 September 2016 13:55:50 CEST Christian Decker via bitcoin-dev
wrote:
> Not sure if the comparison to XML and HTML holds: the lack of closing
> tags makes the meaning of individual tokens ambiguous, like I pointed
> out before. The use of segments gives at most two levels of nesting,
> so any relationship among tokens in the same segment has to rely on
> their relative position, which could result in ambiguities, like
> whether a tag refers to a single input or the transaction as a whole.
Practically all tagged formats make ordering a requirement, so indeed this
is relevant, and not unique.
For instance if you write;
<div> Some line </br>Another line</br>3rd line</div>
you can get a good idea of how ordering is relevant. You can reuse any item
many times.
Whenever there is a possible confusion the specification specifically
explains which order to use.
I'm not sure what you mean with the idea this;
> The use of segments gives at most two levels of nesting
It looks like you assume there is some opening and closing tags, since
otherwise there would be no nesting.
Such tags are not intended, nor documented.
> so any relationship among tokens in the same segment has to rely on
> their relative position, which could result in ambiguities, like
> whether a tag refers to a single input or the transaction as a whole.
I quoted parts of the spec in your previous email stating the same thing,
but I'll repeat here.
Any place that has any sort of possibility to be ambiguous is specified
specifically to have an order. This makes writing and parsing easier.
Since you wrote two emails now with the same issue, and I addressed it
twice, I would urge you to write out some examples which may be confusing
and if you find that the spec is indeed missing requirements then please
share it with us. I did this some time ago and it helps understanding the
ideas by having actual explicit examples. I am not aware of any sort of
ambiguities that the spec allows.
Cheers!
next prev parent reply other threads:[~2016-09-23 13:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 22:45 adiabat
2016-09-22 8:47 ` Tom
2016-09-22 18:27 ` Peter Todd
2016-09-22 18:37 ` Tom
2016-09-22 19:59 ` Jonas Schnelli
2016-09-22 20:07 ` Tom
2016-09-23 11:55 ` Christian Decker
2016-09-23 13:13 ` Tom [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-20 17:15 Tom
2016-09-20 21:31 ` Luke Dashjr
2016-09-21 9:32 ` Tom
2016-09-20 21:56 ` Peter Todd
2016-09-21 9:32 ` Tom
2016-09-22 18:26 ` Peter Todd
2016-09-22 18:47 ` Tom
2016-09-21 12:00 ` Andreas Schildbach
2016-09-21 12:58 ` Tom
[not found] ` <CAAS2fgSpnshZhS7N5R3Qsw_8=NN8sjYGwrnUpdwGzu2TG0-Qgw@mail.gmail.com>
2016-09-21 18:01 ` Gregory Maxwell
2016-09-22 8:56 ` Tom
2016-09-22 11:10 ` Christian Decker
2016-09-22 12:09 ` Tom
2016-09-23 11:42 ` Christian Decker
2016-09-23 13:17 ` Tom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2344192.PKYylsbkSL@kiwi \
--to=tomz@freedommail$(echo .)ch \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox