Meeting minutes
Lionel_Wolberger: Discussed coming meetings.
We'll post re next week
Introduction, Any Updates?
WKD Follow-up from Matt
matatk: AC meeting went very well, the presentation was received well.
… we have follow-ups.
… multiple domains and sub-somains is one potential obstacle. Abhinav mentioned this
… "rel" was mentioned as a potential substitute
… "rel" will only provide the 'well known' information on a particular page, not for the entire site
… For the 'rel' objection, suggest we check in with COGA as to the use case
… feedback was generally positive.
<Zakim> janina, you wanted to suggest answer to "how many" is "enough"
janina: How many? There are enough sites around the web that do it with subdomains, so we will need to handle that use case
matatk: We could use the HTTP Archive and Abhinav's experience to see if we can find some useful data on the % that is structured in that way
… Leonie posed a use case: what about a website for a hotel that has multiple contact pages: one for the spa, one for the hotel
… the answer seemed that there could be a switchboard page, a main 'contact' page that could route to all the others
… seems to be three colors (a) 1:1, one subdomain (b) a middle condition, 1:1 with exceptions (c) 1:many, one to many
Lionel_Wolberger: Asked clarifying questions about subdomains
… the objection, to my mind, is not about sub-domains. It is about hosting distinct services, distinguished by their path
… e.g. a site that has very different services under folder names: mysite.com/gameworld, mysite.com/boatrides, mysite.com/catfood
Abhinav: WKD is domain-wide as currently written
matatk: We need clarity around the use cases
… it is helpful to know all of the WKDs that a site supports, when you go there
… I feel we should check in with COGA on that
janina: they tend to state the use case centered on the user, they need to focus
Lionel_Wolberger: "rel" can live with WKD quite nicely
matatk: "rel" can indicate what's significant on the page, it does not conflict with the site-wide WKD
WKD Github actions and PRs
Issue 240 finalization
Russell: sent some suggestions on placeholder codes to use; refining the format of the number representation.
Russell: Longer-term we were to talk about the explainer
matatk: discussed including the numbers of concepts vs code points being included, to emphasize authoring considerations
Russell: reminder of https://
Russell: we could reference these as authoring tools
matatk: *checked how the authoring example would look - Russell confirms there would be two visually apparent bliss characters next to eachotehr*
Russell: For authoring, there is making existing concepts out of current symbols, and there is also the creation of new symbols - which is a long-term community effort.
Russell: The authoring tool should support accepted concepts primarily. The creation of new symbols is a community specific effort (and wouldn't be the same across symbol sets).