Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B9106200C87 for ; Wed, 17 May 2017 12:18:59 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B76AF160BBA; Wed, 17 May 2017 10:18:59 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 095D3160BB5 for ; Wed, 17 May 2017 12:18:58 +0200 (CEST) Received: (qmail 88673 invoked by uid 500); 17 May 2017 10:18:58 -0000 Mailing-List: contact users-help@pdfbox.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@pdfbox.apache.org Delivered-To: mailing list users@pdfbox.apache.org Received: (qmail 88660 invoked by uid 99); 17 May 2017 10:18:57 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 May 2017 10:18:57 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 8C3A3C1817 for ; Wed, 17 May 2017 10:18:57 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1 X-Spam-Level: * X-Spam-Status: No, score=1 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id wO_0ca4NYR8D for ; Wed, 17 May 2017 10:18:53 +0000 (UTC) Received: from mail.fmode.de (fmode.de [94.247.40.242]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 535F15FDEE for ; Wed, 17 May 2017 10:18:53 +0000 (UTC) Received: from [192.168.1.114] (unknown [212.204.61.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.fmode.de (Postfix) with ESMTPSA id 16936B00E7A for ; Wed, 17 May 2017 12:18:53 +0200 (CEST) From: Peter Pinnau Subject: Custom XMP schemas vs. XMPMediaManagementSchema To: users@pdfbox.apache.org Message-ID: <04fccbc0-d4e8-4309-3f77-0a77ef2a2937@unterbrecher.de> Date: Wed, 17 May 2017 12:18:52 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit archived-at: Wed, 17 May 2017 10:18:59 -0000 Not sure if this is the right place for this topic. I am working on a document management software which already has a number of features to work on PDF documents like real-life paper. My plan is to add some kind of modification history information to the PDF. Let's call it a "feed" in modern speech. I take a look at the Adobe XMP specifications: https://www.adobe.com/content/dam/Adobe/en/devnet/xmp/pdfs/XMPSpecificationPart2.pdf It seems that the "XMP Media Management Schema" with the field "versions" could be the perfect place for the "feed". The specification says that the XMPMM->versions field is a list of version objects. A version object has some properties like date, event, comments ... A corresponding org.apache.xmpbox.type.VersionType exists in xmpbox but is not used as far as I can see. The versions property of org.apache.xmpbox.schema.XMPMediaManagementSchema returns just a List. Is the current implementation incomplete at this point? Is there a chance to get it working? Generally I would prefer to use well-known XMP schemas instead of creating an own. -- Viele Grüße Peter Pinnau --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org For additional commands, e-mail: users-help@pdfbox.apache.org