BAI caf51083a8 长三角共享系统国产化改造项目初始 1 săptămână în urmă
..
markdowns caf51083a8 长三角共享系统国产化改造项目初始 1 săptămână în urmă
samples caf51083a8 长三角共享系统国产化改造项目初始 1 săptămână în urmă
src caf51083a8 长三角共享系统国产化改造项目初始 1 săptămână în urmă
README.md caf51083a8 长三角共享系统国产化改造项目初始 1 săptămână în urmă

README.md

ArcGIS web scene specification

Specification for the ArcGIS web scene document format.

Latest released version is available publicly at developers.arcgis.com/web-scene-specification/

Content

  • src/: the web scene json schema files
  • markdowns/: the documentation generated from the src schema files
  • samples/: sample web scenes for reference and testing

Contributing

  1. Create a new issue that explains the proposal, describes the requirements, and adds some initial mock of spec if possible.
  2. Create a schema PR with the proposed spec change
    • If you're not familiar with creating a schema PR, find a schema person to do these steps

Version / Releases

  • webscene-spec is versioned as major.minor, e.g. 1.5
  • major number denotes a breaking change: 2.x web scenes cannot be read by a 1.x client, and must be rejected
  • to indicate patch releases between versions, webscene-spec releases are numbered with an additional patch number z, (x.y.z)
  • latest release
  • all releases
  • versions < 1.5 are not schema-based

Branching

  • Milestones for past and upcoming Web Scene spec releases include information about release date and target products/versions
  • Release branch for each "shipped" Web Scene spec version, e.g. v1.5
    • The spec release typically happens around the time that the involved products freeze for release
    • Release branches branch off master
    • Release branch gets a release tag when the doc is deployed to developers.arcgis.com
  • master branch contains the latest developments, which are typically released with upcoming version
    • Proposals are thus typically created by branching from (and merging into) master

Tooling

Schema-tooling repo contains various tools for schema and document validation, and markdown generation, and infos on deploying doc