dcmi / usage

DCMI Usage Board - meeting record and decisions
8 stars 5 forks source link

dc/dcterms: date #86

Open tombaker opened 4 years ago

tombaker commented 4 years ago

CHANGING NOW (unless I hear objections!)

PROPOSING FOR FUTURE (to be voted)

kcoyle commented 4 years ago

In those cases where the definitions and comments will be identical between the two namespaces, would it be better to make a kind of "see reference" to the dcterms property? The advantage with that it is that makes it absolutely clear that the two are defined identically. With text you don't know if there are any differences. Somehow I want an indication that the properties have the exact same definition. This will indicate to people that they can treat them as "same as" in any work they are doing.

tombaker commented 4 years ago

would it be better to make a kind of "see reference" to the dcterms property

Thanks - this is indeed the way I am currently handling it! Each "elements/1.1" property has a note saying that "A second property http://localhost:1313/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/date with the same name as this property has been declared in the dcterms: namespace http://purl.org/dc/terms/. See the Introduction to the document DCMI Metadata Terms http://localhost:1313/specifications/dublin-core/dcmi-terms/ for an explanation." The current DCMIMT document has notes like this, but these notes actually link to a specific property.

On Wed, Jan 15, 2020 at 8:32 PM Karen Coyle notifications@github.com wrote:

In those cases where the definitions and comments will be identical between the two namespaces, would it be better to make a kind of "see reference" to the dcterms property? The advantage with that it is that makes it absolutely clear that the two are defined identically. With text you don't know if there are any differences. Somehow I want an indication that the properties have the exact same definition. This will indicate to people that they can treat them as "same as" in any work they are doing.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dcmi/usage/issues/86?email_source=notifications&email_token=AAIOBJUQINZUH7BUZJXL37LQ55QEBA5CNFSM4KHBQDPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJBQXRI#issuecomment-574819269, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIOBJXBLAUQMVZ6WRTRPLTQ55QEBANCNFSM4KHBQDPA .