Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

LocalDateTime

Open
#4 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java

Research direction

Start by reviewing the Java JAXB binding classes and the NeTEx XSD mappings for xs:time, xs:dateTime, and xs:date. Compare the current LocalDateTime choices with LocalDate, ZonedDateTime, and OffsetDateTime, then document the rationale or agree on revised mappings for the affected schema types.

Written by the indexing model from the issue text.

Description

At this moment the bindings specifies:

  • xs:time LocalTime
  • xs:dateTime LocalDateTime
  • xs:date LocalDateTime

The first question is, what is the rationale for LocalDateTime opposed to ZonedDateTime or OffsetDateTime? There are at this moment multiple cases where the ZonedDateTime makes more sense, especially in the European Profile.

What is the reason that xs:date is mapped to LocalDateTime opposed to LocalDate?

Dominant language
Java
Stars
21
Forks
15
Avg merge
34m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from entur/netex-java-model

All issues in entur/netex-java-model

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.