Update datetime titles

[zakjan]

The spec for datetime field mentions that it can be a representative datetime instead of an acquisition datetime.

I suggest to update datetime field titles from "Acquired" to a simple neutral "Datetime", because it can contain any representative datetime depending on the data.

For example, there is a new forecast extension being drafted which is going to use a forecast datetime in datetime field. See stac-extensions/forecast#1 and stac-extensions/forecast#7 for the related discussion.

[m-mohr]

Yeah, this is true and should be changed.

I may even go one step further and give different titles depending on the implemented extensions.

[zakjan]

different titles depending on the implemented extensions

Yes, makes perfect sense. It might require changes in the API, I haven't explored it further yet. For now I just corrected the default title.

[m-mohr]

Ah, haha, I didn't realize this is a PR, thought it's only an issue.

I don't like "Datetime" a lot because it's a bit "technical", basically just the property name with an uppercase D ;-) I'm looking for something that a "non-technical" person would write. Maybe just "Date" or "Date and time" or so... Thoughts?

[zakjan]

It's true, but other field titles are created similarly... created -> Created etc.

[m-mohr]

Yeah, although Created can be found in a dictionary, Datetime can't (I think). But yeah, "Creation Time" could be a longer version of it if we want. But then "Modified" would be "Modification time" (?) which feels a bit long.

[m-mohr]

Fixed in the meanwhile, I think.

[zakjan]

Thanks! I was only concerned about the specific Acquired, I don't mind any other wording if it's generic enough.