Re: [xml-dev] The problems and the future of the web and a formal internet technology proposal
Raphaël Hendricks <rhendricks@netcmail.com> Sun, 24 January 2021 22:40 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 AC52E3A0C7A for <ietf@ietfa.amsl.com>; Sun, 24 Jan 2021 14:40:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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 JRkpjy4uKJem for <ietf@ietfa.amsl.com>; Sun, 24 Jan 2021 14:40:04 -0800 (PST)
Received: from msg-2.mailo.com (msg-2.mailo.com [213.182.54.12]) (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 B52733A0C7B for <ietf@ietf.org>; Sun, 24 Jan 2021 14:39:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=netcmail.com; s=mailo; t=1611527507; bh=VT8Kphy8ay4mm/bexzYJFwABvS1hFBGLkT1OnUWflC0=; 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=fi0eekl+mBm3ks8PoQHVbwMw/Fz8AouT3xAGIBi0S/B6urCoBq312gjhLCGbkKLpl 9ASsyi5wS9q5cCqQbN3hkZalgg6XD4kD/QWkctq5V794qLWyNe64WgEHnglCGzXiym ca7F+brfBJSRiFrkE7IEKAkZcMfAGm/u5gqieC7w=
Received: by b-3.in.mailobj.net [192.168.90.13] with ESMTP via ip-206.mailobj.net [213.182.55.206] Sun, 24 Jan 2021 23:30:59 +0100 (CET)
X-EA-Auth: EhrDqn0uo4IO6PpTghvwabARanwZWsW1r6f32CU5P/qqD1KJP0JHaUVHCrCzyPeQ3b5Oh0amScNrRa/8R+4DzVmZdtcVEW97CzBwf6D+ilI=
In-Reply-To: <CABzTEQCyTSFAuh+VgPQehVJ4yE6wma0qZ9CQWnz2OYVK74Rxyg@mail.gmail.com>
References: <51AEC656-F7E6-40F5-8896-942C03B9ED29@netcmail.com> <CABzTEQCyTSFAuh+VgPQehVJ4yE6wma0qZ9CQWnz2OYVK74Rxyg@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: <1D3EAACC-3429-4C77-86C6-631566C2657E@netcmail.com>
Cc: Sir Timothy Berners-Lee <cos@timbl.com>, Liam Quin <liam@fromoldbooks.org>, Ivan Herman <ivan@w3.org>, Eric Prud'hommeau <eric@w3.org>, IETF Discussion Mailing List <ietf@ietf.org>, xml-dev <xml-dev@lists.xml.org>, public-exploresemdata@w3.org, public-philoweb@w3.org, public-web-copyright@w3.org, public-dntrack@w3.org, 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: Sun, 24 Jan 2021 17:31:46 -0500
To: John Cowan <johnwcowan@gmail.com>
X-Mailer: Apple Mail (2.753.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/q2VT1zgiPk72IFa9rvBwyjaIQZ8>
X-Mailman-Approved-At: Mon, 25 Jan 2021 07:13:25 -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: Sun, 24 Jan 2021 22:40:07 -0000
Dear Mr. John Cowan to all list-users: I am sorry for the delay, there have been many days where I was too weak to answer, since I am battling chronic fatigue syndrome, and have many days where I am non-functionnal; moreover, during the few days where I felt better, I had some pressing issues to handle until a week ago, then I felt bad from monday to thursday and since I felt better afterwards, I prepared the answers for the list on Friday, Saturday and Sunday. > The difficulty with all that is that it is just horribly complicated > and constantly growing, one technology after another. What happens > then is that it becomes just about as hard to write a browser for > XHTML-2.0-plus-long-tail than it is to write on for HTML5/CSS/JS, if > not more so. The idea with the switch to XML is not to allow easier browser development. The idea is to have clean content, properly structured and easy to index and analyze, allowing RDFa for semantic information inclusion, which would vastly improve the adequation of search engine results, at least those search engines not made by companies with the required money to allow them to master the advance artificial inteligence needed to analyze natural language. It also alows data manipulation, generation and verification using standard XML tools such as XSLT / Schematron. > JSON and when needed MicroXML for structured data. JSON doesn't have all the standardized XML manipulation advantages (such as with XSLT). Raphaél Hendricks
- The problems and the future of the web and a form… Raphaël Hendricks
- Re: The problems and the future of the web and a … Phillip Hallam-Baker
- Re: The problems and the future of the web and a … Raphaël Hendricks
- Re: [xml-dev] The problems and the future of the … Raphaël Hendricks
- Re: The problems and the future of the web and a … Raphaël Hendricks
- Re: [xml-dev] The problems and the future of the … John Cowan
- Re: [xml-dev] The problems and the future of the … Raphaël Hendricks