Apparently we use new topics for these meetings
", "time": "2023-03-28T00:35:34Z"}, {"author": "Robert Sparks", "text": "we _can_ use topics at this meeting
", "time": "2023-03-28T00:36:26Z"}, {"author": "Robert Sparks", "text": "not forced to only have the \"jabber\" topic.
", "time": "2023-03-28T00:36:38Z"}, {"author": "Martin Thomson", "text": "inertia is a powerful thing
", "time": "2023-03-28T00:37:16Z"}, {"author": "Robert Sparks", "text": "@chairs - I'm talking with MeetEcho - what slide set didn't look right?
", "time": "2023-03-28T00:37:37Z"}, {"author": "Pete Resnick", "text": "The chair slides didn't seem to appear in the tool.
", "time": "2023-03-28T00:41:12Z"}, {"author": "Robert Sparks", "text": "They are there on the MeetEcho console view.
", "time": "2023-03-28T00:42:48Z"}, {"author": "Russ Housley", "text": "Paul, use the mic
", "time": "2023-03-28T00:45:35Z"}, {"author": "Robert Sparks", "text": "and I'm happy because we're essentially versioning smaller increments in the protocol without using the rfcxml version field.
", "time": "2023-03-28T01:01:53Z"}, {"author": "Kesara Rathnayake", "text": "+1 for smaller increments.
", "time": "2023-03-28T01:03:59Z"}, {"author": "Notification Bot", "text": "A message was moved here from #rswg > regenerating HTML by Kesara Rathnayake.
", "time": "2023-03-28T01:04:25Z"}, {"author": "Alice Russo", "text": "Re: this slide, <u> \"Not used in published RFCs\" is not accurate. It has been used in 3 RFCs: 8771, 8949, 9290.
", "time": "2023-03-28T01:12:59Z"}, {"author": "Kesara Rathnayake", "text": "second point is wrong?
\n$ grep -r "<u " .\n./rfc8949.xml: notation for a UTF-8 string containing the single Unicode character <u format="num-name-lit" pn="u-1">\u00fc</u>. Similarly, "\\u6c34" is a UTF-8 string in\n./rfc8949.xml: diagnostic notation with a single character <u format="num-name-lit" pn="u-2">\u6c34</u>,\n./rfc8949.xml: in diagnostic notation with a single character <u format="num-name-lit" pn="u-3">\ud800\udd51</u>. (Note that all these single-character\n./rfc9290.xml:<u format="lit-name-num" pn="u-1">\u05e9</u>,\n./rfc9290.xml:<u format="lit-name-num" pn="u-2">\u05dc</u>,\n./rfc9290.xml:<u format="lit-name-num" pn="u-3">\u05d5</u>,\n./rfc9290.xml:<u format="lit-name-num" pn="u-4">\u05dd</u>.\n./rfc8771.xml: one-character sequence <u format="num" pn="u-1">.</u> is believed to cause sufficient disorder\n./rfc8771.xml: <u format="num-name" pn="u-2">c</u></td>\n./rfc8771.xml: <u format="num-name" pn="u-3">l</u></td>\n./rfc8771.xml: <u format="num-name" pn="u-4">\u04a4</u></td>\n./rfc8771.xml: than 1 (<u format="num" pn="u-5">\u04a4</u>) .</li>\n./rfc8771.xml: <li pn="section-5-8.2">There are two IDNA2008 DISALLOWED characters: <u format="num-name" pn="u-6"/> U+000C (for good reason!) and <u format="num" pn="u-7">\u04a4</u>.</li>\n./rfc8771.xml: 'I-DUNNO'. For that purpose, <u format="num-lit-name" pn="u-8">-</u>\nAre we doing country as ISO 3166 or in English, or in a native tongue? Does there need to be a canonical name? What about Aotearoa?
", "time": "2023-03-28T01:15:42Z"}, {"author": "Martin Thomson", "text": "we don't need to run the tool one more time; we have the output of the tool, so we can just get postalLine from the rendered text/html/whatever
", "time": "2023-03-28T01:17:48Z"}, {"author": "Robert Sparks", "text": "I think this should be \"we dont care - take a string - use it\"
", "time": "2023-03-28T01:20:32Z"}, {"author": "Eric Rescorla", "text": "So we're clearly going to need a discussion about whether this rewrite of the XML is OK
", "time": "2023-03-28T01:22:56Z"}, {"author": "Eric Rescorla", "text": "It's not at all unusual to have situations where the same document structure maps onto two different identifier sets
", "time": "2023-03-28T01:51:09Z"}, {"author": "Jay Daley", "text": "I understand Martin's point here as being that it is not appropriate for the authors to sign off on something that is then modified before publication, even if we believe that modification is minor.
", "time": "2023-03-28T01:51:19Z"}, {"author": "Eric Rescorla", "text": "For instance, if you have a document written in LaTeX, different styles will have (for instance) 1., 2., .... or I, II, ...
", "time": "2023-03-28T01:51:46Z"}, {"author": "Eric Rescorla", "text": "IIRC, this is USENIX versus IEEE style
", "time": "2023-03-28T01:52:14Z"}, {"author": "Jay Daley", "text": "Kesara points out our RNC uses a notation extension that allows for defaults. So we can rely on that schema if needed - i.e. leave the published RFC with a pointer in it to the version of the schema used at that time
", "time": "2023-03-28T01:54:56Z"}, {"author": "Kesara Rathnayake", "text": "a:defaultValue is used to add defaults in RelaxNG. We already have defaults for some in v3.rng
I'm pretty sure it's canonicalicity :)
", "time": "2023-03-28T02:00:07Z"}, {"author": "Robert Sparks", "text": "canonicalicity -> acanonicalicity -> baconicalicity
", "time": "2023-03-28T02:01:27Z"}, {"author": "Rich Salz", "text": "Does the discussion get simpler if we use the term \"official\" instead of \"canonical\" ?
", "time": "2023-03-28T02:04:44Z"}, {"author": "Rich Salz", "text": "Robert Sparks said:
\n\n\ncanonicalicity -> acanonicalicity -> baconicalicity
\n
Hmm.... bacon.
", "time": "2023-03-28T02:05:12Z"}, {"author": "Alexis Rossi", "text": "I really think we need to write an Archival Policy document that lays out what we mean by these terms, confirms/adjusts what formats cannot change, etc.
", "time": "2023-03-28T02:05:46Z"}, {"author": "Jay Daley", "text": "Yes, agree
", "time": "2023-03-28T02:07:53Z"}, {"author": "Robert Sparks", "text": "Now Paul's done it. Mathmaticians and Physicists will by rioting in the streets by sunset.
", "time": "2023-03-28T02:23:02Z"}, {"author": "Brian Carpenter", "text": "+1 to Alexis
", "time": "2023-03-28T02:27:54Z"}, {"author": "Brian Carpenter", "text": "hand up to adopt Paul's doc
", "time": "2023-03-28T02:28:24Z"}, {"author": "Martin Thomson", "text": "@Paul Hoffman I opened an issue for you about <artwork>