Owen,
Forgive
the latency I am now
back from a week away.
Maybe the robots were
helpful.
Wendell, I'm not sure I
understand the point you
are making about "all
kinds of metrics" but the
core elements of all
performance reports are
the same. All kinds of
metrics can be reported in
StratML Part 2,
Performance Plans/Report,
format. What differs is
the subject matter --
missions, goals,
objectives, stakeholders,
and performance indicators
-- not the structure and
semantics of the reports
themselves.
Goodness
– I can see we are
already failing to
communicate. Our nouns
do not refer to the same
things. To address this,
I would have to go back
and recapitulate the
thread, anchoring it in
context – maybe falling
into more holes along
the way. I think I
won't. To find out more
about OSCAL and its
intended uses, you can
consult any of our
materials or indeed
attend a workshop or
public meeting. I am
sure you would be very
stimulated. If not
encouraged.
Government Computer
News invited me to write
an article on that
topic in 2017, in
follow-up to
two previous articles
entitled "The open,
efficient,
machine-readable
government" and
"Government performance
data: Let's make it open,
machine-readable and
permanent."
Thanks
for the links! I will
pass these along.
The NICE plan is now
available in StratML Part
2 format at
https://stratml.us/drybridge/index.htm#NICE (There is a bit of
latency associated with
the Edit link but it
should open the plan in my
XForm for StratML Part 2,
Performance Plan/Report,
format.) Presumably,
someone is keeping track
of progress on performance
indicators associated with
the goals and objectives
it contains, but as per
the good practice
specified in
section 10 of
GPRAMA, it would be good
if they were being
published in open,
standard, machine-readable
format.
Indeed
it would.
Are OSCAL's performance
reports available on the
Web, i.e., performance
indicators for the
objectives outlined in the
plan for OSCAL? If so, I
may wish to render them in
StratML Part 2 format.
Our
web site is not hard to
find:
http://pages.nist.gov/OSCAL.
Go from there. It
includes copious
hand-authored content as
well as
machine-generated
content. But it's
probably not what you're
looking for.
At
the same time, I don't
think the OSCAL
documentation is where
you should start, or
indeed the OSCAL project
(which after all is only
one of many projects
within our division,
within an OU within an
agency within a
department). OSCAL
itself is likely to be
inscrutable (if not
altogether baffling) if
you do not first take on
this:
which
is an electronic
rendering of the
document found here:
which
(in turn) is among the
most widely downloaded
pieces of public
property on the
Internet. (You can look
up the figures.)
Any/all
of this would be
worthwhile
transformation
capabilities to have
(in/out of StratML,
which also serves as a
bridge to much else, one
should hope). An XSLT
that could render this
catalog (as we call it)
into StratML could be
used not only on this
document but on any
OSCAL catalog derived
from it. This in turn
leverages one of OSCAL's
core features, namely
that it offers an easy
way for producing such
catalogs
programmatically, with
the help of tooling. You
would get all that for
free.
As
for the wider topic, it
is of course very very
extensive, to say
nothing of deep. I think
it would be interesting
to see an argument for
StratML in terms of the
security controls that
are described in SP
800-53. For example
there is obviously
SC-12, "Information
Management and
Retention" – although an
open format does not in
itself solve this
problem, it is a
sine qua non for
solving it, is it not?
But also check out
SI-10, "Information
Input Validation". (How
can you even begin to do
that without StratML or
OSCAL or something
analogous?) Fascinating
stuff.
In
any case we would be
thrilled if you were to
produce any OSCAL-facing
work, as we are even now
entering a phase of (we
think) rapid growth
wherein there are many
opportunities for
applications such as
yours – both to help us
realize the kinds of
integrations we need
(SC-29: Heterogeneity)
and potentially to have
an impact in your space
(giving you another
valuable connection for
your pathway or
"information bus").
Regards,
Wendell
On
8/5/2022 10:12 AM,
Piez, Wendell A. (Fed)
wrote:
Hi
Owen,
Cc:ing
my supervisor Michaela
Iorga here.
😊
The
short answer is that
all kinds of metrics
not only performance
metrics but also any
kind of scan or log
format etc., all sit
outside the scope of
OSCAL – directly
outside, one might
say, since they also
constitute a very
important (though not
the only very
important) segment of
the widely disparate
kinds of documents
that must interface
directly with OSCAL
documents and systems.
That is, OSCAL will
represent metadata
regarding all this
stuff, summarize it
and link to it, but
does not seek to
"subsume" it by
representing it
directly. (Not that
we're against that:
it's just not a goal.)
Largely
because of the
disparity of these
formats but also
because I'm not an
expert (there is a lot
to know), I can't
answer your question
regarding comparisons
of those formats to
StratML. With regard
to OSCAL itself, my
guess is that many or
most kinds of OSCAL
will convert fairly
cleanly into StratML,
but not the reverse,
since OSCAL isn't
actually a documentary
format either. (It is
more like an object
model, supported by
tagging, that is
capable of supporting
certain kinds of
documentary
information.)
To
the extent this is the
case (and OSCAL is not
so large, at least
considered as a tag
set), any document
published in OSCAL
could be rendered in
StratML for
availability in
systems that read
StratML. But not all
documents represented
in StratML would
convert easily into
some or any form of
OSCAL: that would
depend on the case.
Best
regards, Wendell
Wendell, I had
updated my address
book to make your work
address primary but
neglected to check
that my E-mail client
used it on my last
reply.
W/re OSCAL Goal 3:
Continuity - Enable
Continuous
Assessment, I'm
curious to know: a)
how performance
metrics are being
reported, i.e., in
what format, and b)
how that format
compares to StratML
Part 2.
Soon the NICE plan
will also be available
in StratML format.
Owen
On
8/5/2022 8:23 AM,
Wendell Piez wrote:
Hi
again Owen and
Zubin,
Currently
I am playing
much more of a
support than a
leadership role
with respect to
XML
strategy (and
everything
else!) in the
federal
government, but
in that capacity
I am doing the
best I can to
promote the good
work. You can
research our
project at
pages.nist.gov/OSCAL
(and related
repositories).
Hi
Owen,
Thanks
for this. I'm
cc'ing my day
job email
since a good
response is
likely to
require a
little
research.
Write
me back there
too, anytime
--
However,
I can't seem
to find it.
This update
is the best
reference I've
been able to
turn up.
Perhaps
you may have
seen in the
Balisage chat
my reference
to this
objective in
the Department
of Commerce's
plan:
Objective
1.2.2:
Standards
Development
- Strengthen
U.S.
participation
in technical
standards
development
However,
the KPI
associated
with that
objective is
pretty weak:
KPI
1.2.3:
Staff Trained
- Number of
U.S.
Government
staff trained
to effectively
coordinate,
participate,
and influence
technical
standards
development
A better,
more
outcome-oriented
metric would
address the
number of
standards and
SDOs in which
Federal
agencies are
actually
engaged.
I see the
NTTAA reports
at
https://www.nist.gov/standardsgov/nttaa-reports but they leave a lot
to be desired
in terms of
usability and
utility.
Ideally, those
reports would
be published
in StratML
Part 2 format
and the data
from them
would
semi-automatically
roll up to
NIST's &
DOC's
performance
reports.
Any
chance you
might be able
to point me to
a more current
plan for NIST?
Owen