Another serialization option, putting the extensions in the dcat:endpointDescription, which takes a value rdfs:resource. ``` a:dataset-004 a dcat:Dataset ; dct:title "Example Relational Database"@en ; dct:description "individual tables and views are accessible as separate distributions via jdbc connections" @en ; dcat:distribution [ a dcat:Distribution ; dct:title "access table 005: THE_TABLE_NAME"; dcat:accessService a:table-service-005 ] . a:table-service-005 rdf:type dcat:DataService ; dct:title "access table 005: THE_TABLE_NAME"; dct:conformsTo <https://www.cybele-project.eu/relationaltableprofile> ; dct:type <(https://www.cybele-project.eu/table/view> ; dcat:endpointDescription [ ex:accessDatabase [ a ex:Database ; ex:connectionString "jdbc:oracle:thin:@​hostname:1521:my-database"; ex:tableName "THE_TABLE_NAME" ] ] ; dcat:servesDataset a:dataset-004 . ``` Should work as long as ex:accessDatabase subclasses from rdfs:Resource. Nothing is inconsistent with DCAT -- GitHub Notification of comment by smrgeoinfo Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1240#issuecomment-656302238 using your GitHub accountReceived on Thursday, 9 July 2020 19:12:14 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:28:35 UTC