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
Is your feature request related to a problem? Please describe.
A rest call, e.g. https://identifier.buildingsmart.org/uri/buildingsmart/ifc/4.3/class/IfcWall with "Accept" : "application/json" returns the class hierarchy while "Accept : "text/turtle" does not. Is there a particular reason that the response doesn't return the same content regardless of format?
Describe the solution you'd like
It seems as if the Dictionary schema allows for a "ParentClassCode". Eventhough a "ParentClassURI" would have been more useful (similar to rdfs:subClassOf), could "ParentClassCode" be a part of the response for a class URI? This way, at least the class hierarchy would be accessible in a linked data setting.
Describe alternatives you've considered
My knowledge of the API is limited right nowl, but I guess that one alternative would be to use the API, but, a simple access through URI:s is preferrable.
Additional context
application/json:
test/turtle:
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
A rest call, e.g. https://identifier.buildingsmart.org/uri/buildingsmart/ifc/4.3/class/IfcWall with "Accept" : "application/json" returns the class hierarchy while "Accept : "text/turtle" does not. Is there a particular reason that the response doesn't return the same content regardless of format?
Describe the solution you'd like
It seems as if the Dictionary schema allows for a "ParentClassCode". Eventhough a "ParentClassURI" would have been more useful (similar to rdfs:subClassOf), could "ParentClassCode" be a part of the response for a class URI? This way, at least the class hierarchy would be accessible in a linked data setting.
Describe alternatives you've considered
My knowledge of the API is limited right nowl, but I guess that one alternative would be to use the API, but, a simple access through URI:s is preferrable.
Additional context
![Image](https://private-user-images.githubusercontent.com/25506404/407356986-bd25bcdb-7ce6-46c8-a839-f12ab88f5b52.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzMTg4OTMsIm5iZiI6MTczOTMxODU5MywicGF0aCI6Ii8yNTUwNjQwNC80MDczNTY5ODYtYmQyNWJjZGItN2NlNi00NmM4LWE4MzktZjEyYWI4OGY1YjUyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDAwMDMxM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBiYzJmMzVmOTU2MDE1OWViYTZjNWQwNzE0ZTA2MTZkNTE5OWI1YjNlMmRiM2I1ZGEzYThhZmJhOGZlYThkNjMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.DJ6bpe3-rYbGhOi2uAYNcUBKdsEhZNfR2_S3ux4HE-c)
application/json:
test/turtle:
The text was updated successfully, but these errors were encountered: