Change of structure discussed in Oct 24 discussion in Lyon #489
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- splitting the long list of requirements/recommendations (MUST/SHOULD/MAY) from #435 (comment) and #242 (comment) into various sections where they can be better contextualised and explained (as consistent bits) to readers - acknowledging that these recommendations did not fit well as intro material and giving more space in the introduction so that the discussion on types and examples of profiles (#435 (comment)) can 'breathe' better. - provide finer-grained introduction (and better alignment) to other relevant DXWG work (the Profiles Ontology and Profile Negotiation) - put a placeholder for a conceptual model to which the rest can be naturally attached, and for which the Profiles Ontology would provide a straight implementation as a vocabulary. - exploit the notion of role as first introduced in the Profiles Ontology as an interesting pattern to represent the functions that (expressions/components of) profiles can play, as sketched in #435.
|
Changes are visible at https://raw.githack.com/w3c/dxwg/guidance-restructuring-LyonOct24/profiles/index.html |
|
@nicholascar @rob-metalinkage @kcoyle your input in this PR is more than welcome but I think it shouldn't be merged just before the F2F, as it's quite a change and we may want to compare it with the rest of the group at some time in the coming two days. |
Add Lars and Riccardo's warning about using DCAT datasaset parliance
|
Approved in Oct 25 F2F |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The changes here have the following motivations:
splitting the long list of requirements/recommendations (MUST/SHOULD/MAY) from What is a profile? #435 (comment) and profileDesc and the Guidance document #242 (comment) into various sections where they can be better contextualised and explained (as consistent bits) to readers
acknowledging that these recommendations did not fit well as intro material and giving more space in the introduction so that the discussion on types and examples of profiles (What is a profile? #435 (comment)) can 'breathe' better.
provide finer-grained introduction (and better alignment) to other relevant DXWG work (the Profiles Ontology and Profile Negotiation)
put a placeholder for a conceptual model to which the rest can be naturally attached, and for which the Profiles Ontology would provide a straight implementation as a vocabulary.
exploit the notion of role as first introduced in the Profiles Ontology as an interesting pattern to represent the functions that (expressions/components of) profiles can play, as sketched in What is a profile? #435.