OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [regrep-comment] Public Comment: Use of the term "Provenance"


Hi Richard,

Thank you for your comment. Please see our response inline below....

comment-form@oasis-open.org wrote:
Comment from: rmartell@galdosinc.com

[ADVISORY] Use of the term "Provenance"

---------------------------------------

The term "provenance" does not seem apt in Section 5.



In the Dublin Core element set, provenance is defined as "A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity and interpretation."
  
The term "provenance" is described in Webster Online Dictionary as:

1 : ORIGIN, SOURCE
2 : the history of ownership of a valued object or work of art or literature

http://webster.com/cgi-bin/dictionary?book=Dictionary&va=provenance&x=0&y=0

<http://dublincore.org/documents/dcmi-terms/#provenance>



So while these classes can be used to infer lineage through an audit trail, by themselves they are insufficient.
  
The Provenance Information Model classes allow associating a Person or an Organization with a RegistryObject to enable describing the original source or the current responsible party. The ebRIM spec says:

"
5 Provenance Information Model
This chapter describes the classes that enable the description of
the parties responsible for creating, publishing, or maintaining a RegistryObject or RepositoryItem. This
includes information about:
• The registered user that is the submitter of a RegistryObject or RepositoryItem.
• The organization that is the submitter submitted the object on behalf of (Submitting Organization)
• The organization that is responsible for the maintainence of the submitted object (Responsible
Organization)
• Any other persons that have some relationship with the submitted object
"


We suggest just replacing every occurrence of "Provenance" with "Responsible Party".
  
The Provenance Information Model classes classes play a broader role than simply defining the "Responsible Party".
As shown in quoted text above, they can represent the submitting party as well any other user-defined provenance relationship
(e.g. ReviewerOf, ApproverOf etc.)

Also, substitute this text on p.15:



"Responsible Parties Information Model: Defines classes that provide information about the users and organizations that are in some manner responsible for a RegistryObject (creation, submission, maintenance, etc.)."
  
After careful consideration of your comment, we feel that the role played by the Provenance Information Model classes fits the dictionary definition in the English language for the term Provenance. In light of your comment we will describe the term "provenance" in the begining of the "Provenance Information Model" chapter to avoid any confusion.
Thank you for your valuable suggestion.

-- 
Regards,
Farrukh


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
https://lists.oasis-open.org/archives/regrep-comment/200503/msg00008.html
lists.oasis-open.org
crawl=CC-MAIN-2022-21
9548
application/http; msgtype=response
sha1:KL5U5SV4VQY7DAGKQOXL547HXALWMWBG
<urn:uuid:b2c15da9-02c7-49b9-97d4-2c820bcbc68a>
2022-05-19T06:44:48Z
34.233.166.49
text/html
sha1:5BECUCE5QRUTAF3ZCKR7HDCIIWYIP523
<urn:uuid:e827a521-ba6e-419f-998a-25d1436988ee>
https://lists.oasis-open.org/archives/regrep-comment/200503/msg00008.html
response
<urn:uuid:afe271dc-fa1e-41fb-91ef-f8b6601c6517>
isPartOf: CC-MAIN-2022-21
publisher: Common Crawl
description: Wide crawl of the web for May 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-243
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.3-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/