Meeting minutes
Introduction, Any Updates?
matatk: I will have regrets for next week, conflict with TAG
Lionel_Wolberger: Any news on recruitment?
janina: We have a new member that is interested in Adapt
RESOLUTION: TF will not meet in teleconference 24 January
URL Project Vocabulary: Well Known Destination?
<matatk> Most of the things we're discussing in this section of the meeting come from https://
matatk: Suggests deferring naming for a bit ...
matatk: What we call it could take lots of time
janina: Agree we can postpone decision on vocabulary, but we should take care that our discussions use terms precisely
janina: While we may not need an overall label for the work stream, se need to be very precise when we refer to associated specs
matatk: agrees and clarifies
janina: well known URI shall refer to that spec, rel to that spec, etc
DRAFT RESOLUTION: We'll use "Well Known Destinations" provisionally as our class category
RESOLUTION: We'll use "Well Known Destinations" provisionally as our class category
+1
Issues raised in the Well Known Destination/URL Git
matatk: Notes when we build on WKU we have requirements greater than what WKU supports, specifically a subsection of a page isn't supported in WKU
matatk: Abinar also asked how does a UA know what WKDs are supported
matatk: The well known root will return json (or similar) of well known destinations
AnthonySpAbhinav: Asks how pages pointed to from a main corporate site would publish their sets of WKDs
matatk: Understand question is subsite without an individual subdomain
matatk: As we're currently conceiving, we'd need a subdomain
matatk: Notes this would track with password change illustrates this
matatk: Suggestsexamining current page would expose also if less efficient
Lionel_Wolberger: Are we over-reaching with this problem?
matatk: Notes the history is that SaP's proposal came to us as we were looking at creating WKDs in our parallel work process
... trying to solve for many well known destinations, when we have not yet even established one?
matatk: Understand better why site map is raised in this context
Abhinav: Believe we could extend site map to provide machine readable destinations
matatk: Agrees some WKDs are machine to machine, as is password change, but we are initially concerned for end user support in WKDs
janina: We do not only focus on machine to machine here in Adapt; we are focused on usability for humans
Abhinav: zakim, take up item 2
<gb> Issue 240 Could we build symbolic annotations with existing Web standards? (by DuncanMacWeb) [i18n-tracker]
Issue 240 Way Forward
<matatk> Proposal: "Directing issue 240 towards resolution": https://
<matatk> Issue 240: w3c/