Geoconnex alignment recommendations

RDF's built-in class of properties. Do not use it as a catch-all declaration for Geoconnex predicates; classify predicates as owl:ObjectProperty, owl:DatatypeProperty, or owl:AnnotationProperty where possible.

• schema:ImageObject ^c or Resource ^c
• schema:GovernmentOrganization ^c
• schema:Organization ^c
• schema:Person ^c
• schema:SearchAction ^c
• schema:EntryPoint ^c
• schema:ImageObject ^c
• schema:BreadcrumbList ^c
• schema:ListItem ^c
• schema:WebSite ^c
• schema:WebPage ^c
• schema:NewsArticle ^c
• Property ^c
• Datatype ^c
• Class ^c
• Container Membership Property ^c
• List ^c
• Transitive Property ^c
• Symmetric Property ^c
• hyf:HY_HydrographicNetwork ^c
• schema:GeoCoordinates ^c or schema:GeoShape ^c
• geoconnex:MeasuredVariable ^c
• hyf:HY_IndirectPosition ^c
• hyf:HY_DistanceFromReferent ^c
• hyf:HY_DistanceDescription ^c

• hyf:interpolative ^dp
• hyf:linearElement ^op
• hyf:distanceDescription ^op

This is a class-like HY_Features term. Move it from the property inventory to the class inventory if it appears as a property.

This is a class-like HY_Features term. Move it from the property inventory to the class inventory if it appears as a property.

This is a class-like HY_Features term. Move it from the property inventory to the class inventory if it appears as a property.

Model logos as resource links, preferably to a schema:ImageObject or image URL IRI.

This is a property, not a class. Move it from the class inventory to the property inventory.

Keep this as the immediate downstream relation. Use a separate transitive-closure property for reachability queries.

Use schema:geo directly for Schema.org-facing coordinate or shape summaries. Use geo:hasGeometry or geo:defaultGeometry for formal GeoSPARQL geometries.

Model content URLs as IRI objects when aligning to dcat:downloadURL. If a source emits URL strings, normalize them to IRIs during RDF generation.

Model URLs as IRI objects in RDF. If a source emits URL strings, normalize them to IRIs during RDF generation.

Use for sampling or operating frequency when the subject is an SSN/SOSA system, sensor, or procedure. Consider pairing with QUDT for numeric value and unit.

Prefer geo:asWKT for machine spatial reasoning; keep schema:polygon for Schema.org compatibility.

Prefer geo:asWKT for machine spatial reasoning; keep schema:line for Schema.org compatibility.

Prefer geo:asWKT or schema:latitude/schema:longitude where possible. schema:coordinates is useful as a lightweight fallback.

Schema.org encodingFormat is commonly a text media type or URL. Keep it as a datatype property for Geoconnex exports; add dcat:mediaType separately when using controlled media-type resources.

Schema.org temporalCoverage accepts flexible text, dates, and intervals. If the data can be normalized, also add dcterms:temporal with a typed PeriodOfTime node.

When possible, use qudt:hasUnit with a QUDT unit IRI. Keep schema:unitCode for UCUM or Schema.org-compatible literals.

Use schema:unitText only for human-readable unit labels. Add qudt:hasUnit when a controlled unit IRI is known.