Normalize to https://schema.org/NewsArticle in Geoconnex exports. When possible, use qudt:hasUnit with a QUDT unit IRI. Keep schema:unitCode for UCUM or Schema.org-compatible literals. 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. Geoconnex alignment recommendations Recommended RDFS/OWL alignment axioms for an incomplete inventory of Geoconnex graph classes and properties. The ontology aligns hydrologic features with SawGraph/HY_Features, spatial descriptions with GeoSPARQL and Simple Features, web discovery metadata with Schema.org and DCAT, and observations/quantities with SOSA/SSN and QUDT. 2026-06-02 Normalize to https://schema.org/ListItem in Geoconnex exports. Normalize to https://schema.org/WebPage in Geoconnex exports. This is a class-like HY_Features term. Move it from the property inventory to the class inventory if it appears as a property. 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. Use schema:PropertyValue for web markup and QUDT QuantityValue for formal numeric value/unit modeling. Avoid global equivalence because Schema.org PropertyValue is broader. Normalize to https://schema.org/BreadcrumbList in Geoconnex exports. 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. Use schema:geo directly for Schema.org-facing coordinate or shape summaries. Use geo:hasGeometry or geo:defaultGeometry for formal GeoSPARQL geometries. Model URLs as IRI objects in RDF. If a source emits URL strings, normalize them to IRIs during RDF generation. Normalize to https://schema.org/Organization in Geoconnex exports. Use schema:Place for web discovery and GeoSPARQL geo:Feature/geo:Geometry for formal spatial reasoning. 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. Keep this as the immediate downstream relation. Use a separate transitive-closure property for reachability queries. This is a class-like HY_Features term. Move it from the property inventory to the class inventory if it appears as a property. true Avoid using schema:type. Use rdf:type in RDF and @type in JSON-LD. Treat hydrolocations as geospatial features. Use GeoSPARQL geometry properties for precise location and HY_Features linear-reference properties for hydrologic network position. This is a property, not a class. Move it from the class inventory to the property inventory. Normalize to https://schema.org/Person in Geoconnex exports. Schema.org temporalCoverage accepts flexible text, dates, and intervals. If the data can be normalized, also add dcterms:temporal with a typed PeriodOfTime node. Prefer geo:asWKT or schema:latitude/schema:longitude where possible. schema:coordinates is useful as a lightweight fallback. Model logos as resource links, preferably to a schema:ImageObject or image URL IRI. Use schema:unitText only for human-readable unit labels. Add qudt:hasUnit when a controlled unit IRI is known. Do not make this equivalent to sf:Point; Schema.org coordinates are a lightweight web metadata shape, while Simple Features points are formal geometries. RDF's built-in type predicate. It is intentionally not redeclared as a Geoconnex object or datatype property; use it directly for class membership. Model content URLs as IRI objects when aligning to dcat:downloadURL. If a source emits URL strings, normalize them to IRIs during RDF generation. This is a class-like HY_Features term. Move it from the property inventory to the class inventory if it appears as a property. Normalize to https://schema.org/WebSite in Geoconnex exports. Normalize to https://schema.org/logo in Geoconnex exports. For open-data catalogs, type dataset resources as both schema:Dataset and dcat:Dataset rather than asserting global owl:equivalentClass.