7.9 KiB
7.9 KiB
tags:: #zotero title:: @SOSYM-24-00004734_Proof_hi item-type:: document original-title:: SOSYM-24-00004734_Proof_hi language:: en links:: Local library, Web library
-
Attachments
- PDF {{zotero-imported-file RP5CFRYG, "SOSYM-24-00004734_Proof_hi.pdf"}}
-
Notes
-
Annotazioni
(10/10/2024, 14:54:36)
SOSYM-24-00004734_Proof_hi
- “chemaless graph datasets” #5fb236
-
- “Design Science effort” #5fb236
* *
- “KG development and integration method” #5fb236
* *
- “students who tend to perceive symbolic AI as a niche of questionable relevance” #5fb236
* *
- “"citizen knowledge acquisition".” #a28ae5
* *
- ““low-code knowledge graph building”” #a28ae5
* *
- “reate KG structures” #a28ae5
* *
- “RDF/OWL jargon or the ontology-first experience of a tool like Protégé” #5fb236
* *
- “This paper's proposal is a DSML (and associated modeling method deployed as an ADOxx modeling tool) that obscures as much as possible the formal details of knowledge representation standards such as RDF/S and OWL” #5fb236
* *
- “but the focus is still on the schema layer and not on the creation of arbitrary graph structure” #5fb236
* *
- “Section 2 provides extensive information about the problem identification objectives definition. Section 3 discusses design decisions and implementation details. Section 4 presents two application use-cases, Section 5 discusses a series of evaluations. Section 6 comments on related works, and Section 7 concludes our work with a SWOT analysis and outlook” #5fb236
* *
- “Moreover, the current visual tools are limited to saving the created schemas in some basic format and do not care about specialized usage scenarios such as those mentioned above, that may require interoperability.” #5fb236
* *
- “Exposing such exemplars to immediate consumption (the SEO and the GraphRAG use cases described above, but also the cognitive acquisition for novice students) is therefore prioritized.” #5fb236
* *
- “roblem Statement and Objectives Definition” #ffd400
*The section needs improvements. It does not clearly present the problem, it is verbose and should be more focused by clearly presenting the problem, e.g., by discussing explanatory cases and examples. *
- “We aim for a Pareto-driven approach where 80% of the user needs are served by 20% of the RDF-based specifications captured in a DSML-based modeling method” #ffd400
*What do you mean with "served"? *
- “eveloped here as a Design Science artifact” #ffd400
* *
- “weakly structured interviews were used to collect pain points about the tooling they can offer to students and the learning objective affordances of such tooling.” #5fb236
* *
- “GraphRAG scenario was adopted from recent technical propositions available in the literature” #5fb236
* *
- “nd also from KG platform vendors” #5fb236
* *
- “graphical note-taking tools have established this as a popular practice of structuring ideas and was the originating motivation for repurposing here the practice of DSML engineering;” #ffd400
*Why are they not enough to support the specification of concepts and relationships among them (thus box and lines?) *
- “KG building is done by semantic technology experts in specialized tools that first require familiarity with standards such as OWL and RDF, if not with underlying formal logic” #a28ae5
* *
- “TBOX” #ffd400
*Still on the readability of the paper. The work mentions acronyms or concepts, assuming that the reader is aware of them. The authors should revise the paper by ensuring that all the mentioned concepts / technologies are properly introduced especially for the readers that are not experts of the considered domain. A related minor issue is that references re not always given the first time when a given technology is mentioned (e.g. see Langchain, it is mentioned at page 10 the first time, whereas the reference is given at page 17). *
- “usability requirements” #ffd400
*How have you elicited such requirements? It is important to discuss how you have elicited them, e.g., if they come from the interview you have done with stakeholders, or if they come only by the experience of the authors. *
- “schema can be postpone” #5fb236
* *
- “different visual loads:” #5fb236
* *
- “RDF/OWL jargon should be avoided wherever possible,” #5fb236
* *
- “LLM services” #ffd400
*What do you mean? *
- “model-driven editing layer over a standards-compliant KG platform” #5fb236
* *
- “Langchain” #ffd400
* *
- “We decided to add less abstract classes because ADOxx as a metamodeling environment allows us to enforce a series of relation constraints” #5fb236
* *
- “Prefix changing” #ffd400
*It's not explicit the connection between "Prefix changing" and "URI generation" with the requirements given in Section 2. *
- “coupling RAG with RDF” #5fb236
* *
- “AdoScripts in the modeling tool take care of collecting the natural language query and passing it to a Python proxy script that performs the actual KG and LLM access” #5fb236
* *
- “This serves to obtain a subgraph of entities and relations connected to the subject of the user query.” #5fb236
* *
- “Figure 6 presents the flow of the LLM integration through LangChain, emphasizing on the interactions with the KG and the extraction of a subgraph by navigating radial relationships starting from the subject node;” #5fb236
* *
- “the” #ff6666
* *
- “Step 5.” #ffd400
*A concrete example with the variable prompt and results actualized is necessary. *
- “The modeling tool can serve to both building ontologies and graph data as shown in Figure 8.” #5fb236
* *
- “GRAPHxx capabilities were employed in this demo case for designing and querying a KG that can be rolled out on a real world scenario of analyzing interactions between business actors, employees and other constituting elements.” #5fb236
* *
- “We used ADOxx's scripting language to automatically populate diagrams in GRAPHxx.” #5fb236
* *
- “4500 concepts per diagram, also included only prefixes, URIs and labels for ThingIdentifier nodes and RelatedTo connectors” #5fb236
* *
- “conceptual schemas expressed as UML diagrams to graph equivalents.” #5fb236
* *
- “RDF schema generations directly from an intuitive diagramming environment that empowers users to think in free networks of associations close to the RDF data model” #5fb236
* *
- “BPMN2KG acts in a similar way, but does not rely on the BPMN standard, since it provides a visual layer bridging the RDF formalisms with ADOxx meta-metamodeling capabilities.” #ffd400
*WHat are the limitations of tools like BPMN2KG with respect to the requirements presented in Sec. 2? It is necessary to discuss existing works with respect to a set of elicited requirements and then show what are the challenges that still need to be addressed. *
- “SWOT” #5fb236
* *
- “Strengths” #2ea8e5
* *
- “Opportunities” #2ea8e5
* *
- “Weaknesses” #2ea8e5
* *
- “Threats” #2ea8e5
* *