- From: Randall Leeds via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Jun 2016 19:33:09 +0000
- To: public-annotation@w3.org
> I suspect that it shouldn't, but that it is just part of the method described for DOM Level 3 APIs. You don't want to strip markup or escapes from plain text sources that contain it, because they are examples. Makes sense. I only didn't take issue with it because in context with the sentence about HTML/XML it didn't imply removing markup from plain text sources, to me. I would support removing it, though. And the DOM String Comparison part was my mistake not to notice. > I share Addison's concern that perhaps the WA WG doesn't really know why that normalization stuff is there. If we can work through a proposal here and discuss it on our call on Friday we could stay on schedule here. I really appreciate your help clarifying these issues with us. > Personally, I'd be inclined to remove the whole paragraph. I'm also fine with that result. It would be especially nice not to be mentioning specific formats like HTML/XML, and instead issuing guidelines here, if we say anything at all. In HTML/XML, it might be well understood that the text is, well, the text. After all, they are called "Text" nodes. In another application domain, the markup may well be part of the text. Rob, do you think we have enough information in this thread to simplify the language further and propose something that the WG could agree to on Friday? -- GitHub Notification of comment by tilgovi Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/227#issuecomment-223100209 using your GitHub account
Received on Wednesday, 1 June 2016 19:33:13 UTC