> -----Original Message----- > From: Tom Harrison <t...@apnic.net> > Sent: Wednesday, June 17, 2020 7:44 PM > To: Hollenbeck, Scott <shollenb...@verisign.com> > Cc: mario.loffr...@iit.cnr.it; regext@ietf.org > Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rfc7483bis- > 00.txt > > On Wed, Jun 17, 2020 at 01:23:45PM +0000, Hollenbeck, Scott wrote: > > From: regext <regext-boun...@ietf.org> On Behalf Of Mario Loffredo > >> 5) Section 4.4 - The following sentence seems to be inconsistent > >> with the content of some figures (e.g. Fig. 15, 17, 23, ...) where a > >> "lang" element is included in jCard > >> > >> The "lang" attribute may appear anywhere in an object class or data > >> structure except for in jCard objects. > > > > [SAH] Agreed. I'll strike "except for in jCard objects". > > The motivation for including "except in jCard objects" originally was to make > it clear that an implementor couldn't include the lang attribute as defined in > this section in a jCard object. To preserve that aspect while making it clear > that the language-related content defined in jCard may be used, I think the > following would work better: > > The "lang" attribute as defined in this section may appear > anywhere in an object class or data structure, except for in jCard > objects. To avoid any doubt, language-related tags and parameters > defined by jCard itself may be used in jCard objects. > > though the wording is a little awkward.
Thanks for the suggestion, Tom. How about this instead? "The "lang" attribute as defined in this section may appear anywhere in an object class or data structure, except for in jCard objects. The "Language Tag" value described in RFC 7095 [RFC7095] MAY be used in jCard objects." Scott _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
