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

Definition of dct:relation #28

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

Definition of dct:relation #28

tombaker opened this issue Jun 3, 2018 · 8 comments

Comments

@tombaker
Copy link
Collaborator

tombaker commented Jun 3, 2018

See definition_relation.md - see also Issue #27 ('Properties "intended to be used with non-literal values")

DCMI Metadata Terms defines both http://purl.org/dc/elements/1.1/relation and http://purl.org/dc/terms/relation with the following definition and comment:

A related resource.

Recommended best practice is to identify the related resource by means of a
string conforming to a formal identification system.

In addition, DCMI Metadata Terms notes, for dct:relation - see Issue #27 :

This term is intended to be used with non-literal values as defined in the
DCMI Abstract Model.  As of December 2007, the DCMI Usage Board is seeking
a way to express this intention with a formal range declaration.

The ISO WG proposes:

A reference to a related resource.

Best practice is to identify the related resource by means of an URI or a
string conforming to a formal identification system.

Note:

  • In ISO 15836-2, the notes would be "NOTE x to entry:".
  • Definition was originally proposed by ISO WG without initial uppercase and full stop.
@tombaker
Copy link
Collaborator Author

Closing.

@tombaker
Copy link
Collaborator Author

Reopening

@tombaker
Copy link
Collaborator Author

tombaker commented Jul 19, 2018

28a. Definition of dct:relation

DCMI Metadata Terms defines both http://purl.org/dc/elements/1.1/relation and http://purl.org/dc/terms/relation with the following definition:

A related resource.

The current ISO draft proposes a different definition:

A reference to a related resource.

Note that if we were to define things as being "references to", we'd need to consider re-defining, say, dct:subject as "A reference to the topic of the resource" (instead of "The topic of the resource").

Do we agree with this change?

@kcoyle Apologies - I edited this before noticing your upvote, which I believe refers to the change proposed in the comment below.

@tombaker
Copy link
Collaborator Author

tombaker commented Jul 20, 2018

28b. Comment for dct:relation

The comment for dct:relation in DCMIMT currently says:

Recommended best practice is to identify the related resource by means of a
string conforming to a formal identification system.

The current ISO draft proposes a different definition (lightly edited here):

Recommended practice is to identify the related resource by means of a URI or a
string conforming to a formal identification system.

@tombaker
Copy link
Collaborator Author

tombaker commented Aug 24, 2018

28c. Definition of dct:conformsTo

It has been pointed out to me that the ISO draft also defines conformsTo as:

reference to an established standard to which the described resource conforms

whereas in DCMI Metadata Terms, it is defined without "reference to".

An established standard to which the described resource conforms.

This is exactly analogous to the change proposed for dct:relation. I propose that we reject the change.

Here: thumbs-down means "do not change the definition - keep it as is".

@sarahartmann
Copy link
Collaborator

+1, but proposal to adapt the wording to note 2 of #30

@kaiec kaiec changed the title Definition of dct:related Definition of dct:relation Aug 28, 2018
@tombaker
Copy link
Collaborator Author

APPROVED for 28b

Recommended practice is to identify the related resource by means of a URI. 
If this is not possible or feasible, a string conforming to a formal identification 
system may be provided.

@tombaker
Copy link
Collaborator Author

tombaker commented Sep 7, 2018

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

2 participants