MHonArc v2.5.2 -->
wsia message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: RE: [wsia][wsia-requirements][E905]
I mostly like the Eilon version. Is there a reason not to replace "should"
with "must"? Also, I don't see why the case of combining multiple fragments
from the same producer needs specific mention (is it more technically
important than composing fragments from different producers?).
I suggest:
This specification MUST provide a mechanism that ensures that
different presentation fragments can be "safely" combined to a single
document. In particular, if a presentation formats (such as HTML)
mandates uniqueness of tokens in a single document, it MUST be
possible to compose a page in a way that guarantees uniqueness.
Tim
> Can we clarify the intent?
>
> Is the intent to ensure uniqueness of HTML ids and the question of how
> to do it?
>
> If this is the case, would it make sense to try to capture the abstract
> need, along the lines of:
>
> E905A
> This specification should provide a mechanism that ensures that
> different presentation fragments can be "safely" combined to a single
> document. In particular, if a presentation formats (such as HTML)
> mandates uniqueness of tokens in a single document, it should be
> possible to compose a page in a way that guarantees uniqueness. In
> particular, it should be possible to compose presentation fragments
> generated by the same Producer.
>
> (We can still leave it open to whether the Producer generates random
> token, the Consumer rewrites tokens or the Consumer provides information
> that allows the Producer to write those tokens)
>
>
>