Are "flags" really a part of term metadata or are they just for website management?

[baskaufs]

The Normative Document contains a new column called flags. I guess that is to indicate whether a particular term is part of "Simple Darwin Core" or not. If it is really a useful part of the term metadata, then we should mint a utility property in the tdwgutily: namespace for it and actually add it to the term metadata. If it's not actually part of the term metadata, then we should remove it from the "Normative Document" and put it somewhere else. Is it the same information as found here ?

[tucotuco]

Interesting issue. I would not have considered the flags part of the term metadata, but rather another organizational aid, such as organizedInClass. Yet, there is great utility to being able to say that the entire document is normative, and there is great utility in having flags in the term_versions.csv document, as the site uild scripts rely on it (

dwc/build/build.py

Line 266 in 9ed16c0

term["flags"] == "simple"):

) and it just makes things easier. Thus, I would opt for the solution to add a tdwg utility term as @baskaufs proposes. The term organizedInClass uses the namespace dwcattributes. Can we use that here too?

[baskaufs]

We've been considering the dwcattributes namespace to be a general utility namespace and have used it in Audubon Core to indicate similar things, like whether a term is repeatable or required. So we could certainly do that here as an organization aid. I think that is the best solution and it would allow that information (whether a term is a part of Simple Darwin Core) to be obtainable in the machine-readable metadata as well.

[tucotuco]

Sounds good. Now I wish it had a more explicit name, such as usageScope or similar.

…

On Sun, Jul 19, 2020 at 10:41 PM Steve Baskauf ***@***.***> wrote: We've been considering the dwcattributes namespace to be a general utility namespace and have used it in Audubon Core to indicate similar things, like whether a term is repeatable or required. So we could certainly do that here as an organization aid. I think that is the best solution and it would allow that information (whether a term is a part of Simple Darwin Core) to be obtainable in the machine-readable metadata as well. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#255 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADQ726DVWERTRBKFSTJZITR4OOF5ANCNFSM4OVYOIIQ> .

[baskaufs]

The term tdwgutility:usageScope has been added in this commit and will become "live" when this pull request is merged.