Return-Path: Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 95238 invoked from network); 1 Jun 2002 06:49:01 -0000 Received: from eos.telenet-ops.be (195.130.132.40) by daedalus.apache.org with SMTP; 1 Jun 2002 06:49:01 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by eos.telenet-ops.be (Postfix) with SMTP id D3F991FF36 for ; Sat, 1 Jun 2002 08:49:11 +0200 (CEST) Received: from elisabeth (D5E00804.kabel.telenet.be [213.224.8.4]) by eos.telenet-ops.be (Postfix) with SMTP id 4459620191 for ; Sat, 1 Jun 2002 08:49:11 +0200 (CEST) From: "Steven Noels" To: Subject: RE: http://www.openebook.org/ compliance? Date: Sat, 1 Jun 2002 08:49:11 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <004d01c2090b$34526320$0c91fea9@galina> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > From: Ivelin Ivanov [mailto:ivelin@apache.org] > The xml markup appears to be a superset of document-v10. > Issues like resource referencing through a catalog of links have been > addressed. > (This is related to the issue Rob and I discussed recently. > The solution is > similar too, using ids for each link.) Seems like a mixture of XHTML and Dublin Core metadata to me. Ideally, we should have a pipeline that aggregates all documents and publishes them as one eBook 'pkg' document. Interesting thought - does anyone has an eBook reading device on this list?