Skip to content

Provide better guidance for using the standard. #494

@pvretano

Description

@pvretano

Part 1 is written in 2 big sections ... the "common components" section that describes build blocks for creating catalogs and the "deployments" section that describes 3 types of catalogs that can be deployed using these common components.

The way the standard is meant to be used is:

  1. The server implementer selects the type of deployment they want to implement (Crawlable, Searchable or Local Resources catalog)
  2. Then, they implement the building blocks that need to be implemented for the selected deployment type.

It would be very useful if this information was presented very early on in the standard. I'm thinking right before the Common Components section in clause 6.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

Status

To be drafted

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions