{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/dxwg/issues/238","repository_url":"https://api.github.com/repos/w3c/dxwg","labels_url":"https://api.github.com/repos/w3c/dxwg/issues/238/labels{/name}","comments_url":"https://api.github.com/repos/w3c/dxwg/issues/238/comments","events_url":"https://api.github.com/repos/w3c/dxwg/issues/238/events","html_url":"https://github.com/w3c/dxwg/issues/238","id":324218420,"number":238,"title":"Use Case: Profiles of DCAT-AP and various implementation resources","user":{"login":"rob-metalinkage","id":8681313,"avatar_url":"https://avatars3.githubusercontent.com/u/8681313?v=4","gravatar_id":"","url":"https://api.github.com/users/rob-metalinkage","html_url":"https://github.com/rob-metalinkage","followers_url":"https://api.github.com/users/rob-metalinkage/followers","following_url":"https://api.github.com/users/rob-metalinkage/following{/other_user}","gists_url":"https://api.github.com/users/rob-metalinkage/gists{/gist_id}","starred_url":"https://api.github.com/users/rob-metalinkage/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rob-metalinkage/subscriptions","organizations_url":"https://api.github.com/users/rob-metalinkage/orgs","repos_url":"https://api.github.com/users/rob-metalinkage/repos","events_url":"https://api.github.com/users/rob-metalinkage/events{/privacy}","received_events_url":"https://api.github.com/users/rob-metalinkage/received_events","type":"User","site_admin":false},"labels":[{"id":653073651,"url":"https://api.github.com/repos/w3c/dxwg/labels/ucr","name":"ucr","color":"1d76db","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2018-05-17T23:20:18Z","updated_at":"2018-05-30T04:52:06Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Profiles of DCAT-AP and various implementation resource\r\n---\r\n### Development and governance of localised DCAT Application Profiles \r\nStatus: proposed\r\n\r\nIdentifier: \r\n\r\nCreator:  Rob Atkinson (Please Andrea and Makx check details)\r\n\r\nDeliverable(s): (DCAT1.1, AP Guidelines)\r\n\r\n## Tags\r\nProfiles, Semantics\r\n\r\n## Stakeholders\r\nPublishers and users of implementing profiles of DCAT. (This use case is evidence for a wider scope of any cases where the finer grained semantics of catalogues resources needs to address interoperability concerns.)\r\n\r\n## Problem statement\r\nAs evidenced by DCAT-AP and GeoDCAT,  profiles of DCAT may be declared and then specialised by communities of practice or local jurisdictions. GeoDCAT-AP is thus a profile of both DCAT-AP and GeoDCAT,  DCAT-AP-IT is an Italian profile of DCAT-AP.\r\nProfiles may be supported by multiple resources, with different roles. DCAT-AP for example provides documents in multiple formats, SHACL validations for multiple versions of SHACL, spreadsheet templates and other types of implementation resources.\r\nThe DCAT-AP example also illustrates the practical need to describe relationships between different versions of the profile, and for each of these a unique set of implementation resources.\r\n\r\n[link to Makx's presentation at F2F here]\r\n\r\n## Existing approaches\r\nCurrent use of DCAT-AP is a clear example of the need for this pattern in practice.  https://joinup.ec.europa.eu/release/dcat-ap-v11 shows this registered in a catalogue (as a sort of Dataset - which suggests generalisation of DCAT scope) along with a set of implementations resources (described as \"distributions\").\r\n\r\nIn programming languages such as Java, a statement of object interoperability is achieved by statements of inheritance of (possibly multiple) \"interface\" classes. \r\n\r\n\r\n## Links\r\nhttps://joinup.ec.europa.eu/release/dcat-ap-v11\r\n\r\n## Requirements\r\n6.2.1 Version subject [RVSS]\r\n6.2.3 Version identifier [RVSID]\r\n6.8.1 Profile definition [RPFDF]\r\n6.8.2 Profile representation [RPFRP]\r\n\r\n## Related use cases\r\n5.3 Responses can conform to multiple, modular profiles [ID3]\r\n5.4 Dataset Versioning Information [ID4]\r\n5.7 Support associating fine-grained semantics for datasets and resources within a dataset [ID7]\r\n5.20 Modelling resources different from datasets [ID20]\r\n5.24 Harmonising INSPIRE-obligations and DCAT-distribution [ID24]\r\n5.30 Standard APIs for metadata profile negotiation [ID30]\r\n5.39 DCAT Metadata profile integration [ID39]\r\n5.41 Vocabulary constraints [ID41]\r\n\r\n## Comments\r\nThe nature of profile inheritance and attached resources are implications of this Use Case that were previously inferred from the context in which, for example, the DCAT-AP example was raised, i.e.  in more specific Use Cases about single aspects of DCAT expressivity.  A comment was made that without a grounding in typical technical solution patterns it was insufficiently clear that these overarching governance and usage experiences directly drove the inferred requirements. \r\n\r\n\r\n---\r\n"},"comment":{"url":"https://api.github.com/repos/w3c/dxwg/issues/comments/393029825","html_url":"https://github.com/w3c/dxwg/issues/238#issuecomment-393029825","issue_url":"https://api.github.com/repos/w3c/dxwg/issues/238","id":393029825,"user":{"login":"kcoyle","id":1564129,"avatar_url":"https://avatars1.githubusercontent.com/u/1564129?v=4","gravatar_id":"","url":"https://api.github.com/users/kcoyle","html_url":"https://github.com/kcoyle","followers_url":"https://api.github.com/users/kcoyle/followers","following_url":"https://api.github.com/users/kcoyle/following{/other_user}","gists_url":"https://api.github.com/users/kcoyle/gists{/gist_id}","starred_url":"https://api.github.com/users/kcoyle/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kcoyle/subscriptions","organizations_url":"https://api.github.com/users/kcoyle/orgs","repos_url":"https://api.github.com/users/kcoyle/repos","events_url":"https://api.github.com/users/kcoyle/events{/privacy}","received_events_url":"https://api.github.com/users/kcoyle/received_events","type":"User","site_admin":false},"created_at":"2018-05-30T04:52:06Z","updated_at":"2018-05-30T04:52:06Z","author_association":"CONTRIBUTOR","body":"If this is to be based on the information that Makx included in his presentation at F2F3, then it should include the community and maintenance management that he outlines in [slides 5-9](http://makxdekkers.com/DXWG/DCAT-AP.pdf). That is missing from our requirements. Also, nothing about DCAT-AP as he describes it refers to inheritance. As you may recall, at the May 22 meeting we agreed that we would not use the term \"inheritance\" but would speak of relationships or dependencies between profiles. I think we need to adhere to that, here and elsewhere."}}
{"actor":{"display_login":"kcoyle"}}