Identify start page for a component version explicitly in site manifest

During import, the start page for a component version is implied when the url property of a non-alias entry matches the url property of the parent version entry. While this works (at least for all the use cases we've considered thus far), it's obtuse. It would be far better for the start page to be marked explicitly in the site manifest. That way, it's clear to both the person browsing the manifest and for tools to determine which page is acting as the start page.

There are two possible ways to mark the start page:

• Set the start boolean property on the page entry for the start page to true

  "1.0": {
    "url": "/acme/1.0/start.html",
    "pages": [
      {
        "path": "start.adoc",
        "url": "/acme/1.0/start.html",
        "title": "Start Page",
        "start": true
      }
    ]
  }
  

• Set the start (or startPage) string property on the parent version to the resource ref of the start page (e.g., start.adoc)

  "1.0": {
    "url": "/acme/1.0/start.html",
    "start": "start.adoc",
    "pages": [
      {
         "path": "start.adoc",
         "url": "/acme/1.0/start.html",
         "title": "Start Page"
      }
    ]
  }

If we decide on the boolean property (start), I think we need to then ask why we don't use the same strategy for the latest version (latest property on the version instead of the latest property on the component entry). Whatever we decide, we should be consistent.