team looking at "Comparison of ways to use vocabulary in content document"
Email from Jason White
<clapierre> [Jason] The only omission that immediately comes to mind is Web Annotation. The other implementation languages all assume that the metadata are included in the markup of the web page, but Web Annotation does not. A tool (e.g., custom user agent, proxy, browser extension) could maintain a list of trusted annotation providers, and match each page that the user accesses with a list of URIs of pages for which annotations are availab
<clapierre> le.
<clapierre>
<clapierre> I don’t know how strong a use case this is, but it shouldn’t be overlooked altogether either.
Lisa brings up external metadata as an implementation
Concepts of inline vs external needs to be considered at some point
this topic is suggested as a topic for later discussion and separated from inline implementations
all brought up as implementation within the context of a site as a whole vs individual pages
these topics will be taken up at a later date - external metadata, context within a site as a whole
currently suggestion is to limit current docuement to internal to the document
any objectios?
any objection to?
no objections noted
JF holds the position that we need to define the vocabulary first
Topic - Comparisons of vocabulary
Do we have all the topics? Do we have all the pros and cons?
Lisa noted that media queries is not present in document
Michael C. noted that there are other implementation that are not on the implimentations page
Michael C. will update page based on associated issues (in progress)
Compare contrast should be a complete representation of options
<JF> +1 to Michael
Sam has several proposals which should be included for review
Here is an example issue from sam
https://github.com/w3c/personalization-semantics/issues/77
here is another from sam
https://github.com/w3c/personalization-semantics/issues/76
https://github.com/w3c/personalization-semantics/issues/73
from sam https://extensiblewebmanifesto.org/
https://github.com/w3c/personalization-semantics/issues/74
I have listed Sam's issues as a single point of reference for Michael
looking for JF's issues to paste in
<JF> https://github.com/w3c/personalization-semantics/issues/83
thank you
2 week deadline to link issues to the implementations page
Need someone to volunteer to link issues to the the implementaions page
Any objections to linking associated issues to implentations page?
JF has concerns that we are discussing implementations without clearly defining the vocabulary
Any objections two mapping issues within two weeks?
Any objections to mapping issues within two weeks?
JF suggests concentation on looking at issues that have been logged in an effort to make progress
Thaddeus Volunteers
Thaddeus Action
Thaddeus' action - map assiociated issues marked as "implementation" to Comparison of ways to use vocabulary in content page
<scribe> New Header for Orphaned section or equivalent name
Lisa to add issue if deemed appropriate
Consider TPAC meeting
<JF> Hoping that any meeting of this TF does not conflict with AG WG
for the TF
We will work out plans for TPAC based on individual schedules
Michael noted that we have not requested meeting space
I have to drop can someone take over scribe
Michael suggested informal meeting JF suggested a show and tell
I have to drop
from the call
thanks
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Present: clapierre Thaddeus MichaelC Becka11y Roy JF janina Lisa Sharon No ScribeNick specified. Guessing ScribeNick: Thaddeus Inferring Scribes: Thaddeus WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]