FEP-2e40: The FEP Vocabulary Extension Process

Standards Fediverse Enhancement Proposals
, , ,
2

A few things to point out:

  • This has some overlap with FEP-cb76: Content Addressed Vocabulary which proposes a URN namespace for FEPs, instead of an HTTPS URI.

  • You are defining the term fep using https://www.w3id.org/fep# if I understand correctly. However, you also refer to some fep-special term definition that is not actually defined in the proposal, nor is it clear how it differs functionally from the fep term definition. Do you expect the maintenance of multiple w3id purls? What makes a term definition “special”?

    • What if different FEPs conflict in their term definitions while using the same shorthand property name? This implies for future safety, each FEP should define its own namespace. Or, otherwise, a recommendation should be made to ensure terms and property names chosen do not conflict with current or potential future extensions. Generally, a “namespace” (more accurately, a vocabulary) is a collection of terms as defined under the same ontology, and I can see there being multiple different ontologies as projects pick and choose what they need.

    • Is there any consideration given to custom-defined contexts? It is not always the case that one will use a “premade” context, especially if they do not need much from it.

1 Like