OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

openc2 message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [openc2] Action Item - Actuator Profile List


Looks like a great plan to me.

 

-- 

Duncan Sparrell

sFractal Consulting LLC

iPhone, iTypo, iApologize

I welcome VSRE emails. Learn more at http://vsre.info/

 

 

 

From: openc2@lists.oasis-open.org <openc2@lists.oasis-open.org> on behalf of David Kemp <dk190a@gmail.com>
Date: Wednesday, September 1, 2021 at 12:39 PM
To: openc2@lists.oasis-open.org <openc2@lists.oasis-open.org>
Subject: [openc2] Action Item - Actuator Profile List

At today's working meeting I took an action item to update the actuator profile namespace registry contained in the Architecture repo https://github.com/oasis-tcs/oc2arch.

The registry lists all profiles usable by OpenC2, both standard and custom.  It currently lists only profile namespaces (full URIs that uniquely identify each actuator profile).

The Language Spec lists for each profile:

1) a prefix (namespace id) - short name for the profile schema, needed for when we start publishing language and profile schemas
2) property ID and name (e.g., "1024", "slpf") used to identify Targets, Args, Actuators, and Responses defined in actuator profiles.

The separation of responsibilities between registry and language spec is nice in theory but confusing in practice, so I plan to update the registry to contain all information about current and proposed actuator profiles:
1) profile name
2) profile namespace URI
3) profile namespace prefix (NSID)
4) language spec property ID
5) language spec property name
6) document status (standard/custom, proposed / "repo created" / OASIS publication level)

The workflow, to be documented in TC OPS, would be that anyone proposing a standard profile or wishing to register a custom profile would request a listing in the registry, and the registry would be updated with no administrative burden.  Then the TC would update the Language Spec as often as it wishes to incorporate changes to the registry.

Dave



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]