Should lat/long belong to Relationship or EntityProperty?

[Jiaji Zhou]

The brick schema ontology page lists latitude/longitude in the Relationships category, is that a mistake, should they instead be EntityProperties?

Also it appears that the 'latitude' has a typo, is that intentional or by mistake?

Thanks,

Jiaji

[Erik Paulson]

The extra 'T' in Latitude was definitely a typo, the correct property is the way it's supposed to be spelled. It's already been corrected in the code.

Lat/Long probably should be entityProperties - in RDF, there's not really any difference between a "relationship" and an "entityproperty" - they're both "predicates" that can be used in triples. Originally everything was just a "relationship" in the Brick ontology, but in newer versions of Brick we added EntityProperty and have been adding some things there - Lat and Long just predate that so that's why they're still in 'Relationship' - we should probably move them to entity property just to make the documentation a bit more clear, but there's functionally no difference.

-Erik

--
You received this message because you are subscribed to the Google Groups "Brick User Forum (Unified Building Metadata Schema)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to brickschema...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/brickschema/f9ab0a0b-98e6-46c4-9a46-7482fbe5e698n%40googlegroups.com.