Hi JC, This has somehow slipped past me.
On Freitag, 13. August 2021 14:00:06 CEST JC Brand wrote: > So, if you have a stanza with for example, both "subject" and "body" > tags, we can have references for both, and use the "anchor" attribute as > follows (I hope this comes out formatted properly once sent): > > <message type="headline" from="sch...@springfield.city"> > <subject id="subject">Attention Bart Simpson</subject> > <body id="body">Please hand in your homework before the end of the > day</body> > <reference anchor="#subject" begin="9" end="21" type="mention"/> > </message> What about messages with multiple <body/> elements disambiguated by xml:lang? Could some conceivably contain a mention while others don't? Does this require replicating the mention element all over? Same question for <subject/>. Besides that, I don't think that adding an attribute to an element in this way is really acceptable. I would prefer an approach which identifies the XML element without having to modify the XML being referenced. Libraries which currently represent body as a (mappnig of language tags to) string(s) would now need extra magic in order to be able to set ID attributes on those. This feels like a quite major change, and not just to References, but to literally everything else. kind regards, Jonas [1]: https://www.w3.org/TR/REC-xml/#id
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
