I guess thie biggest impact of adopting ADMS for cataloguing profiles is the axiomitisation that a profile is a sort of Dataset, hence we would not need to create a superclass of dcat:Distribution, but merely to align with prof:ImplResourceDesc rdfs:subClassOf dcat:Distribution, This doesnt negate the argument for a "Representation" superclass for clarity, but its a separate issue (i.e it shows profileDesc can complement ADMS and provide an interoperable way of describing key aspects of profiles within an ADMS conformant environment.) (PS - we can easily tweak ProfileDesc to mode closely and formally align with defined ADMS roles - but prov:wasDerivedFrom is not expressive enough in itself to describe constraint conformance mandated by the relationship, so we need some vocabulary somewhere to do this for us. -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/317#issuecomment-418249941 using your GitHub accountReceived on Tuesday, 4 September 2018 05:58:30 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:28:24 UTC