Meeting minutes
https://
PROPOSED: Approve minutes
<pchampin> +0
<YoucTagh> +1
https://
+1
<roba> +1
RESOLUTION: Minutes approved
Check status of actions from last meeting
https://
roba: LarsG has created PR which is approved
LarsG: will ping kcoyle to ask for input
roba: #23, #26 and #27 not yet addressed
roba: No discussion wich nicholascar on #32 yet
nicholascar: don't like full URIs here
… AltP is not correct any more
… should be AltR
roba: cpnr is defined in the document but altr isn't
ACTION: nicholascar to address #32
pchampin: is replacement of altp with altr correct?
… we usually have a table with all prefixes in the document
nicholascar: will tend to that
YoucTagh: revised #44
nicholascar: sceptical of solution
… canonical should be the default
… everything else is alternate
roba: will not implement preferred
… so there will be no implementation evidence
… thus feature at risk
nicholascar: seems like an error in our document
YoucTagh: Intention is to flag the preferred representation for a specific dimension
… canonical is the global fallback
… but we need a way to show which is the best representation
… for a specific combination of dimensions
pchampin: Agree that only one canonical allowed
… so we need something else to convey the semantics
… at the moment we have no way to convey the input dimensions
YoucTagh: that's what the "dim" is for
roba: Currently no driver for "preferred"
nicholascar: There is order of presedence (profle, media type)
… in the model there are default formats for each media type
… we _can_ push this to any dimension (incl. lang)
roba: have implemented slightly differently
… giving error message instead of default
… do YoucTagh have use cases to support the proposal?
YoucTagh: Not now. Solution emerged from our last discussion
roba: Will catch up with nicholascar to see that their implementations
… are similar and adhere to the spec
… we still keep #44 open until the multiple "canonical" is resolved
Review of §7.1
YoucTagh: Have reviewed the text
… in the context of #7
… still unclear if "the profile" refers to "data profile"
… or to "functional profile". Is that on purpose?
roba: Should be "functional profile"
YoucTagh: Spec talks of "human browser"
… we can use URLs without human browsers, however,
… also conforming (with|to) - confusing for non-native speakers -
… Listing in spec (Code listing 1) is not consistent with TTL file
nicholascar: will take care of that
ACTION: nicholascar to find solution for automatic linking of external content
pchampin: All documents in /TR must be self-contained
… there is now an automated process for document publication
… for documents in draft status
<pchampin> PROPOSED: use Echidna to auto-publish working drafts from branch gh-pages
<nicholascar> +1
<roba> +1
<pchampin> +1
<YoucTagh> +1
pchampin: the point is to publish all EDs as WDs
+1
RESOLUTION: use Echidna to auto-publish working drafts from branch gh-pages
ACTION: pchampin to set up echidna to auto-publish working drafts from branch gh-pages
YoucTagh: cnpr:rrd is not clear
… this is already implied when implementing http or qsa
nic
holascar: It implies a hierarchy. We need a diagram to describe it
roba: It seems that the terminology as such is fine.
… We need PRs to fix the minor issues
… then we can mark the issue as due-for-closing
… and high-light it to the group
ACTION: roba to update §7.1 based on YoucTagh's feedback
Next meeting
nicholascar: We should look at the implementation report
roba: Also #37
nicholascar: Can prepare text for that
roba: We cannot assign tasks to nicholascar
… can pchampin have a look at that?
pchampin: Will look into that
ACTION: pchampin to check why we cannot assign tasks to nicholascar