You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VOEvent 2.0 incorporates STC 1.3, yet there's no mention of its compatibility with 2.1. Can we advocate for the adoption of RDF IVOA vocabularies from https://www.ivoa.net/rdf/, even though this link is discussed later in the text?
Including a list of triplets for astronomical coordinate systems seems impractical, especially considering potential evolution over time. Additionally, there's uncertainty about whether ICRS solely relies on the barycenter of the solar system; this aspect requires review by an expert.
Regarding the schema, the complex type "astrocoord" includes an element called "Name." Its usage is unclear; while the xs:documentation indicates it represents a "Named position for the event," "astrocoord" is also associated with "ObservatoryLocation." It would be beneficial to clarify this in the documentation.
In the fourth paragraph, it's worth noting that VOResource is now version 1.1, not 1.0.
The text was updated successfully, but these errors were encountered:
VOEvent 2.0 incorporates STC 1.3, yet there's no mention of its compatibility with 2.1. Can we advocate for the adoption of RDF IVOA vocabularies from https://www.ivoa.net/rdf/, even though this link is discussed later in the text?
Including a list of triplets for astronomical coordinate systems seems impractical, especially considering potential evolution over time. Additionally, there's uncertainty about whether ICRS solely relies on the barycenter of the solar system; this aspect requires review by an expert.
Regarding the schema, the complex type "astrocoord" includes an element called "Name." Its usage is unclear; while the xs:documentation indicates it represents a "Named position for the event," "astrocoord" is also associated with "ObservatoryLocation." It would be beneficial to clarify this in the documentation.
In the fourth paragraph, it's worth noting that VOResource is now version 1.1, not 1.0.
The text was updated successfully, but these errors were encountered: