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.

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

What should be the recommended values for title-type? #49

Closed
GoogleCodeExporter opened this issue Mar 24, 2015 · 3 comments
Closed

What should be the recommended values for title-type? #49

GoogleCodeExporter opened this issue Mar 24, 2015 · 3 comments
Labels
Priority-Medium Spec-OPF The issue affects the OPF 2.0.1 specification (not maintained)

Comments

@GoogleCodeExporter
Copy link

Metadata subgroup divided on how specific this vocabulary should be. Currently 
the recommendation includes values of primary, short, long, sub, series, 
collection, edition, slang. Main question: inconsistent publisher use of 
"series" vs. "collection," lack of clarity as to how they nest. Some feel we 
should not attempt to specify such values at all, and simply rely on integers 
to distinguish title-type 1, title-type 2, etc.; others think these specific 
recommended types are useful, but the spec prose needs to explain the 
distinctions clearly.

Original issue reported on code.google.com by bkasd...@apexcovantage.com on 9 Nov 2010 at 6:27

@GoogleCodeExporter
Copy link
Author

I certainly agree with this; we have MARC and ONIX references for role,  ONIX 
references for scheme, and so on [1]. 

Would clearly be preferable if we could delegate values for title-type to some 
list defined in ONIX, MARC or MODS. Graham, BillK, any suggestions?

[1] 
http://epub-revision.googlecode.com/svn/trunk/build/spec/epub30-publications.htm
l#elemdef-opf-meta-property-values-ancillary

Original comment by markus.g...@gmail.com on 27 Jan 2011 at 1:00

  • Changed state: Accepted
  • Added labels: Spec-OPF

@GoogleCodeExporter
Copy link
Author

Original comment by markus.g...@gmail.com on 27 Jan 2011 at 1:02

  • Added labels: Type-SpecIssue
  • Removed labels: Type-Defect

@GoogleCodeExporter GoogleCodeExporter added Priority-Medium auto-migrated Spec-OPF The issue affects the OPF 2.0.1 specification (not maintained) labels Mar 24, 2015
@GoogleCodeExporter
Copy link
Author

This issue has been addressed in r2823.

title-type allows a string value which can be modified by the scheme property 
to indicate the code list or other source it is drawn from.

Original comment by mgarrish on 25 Apr 2011 at 8:38

  • Changed state: Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority-Medium Spec-OPF The issue affects the OPF 2.0.1 specification (not maintained)
Projects
None yet
Development

No branches or pull requests

1 participant