| View previous topic :: View next topic |
| Author |
Message |
IDPF IDPF Member

Joined: 04 Jan 2006 Posts: 32 Location: Canada
|
Posted: Tue Dec 26, 2006 12:46 pm Post subject: OPS/OPF 2.0 Released as IDPF Informational Documents |
|
|
The IDPF's Open eBook Publication Structure (OEBPS) Working Group has released two working draft specifications, the Open Publication Structure (OPS) 2.0 (internal working draft v0.7) and the Open Packaging Format (OPF) 2.0 (internal working draft v0.7) for public distribution and review as IDPF informational documents.
The IDPF strongly encourages feedback from potential users, developers and others, whether IDPF members or not, for the sake of improving interoperability and quality of IDPF work. The Working Group requests that comments to the specifications be made before Wednesday, January 31st in order to facilitate revision of the specifications. The specifications are available at:
OPS 2.0: http://www.idpf.org/doc_library/informationaldocs/OPS/OPS_2.0_0.7_draft.htm
OPF 2.0: http://www.idpf.org/doc_library/informationaldocs/OPS/OPF_2.0_0.7_draft.htm
Feedback on the draft specifications should be made by posting a reply to this forum topic.
Links to all IDPF specification documents:
http://www.idpf.org/specs.htm
Document Summary
The OPS 2.0 and OPF 2.0 specifications are successors to OEBPS 1.2 which was released as an official IDPF specification in August 2002. The OPS specification describes a standard for representing the content of electronic publications. The OPF specification defines the mechanism by which the various components of an OPS publication are tied together and provides additional structure and semantics to the electronic publication. OPS/OPF will increase the viability and adoption of the previous OEBPS standard as both a cross-reading system interchange and production format as well as a final publication delivery format.
Both OPF and OPS are aligned with the OEBPS Container Format (OCF) specification which defines the standard mechanism by which all components of an electronic publication may be packaged together into a single archive for transmission, delivery and archival purposes. The OCF specification was released as an official IDPF specification on October 27th, 2006.
The OPS/OCF documents were submitted to the IDPF Board of Directors as an Informational Document as defined by the IDPF’s Policies and Procedures, section 4.6.1. While Informational Documents do not have an official specification status in the organization, the Working Group felt it important that IDPF members and the public have the opportunity to review the draft specification in order to obtain feedback on the current state of the proposal as well as to alert IDPF members that a proposal is forthcoming in order to allocate appropriate resources for a proper review. The document is expected to be submitted to the official IDPF output process in Q1 2007 which consists of Board of Director, public, intellectual property and membership review and a final membership vote.
This document was approved for submission by the Working Group on Thursday, December 14th and approved for release by the IDPF Board of Directors as an Informational Document on Friday, December 22nd.
The following documents may prove useful for introduction:
Working Group Charter: http://www.idpf.org/idpf_groups/oebpswg.htm
Specification Requirements: http://www.idpf.org/doc_library/informationaldocs/oebps_requirements.htm
IDPF member presentations on OPS, OPF & OCF: http://www.idpf.org/events/presentations.htm
Document Output Procedure
The OPS/OPF 2.0 documents are currently informational documents. All public comments made on the specification will be considered by the Working Group and, if appropriate, edits to the working drafts will be made. The Working Group expects to submit a final draft specification to the IDPF official output process in Q1 2007.
How to Make Comments on the Informational Documents
All comments are collected and addressed by the Working Groups in the IDPF Standards Forums. Feedback on the draft specifications should be made by posting replies to this forum topic.
I would like to thank all of the contributors to these documents for their hard work and time.
Best,
Nick Bogaty
--
Nick Bogaty
Executive Director
International Digital Publishing Forum (IDPF) |
|
| Back to top |
|
 |
b.wolterding
Joined: 05 Feb 2007 Posts: 15 Location: Europe
|
Posted: Thu Feb 08, 2007 11:12 am Post subject: specification of the "meta" element |
|
|
Even if it may be late, I have a comment to the OPF 2.0 draft specification, regarding the "meta" element used for additional metadata, see Sec. 2.2.
According to the specification, the <meta> tag is supported "analogous to the XHTML 1.1 meta element". Some examples are given, but a more specific definition is missing.
Judging by the OEBPS 1.2 DTD, the following attributes are supported for the "meta" tag: "name", "scheme", "id", "xml:lang", and "content". The attribute "http-equiv", present in the XHTML 1.1 specification, is not supported (of course it would be meaningless here). In addition (like in XHTML), the "name" attribute is constrained to NMTOKEN, so e.g. its value cannot start with a digit.
Extract from the OEBPS 1.2 DTD:
| Code: |
<!ELEMENT meta EMPTY>
<!ATTLIST meta
%CommonAttributes;
content CDATA #REQUIRED
name NMTOKEN #REQUIRED
scheme CDATA #IMPLIED>
|
I am not sure whether the OPF 2.0 DTD will introduce changes at this point. But neither from the examples nor from the specification text, it seems clear to me what the actually supported subset is. For example, the "xml:lang" attribute is not mentioned anywhere in the draft.
In any case, I think the textual OPF specification should be more specific in this respect.
B. Wolterding |
|
| Back to top |
|
 |
Garth Conboy IDPF Member

Joined: 08 Nov 2006 Posts: 10 Location: La Jolla, California
|
Posted: Thu Feb 08, 2007 4:10 pm Post subject: |
|
|
Thank you for your post. There is still time to clairify issues such as these -- we will endevor to do so. It is likely that the OEBPS 1.2 DTD for OPF will be replaced with a RelaxNG specification for OPF 2.0 -- this should afford an opportunity for tighter specification.
Also note the example from the draft -- showing, perhaps, "normal" usage:
| Code: |
<metadata xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:opf="http://www.idpf.org/2007/opf">
<dc:title>Tale of Two Cities</dc:title>
<dc:creator opf:role="aut">Charles Dickens</dc:creator>
…
<meta name="price" content="USD 19.99" />
</metadata>
|
|
|
| Back to top |
|
 |
|