https://github.com/w3c/dpub-metadata

Metadata Task force documents of the Digital Publishing IG
https://github.com/w3c/dpub-metadata

digital-publishing metadata publishing

Last synced: 3 months ago
JSON representation

Metadata Task force documents of the Digital Publishing IG

• Host: GitHub
• URL: https://github.com/w3c/dpub-metadata
• Owner: w3c
• Archived: true
• Created: 2014-08-19T04:39:01.000Z (over 10 years ago)
• Default Branch: gh-pages
• Last Pushed: 2017-09-29T13:54:21.000Z (about 7 years ago)
• Last Synced: 2024-09-25T22:27:20.510Z (3 months ago)
• Topics: digital-publishing, metadata, publishing
• Language: HTML
• Size: 336 KB
• Stars: 5
• Watchers: 34
• Forks: 6
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
The [Digital Publishing Interest Group](https://www.w3.org/dpub/IG), that managed this repository, ***is now closed***, and so is this repository. Activities in the group has been taken up by:

* The [Publishing Business Group](https://www.w3.org/publishing/groups/publ-bg)

* The [Publishing Working Group](https://www.w3.org/publishing/groups/publ-bg)

* The [EPUB 3 Community Group](https://www.w3.org/publishing/groups/epub3-cg)

All these groups are part of the [Publishing@W3C](https://www.w3.org/publishing), born out of the merger of IDPF and W3C.

– Ivan Herman ([email protected])

---

# dpub-metadata #

Documents produced by the [Metadata task force](https://www.w3.org/dpub/IG/wiki/Task_Forces/Metadata) of the [Digital Publishing Interest Group](http://www.w3.org/dpub/IG) of the W3C.

See also a [paged view](http://w3c.github.io/dpub-metadata/) of the document served in HTML.

If you are member of the interest group, and you wish to contribute to the content of this repo, please contact Ivan Herman () or Thierry Michel (), giving them your github login.

## Technical note ##

Note that there are two documents (index.html and interviews.html) that constitute the full report. There is a small jQuery function at the beginning of both documents that mutually link the two documents by modifying the table of content headers. That function is invoked via respec.

Also, the acronym list in the appendix is stored in a separate file (acronym.html) and is included, via respec, into both documents, thereby ensuring consistency.