openitinerary 0.1.1__tar.gz

openitinerary-0.1.1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

openitinerary-0.1.1/PKG-INFO

@@ -0,0 +1,175 @@
+Metadata-Version: 2.4
+Name: openitinerary
+Version: 0.1.1
+Summary: OpenItinerary is an open, vendor-neutral standard for representing travel itineraries as structured data.
+Keywords: itinerary,open,standard,travel,flight,mcp
+Author: kiran94
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Topic :: Utilities
+Classifier: Topic :: Software Development
+Classifier: Topic :: Software Development :: Version Control :: Git
+Requires-Dist: pycountry>=26.2.16
+Requires-Dist: pydantic[email]>=2.13.4
+Requires-Dist: pydantic-extra-types>=2.11.1
+Requires-Dist: tzdata>=2026.3
+Requires-Dist: beautifulsoup4>=4.15.0 ; extra == 'adapters'
+Requires-Dist: fastapi[standard]>=0.141.1 ; extra == 'adapters'
+Requires-Dist: pydantic-ai>=2.22.0 ; extra == 'adapters'
+Requires-Dist: pydantic-ai-slim[duckduckgo]>=2.22.0 ; extra == 'adapters'
+Requires-Dist: pypdf>=6.14.2 ; extra == 'adapters'
+Requires-Python: >=3.11
+Project-URL: Homepage, https://pypi.org/project/openitinerary/
+Project-URL: Repository, https://github.com/kiran94/openitinerary
+Project-URL: Documentation, https://github.com/kiran94/openitinerary/blob/main/README.md
+Provides-Extra: adapters
+Description-Content-Type: text/markdown
+
+# OpenItinerary
+
+[![build](https://github.com/kiran94/openitinerary/actions/workflows/build.yml/badge.svg)](https://github.com/kiran94/openitinerary/actions/workflows/build.yml) ![PyPI Version](https://img.shields.io/pypi/v/openitinerary)
+
+
+OpenItinerary is an open, vendor-neutral standard for representing travel itineraries as structured data.
+
+Inspired by JSON in the data exchange space, OpenItinerary facilitates a common specification that any travel company can produce or consume without relying on proprietary formats. A single itinerary can contain flights, trains, accommodation and other travel related activities from various vendors within a single unified model.
+
+Principles:
+* Vendor Neutral: No dependency on any particular vendor proprietary format. Instead model the underlying travel concepts.
+* Open & Interoperable: Designed to move cleanly between systems and programming languages.
+* Strongly Typed: Fields have clear semantics and avoid ambiguity. Missing concept and fields should be proposed to be added to the standard and there should be no custom metadata "escape hatches".
+* Minimal: Universal Concepts are defined at the base models and domain specifics belong in specialized types.
+* Serialization Friendly: Data model will at *minimum* map cleanly to JSON.
+* Versioning: Schema is versioned and follows standard semantic versioning rules.
+* Single Canonical Time: Date/Times are *always* stored in UTC format. Geographic Places will always store the Time zone in which they take place. Downstream applications are responsible for ensuring that time presented correctly.
+* Internationalization: International differences are handled explicitly. Textual fields will store the language they are stored in so that downstream applications can present/provide translation when needed.
+
+## Implementation
+
+The schema is defined and maintained using *Pydantic Models* however this does not mean that OpenItinerary is a python project. These models are used to generate a **JSON Schema** which serves as the canonical schema of the project.
+
+JSON is the default interchange format because it is universal, readable, and easy to integrate. From this format, other formats can be derived:
+
+```mermaid
+graph LR
+
+Pydantic(Pydantic Models)
+JSONSchema(JSON Schema)
+
+Pydantic --> JSONSchema
+
+JSONSchema --> Typescript
+JSONSchema --> Protobuf
+JSONSchema --> Flatbuffer
+JSONSchema --> ...
+```
+
+*Performance sensitive consumers may want to use binary formats such as Protobuf so the standard only states that JSON is a minimum supported format. Binary formats must represent the same model.*
+
+### Python Package
+
+Install the Python package from PyPI:
+
+```bash
+python -m pip install openitinerary
+```
+
+Import models from the `openitinerary` package:
+
+```python
+from openitinerary.models.itinerary import Itinerary
+```
+
+Generate the current JSON Schema with the installed command:
+
+```bash
+openitinerary --output stdout
+```
+
+### Adapter API configuration
+
+The Adapter API limits each uploaded document to 10 MiB by default. Set
+to a positive integer to configure the
+limit in bytes. The value is loaded when the API process starts, so restart the
+process after changing it.
+
+#### Environment Variables
+
+| Name                                   | Description                                              | Default                 |
+| -------------------------------------- | -------------------------------------------------------- | ----------------------- |
+| `OPEN_ITINERARY_MAX_UPLOAD_SIZE_BYTES` | Maximum size of an uploaded document to the `/adapt` API | `10485760` bytes (10MB) |
+
+## Concepts
+
+* `Itinerary`: An itinerary is an ordered collection of typed segments.
+* `Segment`: A travel activity that happens at a specified time at a specific place.
+* `Place`: A geographical location on the earth.
+
+The `BaseSegment` defined common concepts for all travel related activities and domain specific models such as `FlightSegment` add stronger fields and validation.
+
+## Roadmap
+
+**Schema**
+  - [x] Base Segment Types
+  - [x] Flights and Airports
+  - [x] Train and Train Stations
+  - [x] Accommodation
+  - [x] Transfers
+  - [x] Activities and Tours
+  - [ ] Car Rentals
+  - [ ] Ferries
+  - [ ] Cruises
+
+**Implementations**
+ - [x] PDF Adapter
+ - [x] HTML Adapter
+ - [x] Email Adapter
+ - [ ] Calender Adapter
+ - [ ] ZIP Adapter
+ - [ ] Model Validation API
+ - [x] Adapter API
+ - [x] Python Package
+ - [ ] JSON Schema Package
+ - [ ] Batch Ingestion & Job Processing Service
+
+### Versioning and releases
+
+This repository has two independent versions:
+
+* The **schema version** is defined by `OPEN_ITINERARY_VERSION` in
+  `src/openitinerary/version.py`. Changes to the standard must update this
+  version in the same pull request and regenerate the committed schemas with
+  `make generate_out`.
+* The **Python package version** is defined in `pyproject.toml`. It changes when
+  a new Python distribution is published, including releases containing only
+  Python tooling or adapter changes. Such changes do not require a schema
+  version bump.
+
+Schema versions follow semantic versioning. Breaking changes increment the
+major version, backwards-compatible additions increment the minor version, and
+small corrections to schema documentation or metadata increment the patch
+version. Generated schema directories intentionally use only the major and
+minor components, for example `schemas/0.1/itinerary.schema.json`. A patch
+release updates the schema for that minor line rather than creating a new
+directory.
+
+Package version changes are made by a developer in a pull request intended to
+create a release. Use `uv version` so `pyproject.toml` and `uv.lock` remain in
+sync, then commit both files:
+
+```bash
+uv version --bump patch --no-sync
+```
+
+Use `minor` or `major` instead of `patch` when appropriate. Pull requests are
+published as beta versions for testing. After a package-version change is
+merged to `main`, the committed version is built and published to PyPI. A merge
+that does not change the package version does not publish a stable release.
+
+## License
+
+Copyright 2026 Kiran Patel.
+
+Licensed under the [Apache License, Version 2.0](LICENSE).

openitinerary-0.1.1/README.md

@@ -0,0 +1,146 @@
+# OpenItinerary
+
+[![build](https://github.com/kiran94/openitinerary/actions/workflows/build.yml/badge.svg)](https://github.com/kiran94/openitinerary/actions/workflows/build.yml) ![PyPI Version](https://img.shields.io/pypi/v/openitinerary)
+
+
+OpenItinerary is an open, vendor-neutral standard for representing travel itineraries as structured data.
+
+Inspired by JSON in the data exchange space, OpenItinerary facilitates a common specification that any travel company can produce or consume without relying on proprietary formats. A single itinerary can contain flights, trains, accommodation and other travel related activities from various vendors within a single unified model.
+
+Principles:
+* Vendor Neutral: No dependency on any particular vendor proprietary format. Instead model the underlying travel concepts.
+* Open & Interoperable: Designed to move cleanly between systems and programming languages.
+* Strongly Typed: Fields have clear semantics and avoid ambiguity. Missing concept and fields should be proposed to be added to the standard and there should be no custom metadata "escape hatches".
+* Minimal: Universal Concepts are defined at the base models and domain specifics belong in specialized types.
+* Serialization Friendly: Data model will at *minimum* map cleanly to JSON.
+* Versioning: Schema is versioned and follows standard semantic versioning rules.
+* Single Canonical Time: Date/Times are *always* stored in UTC format. Geographic Places will always store the Time zone in which they take place. Downstream applications are responsible for ensuring that time presented correctly.
+* Internationalization: International differences are handled explicitly. Textual fields will store the language they are stored in so that downstream applications can present/provide translation when needed.
+
+## Implementation
+
+The schema is defined and maintained using *Pydantic Models* however this does not mean that OpenItinerary is a python project. These models are used to generate a **JSON Schema** which serves as the canonical schema of the project.
+
+JSON is the default interchange format because it is universal, readable, and easy to integrate. From this format, other formats can be derived:
+
+```mermaid
+graph LR
+
+Pydantic(Pydantic Models)
+JSONSchema(JSON Schema)
+
+Pydantic --> JSONSchema
+
+JSONSchema --> Typescript
+JSONSchema --> Protobuf
+JSONSchema --> Flatbuffer
+JSONSchema --> ...
+```
+
+*Performance sensitive consumers may want to use binary formats such as Protobuf so the standard only states that JSON is a minimum supported format. Binary formats must represent the same model.*
+
+### Python Package
+
+Install the Python package from PyPI:
+
+```bash
+python -m pip install openitinerary
+```
+
+Import models from the `openitinerary` package:
+
+```python
+from openitinerary.models.itinerary import Itinerary
+```
+
+Generate the current JSON Schema with the installed command:
+
+```bash
+openitinerary --output stdout
+```
+
+### Adapter API configuration
+
+The Adapter API limits each uploaded document to 10 MiB by default. Set
+to a positive integer to configure the
+limit in bytes. The value is loaded when the API process starts, so restart the
+process after changing it.
+
+#### Environment Variables
+
+| Name                                   | Description                                              | Default                 |
+| -------------------------------------- | -------------------------------------------------------- | ----------------------- |
+| `OPEN_ITINERARY_MAX_UPLOAD_SIZE_BYTES` | Maximum size of an uploaded document to the `/adapt` API | `10485760` bytes (10MB) |
+
+## Concepts
+
+* `Itinerary`: An itinerary is an ordered collection of typed segments.
+* `Segment`: A travel activity that happens at a specified time at a specific place.
+* `Place`: A geographical location on the earth.
+
+The `BaseSegment` defined common concepts for all travel related activities and domain specific models such as `FlightSegment` add stronger fields and validation.
+
+## Roadmap
+
+**Schema**
+  - [x] Base Segment Types
+  - [x] Flights and Airports
+  - [x] Train and Train Stations
+  - [x] Accommodation
+  - [x] Transfers
+  - [x] Activities and Tours
+  - [ ] Car Rentals
+  - [ ] Ferries
+  - [ ] Cruises
+
+**Implementations**
+ - [x] PDF Adapter
+ - [x] HTML Adapter
+ - [x] Email Adapter
+ - [ ] Calender Adapter
+ - [ ] ZIP Adapter
+ - [ ] Model Validation API
+ - [x] Adapter API
+ - [x] Python Package
+ - [ ] JSON Schema Package
+ - [ ] Batch Ingestion & Job Processing Service
+
+### Versioning and releases
+
+This repository has two independent versions:
+
+* The **schema version** is defined by `OPEN_ITINERARY_VERSION` in
+  `src/openitinerary/version.py`. Changes to the standard must update this
+  version in the same pull request and regenerate the committed schemas with
+  `make generate_out`.
+* The **Python package version** is defined in `pyproject.toml`. It changes when
+  a new Python distribution is published, including releases containing only
+  Python tooling or adapter changes. Such changes do not require a schema
+  version bump.
+
+Schema versions follow semantic versioning. Breaking changes increment the
+major version, backwards-compatible additions increment the minor version, and
+small corrections to schema documentation or metadata increment the patch
+version. Generated schema directories intentionally use only the major and
+minor components, for example `schemas/0.1/itinerary.schema.json`. A patch
+release updates the schema for that minor line rather than creating a new
+directory.
+
+Package version changes are made by a developer in a pull request intended to
+create a release. Use `uv version` so `pyproject.toml` and `uv.lock` remain in
+sync, then commit both files:
+
+```bash
+uv version --bump patch --no-sync
+```
+
+Use `minor` or `major` instead of `patch` when appropriate. Pull requests are
+published as beta versions for testing. After a package-version change is
+merged to `main`, the committed version is built and published to PyPI. A merge
+that does not change the package version does not publish a stable release.
+
+## License
+
+Copyright 2026 Kiran Patel.
+
+Licensed under the [Apache License, Version 2.0](LICENSE).

openitinerary-0.1.1/pyproject.toml

@@ -0,0 +1,62 @@
+[project]
+name = "openitinerary"
+version = "0.1.1"
+description = "OpenItinerary is an open, vendor-neutral standard for representing travel itineraries as structured data."
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+requires-python = ">=3.11"
+keywords = [
+    "itinerary",
+    "open",
+    "standard",
+    "travel",
+    "flight",
+    "mcp",
+]
+classifiers = [
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Topic :: Utilities",
+    "Topic :: Software Development",
+    "Topic :: Software Development :: Version Control :: Git",
+]
+dependencies = [
+    "pycountry>=26.2.16",
+    "pydantic[email]>=2.13.4",
+    "pydantic-extra-types>=2.11.1",
+    "tzdata>=2026.3",
+]
+
+[[project.authors]]
+name = "kiran94"
+
+[project.optional-dependencies]
+adapters = [
+    "beautifulsoup4>=4.15.0",
+    "fastapi[standard]>=0.141.1",
+    "pydantic-ai>=2.22.0",
+    "pydantic-ai-slim[duckduckgo]>=2.22.0",
+    "pypdf>=6.14.2",
+]
+
+[project.scripts]
+openitinerary = "openitinerary:main"
+
+[project.urls]
+Homepage = "https://pypi.org/project/openitinerary/"
+Repository = "https://github.com/kiran94/openitinerary"
+Documentation = "https://github.com/kiran94/openitinerary/blob/main/README.md"
+
+[build-system]
+requires = ["uv_build>=0.11.8,<0.12.0"]
+build-backend = "uv_build"
+
+[dependency-groups]
+dev = [
+    "pytest>=9.0.3",
+    "ruff>=0.15.20",
+]
+
+[tool.ruff]
+line-length = 120

openitinerary-0.1.1/pyproject.toml.orig

@@ -0,0 +1,56 @@
+[project]
+name = "openitinerary"
+version = "0.1.1"
+description = "OpenItinerary is an open, vendor-neutral standard for representing travel itineraries as structured data."
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [
+    { name = "kiran94" }
+]
+requires-python = ">=3.11"
+keywords = [ "itinerary", "open", "standard", "travel", "flight", "mcp" ]
+classifiers = [
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Topic :: Utilities",
+    "Topic :: Software Development",
+    "Topic :: Software Development :: Version Control :: Git"
+]
+dependencies = [
+    "pycountry>=26.2.16",
+    "pydantic[email]>=2.13.4",
+    "pydantic-extra-types>=2.11.1",
+    "tzdata>=2026.3",
+]
+
+
+[project.optional-dependencies]
+adapters = [
+    "beautifulsoup4>=4.15.0",
+    "fastapi[standard]>=0.141.1",
+    "pydantic-ai>=2.22.0",
+    "pydantic-ai-slim[duckduckgo]>=2.22.0",
+    "pypdf>=6.14.2",
+]
+
+[project.scripts]
+openitinerary = "openitinerary:main"
+
+[project.urls]
+Homepage = "https://pypi.org/project/openitinerary/"
+Repository = "https://github.com/kiran94/openitinerary"
+Documentation = "https://github.com/kiran94/openitinerary/blob/main/README.md"
+
+[build-system]
+requires = ["uv_build>=0.11.8,<0.12.0"]
+build-backend = "uv_build"
+
+[dependency-groups]
+dev = [
+    "pytest>=9.0.3",
+    "ruff>=0.15.20",
+]
+
+[tool.ruff]
+line-length = 120

openitinerary-0.1.1/src/openitinerary/__init__.py

@@ -0,0 +1,43 @@
+import argparse
+import json
+import logging
+import os
+from pathlib import Path
+
+from openitinerary.models.itinerary import Itinerary
+from openitinerary.version import OPEN_ITINERARY_VERSION, derive_major_minor
+
+logging.basicConfig(format=logging.BASIC_FORMAT, level=logging.INFO)
+logger = logging.getLogger(__name__)
+
+SCHEMAS_FOLDER = "schemas"
+SCHEMAS_FILE = "itinerary.schema.json"
+
+
+def main() -> None:
+    parser = argparse.ArgumentParser()
+    parser.add_argument("-o", "--output", choices=["stdout", "versioned"], default="stdout")
+    parser.add_argument("-i", "--indent", action="store_true")
+
+    args = parser.parse_args()
+
+    logger.debug("generating schema from Itinerary")
+    schema = Itinerary.model_json_schema()
+
+    indent = 4 if args.indent else None
+
+    if args.output == "stdout":
+        print(json.dumps(schema, indent=indent))
+    elif args.output == "versioned":
+        major_minor_folder = derive_major_minor(OPEN_ITINERARY_VERSION)
+        versioned_folder = Path(os.getcwd()) / SCHEMAS_FOLDER / major_minor_folder
+        versioned_file = versioned_folder / SCHEMAS_FILE
+
+        logger.info("output schema to %s", versioned_file)
+
+        os.makedirs(versioned_folder, exist_ok=True)
+
+        with open(versioned_file, "w") as f:
+            json.dump(schema, f, indent=indent)
+    else:
+        raise NotImplementedError({args.output})