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

Comment for dct:title #20

Closed
tombaker opened this issue Jun 2, 2018 · 8 comments
Closed

Comment for dct:title #20

tombaker opened this issue Jun 2, 2018 · 8 comments

Comments

@tombaker
Copy link
Collaborator

tombaker commented Jun 2, 2018

See note_title.md

Add a comment for http://purl.org/dc/terms/title:

Typically, a Title will be a name by which the resource is formally known.

If in doubt about what constitutes the title, repeat the Title element and
include the variants in second and subsequent Title iterations.

Note:

  • These would appear in ISO 15836-2 as "NOTE 1 to entry:" and "NOTE 2 to entry:".
@tombaker
Copy link
Collaborator Author

tombaker commented Jun 2, 2018

Note that the ISO WG actually suggests changing the definition to read:

A name given to the resource; usually a name by which the resource is
formally known. 

Older Usage Board members may vaguely recall discussions of this very point in
the early 2000s involving somewhat inconclusive discussions about what might be
considered "formal". Before 2006, the comment for Title read:

Typically, a Title will be a name by which the resource is formally known.

Exercising his judgement as Chair, Tom has edited this proposal into one for
reinstating the earlier comment.

@tombaker
Copy link
Collaborator Author

tombaker commented Jun 2, 2018

The second comment (about repeating the Title "element"), seems more appropriate to a user guide than to the main vocabulary specification.

@tombaker tombaker added this to the By June 15 - "easy" proposals milestone Jun 2, 2018
@tombaker tombaker changed the title Add comment for dct:title Comment for dct:title Jun 3, 2018
@vcharles89
Copy link

I would really prefer to keep the original definition: A name given to the resource; usually a name by which the resource is formally known. In other domain than libraries like museum, the title is really just a name given to the resource. At Europeana, we came back to the original definition to make it clear that a title doesn't have to be title as defined in the library domain. In some case title is used for its functional role only: finding stuff from the search.

@osma
Copy link
Collaborator

osma commented Jun 27, 2018

RDF triples have no order, so when expressing DC metadata as RDF the phrase "second and subsequent Title iterations" becomes somewhat meaningless.

@jneubert
Copy link
Collaborator

+1 to @osma . Instead of adding "second and subsequent" title properties, better http://purl.org/dc/terms/alternative should be used.
So I tend to agree with @vcharles89 Leave the definition as it is.

@juhahakala
Copy link

The original definition has been restored to the ISO draft, and the (added) note has been removed from it. Note that in ISO standards the usage of articles if forbidden in term definitions; therefore just "name given to the resource", not "a name given to the resource".

@aisaac
Copy link
Collaborator

aisaac commented Jul 13, 2018

So we can close this one if the proposals have been rescinded?

@tombaker tombaker removed the comments label Jul 18, 2018
@tombaker
Copy link
Collaborator Author

@aisaac We can indeed close issues for proposals that have been withdrawn... Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants