New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 6.0 planning (goal: 2019-12-01) #2376
Comments
I think this is good to go too:
|
|
PolicyPages seems non-controversial #2350 |
Is it too late to get in:
|
Running behind on this, but at least we know how 2020 will start! Thanks all... |
ok most of 6.0 is up at http://webschemas.org/docs/releases.html#v6.0 for review. I still need to work on the datasets part (top of this page), plus improve the renaming of ProductReturn* to MerchantReturn* terms so that old descriptions point to newer. |
Update: I propose we come back to 'Revisit/improve work around funding esp of datasets, #383 /cc @chrisgorgo' later in the month for v7. I have a little more work to do on dataset funding then I think we're ready to declare 6.0 release candidate. |
I've been looking at the dataset (etc) funding piece (and whiteboard diagrams from discussion with @chrisgorgo). Since it is a complex pattern touching ~6 types I think it deserves writing up in a doc or dedicated issue for better sanity checking, including a properly worked example, so I'll postpone the implementation until next release. |
Sounds ok to me, but pinging @natashafn for additional comments. |
Yep, sounds good. |
Stale issue message |
Planning issue for 6.0
datasets-related topics:
Revisit/improve work around funding esp of datasets, #383 /cc @chrisgorgo
modelling acknowledgements eg. for datasets #2266 (postponed for post-6.0 --@danbri)
Add a maintainer property per #2311
isPartOf / hasPart --- json-ld should expect a link not a string so add URL as a type #2321
...
#2381 clarify via rename that product return policy is merchant-level
#2397 - generalized datePosted
#637 - made offers and itemOffered true inverses
Candidate PRs for 6.0 release
The text was updated successfully, but these errors were encountered: