IETF Logo Mail Archive

Re: [xml-dev] The problems and the future of the web and a formal internet technology proposal

Raphaël Hendricks <rhendricks@netcmail.com> Mon, 04 January 2021 22:34 UTC

Return-Path: <rhendricks@netcmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 087F73A0888 for <ietf@ietfa.amsl.com>; Mon, 4 Jan 2021 14:34:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.219
X-Spam-Level:
X-Spam-Status: No, score=-0.219 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=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=netcmail.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 Z1V3-TYNsBuf for <ietf@ietfa.amsl.com>; Mon, 4 Jan 2021 14:34:50 -0800 (PST)
Received: from msg-1.mailo.com (msg-1.mailo.com [213.182.54.11]) (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 B47593A0864 for <ietf@ietf.org>; Mon, 4 Jan 2021 14:34:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=netcmail.com; s=mailo; t=1609799609; bh=pl1I6ZkkQUPTyqGgmniGYmBoKJkWg6Jes/v0En2qB10=; h=X-EA-Auth:In-Reply-To:References:Mime-Version:Content-Type: Message-Id:Cc:Content-Transfer-Encoding:From:Subject:Date:To: X-Mailer; b=oQfr4FomIUS1ZLDM5bl9Xd4P6VYI17kDNWcnRPavwhawpnVBQ/DXEAmux1VM+3qi6 jK5ktYgNG/NaAiIQ5M5FszZBLik6t3TYGltxacZKeY1hBLNCKZtSCFjw6WkdTSfe81 8Lw8pbe408R8uaZiHwbcgli/MhP+oYwq/G+wctVg=
Received: by b-5.in.mailobj.net [192.168.90.15] with ESMTP via ip-206.mailobj.net [213.182.55.206] Mon, 4 Jan 2021 23:33:29 +0100 (CET)
X-EA-Auth: VwmFZsXV+P8tUPlp3piDEVNZzw2vS1AA9p5DaW5jhhYLle+yhwxZRRh4+cPQuWTy3O9Rb+28EBXCziX1jF4Lt5CHw3NowsKyc/7qZruJuR8=
In-Reply-To: <CAHKy_pNrQ1yXzpPkif2gW1K75r8SJNvyfw+-KEVw2tR7XnnCFA@mail.gmail.com>
References: <51AEC656-F7E6-40F5-8896-942C03B9ED29@netcmail.com> <CAHKy_pNrQ1yXzpPkif2gW1K75r8SJNvyfw+-KEVw2tR7XnnCFA@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset="ISO-8859-1"; delsp="yes"; format="flowed"
Message-Id: <E82400DF-24C4-4EB2-A12A-86772B6AE158@netcmail.com>
Cc: project-admin@oasis-open.org
Content-Transfer-Encoding: quoted-printable
From: Raphaël Hendricks <rhendricks@netcmail.com>
Subject: Re: [xml-dev] The problems and the future of the web and a formal internet technology proposal
Date: Mon, 04 Jan 2021 17:34:46 -0500
To: Sir Timothy Berners-Lee <cos@timbl.com>, Ivan Herman <ivan@w3.org>, Eric Prud'hommeau <eric@w3.org>, IETF Discussion Mailing List <ietf@ietf.org>, xml-dev@lists.xml.org, public-exploresemdata@w3.org, public-philoweb@w3.org, public-web-copyright@w3.org, public-dntrack@w3.org, Liam Quin <liam@fromoldbooks.org>
X-Mailer: Apple Mail (2.753.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CUwAGy5Y2MVnBVBx7jGhyDD6rnU>
X-Mailman-Approved-At: Wed, 06 Jan 2021 13:16:29 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2021 22:34:53 -0000

Hello to all list members. I wish to bring an precision to my first  
message, because a point in a reply makes me suspect that a point was  
not clear in my message and can lead everyone to an erroneous  
understanding

someone answered:
> Mercury is a fine statically-typed, restricted variant of Prolog, and
> even used as implementation language for Prince XML, but if you want
> to push for logical programming on document data,

I wish to say that I was talking about the Mercury language as an  
example, a possibility for the second technological platform, and,  
here is the point which may have been unclear, I recommand that the  
second platform (the remote software execution platform) give-up all  
HTML/XML baggage, it should use pure software code, no page/markup  
stuff of any kind. Some may have accidently been led to think that I  
am pushing XML for both platforms, this is not the case. I am not  
pushing for logical programming on document data as is being suggested.

Raphaël Hendricks

v2.23.0 | Report a Bug | By Email