37 open for the method's author, 2 blocking. 6 for ourselves. Each is tied to the assertions it blocks.
Ordered by blast radius: how much of the specification changes depending
on the answer. The blocking tier is the one worth a conversation rather than an email.
An answered by patent status means the patent description
settled it after the question was written; those are kept at the end.
High 9
Q-G-0006 · open
May a State Restriction reference another object's state? If so, are mutually recursive state definitions intended, or must the dependency graph be acyclic?
Blocks nothing currently in the spec.
Q-G-0007 · open
Is state membership asserted into the graph (rdf:type), or purely derived? Assertion is monotonic and never retracts, which conflicts with lifecycle progression.
Blocks nothing currently in the spec.
Q-G-0008 · open
Is state evaluated at business time, at transaction time, or both? The blog says "at a particular point in time" without saying which clock.
Blocks nothing currently in the spec.
Q-G-0009 · open
Is the transitioning instance always the Object of the SPOP triple, per claim 1? Can a Filter gate the Subject side without an inverse property?
Blocks nothing currently in the spec.
Q-G-0010 · open
Are an Operation's Filters conjunctive, with disjunction expressed as multiple Operations?
Blocks nothing currently in the spec.
Q-G-0012 · open
In a composed Filter, which model declares the predicate — the Subject model, the Object model, or the parent?
Blocks nothing currently in the spec.
Q-G-0013 · open
On import, the child's Main Thing becomes a subclass of the parent's Main Thing. Does the child then inherit the parent's Properties, States and Operations? Inheriting States would multiply partitions.
Blocks nothing currently in the spec.
Q-G-0014 · open
Can one Operation transition more than one object? Claim 4's "storing optionally the second object data" suggests yes; if so, what is the atomicity?
Blocks nothing currently in the spec.
Q-G-0015 · open
Is Authorization checked before or after Filters? Checking after can leak other objects' states through error messages.
Blocks nothing currently in the spec.
Provenance and materials 18
Q-G-0024 · open
Do you still have the glossary content? The plugin is dead, the index page was already empty in 2013, and only 7 of 17 term definitions survive in the Wayback Machine. Your own controlled vocabulary is the highest-value missing artefact.
Blocks nothing currently in the spec.
Q-G-0025 · open
Two documents exist in the archive but not on the live site: /business-capability-definition-using-pciml/ and /reference-reading-guide/. Were they withdrawn deliberately?
Blocks nothing currently in the spec.
Q-G-0026 · open
The Method page defers the Technical API and Platform API to "see Post (to be published)". Were those ever written?
Blocks nothing currently in the spec.
Q-G-0027 · open
Eight images named Why-PMDA1-7 are on the site but referenced by no page. Is that an unpublished deck? Is there a fuller version?
Blocks nothing currently in the spec.
Q-G-0028 · open
The live site reports zero comments, but archived ?replytocom=187 and 188 show comments existed on The Product. Were they deleted, and is there anything in them worth keeping?
Blocks nothing currently in the spec.
Q-G-0029 · open
Is there unreleased material — code, the prototype, tightened semantics, notes? Is any of it subject to an obligation to someone else?
Blocks nothing currently in the spec.
Q-G-0031 · open
PAT:us9378071b2#para-2014 fixes the Filter's quantifier as existential in the engine. Does the notation allow a modeller to ask for anything else — EVERY, NONE, a count comparison — or is existential the only proposition PCIML can state?
Blocks nothing currently in the spec.
Q-G-0032 · open
pciml:hasPrerequisiteSubject and pciml:hasPrerequisiteObject induce a partial order over a Thing's States. Where several State Restrictions hold at once, is the intended reading "the maximal State under that order"? And is the order guaranteed acyclic?
Blocks nothing currently in the spec.
Q-G-0033 · open
The worked Filter table transitions the proposition's Subject in one row (Activate Artist) and an object in neither position in two more (the Instantiate rows). So what determines which object an Operation transitions — is it named on the Operation, or derived from the proposition by a rule we have not found?
Blocks PM-FLT-0080, PM-OPR-0030
Q-G-0034 · open
Both worked Derivation formulas are ambient calls — afn:now() and pmda:User(). Was that intended as the general case for Derivation formulas, or a convenience for the two audit fields? If general, the method cannot support bit-identical replay without a change.
Blocks nothing currently in the spec.
Q-G-0035 · open
The Condition table has a Condition Type column with values Error and Warning. Does a Warning Condition that does not hold still permit the transition? If so there are two Condition semantics and the spec records only one.
Blocks nothing currently in the spec.
Q-G-0036 · open
PCIML has one Property construct doing two jobs: data slots that State Restrictions read, and relationship predicates that Filters traverse. Was that deliberate, or is the distinction implicit? A tool almost certainly has to separate them.
Blocks nothing currently in the spec.
Q-G-0037 · open
Are Object, Component and Universe a normative three-level hierarchy, or just the example depth of a relation that recurses without limit? The single-mechanism claim suggests the latter.
Blocks nothing currently in the spec.
Q-G-0038 · open
Are viewpoint, scope and abstraction the complete classification scheme, or is there a fourth axis — which capability a model belongs to? Widening this later means migrating every model in existence.
Blocks PM-CLS-0030
Q-G-0039 · open
The description names a PCIML construct Resource (801) once, at [para-1954], as "the construct Resource 801 that describes the Object", and never again. Is it an earlier name for Thing, a superclass of Thing and Property, or something dropped before filing?
Blocks nothing currently in the spec.
Q-G-0040 · open
The Condition table's Enforces Property in Condition column holds property names in rows r3-r9 and State names in rows r10-r14 (New Artefact, Created Artefact). Is the column used inconsistently, or does it mean something different for Artefact rows? As transcribed, every Artefact Condition is unevaluable: there is no property by that name to require.
Blocks nothing currently in the spec.
Q-G-0041 · open
Which State does a given Operation achieve? pciml:achieves is named in the patent, but none of the three transcribed blog tables records the Operation-to-State pairing — the Filter table names Operations, the Condition and Derivation tables name target States, and nothing joins them. The demo currently infers the pairing from naming convention and says so on screen. Is there a source that gives it, or was it only ever implicit?
Blocks nothing currently in the spec.
Q-G-0042 · open
The Condition table gives the State as Create Artist in rows r4-r6 (an Operation name; every other c3 cell holds a State) and as CreatedUser in rows r8-r9 (one word here, two in c1 of the same rows). Neither is the name of any State. Were Created Artist and Created User meant? As transcribed, five of the twelve Conditions attach to no State and can never fire, and the demo reports them as unattached rather than correcting the spelling.
Blocks nothing currently in the spec.