PLUS 2.0.1 Data Mining Field

[blue-j]

The spec lists the CV as:

http://ns.useplus.org/ldf/vocab/DMI-UNSPECIFIED (Unspecified - no prohibition defined)
http://ns.useplus.org/ldf/vocab/DMI-ALLOWED (Allowed)
http://ns.useplus.org/ldf/vocab/DMI-PROHIBITED-AIMLTRAINING (Prohibited for AI/ML training)
http://ns.useplus.org/ldf/vocab/DMI-PROHIBITED-GENAIMLTRAINING (Prohibited for Generative AI/ML training)
http://ns.useplus.org/ldf/vocab/DMI-PROHIBITED-EXCEPTSEARCHENGINEINDEXING (Prohibited except for search engine indexing)
http://ns.useplus.org/ldf/vocab/DMI-PROHIBITED (Prohibited)
http://ns.useplus.org/ldf/vocab/DMI-PROHIBITED-SEECONSTRAINT (Prohibited, see Other Constraints property)
http://ns.useplus.org/ldf/vocab/DMI-PROHIBITED-SEEEMBEDDEDRIGHTSEXPR (Prohibited, see Embedded Encoded Rights Expression property)
http://ns.useplus.org/ldf/vocab/DMI-PROHIBITED-SEELINKEDRIGHTSEXPR (Prohibited, see Linked Encoded Rights Expression property)

while the ExifTool documentation uses:

'DMI-ALLOWED' = Allowed
'DMI-PROHIBITED' = Prohibited
'DMI-PROHIBITED-AIMLTRAINING' = Prohibited for AI/ML training
'DMI-PROHIBITED-EXCEPTSEARCHENGINEINDEXING' = Prohibited except for search engine indexing
'DMI-PROHIBITED-GENAIMLTRAINING' = Prohibited for Generative AI/ML training
'DMI-PROHIBITED-SEECONSTRAINT' = Prohibited, see plus:OtherConstraints
'DMI-PROHIBITED-SEEEMBEDDEDRIGHTSEXPR' = Prohibited, see iptcExt:EmbdEncRightsExpr
'DMI-PROHIBITED-SEELINKEDRIGHTSEXPR' = Prohibited, see iptcExt:LinkedEncRightsExpr
'DMI-UNSPECIFIED' = Unspecified - no prohibition defined

I was wondering if the outward facing values might be more like the spec, so field designations aren't technical.  These values normally face users who are working with media, not developers, so things like

"...see plus:OtherConstraints"
"...see iptcExt:EmbdEncRightsExpr"
"...see iptcExt:LinkedEncRightsExpr"

I suspect are off-putting?  I reserve the right to be wrong, but those are my .02.  We can modify presentation over here easily, so there is no practical pressure, but I thought it worth asking about.

- J

[Phil Harvey]

I changed this in an attempt to be more concise and precise, and more inline with the ExifTool tag names.  But if anyone else thinks this is off-putting, let me know and maybe it is worth changing.

- Phil