Adding attribute on Entity for publication meta-information (e.g. for public, or restricted dataset-filtering purposes)

[JohanEntur]

Once more I am clicking buttons on behalf of Entur.
This was created ages ago by people in Entur but it was never merged up to CEN.

[skinkie]

Is "future use" something that is in scope or out scope, because for example a ValidityBetween should have been provided.

[JohanEntur]

where are you quoting from?

[skinkie]

where are you quoting from?

The ideas in my mind after reviewing this addition.

[JohanEntur]

aha well. yes and no. our customers keep requesting "send file import later"-features so that they are able to sync their real-time systems (which have a much slower turnover than our import), but.... I dont know. As you say, it could be a validty date too but it requires so much from the various system to a) know about the value b) know what it means c) implement logic for it. I dont think the world is ready for such advanced syncronized data activation.

But, maybe this is not the usecase you were thinking of.

[skinkie]

My use case is basically, there will be renovated station in the future. But obviously the planned state is available. I think people are interested in knowing what the station looks like in the future.

[JohanEntur]

so its a stopplace with versions

[trurlurl]

Suggestions for a more precise name: publicationSharingPolicy, publicationVisibility

[vpaturet]

We would prefer to stick to "publication" for concision. This does not seem to collide or cause ambiguity with other existing attributes.

[vpaturet]

@skinkie We are refreshing this PR, could you change the target branch from v2.0 to v2.1-wip?
(This requires write access, I cannot do it)

[vpaturet]

My use case is basically, there will be renovated station in the future. But obviously the planned state is available. I think people are interested in knowing what the station looks like in the future.

As Johan said, this feature is orthogonal to validity period or future state. It is about the audience (is this entity intended to be communicated to the public or is it internal?)

[skinkie]

@vpaturet@JohanEntur I don't have the permissions to change your target branch.

[TuThoThai]

@vpaturet@JohanEntur I don't have the permissions to change your target branch.

@skinkie, @vpaturet, @JohanEntur, since the PR is based on a fork of the repo in another organisation (Entur), I cannot change the target either.
Only solution is to redo the PR using a feature branch in this repo, based on branch v2.1-wip

I will look at it later for the redo.

[skinkie]

@vpaturet@JohanEntur I don't have the permissions to change your target branch.

@skinkie, @vpaturet, @JohanEntur, since the PR is based on a fork of the repo in another organisation (Entur), I cannot change the target either. Only solution is to redo the PR using a feature branch in this repo, based on branch v2.1-wip

I will look at it later for the redo.

Just let Johan do the work, single click.

[vpaturet]

@skinkie@TuThoThai Thanks, we managed to change the target branch and update the PR.