masinter / pdf-data-cg-charter Goto Github PK

https://github.com/tabulapdf/tabula shares some of the same approach as Abe's PDFData but made some different choices; document these and resolve them.

"It would be really good if it were easy to create PDFs where one could readily extract:"

• images complete with captions;
• data tables (see CSV on the Web WG [1]);
• the text (with markup), tables of content and indexes;
• annotations (see annotations WG [2]);
• citations (see Force 11 guidelines [3]);
• disambiguation using RDFa, ITS tags to aid machine translation, schema.org for discovery and more.

[1] http://www.w3.org/2013/csvw/
[2] http://www.w3.org/annotation/
[3] https://www.force11.org/datacitation
[4] http://standards.data.gov.uk/profile/viewing-government-documents-profile

I'm leaning toward a weekly meeting and some focus, but that the group should have a short time horizon -- plan to be done in 6 months? If feasible; any case no more than a year.

The charter should be ready for approval in September, but we could get started sooner on most of the deliverables.

https://www.w3.org/2013/04/odw/Role_of_PDF_and_Opendata_final.pdf

https://jacattell.wordpress.com/2016/02/28/publishing-opendata-in-portable-document-format-pdf-files/

This issue is about the description of the CG that is in W3C's list of community groups, e.g., if you look for all current CGs or if you do a search.

I originally put in a very terse 'description' for the CG and said "A charter will be posted soon".

What we need is a paragraph describing the group that will make people want to join. And at least a pointer to the charter.

There is no apparent UI to change the group description except to ask the site manager, so unfortunately that seems necessary.

https://www.w3.org/TR/2014/WD-csvw-ucr-20140327/

shows some interesting use cases which should work independently of whether the document is HTML or PDF.

PDF supports all of the same features that HTML does, as far as they are required for LOD; What’s missing?
§ Education – How do we get this message out to the world?
a primer?
§ Specifications – How to map existing HTML-based LOD to PDF? (and back!)
§ Tools, Samples and Demonstrations – How does someone actually do LOD with PDF?
(Both authoring and extraction/processing

What documents should we produce?
Consider the analogy with accessibility: there's WCAG (Web Content Accessibility Guidelines) which establishes various levels of accessibility, and there are notes defining how to accomplish those levels for various formats, including PDF (https://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140408/pdf.html) but also others.

For linked data, there are levels of 'open data' (right now we have 5 stars), and then there are techniques for accomplishing those.

This community group could focus on 'techniques for Data in PDF (covering directions for adding to a generic format), but this would provide a more inclusive roadmap.

"Complete tooling for open data in PDFs should be able to extract and act upon the following objects:"

doesn't belong in the "Goals" section. It's a wishlist of ideal state for any document in any format, and belongs in a "Requirements" document, but the list doesn't belong in the charter goals.

"Specify an establish best practices for inserting, maintaining, and extracting relevant information."

Phil's list was a "it would be nice if" or we should show how to extract all those things if they're there.

https://github.com/Aiybe/PDFData

consider JSON-LD where RDFa is mentioned, don't be so specific.
Keep it simple