Skip to content

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

Open
JohanEntur wants to merge 2 commits intoTransmodelEcosystem:v2.0from
entur:publication_enum_for_entity
Open

Adding attribute on Entity for publication meta-information (e.g. for public, or restricted dataset-filtering purposes)#899
JohanEntur wants to merge 2 commits intoTransmodelEcosystem:v2.0from
entur:publication_enum_for_entity

Conversation

@JohanEntur
Copy link
Copy Markdown
Collaborator

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.

Comment thread xsd/netex_framework/netex_responsibility/netex_version_support.xsd Outdated
@skinkie
Copy link
Copy Markdown
Contributor

skinkie commented May 19, 2025

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

@JohanEntur
Copy link
Copy Markdown
Collaborator Author

where are you quoting from?

@skinkie
Copy link
Copy Markdown
Contributor

skinkie commented May 19, 2025

where are you quoting from?

The ideas in my mind after reviewing this addition.

@JohanEntur
Copy link
Copy Markdown
Collaborator Author

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
Copy link
Copy Markdown
Contributor

skinkie commented May 19, 2025

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
Copy link
Copy Markdown
Collaborator Author

so its a stopplace with versions

@ue71603 ue71603 added enhancement non semantic enhacement: technical enhancement, etc. group_decision_needed Must be discussed during a CEN TC278 WG3 SG9 plenary labels May 21, 2025
<xsd:documentation>Whether ENTITY is currently in use. Default is "active".</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="publication" type="PublicationEnumeration" use="optional" default="public">
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestions for a more precise name: publicationSharingPolicy, publicationVisibility

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@Aurige Aurige added the needs documentation update The NeTEx document needs to be updated label May 21, 2025
@Aurige Aurige modified the milestones: netex_2.0, netex_2.1 May 21, 2025
@vpaturet vpaturet force-pushed the publication_enum_for_entity branch from d0abfc4 to b237693 Compare April 14, 2026 09:37
@vpaturet
Copy link
Copy Markdown

@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
Copy link
Copy Markdown

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?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement non semantic enhacement: technical enhancement, etc. group_decision_needed Must be discussed during a CEN TC278 WG3 SG9 plenary needs documentation update The NeTEx document needs to be updated

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants