Re: [calsify] Getting started with the calendar persistence format

Ronald Tse <tse@ribose.com> Mon, 19 October 2020 23:30 UTC

Return-Path: <tse@ribose.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59A7E3A100E for <calsify@ietfa.amsl.com>; Mon, 19 Oct 2020 16:30:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level:
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ribose.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gCFe8dGWmY3i for <calsify@ietfa.amsl.com>; Mon, 19 Oct 2020 16:30:39 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-eopbgr1300051.outbound.protection.outlook.com [40.107.130.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1B133A100D for <calsify@ietf.org>; Mon, 19 Oct 2020 16:30:38 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kUDs65g/OwbFgkJIfUZLIwt5VSgEyprjH0TL2cuCG4ZB5Nyntvnp/NaiIDvNFSS/j2B/5GCVBw6fWkm8sUhzHAGhebZL/eM6WSBUhbs1X5xxIddC+EU8CNyEUCqDKCac39l6l2AhcNsz/cXaPEMzLyV2hg3G87UvtXvokjF561XT723B/M1EwCiabu8R+OaU2VMabRAQmx4qRmYQ9Ti5VbNq0GyohciIBK7MeacRFU11WrGD9+4pJbSM1Vn/oowotgcV3X0fSvuoXPUOqqhJE1wknZ8wvbc3+Y7c8FjhxuEFA0A1ahJbhXM6F7NHsi2YC6yPFu31bsDF8ICPmZ225Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=x+8/KQRP91a581DydGzdqNzlKJGNkpaHXQk95uLearE=; b=FYTrKxuy4LHgI+qsliL4YqQSdvnH1twV6gUH5pGyrJC/qaKD5fWkUKa6SiZQzRGhOM8SwVzUw1DKpoKMROQK6n4Msj92X2oi2rHU/es4KJCtsPhV9g88rkWClISkLsYy6iBDCxBW7lJAFpSy3ejHGl2ahGM8pveHXaDtbv3iFaJiUNqYvrC/oJhmk+qWLu1VCqXXzro0PSLxAdjGjTlSNwpzG+bMSaNPT0ssHkUVu2V0LXZutKd8XWueE0/wdDO56HjXmuazxj1K073dT83JnsnBZJxCIkRylVG+I2GG6PlV5tHkYXir8zow2/IuE0PwBSuNZ1+N3eCrTYwDlUgp6Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ribose.com; dmarc=pass action=none header.from=ribose.com; dkim=pass header.d=ribose.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ribose.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=x+8/KQRP91a581DydGzdqNzlKJGNkpaHXQk95uLearE=; b=DZaRYyOXWfO4aN218ZRCIMUxCGSEDKMChdSNbjcHmFeiFF2zSSEknngHocKMhRZb6Z3ouLkxgidCBWY8iPdaj3fepXLNLwrXwaSeFsmdMOhtew7+OZw3d+SQSh1rEt3Lj5G8IaV3rq84jguYQkZ6WYsueMWku7Z3FyqKCJLAmNk=
Received: from HK0PR01MB2900.apcprd01.prod.exchangelabs.com (2603:1096:203:98::14) by HK0PR01MB2897.apcprd01.prod.exchangelabs.com (2603:1096:203:97::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.24; Mon, 19 Oct 2020 23:30:33 +0000
Received: from HK0PR01MB2900.apcprd01.prod.exchangelabs.com ([fe80::b8:4b19:ebf4:7724]) by HK0PR01MB2900.apcprd01.prod.exchangelabs.com ([fe80::b8:4b19:ebf4:7724%5]) with mapi id 15.20.3477.028; Mon, 19 Oct 2020 23:30:33 +0000
From: Ronald Tse <tse@ribose.com>
To: Ujjwal Sharma <ryzokuken@igalia.com>
CC: "calsify@ietf.org" <calsify@ietf.org>
Thread-Topic: [calsify] Getting started with the calendar persistence format
Thread-Index: AQHWo0GwGjTIredru0qplU+nj0MZpqmZX5UAgAA/4QCABeLugIAAFsUA
Date: Mon, 19 Oct 2020 23:30:33 +0000
Message-ID: <55B0F7E9-114C-4830-87E5-523CC56D3528@ribose.com>
References: <668b5100-aab0-4353-bc11-132ed1f3785a@dogfood.fastmail.com> <F5EE6657-7355-417E-9BE7-E082138C6275@RIBOSE.COM> <c4213d07-d8fa-80f6-8741-e9f6e48ae382@igalia.com>
In-Reply-To: <c4213d07-d8fa-80f6-8741-e9f6e48ae382@igalia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3608.120.23.2.1)
authentication-results: igalia.com; dkim=none (message not signed) header.d=none;igalia.com; dmarc=none action=none header.from=ribose.com;
x-originating-ip: [58.153.245.161]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ebbc4ab4-9e84-4dd7-23fa-08d87486f98f
x-ms-traffictypediagnostic: HK0PR01MB2897:
x-microsoft-antispam-prvs: <HK0PR01MB289764C1B55FBBF5740A9EE9D71E0@HK0PR01MB2897.apcprd01.prod.exchangelabs.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 7SqE2WchkSG8ACYAzY39ji0yCvgDSlYxShF6aiPTXdxLVFxlaftOebp44U0cLC17LFA4lO3jvISjFZHpWIvf9SeVAKVeDXi2jzdtv5enLME5/nU7F4+d2DLODPHlPyjl9bDHy+mP58tDJGk1pgpg8VbFWNzn6IzlqgtUEBnHKHii4sQJoLoe2Xue8mXbNipQE4M0Z4tc026QNSZx5sBIJjhWSAOco+wLgUdstACyv4pmHN0PS9jZEVRajOkQmKK1kgm/mLBTJpOpfYlCJ9nPcrePyjD9bEF+AnQCbIfJ0FxyVjvsyGYlT5ztvt7i0FRFv+HsGz1HajMeijxoGQkBam7mEWoSe4cb8xflEZa7Pq+4h3aqJ3zvjacrKrQfX1a21S+JeTdhYyJMx8/thXSxkQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:HK0PR01MB2900.apcprd01.prod.exchangelabs.com; PTR:; CAT:NONE; SFS:(346002)(376002)(366004)(136003)(396003)(39830400003)(53546011)(5660300002)(6506007)(36756003)(6916009)(8676002)(4326008)(2906002)(71200400001)(316002)(166002)(966005)(186003)(6512007)(478600001)(8936002)(33656002)(66556008)(83380400001)(86362001)(64756008)(2616005)(66446008)(66476007)(26005)(76116006)(91956017)(66946007)(6486002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: 6OMRt7n+xuPu/mTFFGllCBjzJOK0Xxz/BH1nI3Iafhv3Bihv4N89hNsAUUTdYf/84e+OgLL7BFEVlxqHOzvubTobzfIF+cv/8dIy/1qgMEAdhrQbOylbFjZjiqBXzsxi6v1CP2ilsQpOINKF5SOzv44WAc9dw3ssQlECen01M/GFCU957W4julPffaCFauXBoJKg3eXD5ZMD62TloG7vuKvtUNcInEsLHIaPZZyLuDcqPYs/tYSDKXfYgTCpZfm88qx0TzvZv0ZtToHOPKdRAantyCcFsJuI0+PNrBy3gN7k0MXvGA2yGQTpYK3iz51mUMMSeTZA46YbtMi8fJINAuPymWRJDKeiLw/xEAaL/GUFsE4fpjCb7O2/S1Z8B13MYdFt27H/Oay7cYiZ37b4LIYysQi2Cw2P/YOUU6Gu1FaKzKN975bz5hgE24CTwtswHkqW793O1pb8h3HzKkXGPdG3gLnZ1OIDdmGwJk5Bj4RFXW7Px6yPdI2iCc5mZ6k+El0xzba2xMXFBLgYrg7lxlFTE8lU4KbI+R8t6AlobXRkEyOjk1iLQyJO0ntQkBn5htB92N6RPIOcwod9OR1V+CK/Hv55zVGjRAAM7SugATdIlq4fsQDIwFWaOyTLr7I4rzBlyFazL47aK4tfwxGFXA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_55B0F7E9114C483087E5523CC56D3528ribosecom_"
MIME-Version: 1.0
X-OriginatorOrg: ribose.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HK0PR01MB2900.apcprd01.prod.exchangelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ebbc4ab4-9e84-4dd7-23fa-08d87486f98f
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Oct 2020 23:30:33.2533 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: d98a04ff-ef98-489b-b33c-13c23a2e091a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: C5+xmgYc9BuI+uAw4/7lxtluUBQJlCFrVcwq/sWRE4wL+VZyTwGE6Y/1+xudLGLJ
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HK0PR01MB2897
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/tyofPx_IYl4Bf4tQD-TokazStZk>
Subject: Re: [calsify] Getting started with the calendar persistence format
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2020 23:30:42 -0000

Hi Ujjwal,

Would you be able to point me to the draft to see what the problem is?

Here’s a sample document that works:
https://raw.githubusercontent.com/metanorma/mn-samples-ietf/master/sources/antioch/document.adoc

(https://github.com/metanorma/mn-samples-ietf provides working examples)

If you have these two lines in your adoc file header (under the title but before the content, which is separated with a blank line):

"
:mn-document-class: ietf
:mn-output-extensions: rfc,xml,txt,html,rxl
“

Then you should be able to just run this:
metanorma draft-ryzokuken-timestamp-information.adoc

Ron

_____________________________________

Ronald Tse
Ribose Inc.

On Oct 20, 2020, at 6:09 AM, Ujjwal Sharma <ryzokuken@igalia.com<mailto:ryzokuken@igalia.com>> wrote:

Hi Ronald!

Thanks for the suggestion. Write once, publish anywhere (although
perhaps with minimal changes) is indeed a priority, especially given our
time constraints. I tried setting up metanorma today, but for some
reason, it fails for me locally.

My input:

metanorma --type rfc3 draft-ryzokuken-timestamp-information.adoc

Error:

Error: loading gem `metanorma-rfc3` failed. Exiting.

This works with or without `-x xmlrfc`. What seems to be wrong here? Am
I missing a gem? A simple web search doesn't return anything useful, and
no gem named `metanorma-rfc3` can be found.

I thought there was something wrong with my setup, but I tried multiple
times, ran `metanorma setup` properly, tried the docker version, but no
luck. The same error each time. Could you help me figure out what I missed?

Best,
Ujjwal

On 10/16/20 9:45 AM, Ronald Tse wrote:
Hi Ujjwal,

(Thanks Bron for the plug!)

Metanorma is one of the officially listed processors for IETF documents
(alongside mmark and kramdown-rfc2629).

CalConnect uses Metanorma to publish standards, and a number of SDOs do
so as well (ITU, OGC, BIPM, who also work with date/time).

If there is any intention to cross-publish into CalConnect or ISO, the
ability to "write once, publish anywhere” becomes important.

Given that we’re the folks behind it, I’m happy to serve as your
personal support if you run into any Metanorma problems :-)

Kind regards,
Ron
_____________________________________

Ronald Tse
Ribose Inc.

On Oct 16, 2020, at 8:27 AM, Bron Gondwana <brong@fastmailteam.com<mailto:brong@fastmailteam.com>
<mailto:brong@fastmailteam.com>> wrote:


Hi Ujjwal,

There's a variety of options for writing drafts.  I personally use a
workflow based on mmark, for example:

https://github.com/brong/draft-gondwana-effective-terminology

There's also metanorma, which allows you to create a variety of
outputs.  There's documentation here:

https://www.metanorma.com/author/ietf/

Or you can use tools like:

https://github.com/cabo/kramdown-rfc2629

Basically, they're all toolchains that generate RFC XML format documents.

In order to publish to the IETF, you need a datatracker account, and
you'll need to upload there:

https://datatracker.ietf.org/submit/tool-instructions/

Cheers,

Bron.

On Fri, Oct 16, 2020, at 09:21, Ujjwal Sharma wrote:
Hello everyone!

Thanks for the amazing discussions and help yesterday. Given our
constrained timeline, I suppose I should start working on the drafts
immediately.

On the IETF side of things, I suppose I'd need to start by creating an
I-D? Is there a set of resources you could point me to in order to get
up and running quickly?

Also, what should I do to get the ball rolling on the CalConnect/ISO
side of things?

Best,
Ujjwal

--
Ujjwal "Ryzokuken" Sharma (he/him)

Compilers Hacker, Node.js Core Collaborator and Speaker


_______________________________________________
calsify mailing list
calsify@ietf.org<mailto:calsify@ietf.org> <mailto:calsify@ietf.org>
https://www.ietf.org/mailman/listinfo/calsify


*Attachments:*

 * signature.asc


--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com<mailto:brong@fastmailteam.com> <mailto:brong@fastmailteam.com>


_______________________________________________
calsify mailing list
calsify@ietf.org<mailto:calsify@ietf.org> <mailto:calsify@ietf.org>
https://www.ietf.org/mailman/listinfo/calsify

--
Ujjwal "Ryzokuken" Sharma (he/him)

Compilers Hacker, Node.js Core Collaborator and Speaker