Sense Atlas Front End

A

Add a log in/out widget to the footer (email and "go" button to log in, logout button to log out).

Other: [RESOLVED] Logging in and out of Sense Atlas currently happens out of band.

Adjacent nodes in the left-side lozenge UI can be kind of ambiguous.

Other: Put the type icons in the adjacent node elements.; Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.

Almost all Web templating languages allow for broken markup (a major reason we're still using XSLT is because it doesn't).

Other: Survey other templating languages.

Alter the template so that the editing widgets do not show up unless there is a registered user detected.

Has Broader: Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.
Other: [RESOLVED] The editing widgets show up even if there is no current logged-in user.

Always focus the network when you select it or create a new one.

Other: Changing the focus isn't really that big a deal and it can always be changed later.; Do we always want to focus the new network?; Maybe the user just wants to look at the other network (or create one and not switch to it).; Switching the focus without being conspicuous about it could cause the user to make a mistake.

An autofilled text box has an unlimited capacity and is easier to deal with than a dropdown when there are lots of entities.

Other: Implement the network switcher as a an autofilling text box.

Automatically importing the entity may make sense for creating new networks but could make a mess with existing ones.

Other: Automatically import the node; people can remove it later.

[ADOPTED] Only focus the new network if the user explicitly signals to do so (i.e., through a dedicated button).

Has Narrower: Make sure the UI has a "Set Focus" button.
Other: Do we always want to focus the new network?; Extra buttons are potentially clutter.; The user's intent is always clear.

B

The backlinks transform is actually extremely goofed and contributing to slow page delivery, which will only get worse if it has to parse more forward links too.

Other: Create a "forward links" transform to attach residual links to opaque (e.g. static) documents, analogous to the backlinks transform.; Fix the backlinks transform so that it only produces non-redundant links, and only for the subject document and any fragments thereof.

C

Changing the focus isn't really that big a deal and it can always be changed later.

Other: Always focus the network when you select it or create a new one.

Client wants to use the IBIS tool (Sense Atlas) in everyday operations.

Has Narrower: Plan projects and resources with the use of the Process Model Ontology.; [RESOLVED] Client wants the ability to create multiple IBIS networks.
Other: Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.

Could we establish that an argument is an argument purely by inference?

Other: There is no upgrade/downgrade path to go from { issue ↔ argument ↔ goal ↔ target } or { position ↔ task }.

Create (and run) a SPARQL script that does the appropriate surgery to add the forward-links transform to the transform queue.

Has Broader: Create a "forward links" transform to attach residual links to opaque (e.g. static) documents, analogous to the backlinks transform.
Has Narrower: Fix the bug in RDF::LMDB that is preventing the default graph from being selected.
Other: SPARQL should also be selecting the default graph with a `GRAPH ?g` construct, but the quad store isn't doing it.

Create a "forward links" transform to attach residual links to opaque (e.g. static) documents, analogous to the backlinks transform.

Has Broader: Create a one-off front page that promotes Sense Atlas and explains to people what they're looking at.
Has Narrower: Create (and run) a SPARQL script that does the appropriate surgery to add the forward-links transform to the transform queue.; Fix the backlinks transform so that it only produces non-redundant links, and only for the subject document and any fragments thereof.
Other: How do we account for the dynamic elements on the page from the graph?; It is wasteful to extract the graph data out of the RDFa in the document, throw it away, and then extract it again, as it moves through the transformation pipeline.; The backlinks transform is actually extremely goofed and contributing to slow page delivery, which will only get worse if it has to parse more forward links too.

Create a keyboard event handler that submits the form for all forms that only contain a datetime-local widget (as a non-hidden control).

Has Broader: Expand the script that manages the adjacent entity controls so that it also attaches to the "agent" controls.
Other: It turns out that (at least in Firefox) the `datetime-local` input does not let you set a valid ISO8601/W3CDTF time stamp, only a truncated one.; The datetime-local input type does not seem to elicit form submission with the enter key like a text box does (in Firefox).; `Date.prototype.toISOString()` encodes the time zone offset as Zulu (UTC) no matter what it actually is.

Create a new <datalist> for autofilling foaf:Agent entities.

Has Broader: Expand the script that manages the adjacent entity controls so that it also attaches to the "agent" controls.

Create a one-off front page that promotes Sense Atlas and explains to people what they're looking at.

Has Narrower: Create a "forward links" transform to attach residual links to opaque (e.g. static) documents, analogous to the backlinks transform.
Other: How do we account for the dynamic elements on the page from the graph?; The front page of senseatlas.net is also super janky.

Create a pop-up "jump to entity"/"create new unconnected entity" interface.

Has Broader: It would be useful, from the keyboard, to be able to jump to an entity you know is in the graph but not immediately connected.
Other: From the entity UI, there is no mechanism for adding a new entity that is not attached to the current entity.

Create a template for pm:Target.

Has Broader: Rough out the new classes and try loading them with instance data; take notes for what can be improved.; Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.
Has Narrower: Expand the script that manages the adjacent entity controls so that it also attaches to the "agent" controls.

Create a template for pm:Task.

Has Broader: Rough out the new classes and try loading them with instance data; take notes for what can be improved.; Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.
Has Narrower: Expand the script that manages the adjacent entity controls so that it also attaches to the "agent" controls.
Other: The datetime-local input type does not seem to elicit form submission with the enter key like a text box does (in Firefox).

Create ibis:endorsed-by relations widget, i.e. the ability to "like" an entity.

Has Broader: Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.
Other: How do you get the users into the system?

D

Debugging XSLT 1.0 in particular is brutal, due to years of neglect from the browser vendors.

Other: Despite being standard, reliable, and fast to execute, and built into every browser, XSLT 1.0 in particular is really clunky to work with.

Despite being standard, reliable, and fast to execute, and built into every browser, XSLT 1.0 in particular is really clunky to work with.

Other: Debugging XSLT 1.0 in particular is brutal, due to years of neglect from the browser vendors.; The XSLT component kind of sucks.; There is likewise the persistent threat that one of the browser vendors (say Chrome) removes support for XSLT 1.0.; Try messing around with SaxonJS?

Devise a radial clumping algorithm for determining the θ of each node.

Other: Perhaps the ridiculous distances (r) between nodes will resolve itself if the ridiculous radial distance (θ) is fixed.; The math on the hyperbolic sugiyama visualization is wrong; nodes farther down rank are miles apart from each other (both r and θ).

Dispatching templates on the server side would afford getting rid of that clunky and ridiculous client-side dispatcher.

Other: Getting rid of the clunky client-side dispatcher would also get rid of that giant RDF/XML file containing all the vocabs, which isn't used for anything else.; Modify the transform that inserts XSLT processing instructions to match against asserted types (or specific resources).; Use the import precedence native to XSLT.

Do we always want to focus the new network?

Other: Always focus the network when you select it or create a new one.; Do we show the UI to focus the network if it's already focused?; Is the focus a property of the graph, or a property of the user state?; Make some UI that affords creating a new IBIS network (or SKOS concept scheme) from an entity or network overview.; Make some UI that affords switching IBIS networks.; [ADOPTED] Only focus the new network if the user explicitly signals to do so (i.e., through a dedicated button).

Do we show the UI to focus the network if it's already focused?

Other: Do we always want to focus the new network?; Keep the focus button and disable it, and change the text to say "Focused".; No, remove the set focus button if the network in question is already focused.; Yes, always show the focus button and make clicking on it a no-op.

Do we want to be able to ascribe a value to the goal specifically, rather than the target—which has a budget?

Other: Rough out the new classes and try loading them with instance data; take notes for what can be improved.

Double-check the behaviour of datetime-local in Chrome and Safari.

Other: The datetime-local input type does not seem to elicit form submission with the enter key like a text box does (in Firefox).

Dropdowns are easy to implement.

Other: Implement the network switcher as a dropdown.; Radio buttons are just as easy to implement (over a small, fixed set of elements) as dropdowns.; Use a dropdown to select between IBIS network and SKOS concept scheme like in the initialization phase.

Dropdowns can get huge and unwieldy.

Other: Implement the network switcher as a dropdown.

Dropdowns hide the available options behind a click.

Other: There is a bigger target to click with radio buttons.; Use a dropdown to select between IBIS network and SKOS concept scheme like in the initialization phase.

The datetime-local input type does not seem to elicit form submission with the enter key like a text box does (in Firefox).

Other: Create a keyboard event handler that submits the form for all forms that only contain a datetime-local widget (as a non-hidden control).; Create a template for pm:Task.; Double-check the behaviour of datetime-local in Chrome and Safari.
See Also

The display is still goofed on a mobile screen.

Other

[DONE] Create a template for pm:Goal.

Has Broader: Rough out the new classes and try loading them with instance data; take notes for what can be improved.; Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.
Has Narrower: Expand the script that manages the adjacent entity controls so that it also attaches to the "agent" controls.

[DONE] Put Sense Atlas online so the client can observe its development.

Has Broader: Rough out the new classes and try loading them with instance data; take notes for what can be improved.
Other: Unlike IBIS which is half a century old, the PM ontology has never been road-tested, and will likely require several iterations to get right.

`Date.prototype.toISOString()` encodes the time zone offset as Zulu (UTC) no matter what it actually is.

Other: Create a keyboard event handler that submits the form for all forms that only contain a datetime-local widget (as a non-hidden control).
See Also

E

Even once caching is implemented, a full server round-trip for the whole page with every POST is costly and often unnecessary.

Other

Expand the script that manages the adjacent entity controls so that it also attaches to the "agent" controls.

Has Broader: Create a template for pm:Target.; Create a template for pm:Task.; [DONE] Create a template for pm:Goal.
Has Narrower: Create a keyboard event handler that submits the form for all forms that only contain a datetime-local widget (as a non-hidden control).; Create a new <datalist> for autofilling foaf:Agent entities.

Extra buttons are potentially clutter.

Other: [ADOPTED] Only focus the new network if the user explicitly signals to do so (i.e., through a dedicated button).

F

Fix the backlinks transform so that it only produces non-redundant links, and only for the subject document and any fragments thereof.

Has Broader: Create a "forward links" transform to attach residual links to opaque (e.g. static) documents, analogous to the backlinks transform.
Other: The backlinks transform is actually extremely goofed and contributing to slow page delivery, which will only get worse if it has to parse more forward links too.

Fix the bug in RDF::LMDB that is preventing the default graph from being selected.

Has Broader: Create (and run) a SPARQL script that does the appropriate surgery to add the forward-links transform to the transform queue.
Other: SPARQL should also be selecting the default graph with a `GRAPH ?g` construct, but the quad store isn't doing it.

From the entity UI, there is no mechanism for adding a new entity that is not attached to the current entity.

Other: Create a pop-up "jump to entity"/"create new unconnected entity" interface.

The focus is confusing but needed to disambiguate which issue network to attach a new entity to.

Other: Why not just attach a new entity to all the issue networks its neighbour is currently in?; [RESOLVED] For writing to the graph, the IBIS tool requires a "focus" node with which to associate new entries. This is associated with a state object, which is in turn associated with the current user.

The front page of senseatlas.net is also super janky.

Other: Create a one-off front page that promotes Sense Atlas and explains to people what they're looking at.; The template for ibis:Network (skos:ConceptScheme) is really shabby.

G

Getting rid of the clunky client-side dispatcher would also get rid of that giant RDF/XML file containing all the vocabs, which isn't used for anything else.

Other: Dispatching templates on the server side would afford getting rid of that clunky and ridiculous client-side dispatcher.; Use the import precedence native to XSLT.

H

How do we account for the dynamic elements on the page from the graph?

Other: Create a "forward links" transform to attach residual links to opaque (e.g. static) documents, analogous to the backlinks transform.; Create a one-off front page that promotes Sense Atlas and explains to people what they're looking at.

How do we match templates to resources?

Other: Modify the transform that inserts XSLT processing instructions to match against asserted types (or specific resources).; Use the import precedence native to XSLT.

How do we select the type of network to be created?

Other: Make some UI that affords creating a new IBIS network (or SKOS concept scheme) from an entity or network overview.; Use a dropdown to select between IBIS network and SKOS concept scheme like in the initialization phase.; Use radio buttons to select between IBIS network and SKOS concept scheme.

How do you get the users into the system?

Other: Create ibis:endorsed-by relations widget, i.e. the ability to "like" an entity.; There will need to be some kind of representation of foaf:Person (who can be attached to an authentication principal).

I

If an entity is not immediately connected to the current one, you have to hunt through the visualization or go back to the scheme view to find it.

Other: It would be useful, from the keyboard, to be able to jump to an entity you know is in the graph but not immediately connected.

If every RDF class (and individual resource) that mattered could be assigned its own XSLT transform, then we could have sane defaults for unspecified classes.

Other: Modify the transform that inserts XSLT processing instructions to match against asserted types (or specific resources).

If one of the browser vendors removed support for XSLT 1.0, we could move XSLT processing to the server side.

Other: Part of the reason for client-side template processing is to shift the cost of computing templates to the user, who (usually) has ample such resources to spare.; There is likewise the persistent threat that one of the browser vendors (say Chrome) removes support for XSLT 1.0.

If we navigate to the overview of a network which is not in focus, how do we take focus?

Other: Should the focus button also navigate to the network overview?

Implement the network switcher as a an autofilling text box.

Has Broader: Make some UI that affords switching IBIS networks.
Other: An autofilled text box has an unlimited capacity and is easier to deal with than a dropdown when there are lots of entities.; An autofilled text box will take up less space.; Autofilled text boxes are implemented inconsistently across browsers.; There will be an ambiguity with the intent of typing in a value not found in the autofill: are you renaming the current network or making a new one?

Implement the network switcher as a dropdown.

Has Broader: Make some UI that affords switching IBIS networks.
Other: Dropdowns are easy to implement.; Dropdowns can get huge and unwieldy.

Importing nodes from one network to another is a pain in the ass.

Other: It will often be quicker to bulk-import a bunch of nodes and then prune out any extraneous ones.; Make it possible to import all of a node's neighbours as well.

Improve the UI for ibis:Network and skos:ConceptScheme.

Has Broader: Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.
Other: The template for ibis:Network (skos:ConceptScheme) is really shabby.

Is the focus a property of the graph, or a property of the user state?

Other: Do we always want to focus the new network?

It is currently difficult to answer the question, when looking at an issue network, "what still needs to be done?"

Other: It would be handy if active entities could be easily visually differentiated from inactive ones.

It is wasteful to extract the graph data out of the RDFa in the document, throw it away, and then extract it again, as it moves through the transformation pipeline.

Other: Create a "forward links" transform to attach residual links to opaque (e.g. static) documents, analogous to the backlinks transform.; Update the faux-monad Intertwingler::Representation::Nokogiri to reference a subclass of Nokogiri that has an accessor for the RDF.

It turns out that (at least in Firefox) the `datetime-local` input does not let you set a valid ISO8601/W3CDTF time stamp, only a truncated one.

Other: Create a keyboard event handler that submits the form for all forms that only contain a datetime-local widget (as a non-hidden control).
See Also

It will often be quicker to bulk-import a bunch of nodes and then prune out any extraneous ones.

Other

It would be handy if active entities could be easily visually differentiated from inactive ones.

Other: It is currently difficult to answer the question, when looking at an issue network, "what still needs to be done?"; Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.; Use the saturation to differentiate active from inactive entities.

It would be useful, from the keyboard, to be able to jump to an entity you know is in the graph but not immediately connected.

Has Narrower: Create a pop-up "jump to entity"/"create new unconnected entity" interface.
Other: If an entity is not immediately connected to the current one, you have to hunt through the visualization or go back to the scheme view to find it.

The issue/position/argument type toggle widget is a vestige from the original 2013 prototype and never actually made any sense.

Other: Replace the type toggle widget with an upgrade/downgrade widget in either type vertical.; Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.

K

Keep the focus button and disable it, and change the text to say "Focused".

Other: Do we show the UI to focus the network if it's already focused?

M

Make a field in the UI for (re)setting the network's name.

Has Broader: Make a unified UI for switching and/or creating new IBIS networks, SKOS concept schemes.
Other: What about the ability to rename a network?

Make a toggle for whether the node should be included.

Other: There appears to be a general issue of getting nodes into networks.; What about the IBIS entity in context? Does it get ported to the other network?

Make a unified UI for switching and/or creating new IBIS networks, SKOS concept schemes.

Has Narrower: Make a field in the UI for (re)setting the network's name.; Make some UI that affords creating a new IBIS network (or SKOS concept scheme) from an entity or network overview.; Make some UI that affords switching IBIS networks.
Other: [RESOLVED] Client wants the ability to create multiple IBIS networks.

Make it possible to import all of a node's neighbours as well.

Other: Importing nodes from one network to another is a pain in the ass.; It will often be quicker to bulk-import a bunch of nodes and then prune out any extraneous ones.

Make some UI that affords creating a new IBIS network (or SKOS concept scheme) from an entity or network overview.

Has Broader: Make a unified UI for switching and/or creating new IBIS networks, SKOS concept schemes.
Other: Do we always want to focus the new network?; How do we select the type of network to be created?; What about the IBIS entity in context? Does it get ported to the other network?; What about the ability to rename a network?

Make some UI that affords switching IBIS networks.

Has Broader: Make a unified UI for switching and/or creating new IBIS networks, SKOS concept schemes.
Has Narrower: Implement the network switcher as a an autofilling text box.; Implement the network switcher as a dropdown.; Make sure the UI has a "Set Focus" button.
Other: Do we always want to focus the new network?; What about the IBIS entity in context? Does it get ported to the other network?

Make sure the UI has a "Set Focus" button.

Has Broader: Make some UI that affords switching IBIS networks.; [ADOPTED] Only focus the new network if the user explicitly signals to do so (i.e., through a dedicated button).

Maybe the user just wants to look at the other network (or create one and not switch to it).

Other: Always focus the network when you select it or create a new one.

Modify the content inventory vocab to include a new class and properties to represent a template.

Has Broader: Modify the transform that inserts XSLT processing instructions to match against asserted types (or specific resources).

Modify the transform that inserts XSLT processing instructions to match against asserted types (or specific resources).

Has Broader: Use the import precedence native to XSLT.
Has Narrower: Modify the content inventory vocab to include a new class and properties to represent a template.
Other: Dispatching templates on the server side would afford getting rid of that clunky and ridiculous client-side dispatcher.; How do we match templates to resources?; If every RDF class (and individual resource) that mattered could be assigned its own XSLT transform, then we could have sane defaults for unspecified classes.

The math on the hyperbolic sugiyama visualization is wrong; nodes farther down rank are miles apart from each other (both r and θ).

Other: Devise a radial clumping algorithm for determining the θ of each node.

N

No, remove the set focus button if the network in question is already focused.

Other: Do we show the UI to focus the network if it's already focused?

No, stay where you are. Use a dedicated "Go" button to navigate.

Other: Should the focus button also navigate to the network overview?

Note that an entity can be an ibis:Argument and an pm:Goal/Task at the same time.

Other: Replace the type toggle widget with an upgrade/downgrade widget in either type vertical.; There is no upgrade/downgrade path to go from { issue ↔ argument ↔ goal ↔ target } or { position ↔ task }.

O

Only show the nodes in an unfocused network that are immediately adjacent to the ones in the focused network (and do so at half opacity), like is already done with skos:Concept.

Other: When a node is in more than one issue network, the visualization shows the amalgamation of all the networks.

Override form POST actions with scripting.

Other: Even once caching is implemented, a full server round-trip for the whole page with every POST is costly and often unnecessary.

P

Part of the reason for client-side template processing is to shift the cost of computing templates to the user, who (usually) has ample such resources to spare.

Other: If one of the browser vendors removed support for XSLT 1.0, we could move XSLT processing to the server side.; Try messing around with SaxonJS?

Perhaps the ridiculous distances (r) between nodes will resolve itself if the ridiculous radial distance (θ) is fixed.

Other: Devise a radial clumping algorithm for determining the θ of each node.

Plan projects and resources with the use of the Process Model Ontology.

Has Broader: Client wants to use the IBIS tool (Sense Atlas) in everyday operations.
Other: Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.; Unlike IBIS which is half a century old, the PM ontology has never been road-tested, and will likely require several iterations to get right.
See Also

Put a link in the footer back to the "top".

Other

Put the type icons in the adjacent node elements.

Other: Adjacent nodes in the left-side lozenge UI can be kind of ambiguous.

R

Radio buttons are just as easy to implement (over a small, fixed set of elements) as dropdowns.

Other: Dropdowns are easy to implement.; Use radio buttons to select between IBIS network and SKOS concept scheme.

Replace the type toggle widget with an upgrade/downgrade widget in either type vertical.

Has Broader: Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.
Other: Note that an entity can be an ibis:Argument and an pm:Goal/Task at the same time.; The issue/position/argument type toggle widget is a vestige from the original 2013 prototype and never actually made any sense.; There is no upgrade/downgrade path to go from { issue ↔ argument ↔ goal ↔ target } or { position ↔ task }.

Rescanning the document (which we assume to be altered from the previous transform) may be the only reliable way to ensure that it matches the content.

Other: Update the faux-monad Intertwingler::Representation::Nokogiri to reference a subclass of Nokogiri that has an accessor for the RDF.

Rough out the new classes and try loading them with instance data; take notes for what can be improved.

Has Narrower: Create a template for pm:Target.; Create a template for pm:Task.; [DONE] Create a template for pm:Goal.; [DONE] Put Sense Atlas online so the client can observe its development.
Other: Do we want to be able to ascribe a value to the goal specifically, rather than the target—which has a budget?; Unlike IBIS which is half a century old, the PM ontology has never been road-tested, and will likely require several iterations to get right.

[RESOLVED] Client wants the ability to create multiple IBIS networks.

Has Broader: Client wants to use the IBIS tool (Sense Atlas) in everyday operations.
Has Narrower: What about the ability to rename a network?
Other: Make a unified UI for switching and/or creating new IBIS networks, SKOS concept schemes.; [RESOLVED] For writing to the graph, the IBIS tool requires a "focus" node with which to associate new entries. This is associated with a state object, which is in turn associated with the current user.

[RESOLVED] For writing to the graph, the IBIS tool requires a "focus" node with which to associate new entries. This is associated with a state object, which is in turn associated with the current user.

Other: Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.; The focus is confusing but needed to disambiguate which issue network to attach a new entity to.; [RESOLVED] Client wants the ability to create multiple IBIS networks.
See Also

[RESOLVED] It is currently not possible to navigate to the "top" cgto:Space from either an entity or a network.

Other

[RESOLVED] Logging in and out of Sense Atlas currently happens out of band.

Other: Add a log in/out widget to the footer (email and "go" button to log in, logout button to log out).

[RESOLVED] The editing widgets show up even if there is no current logged-in user.

Other: Alter the template so that the editing widgets do not show up unless there is a registered user detected.; Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.

[RESOLVED] The unlink button appears to be broken (again?) for ibis:suggested-by.

Other: Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.

S

Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.

Has Broader: Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.
Has Narrower: Alter the template so that the editing widgets do not show up unless there is a registered user detected.; Create a template for pm:Target.; Create a template for pm:Task.; Create ibis:endorsed-by relations widget, i.e. the ability to "like" an entity.; Improve the UI for ibis:Network and skos:ConceptScheme.; Replace the type toggle widget with an upgrade/downgrade widget in either type vertical.; Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.; [DONE] Create a template for pm:Goal.
Other: Adjacent nodes in the left-side lozenge UI can be kind of ambiguous.; Client wants to use the IBIS tool (Sense Atlas) in everyday operations.; It would be handy if active entities could be easily visually differentiated from inactive ones.; Plan projects and resources with the use of the Process Model Ontology.; The UI for adding and connecting adjacents messes up in annoying and data-destructive ways.; The XSLT component kind of sucks.; The issue/position/argument type toggle widget is a vestige from the original 2013 prototype and never actually made any sense.; The template for ibis:Network (skos:ConceptScheme) is really shabby.; There is no upgrade/downgrade path to go from { issue ↔ argument ↔ goal ↔ target } or { position ↔ task }.; There is still no capability to use ibis:replaces effectively.; [RESOLVED] For writing to the graph, the IBIS tool requires a "focus" node with which to associate new entries. This is associated with a state object, which is in turn associated with the current user.; [RESOLVED] The editing widgets show up even if there is no current logged-in user.; [RESOLVED] The unlink button appears to be broken (again?) for ibis:suggested-by.

Should the focus button also navigate to the network overview?

Other: If we navigate to the overview of a network which is not in focus, how do we take focus?; No, stay where you are. Use a dedicated "Go" button to navigate.; Yes, always show the focus button and make clicking on it a no-op.; Yes, focusing the network should also go to it.

Solve for mobile.

Other: The display is still goofed on a mobile screen.

SPARQL should also be selecting the default graph with a `GRAPH ?g` construct, but the quad store isn't doing it.

Other: Create (and run) a SPARQL script that does the appropriate surgery to add the forward-links transform to the transform queue.; Fix the bug in RDF::LMDB that is preventing the default graph from being selected.

Survey other templating languages.

Other: Almost all Web templating languages allow for broken markup (a major reason we're still using XSLT is because it doesn't).; The XSLT component kind of sucks.

Switching the focus without being conspicuous about it could cause the user to make a mistake.

Other: Always focus the network when you select it or create a new one.

T

The template for ibis:Network (skos:ConceptScheme) is really shabby.

Other: Improve the UI for ibis:Network and skos:ConceptScheme.; Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.; The front page of senseatlas.net is also super janky.

There appears to be a general issue of getting nodes into networks.

Other: Make a toggle for whether the node should be included.; What about getting nodes out of networks? How do you remove an IBIS entity (SKOS concept) from a network (concept scheme)?

There are only two choices: IBIS network and SKOS concept scheme.

Other: Use radio buttons to select between IBIS network and SKOS concept scheme.

There is a bigger target to click with radio buttons.

Other: Dropdowns hide the available options behind a click.; Use radio buttons to select between IBIS network and SKOS concept scheme.

There is likewise the persistent threat that one of the browser vendors (say Chrome) removes support for XSLT 1.0.

Other: Despite being standard, reliable, and fast to execute, and built into every browser, XSLT 1.0 in particular is really clunky to work with.; If one of the browser vendors removed support for XSLT 1.0, we could move XSLT processing to the server side.

There is no upgrade/downgrade path to go from { issue ↔ argument ↔ goal ↔ target } or { position ↔ task }.

Other: Could we establish that an argument is an argument purely by inference?; Note that an entity can be an ibis:Argument and an pm:Goal/Task at the same time.; Replace the type toggle widget with an upgrade/downgrade widget in either type vertical.; Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.

There is still no capability to use ibis:replaces effectively.

Other: Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.

There will be an ambiguity with the intent of typing in a value not found in the autofill: are you renaming the current network or making a new one?

Other: Implement the network switcher as a an autofilling text box.

There will need to be some kind of representation of foaf:Person (who can be attached to an authentication principal).

Other: How do you get the users into the system?

Try messing around with SaxonJS?

Other: Despite being standard, reliable, and fast to execute, and built into every browser, XSLT 1.0 in particular is really clunky to work with.; Part of the reason for client-side template processing is to shift the cost of computing templates to the user, who (usually) has ample such resources to spare.
See Also

U

The UI for adding and connecting adjacents messes up in annoying and data-destructive ways.

Other

The user's intent is always clear.

Other: [ADOPTED] Only focus the new network if the user explicitly signals to do so (i.e., through a dedicated button).

Unlike IBIS which is half a century old, the PM ontology has never been road-tested, and will likely require several iterations to get right.

Other: Plan projects and resources with the use of the Process Model Ontology.; Rough out the new classes and try loading them with instance data; take notes for what can be improved.; [DONE] Put Sense Atlas online so the client can observe its development.

Update the faux-monad Intertwingler::Representation::Nokogiri to reference a subclass of Nokogiri that has an accessor for the RDF.

Other: It is wasteful to extract the graph data out of the RDFa in the document, throw it away, and then extract it again, as it moves through the transformation pipeline.; Rescanning the document (which we assume to be altered from the previous transform) may be the only reliable way to ensure that it matches the content.

Use a dropdown to select between IBIS network and SKOS concept scheme like in the initialization phase.

Other: Dropdowns are easy to implement.; Dropdowns hide the available options behind a click.; How do we select the type of network to be created?

Use radio buttons to select between IBIS network and SKOS concept scheme.

Other: How do we select the type of network to be created?; Radio buttons are just as easy to implement (over a small, fixed set of elements) as dropdowns.; There are only two choices: IBIS network and SKOS concept scheme.; There is a bigger target to click with radio buttons.

Use the import precedence native to XSLT.

Has Narrower: Modify the transform that inserts XSLT processing instructions to match against asserted types (or specific resources).
Other: Dispatching templates on the server side would afford getting rid of that clunky and ridiculous client-side dispatcher.; Getting rid of the clunky client-side dispatcher would also get rid of that giant RDF/XML file containing all the vocabs, which isn't used for anything else.; How do we match templates to resources?; The way the template "inheritance" currently works is extremely messy.

Use the saturation to differentiate active from inactive entities.

Other: It would be handy if active entities could be easily visually differentiated from inactive ones.

W

The way the template "inheritance" currently works is extremely messy.

Other: The XSLT component kind of sucks.; Use the import precedence native to XSLT.

What about getting nodes out of networks? How do you remove an IBIS entity (SKOS concept) from a network (concept scheme)?

Other: There appears to be a general issue of getting nodes into networks.

What about the ability to rename a network?

Has Broader: [RESOLVED] Client wants the ability to create multiple IBIS networks.
Other: Make a field in the UI for (re)setting the network's name.; Make some UI that affords creating a new IBIS network (or SKOS concept scheme) from an entity or network overview.

What about the IBIS entity in context? Does it get ported to the other network?

Other: Automatically import the node; people can remove it later.; Make a toggle for whether the node should be included.; Make some UI that affords creating a new IBIS network (or SKOS concept scheme) from an entity or network overview.; Make some UI that affords switching IBIS networks.

When a node is in more than one issue network, the visualization shows the amalgamation of all the networks.

Other: Only show the nodes in an unfocused network that are immediately adjacent to the ones in the focused network (and do so at half opacity), like is already done with skos:Concept.

Why not just attach a new entity to all the issue networks its neighbour is currently in?

Other: The focus is confusing but needed to disambiguate which issue network to attach a new entity to.

X

The XSLT component kind of sucks.

Other: Despite being standard, reliable, and fast to execute, and built into every browser, XSLT 1.0 in particular is really clunky to work with.; Ship a front end with interfaces for IBIS, PM, and a rudimentary FOAF/ORG editor.; Survey other templating languages.; The way the template "inheritance" currently works is extremely messy.

Y

Yes, always show the focus button and make clicking on it a no-op.

Other: Do we show the UI to focus the network if it's already focused?; Should the focus button also navigate to the network overview?

Yes, focusing the network should also go to it.

Other: Should the focus button also navigate to the network overview?

A

Add a log in/out widget to the footer (email and "go" button to log in, logout button to log out).

Adjacent nodes in the left-side lozenge UI can be kind of ambiguous.

Almost all Web templating languages allow for broken markup (a major reason we're still using XSLT is because it doesn't).

Alter the template so that the editing widgets do not show up unless there is a registered user detected.

Always focus the network when you select it or create a new one.

An autofilled text box has an unlimited capacity and is easier to deal with than a dropdown when there are lots of entities.

An autofilled text box will take up less space.

Autofilled text boxes are implemented inconsistently across browsers.

Automatically import the node; people can remove it later.

Automatically importing the entity may make sense for creating new networks but could make a mess with existing ones.

[ADOPTED] Only focus the new network if the user explicitly signals to do so (i.e., through a dedicated button).

B

The backlinks transform is actually extremely goofed and contributing to slow page delivery, which will only get worse if it has to parse more forward links too.

C

Changing the focus isn't really that big a deal and it can always be changed later.

Client wants to use the IBIS tool (Sense Atlas) in everyday operations.

Could we establish that an argument is an argument purely by inference?

Create (and run) a SPARQL script that does the appropriate surgery to add the forward-links transform to the transform queue.

Create a "forward links" transform to attach residual links to opaque (e.g. static) documents, analogous to the backlinks transform.

Create a keyboard event handler that submits the form for all forms that only contain a datetime-local widget (as a non-hidden control).

Create a new <datalist> for autofilling foaf:Agent entities.

Create a one-off front page that promotes Sense Atlas and explains to people what they're looking at.

Create a pop-up "jump to entity"/"create new unconnected entity" interface.

Create a template for pm:Target.

Create a template for pm:Task.

Create ibis:endorsed-by relations widget, i.e. the ability to "like" an entity.

D

Debugging XSLT 1.0 in particular is brutal, due to years of neglect from the browser vendors.

Despite being standard, reliable, and fast to execute, and built into every browser, XSLT 1.0 in particular is really clunky to work with.

Devise a radial clumping algorithm for determining the θ of each node.

Dispatching templates on the server side would afford getting rid of that clunky and ridiculous client-side dispatcher.

Do we always want to focus the new network?

Do we show the UI to focus the network if it's already focused?

Do we want to be able to ascribe a value to the goal specifically, rather than the target—which has a budget?

Double-check the behaviour of datetime-local in Chrome and Safari.

Dropdowns are easy to implement.

Dropdowns can get huge and unwieldy.

Dropdowns hide the available options behind a click.

The datetime-local input type does not seem to elicit form submission with the enter key like a text box does (in Firefox).

The display is still goofed on a mobile screen.

[DONE] Create a template for pm:Goal.

[DONE] Put Sense Atlas online so the client can observe its development.

`Date.prototype.toISOString()` encodes the time zone offset as Zulu (UTC) no matter what it actually is.

E

Even once caching is implemented, a full server round-trip for the whole page with every POST is costly and often unnecessary.

Expand the script that manages the adjacent entity controls so that it also attaches to the "agent" controls.

Extra buttons are potentially clutter.

F

Fix the backlinks transform so that it only produces non-redundant links, and only for the subject document and any fragments thereof.

Fix the bug in RDF::LMDB that is preventing the default graph from being selected.

From the entity UI, there is no mechanism for adding a new entity that is not attached to the current entity.

The focus is confusing but needed to disambiguate which issue network to attach a new entity to.

The front page of senseatlas.net is also super janky.

G

Getting rid of the clunky client-side dispatcher would also get rid of that giant RDF/XML file containing all the vocabs, which isn't used for anything else.

H

How do we account for the dynamic elements on the page from the graph?

How do we match templates to resources?

How do we select the type of network to be created?

How do you get the users into the system?

I

If an entity is not immediately connected to the current one, you have to hunt through the visualization or go back to the scheme view to find it.

If every RDF class (and individual resource) that mattered could be assigned its own XSLT transform, then we could have sane defaults for unspecified classes.

If one of the browser vendors removed support for XSLT 1.0, we could move XSLT processing to the server side.

If we navigate to the overview of a network which is not in focus, how do we take focus?

Implement the network switcher as a an autofilling text box.

Implement the network switcher as a dropdown.

Importing nodes from one network to another is a pain in the ass.

Improve the UI for ibis:Network and skos:ConceptScheme.

Is the focus a property of the graph, or a property of the user state?

It is currently difficult to answer the question, when looking at an issue network, "what still needs to be done?"

It is wasteful to extract the graph data out of the RDFa in the document, throw it away, and then extract it again, as it moves through the transformation pipeline.

It turns out that (at least in Firefox) the `datetime-local` input does not let you set a valid ISO8601/W3CDTF time stamp, only a truncated one.

It will often be quicker to bulk-import a bunch of nodes and then prune out any extraneous ones.

It would be handy if active entities could be easily visually differentiated from inactive ones.

It would be useful, from the keyboard, to be able to jump to an entity you know is in the graph but not immediately connected.

The issue/position/argument type toggle widget is a vestige from the original 2013 prototype and never actually made any sense.

K

Keep the focus button and disable it, and change the text to say "Focused".