---
title: 'AstroCo: Semantic Astronomy Tool'
url: https://www.emergentmind.com/topics/astroco
type: topic
---

# AstroCo: Semantic Astronomy Tool

Searching arXiv for the relevant paper on AstroCo / AstroConcepts to ground the article in the literature.
AstroCo denotes AstroConcepts, a semantic software tool for astronomical concepts implemented as a Google Chrome plug-in that interrogates the Etymological Dictionary of Astronomy and Astrophysics developed at Paris Observatory. Its core function is to provide in-context definitions of astronomical terms present on Web pages: when a concept is selected, a pop-up window displays the definition of the available English or French term. The tool was introduced as a semantic access layer for astronomy terminology on the Web and was explicitly framed as potentially useful for implementation in Virtual Observatory services [1206.0595].

## 1. Definition and scope

AstroCo was created to address a specific terminological problem: astronomical concepts on the Web are scattered among many partial references, including printed dictionaries, encyclopedias, and web pages, which are neither exhaustive nor regularly updated. In this setting, users must jump from one site to another to look up definitions and cannot query a unified, semantic source of up-to-date concepts [1206.0595].

The software is tightly coupled to the Etymological Dictionary of Astronomy and Astrophysics, described as a MySQL/PHP interactive database maintained at Paris Observatory. That dictionary already holds approximately 10,000 vetted English entries, with French and Persian equivalents, plus full etymologies. AstroCo extends that resource into a browsing-time lookup system, making it possible to access definitions immediately and in context without leaving the current page [1206.0595].

This suggests that AstroCo is best understood not as a standalone lexicon, but as an interface layer over a curated lexical and semantic backend. A plausible implication is that its significance lies less in lexical coverage alone than in the coupling of authoritative terminology with lightweight semantic delivery.

## 2. Architectural design and semantic model

AstroCo follows a client–server architecture. On the client side, it is a Google Chrome extension written in JavaScript. Once installed, it listens for user text selections on any Web page. On the server side, it relies on a SKOS-encoded version of the Etymological Dictionary, hosted on a remote server under standard HTTP/S. The extension issues HTTP(S) GET requests, or AJAX calls, carrying the selected term, and the server responds with a small JSON or XML payload containing the SKOS definition and metadata [1206.0595].

The semantic representation is based on SKOS, the Simple Knowledge Organization System. SKOS is used to represent concepts, labels, definitions, and relations. The choice of SKOS is motivated by the fact that it is recommended by the IVOA for knowledge-organization schemes and hides OWL’s complexity. The current release does not ship a full OWL ontology or SPARQL endpoint; instead, the dictionary was converted to a SKOS RDF graph, and the plug-in queries a lightweight REST API over that graph [1206.0595].

The formal lookup model is presented as two mappings. Let $W$ be the set of words selectable in the browser, $C$ the set of SKOS concepts, and $D$ the set of text definitions. Then

$$
f\colon W \to C
\quad\text{and}\quad
g\colon C \to D.
$$

When a user highlights $w \in W$, the plug-in computes $c=f(w)$ by matching `skos:prefLabel` or `skos:altLabel`, then retrieves $g(c)$ [1206.0595].

The paper also gives a representative SPARQL pattern for a possible extension:

$$
\texttt{SELECT ?def WHERE \{}
\quad\texttt{?concept\ skos:prefLabel\ "star"@en;\ skos:definition\ ?def\}.
$$

Since the same source explicitly states that no full SPARQL endpoint is shipped in the current release, this query should be read as illustrative rather than as a description of deployed functionality [1206.0595].

## 3. Integration with the Etymological Dictionary of Astronomy and Astrophysics

AstroCo’s backend is the Etymological Dictionary of Astronomy and Astrophysics, and the plug-in’s query, retrieval, and display flow is straightforward. A user highlights a word on a Web page; the extension sends an HTTP request such as `GET https://dictionary.obspm.fr/lookup?term=highlightedWord`; the server returns a minimal JSON object containing a concept URI, label, language, and definition; and the plug-in renders a floating pop-up anchored to the selection [1206.0595].

The returned object is described in the following form:

```json
{
  "conceptURI":"http://.../skos/concept123",
  "label":"star",
  "language":"en",
  "definition":"A luminous sphere of plasma... (etymology, related terms)"
}
```

The data schema is optimized for efficient term resolution. The SKOS graph is stored in a native triplestore such as Jena TDB or Virtuoso, or alternatively in a relational mirror with text indexes on `skos:prefLabel` and `skos:altLabel`. An LRU cache in the plug-in avoids repeated round trips for recently queried terms, while server-side full-text indexes on labels and alternate labels accelerate exact and near-match look-ups [1206.0595].

These implementation details indicate that AstroCo was designed as a low-friction retrieval system rather than as a heavy semantic reasoning environment. A plausible implication is that latency reduction and simplicity of deployment were prioritized over ontology-level expressivity.

## 4. User interaction and interface behavior

The user workflow is minimal. A Chrome user installs AstroCo from the Chrome Store in a two-click process. On any Web page, the reader selects a term in English or French. A right-click menu or automatic pop-up appears, displaying the English definition. If desired, the user clicks a link in the pop-up to open the full entry in the Etymological Dictionary’s Web interface, which shows etymology, equivalents, related concepts, and detailed notes [1206.0595].

Language handling is asymmetric but explicit: selection may be of English or French terms, while definitions are always returned in English [1206.0595]. The interface is described as a small semi-transparent box with rounded corners placed next to the highlighted word. It shows the term in bold, its brief definition in plain text, and a “More…” link at the bottom for the full dictionary entry. The design emphasizes minimal intrusion through neutral colors, compact size, and crisp typography [1206.0595].

Because the software operates on arbitrary Web pages, its interface model is fundamentally contextual rather than document-centric. This suggests that AstroCo aimed to transform passive reading into terminology-aware browsing without requiring migration to a dedicated reference portal.

## 5. Applications in astronomy and the Virtual Observatory

AstroCo’s immediate use cases are centered on everyday browsing for astronomers and educators. It enables quick resolution of unfamiliar or archaic terms encountered in research papers, blogs, or educational sites without switching tabs. It also supports bilingual comprehension, since language learners can highlight French or English astronomy terms and obtain the precise English definition [1206.0595].

The tool was also framed as relevant for amateurs and the broader public, for example by allowing stargazers using online sky-map services to clarify terms such as “declination” or “supernova remnant” instantly [1206.0595]. More technically, the paper emphasizes its potential role in Virtual Observatory infrastructure. Because AstroCo is built on SKOS, its vocabulary can be directly consumed by VO registries or data-discovery tools to annotate datasets with standard concept URIs. Future pilot prototypes could embed AstroCo in VO portals so that any concept in a data table or service description can be clicked for definition and semantic context [1206.0595].

This relationship to the VO ecosystem is central to the software’s conceptual importance. The authors explicitly note that another expected use of the facility could be implementation in Virtual Observatory services, and the choice of SKOS is aligned with IVOA recommendations [1206.0595]. A plausible implication is that AstroCo was conceived not merely as a browser convenience, but as a lightweight semantic interoperability component for astronomy e-infrastructure.

## 6. Evaluation, limitations, and prospective development

The paper reports no formal user studies. Feedback from early testers at VO-Paris (CDS) is described as anecdotally positive, particularly with respect to ease of installation and immediate utility. Typical round-trip lookup, from client highlight to server reply to pop-up render, is reported to take under 200 ms on a broadband link, with network latency dominating the response time [1206.0595].

Several limitations are stated directly. Definitions are always in English, with no French-language definitions yet. There is no fuzzy matching or morphological normalization beyond exact `prefLabel` and `altLabel` lookup, so plural forms require explicit alternate labels. There is also no offline mode, since the plug-in requires network access to the SKOS server [1206.0595].

Proposed extensions include on-the-fly lemmatization and fuzzy matching, extension of the backend to a full SPARQL endpoint, multilingual definitions including French and Persian and eventually Spanish and German, and direct embedding of the vocabulary into VO tools such as Aladin and TOPCAT for in-context concept-driven data discovery [1206.0595].

These limitations clarify a common misconception: AstroCo is not presented as a complete ontology browser or multilingual terminological platform in its current form. Rather, it is a lightweight semantic lookup tool whose architecture leaves open the possibility of richer semantic and multilingual services.

## 7. Significance in semantic astronomy infrastructure

AstroCo was presented as successfully bridging the gap between a rich offline dictionary and the fluid browsing environment of the Web, giving immediate, reliable definitions of astronomical concepts in situ. By relying on SKOS and following IVOA recommendations, it was described as fully compatible with Virtual Observatory interoperability goals [1206.0595].

Its broader significance lies in demonstrating how a dedicated semantic layer can transform ordinary Web pages into concept-aware resources. The modular design—client-side JavaScript plus a RESTful SKOS backend—makes the system easy to install, fast in operation, and extensible toward SPARQL services, multilingual definitions, and tighter VO integration [1206.0595].

In that sense, AstroCo occupies a specific niche within astronomy cyberinfrastructure: not large-scale data management, not event brokering, and not ontology engineering in the strong formal sense, but semantic mediation at the point of reading. This suggests an infrastructural role in which terminological standardization, dictionary curation, and lightweight semantic delivery are linked directly to the workflows of research, education, and online discovery.

Source: https://www.emergentmind.com/topics/astroco