Use case: a vendor or a spec for a gateway to another protocol that provides more info wants to provide additional metadata fields that are standard in About & Configuration.
The 14.12 About interface spec (https://allseenalliance.org/framework/documentation/learn/core/about-announcement/interface) does not say whether the metadata fields in About can be extended or must be only the set in the spec. The 14.12 Configuration interface spec (https://allseenalliance.org/framework/documentation/learn/core/about-announcement/interface) on the other hand explicitly states "The OEM or application developer can add additional fields." Questions: * Does this mean that it is NOT legal for OEM or app developer to add additional fields to the About data? * If an additional field is read-only, should it be added to aboutData, or configMap, or both? * If an additional field is read-write, should it be added to aboutData, or configMap, or both? * Is there any expected naming convention for the names of the additional fields? (e.g., to avoid future conflicts with anything that might be a standard) * Is it possible for a client app to reliably know the semantics of an additional field? (e.g., if the field name is unique enough? Or some other rule?) Dave
_______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core
