Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Profiles/Formats: Document actual mechanics #88

Open
kba opened this issue Oct 26, 2016 · 0 comments
Open

Profiles/Formats: Document actual mechanics #88

kba opened this issue Oct 26, 2016 · 0 comments

Comments

@kba
Copy link
Owner

kba commented Oct 26, 2016 •
edited
Loading

Their function is to convey what kind of hOCR/HTML markup is to be expected, so it's kind of like a set of capabilities with additional description of the purpose or origin of the data.

If profiles are conceptually distinct from the HTML markup restrictions (formats?), we could introduce a ocr-profile metadata field or similar and create a base list of profiles, including samples. If profiles and formats are related enough, they should be merged (#62)

See also #17 (comment)
@kba kba changed the title Profiles: Document actual mechanics Profiles/Formats: Document actual mechanics Oct 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kba