FTC ideas

_data/navigation.yml

@@ -17,6 +17,8 @@ docs:
       - title: Finding Building Blocks
         url: /use/finding
       - title: Reusing schemas
+      - title: Reusing schemas
+        url: /use/ftc
       - title: Linked Data / JSON-LD Context
   - title: Creating Building Blocks
     children:

_pages/index.markdown

@@ -4,11 +4,11 @@ permalink: /
 ---
 This is the documentation for OGC Building Blocks, a specification component packaging approach that can be used to **add documentation** to existing specification components, or to assemble specifications cost-effectively using a test-driven approach.
 
-Building Blocks may be various [types](/overview/types) - however the emphasis is semantically annotated schemas for use in OGC API definitions. 
+This packaging supports testing of examples, and validation using rules inherited from other Building Blocks that are re-used (by aggregation or profiling) to create compatible specifications for specific applications.
 
-A key application is the [register of OGC Specification Building blocks](https://opengeospatial.github.io/bblocks/register/)
+Building Blocks make various different [types](/overview/types) of specification component accessible in a common, convenient form and registers.  A key innovation is support for **semantically annotated schemas**, suitable for use in OpenAPI definitions. 
 
-This packaging supports testing of examples, and validation using rules inherited from other Building Blocks that are re-used (by aggregation or profiling) to create compatible specifications for specific applications.
+The Building Block documentation framework is the basis of the [register of OGC Specification Building blocks](https://opengeospatial.github.io/bblocks/register/). 
 
 OGC BuildingBlocks can be organised into [registers](/overview/registers) for convenience, each repository creating a local register that can be aggregated into another application domain register.
 

_pages/use/finding.md

@@ -3,12 +3,15 @@ title: Finding Building Blocks
 permalink: /use/finding
 ---
 
-Whilst components described as Building Blocks may be referenced by individual specifications, due to evolution and legacy issues this is not consistent and is a challenge for discovery.  General text search options may assist.
 
-The OGC Building Block Framework provides two improved approaches:
+Whilst components described as Building Blocks may be referenced by individual specifications, due to evolution of the specification publication process over time this is not consistent in terms of identification or disposition of published artefacts. Such components may be published as discrete resources, or bundled in larger packages. They may or may not be in consistent machine-readable forms. This leads to many challenges for discovery of such components.  General text search options may assist, but will be subject to limited ability to precisely recall only relevant components.
+
+The OGC Building Block Framework provides three improved approaches for discovery:
 
 1. [Registers](/overview/registers)
 1. [RAINBOW (OGC Knowledge Graph)]() 
+1. Transparent Dependencies 
+
 
 # Well-known Building Blocks registers
 

_pages/use/ftc.md

@@ -1,30 +1,12 @@
 ---
-title: Finding Building Blocks
-permalink: /use/finding
+title: Feature Type Catalogs
+permalink: /use/ftc
 ---
 
-Whilst components described as Building Blocks may be referenced by individual specifications, due to evolution and legacy issues this is not consistent and is a challenge for discovery.  General text search options may assist.
+The concept of a "Feature Type Catalog" (FTC) has been widely accepted as a concept, however interoperable implementations have been slow to emerge.
 
-The OGC Building Block Framework provides two improved approaches:
+This may be because FTCs in practice need to be technically aligned with the underlying infrastructure publishing Features as data, and this in turn has two distinct aspects: persistence (how features are stored) and transfer (how they are exposed). Both of these aspects tend to be technology dependent, and hence expression of Feature Types is often tied to one or other of such aspects.
 
-1. [Registers](/overview/registers)
-1. [RAINBOW (OGC Knowledge Graph)]() 
+Building Blocks provide a new opportunity to publish Feature Types in a technology agnostic way, using multiple schemas mapped to common semantic models, supported by examples and validation.
 
-# Well-known Building Blocks registers
-
-## OGC Specifications
-
-- [OGC Specification Building Blocks](https://opengeospatial.github.io/bblocks/register/) - Building Blocks defined by OGC specifications. (_may include common utility patterns common to multiple specifications_)
-
-## OGC Specifications (in development)
-
-- [OGC API - SOSA](https://opengeospatial.github.io/ogcapi-sosa/) - Implementation of the [OMS/ISO 19156 standard](http://www.opengis.net/def/docs/20-082r4) using the [SOSA ontology](https://www.w3.org/TR/vocab-ssn/).
-- [OGC API Records - GeoDCAT](https://ogcincubator.github.io/geodcat-ogcapi-records/) - Implementation of GeoDCAT using OGC API Records
-
-## Incubator
-
-- [OGC Incubator Building Blocks](https://ogcincubator.github.io/bblocks/) - Building Blocks needed by multiple application domains. (_not yet formally transferred to an appropriate SWG_)
-
-## Projects
-
-- [ILIAD Digital Twin of the Ocean - OGC API Profiles](https://ogcincubator.github.io/iliad-apis-features/)
+Effectively this means the design pattern of a schema mapped to a Class with a Frame (a set of properties). Building Blocks can handle abstract