Dendron workspace sync

djradon · djradon · commit 69de169140c1 · 2024-05-01T16:22:35.000-07:00
## Synced vaults:
- public-notes

Dendron version: 0.124.0
Hostname: g11
diff --git a/ar.agents-and-the-semantic-web.md b/ar.agents-and-the-semantic-web.md
@@ -0,0 +1,34 @@
+---
+id: 878kg6rkvxkaldjauswgqk5
+title: Agents and the Semantic Web
+desc: ''
+updated: 1712599443140
+created: 1712599253213
+---
+
+- url: https://www.nku.edu/~foxr/CSC625/NOTES/agents.ppt
+
+## Types of Environments
+
+* Accessible vs. inaccessible:  agent’s sensors give it access to the complete state of the environment at each point in time
+* Deterministic vs. non-deterministic:  next state of the environment is completely determined by the current state and the action executed by the agent
+* Episodic vs. non-episodic:  agent’s experience is divided into atomic episodes, each episode consisting of a perception-action pair where the action is a single action/event
+* Static vs. dynamic:  environment is unchanged during the agent’s deliberation of an action
+* Discrete vs. continuous:  limited number of distinct, clearly defined percepts and actions
+* Single agent:  the agent works in isolation (no other agents around)
+
+## Types of Agents
+
+Reflex Agent
+simplest form,  the agent merely reacts to its environment – no memory, no internal states, no planning
+
+State-based Agent
+the next step up is an agent that keeps track of its current (and possibly previous) state(s), this can help with planning and understanding
+
+Goal-oriented Agent
+this agent has the ability to plan out a sequence of states to achieve in order – planning might be based on a table-lookup approach or something more elaborate using a search mechanism and available planning knowledge
+
+Utility-based Agent
+the agent has the ability to determine the usefulness of a plan step toward achieving its goals so that it can achieve the goals in a more optimal fashion, and possibly have better final results for goal
+
+![](/assets/images/2024-04-08-11-04-02.png)
diff --git a/ar.an-initial-comparison-of-selected-agent-based-simulation-tools-in-the-context-of-industrial-health-and-safety-management.md b/ar.an-initial-comparison-of-selected-agent-based-simulation-tools-in-the-context-of-industrial-health-and-safety-management.md
@@ -0,0 +1,16 @@
+---
+id: 51aty4mlflj5k7lj0eogjlj
+title: >-
+  An Initial Comparison of Selected Agent Based Simulation Tools in the Context
+  of Industrial Health and Safety Management
+desc: ''
+updated: 1712679588717
+created: 1712679510444
+---
+
+- https://dl.acm.org/doi/fullHtml/10.1145/3543712.3543745
+- comparands: [[prdct.netlogo]] [[prdct.gama]] [[prdct.repast-simphony]]
+
+## Summary
+
+- NetLogo and GAMA appear to be more suitable than Repast. The latter - although very versatile - requires a high amount a programming skills. GAMA's primary strength on the other hand is the heavy focus on GIS data involvement, while NetLogo is not only very intuitive in learning but offers also a large number of features.
diff --git a/ar.an-ontology-for-supporting-the-evolution-of-virtual-reality-scenarios.md b/ar.an-ontology-for-supporting-the-evolution-of-virtual-reality-scenarios.md
@@ -0,0 +1,32 @@
+---
+id: sogw5ltzq6qgctlvh2xw4yp
+title: An Ontology for Supporting the Evolution of Virtual Reality Scenarios
+desc: ''
+updated: 1712858924913
+created: 1712858553876
+---
+
+- https://cgi.csc.liv.ac.uk/~valli/OWLED2015/OWLED_2015_paper_5.pdf
+- related: [[prdct.cojack]]
+
+
+## Abstract
+
+Serious games with 3D interfaces are Virtual Reality (VR) systems that are becoming common for the training of military and emergency teams. A platform for the development of serious games should allow the addition of semantics to the virtual environment and the modularization of the artificial in- telligence controlling the behaviors of non-playing characters in order to support a productive end-user development environment. In this paper, we report the on- tology design activity performed in the context of the PRESTO project aiming to realize a conceptual model able to abstract the developers from the graphi- cal and geometrical properties of the entities in the virtual reality, as well as the behavioral models associated to the non-playing characters.
+
+## Highlights
+
+- we focus on the experience of using Semantic Web techniques, and in particular lightweight ontologies, for the high level description of the artificial entities (including characters) and their behaviors in gaming in order to uncouple the descrip- tion of scenarios performed by the trainers from their physical implementation in charge to the developers. Differently from a number of works in literature that often uses on- tologies for a detailed description of the geometrical properties of space and objects, the focus of our work is on the description of the entities of a VR scenario from the cogni- tive point of views of the trainers and the developers alike, in a way that is semantically well founded and independent of a specific game or scenario [1], and with the goal of fostering clarity, reuse, and mutual understanding.
+
+- The open problems addressed by this project may be summarized as follows:
+1. the perception of the virtual environment by an artificial character and the execution
+of its models and procedures must be able to adapt to the context, to its history
+and status (fatigue, emotions, intake of stimulants such as caffeine or depressants
+such as alcohol) and must maintain a level of variability (i.e. in the accuracy of the
+vision, the rate of reaction, in the choices among alternatives) such that the behavior
+is plausible but not trivially predictable;
+2. the representation of procedures and patterns of behavior must be independent of
+one specific usage scenario and accessible to training specialists (i.e. industrial
+safety or civil protection) rather than just a computer, in an environment facilitating
+the definition and configuration of training scenarios by such specialists.
+
diff --git a/ar.applied-temporal-rdf-efficient-temporal-querying-of-rdf-data-with-sparql.md b/ar.applied-temporal-rdf-efficient-temporal-querying-of-rdf-data-with-sparql.md
@@ -0,0 +1,41 @@
+---
+id: 8q3wkicfurf0iva76qwio2k
+title: Applied Temporal Rdf Efficient Temporal Querying of Rdf Data with Sparql
+desc: >-
+  Each time interval is represented by exactly one named graph, where all
+  triples belonging to this graph share the same validity period.
+updated: 1713376324244
+created: 1712869321664
+---
+
+- https://drive.google.com/open?id=1-V3E93i9gqdOEHzVMyiHJMTGjahh62GU&usp=drive_fs
+
+## Abstract
+
+Many applications operate on time-sensitive data. Some of these data are only valid for certain intervals (e.g., job-assignments, ver- sions of software code), others describe temporal events that happened at certain points in time (e.g., a person’s birthday). Until recently, the only way to incorporate time into Semantic Web models was as a data type property. Temporal RDF, however, considers time as an additional dimension in data preserving the semantics of time. 
+
+In this paper we present a syntax and storage format based on named graphs to express temporal RDF. Given the restriction to preexisting RDF-syntax, our approach can perform any temporal query using stan- dard SPARQL syntax only. For convenience, we introduce a shorthand format called τ -SPARQL for temporal queries and show how τ -SPARQL queries can be translated to standard SPARQL. Additionally, we show that, depending on the underlying data’s nature, the temporal RDF ap- proach vastly reduces the number of triples by eliminating redundancies resulting in an increased performance for processing and querying. Last but not least, we introduce a new indexing approach method that can significantly reduce the time needed to execute time point queries (e.g., what happened on January 1st).
+
+## Highlights
+
+### Related Approaches
+
+#### Temporal Extensions
+
+- Welty and Fikes [6], Kim et al. [7] and the tOWL [8] project aim at introducing temporal entities into OWL.
+
+#### Time Encoded in the Data Model
+
+- lose the semantics of time
+- temporal properties can't be attached to relations
+
+#### Graph Versions and Version Management Systems
+
+- SemVersion uses its own data model that contains the user’s ontology and its evolution. Our proposi- tion is not to introduce a new data model, but, storing the elements of the users’ data model inside different named graphs according to their temporal context.
+
+### Proposed Temporal Syntax
+
+- As in most of the approaches dealing with temporal entities, we model time as a 1-dimensional discrete value (i.e. no branching time)
+- we extended OWL- Time with a new date format type called IntegerTime to express non-calendaric time representations such as version numbers.
+- We refer to a set of temporally related named graphs as a temporal graph. Each time interval is represented by exactly one named graph, where all triples belonging to this graph share the same validity period.
+  
diff --git a/ar.assessment-and-benchmarking-of-spatially-enabled-rdf-stores-for-the-next-generation-of-spatial-data-infrastructure.md b/ar.assessment-and-benchmarking-of-spatially-enabled-rdf-stores-for-the-next-generation-of-spatial-data-infrastructure.md
@@ -0,0 +1,15 @@
+---
+id: l8mxuujoo2p7ydvttea8v4n
+title: >-
+  Assessment and Benchmarking of Spatially Enabled Rdf Stores for the Next
+  Generation of Spatial Data Infrastructure
+desc: ''
+updated: 1714508988026
+created: 1714498601292
+---
+
+- https://www.mdpi.com/2220-9964/8/7/310
+
+## Abstract
+
+Geospatial information is indispensable for various real-world applications and is thus a prominent part of today’s data science landscape. Geospatial data is primarily maintained and disseminated through spatial data infrastructures (SDIs). However, current SDIs are facing challenges in terms of data integration and semantic heterogeneity because of their partially siloed data organization. In this context, linked data provides a promising means to unravel these challenges, and it is seen as one of the key factors moving SDIs toward the next generation. In this study, we investigate the technical environment of the support for geospatial linked data by assessing and benchmarking some popular and well-known spatially enabled RDF stores (RDF4J, GeoSPARQL-Jena, Virtuoso, Stardog, and GraphDB), with a focus on GeoSPARQL compliance and query performance. The tests were performed in two different scenarios. In the first scenario, geospatial data forms a part of a large-scale data infrastructure and is integrated with other types of data. In this scenario, we used ICOS Carbon Portal’s metadata—a real-world Earth Science linked data infrastructure. In the second scenario, we benchmarked the RDF stores in a dedicated SDI environment that contains purely geospatial data, and we used geospatial datasets with both crowd-sourced and authoritative data (the same test data used in a previous benchmark study, the Geographica benchmark). The assessment and benchmarking results demonstrate that the GeoSPARQL compliance of the RDF stores has encouragingly advanced in the last several years. The query performances are generally acceptable, and spatial indexing is imperative when handling a large number of geospatial objects. Nevertheless, query correctness remains a challenge for cross-database interoperability. In conclusion, the results indicate that the spatial capacity of the RDF stores has become increasingly mature, which could benefit the development of future SDIs.
diff --git a/ar.classifying-processes.md b/ar.classifying-processes.md
@@ -0,0 +1,28 @@
+---
+id: 03g5n90pq0fbkoqz7yi9l2e
+title: Classifying Processes
+desc: ''
+updated: 1713329410221
+created: 1713327824966
+---
+
+- https://ontology.buffalo.edu/smith/articles/Classifying_Processes.pdf
+- topics: [[t.km.ontology]] [[prdct.basic-formal-ontology]]
+- mentions: [[prdct.information-artifact-ontology]]
+
+## Highlights
+
+- Processes, in particular, cannot change on the four-dimensionalist view, because processes are changes  ^wv5719t8809u
+- Continuants may change not only through change in qualities but also in other ways. For example they may gain and lose parts over time, as for example when you gain and lose cells from your body. To address such changes, BFO’s instance-level continuant parthood relation is indexed by time. The counterpart relation on the side of occurrents, in contrast, holds always in a non-indexed way.
+
+
+### Processes as Dependent Entities
+
+- Processes themselves stand to the independent continuants which are their participants in a relation that is analogous to that in which qualities stand to the independent continuants which are their bearers. In both cases we have to deal with the relation of what BFO calls specific dependence.
+
+- Something which processes may share is a **process profile** -- each contains an instantiation of multiple process profile universals.
+
+## Conclusion
+
+- One important next step will deal with the ways in which such classification is complicated by the fact that processes are embedded within a series of larger process wholes, each nested within yet larger process wholes. 
+- Human physiological processes, too, are embedded within series of larger wholes in this way. When studying the heart, for example, physiologists may investigate processes within the interior of the left ventricle, interactions between the left ventricle and other parts of the cardiovascular system, interactions between this system and other bodily systems, and so on. Physiologists may be interested in the processes involving multiple organisms; for example they may be interested in some given organism as part of one or other larger whole which includes some population of organisms of a relevant similar type (all humans, all human babies of a given birth weight, all athletes, and so on). Normal processes are defined for this larger population (as normal qualities were defined above), and deviations from this norm are defined for the single organism relative thereto.
diff --git a/ar.reddit.net-compatible-scripting-languages-for-users-to-write-their-own-scripts-to-query-manipulate-objects-properties-in-the-app.md b/ar.reddit.net-compatible-scripting-languages-for-users-to-write-their-own-scripts-to-query-manipulate-objects-properties-in-the-app.md
@@ -0,0 +1,12 @@
+---
+id: 64on4c24sxn4966e2azjtf8
+title: >-
+  Net Compatible Scripting Languages for Users to Write Their Own Scripts to
+  Query Manipulate Objects Properties in the App
+desc: ''
+updated: 1712291308572
+created: 1712291301840
+---
+
+- url: https://www.reddit.com/r/csharp/comments/whkweb/netcompatible_scripting_languages_for_users_to/
+- 
diff --git a/ar.the-acimov-methodology-agile-and-continuous-integration-for-modular-ontologies-and-vocabularies.md b/ar.the-acimov-methodology-agile-and-continuous-integration-for-modular-ontologies-and-vocabularies.md
@@ -0,0 +1,39 @@
+---
+id: qv2k0ar4j0ef1meop2bzigz
+title: >-
+  The Acimov Methodology Agile and Continuous Integration for Modular Ontologies
+  and Vocabularies
+desc: ''
+updated: 1712849614451
+created: 1712783360619
+---
+
+- https://www.emse.fr/~zimmermann/Papers/mk2023.pdf
+- topics: [[t.km.ontology.modular]]
+
+## Abstract
+
+- This work describes the Agile and Continuous Integration for Modular Ontologies and Vocabularies (ACIMOV) ontology engineering methodology for developing ontologies and vocabularies. ACIMOV extends the SAMOD agile methodology to (1) ensure alignment to selected reference ontologies; (2) plan module development based on dependencies; (3) define ontology modules that can be specialized for specific domains; (4) empower active collaboration among ontology engineers and domain experts; (5) enable application developers to select views of the ontology for their specific domain and use case. ACIMOV adopts the standard git-based approach for coding, leveraging agility and DevOps principles. It has been designed to be operationalized using collaborative software development platforms such as Github or Gitlab, and tooled with continuous integration and continuous deployment workflows (CI/CD workflows) that run syntactic and semantic checks on the repository, specialize modules, generate and publish the ontology documentation.
+
+
+## Highlights
+
+### Agile ontology engineering methods
+
+Many ontology engineering methodologies have been proposed over time, including METHONTOLOGY [ 9], On-To-Knowledge [ 10], DILIGENT [ 11 ], the “Ontology Development 101” [ 12], NeOn [ 13]. Some directly transpose software engineering methodologies, for example UPON Lite [ 14] is based on Rational Unified Process. The LOT methodology [ 15] adopts a V-model approach with conditional feedback at upstream development stages. Other early methods pro- posed to rely and align with existing ontologies to bootstrap new ontologies as in SENSUS [16 ]. More recently, methodologies are inspired by the principles of Agile software engineering, which promote collaboration between developers and stakeholders by producing regular updates of the product1. Among these methods, AMOD [ 17 ] and CD-OAM [ 18 ] are based on SCRUM. AMOD is the first method that describes the cycle of ontology development in a SCRUM sprint. CD-OAM enriches AMOD by describing the management the ontology commitment user community. XPOD [ 19 ] and eXtreme ontology method [ 20] are based on eXtreme Programming. The Lean Ontology Development (LOD) [21] is inspired by the Lean approach: Build-Measure- Learn. SAMOD [ 1 ] is revisiting the motivating scenarios and competency questions of Uschold and Gruninger [22], additionally considering ontology modules and test-driven development.
+
+### Git and CI/CD for ontology engineering
+
+Before the democratization of these frameworks, a few preliminary approaches such as VoCol [ 23 ] or OnToology [ 24] were proposed in the ontology engineering community using Github applications2. [[prdct.ontology-development-kit]] (ODK) [ 25] uses Travis CI to run workflows with the ROBOT tool [ 26 ] developed by the Open Biological and Biomedical Ontologies (OBO) community. CI/CD pipelines are reported for the publication of different ontologies, such as the Financial Industry Business Ontology (FIBO) in [ 27], the International Data Spaces Information Model (IDSA) in [ 28], and the CASE Cyber Ontology3. Specific Github actions are available on the Github marketplace for running RDFLint4, validating RDF syntaxes5,6, or validating RDF files against SHACL shapes7 or ShEx [29].
+
+## Methodology
+
+Step 1 Collect requirements and identify reference ontologies.
+Step 2 Review meeting (an event)
+Step 3 Select relevant modules from reference ontologies
+Step 4 Manage modelet backlog
+Step 5 Modelet development meeting (an event)
+Step 6 Develop and test modelets
+Step 7 Integrate modelet and release ontology artifacts
+
+
diff --git a/t.lit.perspective.first-person.md b/t.lit.perspective.first-person.md
@@ -0,0 +1,9 @@
+---
+id: sjv7zxwbxqr6oh0j3osvmly
+title: First Person
+desc: ''
+updated: 1698948617994
+created: 1698948617994
+---
+
+- The "me" perspective. Common in [[t.humanities.literature]] but uncommon in [[c.software.game-framework.interactivefiction]]
diff --git a/t.lit.perspective.second-person.md b/t.lit.perspective.second-person.md
@@ -0,0 +1,47 @@
+---
+id: i5rquecajlnh0llcegl22qz
+title: Second Person
+desc: ''
+updated: 1698947779638
+created: 1698947779638
+---
+
+- addresses the audience, like "Choose Your Own Adventure", [[c.software.game-framework.interactivefiction]] or most text adventures
+- "who is the you in a second person point of view story? There are actually a few different possibilities:
+
+    The narrator is addressing the reader
+
+    The narrator is addressing themselves
+
+    The narrator is addressing another character"
+
+## Pros
+
+-   In a second person narrative, the writer casts the reader as the main character. **The reader is placed at the very centre of the story**, which makes for an intense and immersive reader experience.
+    
+
+-   This POV can also be used **to reinforce the key themes and ideas of the story**. Perhaps the narrator wants to distance themselves from their own narrative because the topic is difficult to think or talk about. Or perhaps self-talk is central to your narrator's identity.
+    
+
+-   **Second person POV is an exciting challenge for a writer**. And an original and intriguing format for a reader. To avoid putting too much pressure on either party, short stories written in the second person provide a good introduction to this mode of storytelling.
+
+## Cons
+
+-   **It’s not something writers or readers are used to**. It’s rare to come across fiction written in the second person. And – honestly – writers don’t tend to consider it as one of the narrative formats available to them.
+    
+
+-   **Readers don’t always like it**. They may feel uncomfortable or alienated from events when being told by a narrator that they have acted or spoken in ways that feel far removed from their own real life experience.
+    
+
+-   Because readers don’t tend to like second person point of view narratives, **it’s much harder to convince an agent or publisher** that your story has commercial potential.
+    
+
+-   A reader will inevitably question this form of storytelling. So a writer has to convince the reader that the second person point of view is necessary to the narrative. **Very few stories really require it** – so writers simply choose other points of view.
+
+
+## Resources
+
+### Resource Lists
+
+- https://www.aplaceofintent.co.uk/blog/6-examples-and-excerpts-of-second-person-point-of-view-in-fiction
+
diff --git a/t.lit.perspective.third-person.limited.md b/t.lit.perspective.third-person.limited.md
@@ -0,0 +1,7 @@
+---
+id: neq41632yru85w9mtbevu3v
+title: Third-Person Limited
+desc: ''
+updated: 1698948000939
+created: 1698948000939
+---
diff --git a/t.lit.perspective.third-person.md b/t.lit.perspective.third-person.md
diff --git a/t.lit.perspective.third-person.omniscient.md b/t.lit.perspective.third-person.omniscient.md
