Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alternative approaches to dimensions #1

Open
jokroese opened this issue Apr 3, 2024 · 1 comment
Open

Alternative approaches to dimensions #1

jokroese opened this issue Apr 3, 2024 · 1 comment

Comments

@jokroese
Copy link
Member

jokroese commented Apr 3, 2024

In this part of the data model:

        cidoc:P43_has_dimension [
            a cidoc:E54_Dimension ;
            # could additionally have cidoc:P2_has_type mosa:Height (for example)
            schema:unitText "cm" ;
            schema:value 165 ],
        [ 
            a cidoc:E54_Dimension ;
            # could additionally have cidoc:P2_has_type mosa:Width (for example)
            schema:unitText "cm" ;
            schema:value 9 ],
        [ 
            a cidoc:E54_Dimension ;
            # could additionally have cidoc:P2_has_type mosa:Width (for example)
            schema:unitText "cm" ;
            schema:value 6 ] ;

There's the following comment:

by using CIDOC-CRM's P43_has_dimension, we are committing to objects being "cidoc:E70_Thing"s (because that's the deomain of the predicate)
dimension could also be made part of the mosa:physical_object property (depending on how "debatable" this info is considered)

Could we instead define (e.g.) height through schema's height property (https://schema.org/height)? Would that avoid us committing to It being a 'Thing' in CIDOC's sense? (height is also a property of schema's 'Thing' type, but in schema Thing is more general, with subtypes such as 'Person'.)

@jokroese
Copy link
Member Author

jokroese commented Apr 3, 2024

We could also make use of schema's (experimental) size property https://schema.org/size.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant