Scenarios | UI | Sender FOAF | Sender Memo | Policy | Receiver FOAF | Reasoner
Challenge |
Justification
Pane |
Lawyer
View |
Other | |
Scenario 1a With GUI and cross-ontology reasoning.
Working Demo (MAY NOT CHANGE FILES, EXCEPT IF THE DEMO STILL WORKS) |
MA GUI MA GUI Dev. Version Select the following parameters for the GUI: |
Sender:Mia Analysa | Document: Fusion->Analysa->RFI->RBGuy |
Policy: MGL_6-172.n3 |
Receiver: Fred Agenti |
|||||
Scenario 1a With GUI and common core ontology
Working Demo (MAY NOT CHANGE FILES, EXCEPT IF THE DEMO STILL WORKS) |
MA GUI MA GUI Dev. Version Select the following parameters for the GUI: |
Sender:Mia Analysa | Document: Fusion->Analysa->RFI->RBGuyCore |
Policy: MGL_6-172_core10.n3 |
Receiver: Fred Agenti |
|||||
Scenario 1a -
Mia to Feddy |
MA
* UI should be able to identify the policy, serve the subjective portions as queries, obtain assertions, and deliver to the reasoner - SAM will attempt to produce this result through the log generator LALANA will help with AIR annotation form K will confirm the subjective portions and assist with user queries * SAM will work on a standard ontology for the envelope describing the transaction - sender, receiver, etc K will determine if there are NIEM tag names available that could be used |
Mia FOAF
* needs better image (K will find) |
Mia Memo w/xmp | MGL 6-172
* Asks if recipient is a "Criminal Justice Agency" - needs to call MGL 66A-1 determine if the recipient matches any of the definitions of CJA and return that result to 6-172. IAN & LALANA will provide a sample to showing how to use air:justifies to pass an assertion back that the justification pane can report PGR will code * Requires CJAs to be pre-approved by "the Board" - needs to see if the particular organization is on an approved list (separate document) PGR can code using log:includes. * Permits CJAs to receive information to the extent of the "scope" granted by "the Board" - needs to be able to bring back a "scope" value from the Board document and make that part of the 6-172 policy pattern SAM has a suggestion for making "scope" a policy and using air:justifies. PGR can code * proofread the patterns against the original text (e.g., (1) our result is not from the rule in para. 2 K can correction assertions (2) why doesn't it also determine compliance with requests from "anyone"?) (PGR - last priority - debug to make "anyone" rules first order) * 2010 version is not complete? |
Feddy FOAF
*Needs to say that authorized purpose is "apprehension" (NOT "prosecution") K will edit |
* See question in policy col. re: expressing why Receiver's org is a CJA | * See question in policy col. re: expressing why Receiver's org is a CJA | The 2009 version of these files do produce output | ||
Scenario 1b With GUI and cross-ontology reasoning.
Working Demo (MAY NOT CHANGE FILES, EXCEPT IF THE DEMO STILL WORKS) |
MA GUI MA GUI Dev. Version Select the following parameters for the GUI: |
Sender:Mia Analysa | Document: Fusion->Analysa->RFI->RBGuy |
Policy: MGL_6-172.n3 |
Receiver: Maury Copp |
|||||
Scenario 1b With GUI and common core ontology.
Working Demo (MAY NOT CHANGE FILES, EXCEPT IF THE DEMO STILL WORKS) |
MA GUI MA GUI Dev. Version Select the following parameters for the GUI: |
Sender:Mia Analysa | Document: Fusion->Analysa->RFI->RBGuyCore |
Policy: MGL_6-172_core10.n3 |
Receiver: Maury Copp |
|||||
Scenario
1b - Mia to Maury |
MA | Mia | Mia Memo
w/xmp |
MGL 6-172
(may require debugging, as there is no output) |
Maury
(might be the problem as it is the only changed item from scenario 1) PGR to debug |
No output
BILL created a version which produces the correct output ONLY of determining the pattern match for MA definition of CJA to MD authorized purpose |
||||
Scenario 2a With GUI and cross-ontology reasoning.
Working Demo (MAY NOT CHANGE FILES, EXCEPT IF THE DEMO STILL WORKS) |
DHS GUI DHS GUI Dev. Version Select the following parameters for the GUI: |
Sender: Fred Agenti |
Document: Fusion->Received->FBI->FeddyToMia |
Policy: 5_USC_552a.n3 |
Receiver:Mia Analysa | |||||
Scenario 2a -
Feddy to Mia |
DHS | Feddy -
* most likely needs editing because PRIVACYACT policy ran with small logs in testing (not using these FOAFS or documents) * needs an image K will find |
Feddy Memo w/xmp
* could need editing because no output could signal not receiving critical rdf K suggests to look for the exact match between property for PII in xmp and property in policy |
Privacy Act (5 USC 552a)
* Requests results from policies not in our system (which models real life where some of these policies don't exist)...could address through an else assertion that says "policy x not found" but they can potentially stack up to a long list... is there another way to aggregate them and make them available? IAN - send an example of filter_property; OSHANI - create a modification to the justification that allows you to aggregate the rule not found; PGR create an else assertion to a triple that says a policy file is missing * debug - last resort to get justification (PGR - all other tasks on this task list should be done ahead of this) |
Mia | No output (2009 or 2010)
PGR to debug - with strong emphasis on FOAF, xmp, and sameas KB (to understand Mia's FOAF in light of policy) |
||||
Scenario 2b -
Working Demo |
||||||||||
Scenario 2b -
Feddy edits policy & runs Feddy to Mia again |
DHS | Feddy | Feddy
Memo w/xmp |
Privacy Act | Mia | * Major activity - still need to decide which mechanism to use as the
platform for this editor and build it out
MIKE S - sees challenges related to all factors affected...will consider and report suggestions |
||||
Scenario 3a With GUI, cross-ontology reasoning and prompting for subjective criteria.
Working Demo (MAY NOT CHANGE FILES, EXCEPT IF THE DEMO STILL WORKS) |
MD GUI MD GUI Dev. Version Select the following parameters for the GUI: |
Sender: Maury Copp |
Document: Fusion->Copp->Replies->ToMia |
Policy: MdCodeComLaw_12_15_01_11.n3 |
Receiver: FL Dept. Law Enforcement |
|||||
Scenario 3a -
Maury to FDLE |
MD | Maury
* needs better image K will find |
Maury
Memo w/xmp |
Md. Code, Com. Law, Ch. 12, Subtitle 15 § 01.11 | FDLE
* debug (SAM's updated version of the log generator - in python - works for Maury to Mia, so this is a problem caused by changing to FDLE) PGR *org not person - use logo as image |
No output
BILL's code correctly determines pattern match of MD definition of CJA and FDLE authorized purpose |
||||
Scenario 3b With GUI and cross-ontology reasoning.
Working Demo (MAY NOT CHANGE FILES, EXCEPT IF THE DEMO STILL WORKS) |
MD GUI MD GUI Dev. Version Select the following parameters for the GUI: |
Sender:Mia Analysa | Document: Fusion->Copp->Replies->ToMia |
Policy: MGL_6-172.n3 Note that you will need to select this policy by hand. |
Receiver: FL Dept. Law Enforcement |
|||||
Scenario 3b With GUI and common core ontology.
Working Demo (MAY NOT CHANGE FILES, EXCEPT IF THE DEMO STILL WORKS) |
MD GUI MD GUI Dev. Version Select the following parameters for the GUI: |
Sender:Mia Analysa | Document: Fusion->Copp->Replies->ToMiaCore |
Policy: MGL_6-172_core10.n3 Note that you will need to select this policy by hand. |
Receiver: FL Dept. Law Enforcement |
|||||
Scenario 3b -
Mia to FDLE |
MD
*UI needs to permit a party to override the policy named in the document's xmp RAFAEL has offered to create the UI upgrade next week (by 3/28) SAM/JIM will supervise as needed |
Mia | Maury
Memo |
MGL 6-172 | FDLE | No means in UI to enter a policy overriding the one in the xmp | ||||
ALL
Scenarios * All files - rule for 2009 vs. 2010 * All files - may only contain tags from own jurisdiction |
* Sometimes have to click more than once (to get image, to get policy
name, to get submitted)?
JIM will fix * (NOTE: see Sam's new "&print_log=true" function for seeing the log generated) |
ensure each | * where/how to put ontology "knowledge base" -- sameas statements so
that a policy using one state's ontology can understand information
from other locations
* whether to map ontologies to the extent possible to NIEM & GFIPM? (or to Sam's proposed "base:") * eliminate the "32, blue, Republican" problem by creating and inserting a standard phrasing with each assertion about what the rule requires (the pattern and the exact citation) K & SAM will work out standard phrasing to explain what the rule requires * each policy needs a final assertion for if nothing fires (empty justification) PGR |
* fix so "short names" always appear
K will send instances OSHANI will fix * Hal requests that FOAF parameters displayed be some more logical short version (e.g., no long/lat) NOT POSSIBLE NOW (because of general purpose nature of Tabulator) |
* fix so "short names" always appear
K will send instances OSHANI will fix * nothing appears (or something illogical appears) under "Rule" K will send instances OSHANI will fix |
DEMO Functionality:
* NEED a web-based output, since all demo recipients are barred from downloading the Firefox extension for tabulator LALANA may be able to implement JIM's masters work (summer UROP?) * Level of effort to make ASK A QUERY (log generator & run) offer/accept more options (summer UROP?) * Other ideas about how to let people play with the function? * Create a video OSHANI will create first with K (week of 3/29?) |