- From: Jacob via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Jul 2015 20:44:47 +0000
- To: public-annotation@w3.org
With regards to Doug's question about schema.org, IIRC it was floated that we swap out various properties and entities reused from Dublin Core for equivalent properties and entities that appear in schema.org. It's been quite a number of months since it came up and I don't recall if we ever had a consensus on whether or not that was a good idea. _____________________________________________________ Jacob Jett Research Assistant Center for Informatics Research in Science and Scholarship The Graduate School of Library and Information Science University of Illinois at Urbana-Champaign 501 E. Daniel Street, MC-493, Champaign, IL 61820-6211 USA (217) 244-2164 jjett2@illinois.edu On Wed, Jul 8, 2015 at 3:32 PM, Rob Sanderson <notifications@github.com> wrote: > From #46 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_web-2Dannotation_issues_46&d=AwMCaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=npggDwlZ6PziBzPBZthSo0f8iGOgRMf9ulO6o4WwfiA&m=9cnfJVPx-qxWO38PSSORSfl1nwIZxfJmQTkblpHV71o&s=uw9qI0fDjwrCpWlMhCWgij_hhvqBxaMmheZaoWbCrAY&e=>, > there is the question of whether the namespace should change for the model. > > Note that this is only a concern from the RDF perspective, not the > preferred JSON serialization which won't have even a prefix, let alone the > complete namespace (per #12 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_web-2Dannotation_issues_12&d=AwMCaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=npggDwlZ6PziBzPBZthSo0f8iGOgRMf9ulO6o4WwfiA&m=9cnfJVPx-qxWO38PSSORSfl1nwIZxfJmQTkblpHV71o&s=9WBg5dShOKybIT2kbb3gJVgIgxDPGC8TQ6ctVPdtwrE&e=>). > > > From the telco on 2015-07-08, some of the discussion included: > > - There's a lot of use of the namespace > - Changing namespaces is generally a bad idea > - Backwards compatibility without changing the namespace is important > - The CG spec is explicitly a draft, so we need not feel too > constrained by changing the definitions in a non-backwards-compatible way > - It demonstrates continuity and inclusion, rather than division and > competition, hopefully avoiding splitting the community of practice > - It has the oa acronym ... which would be confusing without the > history > > The decision on the call was to defer the decision until later. > > — > Reply to this email directly or view it on GitHub > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_web-2Dannotation_issues_53&d=AwMCaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=npggDwlZ6PziBzPBZthSo0f8iGOgRMf9ulO6o4WwfiA&m=9cnfJVPx-qxWO38PSSORSfl1nwIZxfJmQTkblpHV71o&s=lhsme9Hg0YqqNTQBnaKsUkRIyaecF7C3HX5j-OUyiVA&e=> > . > -- GitHub Notif of comment by jjett See https://github.com/w3c/web-annotation/issues/53#issuecomment-119726242
Received on Wednesday, 8 July 2015 20:44:49 UTC