Topic: applicability and risk
assessment of SW practices to
the semantic
modeling a,k.a. taxonomy a.k.a. ontology component of
the Roadmap that
PF is
pursuing.
problem: how to link with 'standard'
concepts
not
published as RDF
help using SKOS
other stable vocabularies that we
might
use?
Example Possible
Sequence
Centering the topic (25% of
time)
PF background
Roadmap
scripted widgets bound
to platform accessibility
APIs
[platform ::= Java |
OS,
mostly]
page structure and
navigation
syntax tree contains
too
much noise to
succeed with just markup semantics
metadata tailors
and
repairs syntax
tree so there is reliable extraction of an
abstract graph fit for [a
variety of
forms of] intrapage
navigation
user agents including AT
provide
"different strokes
for different folks" climate of navigation
functions over the
captured common model of page structure.
author tools coach
authors in
bringing navigable
abstraction of syntax up to snuff.
more general metadata
applications
knowledge augmentation that is
assistive for those with
reading-impairing
conditions
query
word, get dictionary entry
flag
figurative use
Terms of
Art
various
drivers of reading difficulty (c.f. S/W complexity
metrics)
[what
is there in the IMS
taxonomy
that
addresses this domain?]
applications in
the DI
framework (device
characterization, user factors, content factors)
role of taxonomies in
Roadmap and
accessibility
metadata in Web
documents
knowledge
in
pertinent
dictionaries/thesauri
wide use of stable core
recognize terms
by
syntactic
pattern
apply semantics
by
out-of-band reading
stable spec
emerging use of SW potential
processors that
dereference
and process
dictionary/thesaurus backups
transitive
dereference
until what you need
to know is reduced to trusted terms
[computed
equivalence
of
terms?]
[SW
BP
alternate/amendment
for this high-end processing model
welcome]
perceived challenges
multi-level
stability
the terms that
offer
a
convergence target for "platform" APIs must exhibit lots of
stability
for the platform APIs not to break away from rendezvous
process.
failthful
(normative)
import of concepts not published in RDF or by
URI.
assertions
about classes
defined by intension (queries
and selectors)
SW BP
background (how does this
conversation
fit in your world in
seven-league steps)
general area
of
work
what modules of
practice
are stabilizing
already/soon (i.e. topics in order of
calendar
prospects)
where they see
their
work
or other prior art applicable to our problems.
q+a by queue: fill in
and
confirm we heard each
other.
Brass tacks -
specific examples with low-risk approaches
(up to 50% of time)
preferred - SW BP
delegates
discuss
examples drawn from PF shopping list
second choice - PF nominates
concrete
examples
for discussion
compare/contrast use
of skos:definition
vs.
skos:broader for import of and derivation from terms in stable
use
but not
in RDF publications.
best practice
for
[SKOS?]
upgrade to W3C spec style re RFC-2119 terms?
More general
issues and advice (as time permits)
[q+a by
queue]
emulating logic and rule languages in
SW
notations; or
embedding (XPath).
application of SKOS to syntax terms?
Follow-up (15% of
time)
actions accepted
another meeting?
Who/Where/How ask technical
support
questions?
other
form of persistent liaison?
Be Done