Section structure and link pass #673
Conversation
|
Until now, I noticed some broken links in the main README, related to "contents", "multiple contents", "content groups" and "group metadata", and I tried to reorganize that by introducing a dedicated "Tile Contents" section that explains contents, multiple contents, and groups, so that it is possible to refer to this section where appropriate. The current state is a DRAFT, for early feedback whether the new structure makes sense. |
specification/README.md
Outdated
|
|
||
|  | ||
|
|
||
| The `content.uri` of each content object refers to the tile's binary content in one of the tile formats that are defined in the [Tile format specifications](#tile-format-specifications)), or another tileset JSON to create a tileset of tilesets (see [External tilesets](#external-tilesets)). |
There was a problem hiding this comment.
binary content
Not all tile formats are binary any more, notably .gltf
(I see this was copied from some outdated text below)
The structure looks good to me. |
|
I did a pass for checking the links. In addition to the where the (An aside: I didn't try out what happens when there is a (markdown) file (!) called Links of this form are probably not "valid" in the strictest sense. At least, they do not allow browsing to them with a CTRL+Click in VSCode, for example. So I changed them to where appropriate. |
|
We still have to sort out whether the |
| ### Upcoming | ||
|
|
||
| [3D Tiles Next](./next) is a set of new capabilities for the future of 3D Tiles. Provided as draft extensions to the [3D Tiles 1.0](../specification) specification, these features may be incorporated into 3D Tiles 2.0 in the future. | ||
|
|
||
| - [Tile Content](./next#tile-content): glTF 2.0 assets may be used directly as tile content, without intermediate formats, improving interoperability with 3D content and tooling ecosystems. Tiles may reference multiple contents — for organization, styling, and filtering — and contents may be collected into groups similar to map layers in mapping applications. | ||
| - [Implicit Tiling](./next#implicit-tiling): Common subdivision schemes and spatial index patterns may be declared without listing bounding volumes exhaustively. Reduces tileset size, and enables new optimizations including faster traversal, raycasting, random access, and spatial queries. | ||
| - [Metadata](./next#metadata): Metadata in 3D Tiles gains more expressiveness and flexibility, with a well-defined type system, new encoding options (e.g. JSON or binary), and a range of granularity options. Metadata may be associated with high-level objects like tilesets, tiles, or tile content groups, or with individual vertices and texels on glTF 2.0 geometry. | ||
|
|
||
| A curated list of resources for developers can be found on the [3D Tiles Next Resources](./next/RESOURCES.md) page. | ||
|
|
There was a problem hiding this comment.
This could be replaced by a more formal version history. That's what this checkbox in #651 was about:
- Add version history (include deprecations)
Doesn't have to hold up this PR though.
Some points from the checklist at #651 include
This PR will collect some of the related fixes.