Join GitHub today
It would be great if anyone could write e.g. gs1voc:AllergenTypeCode-WHEAT or somesuch without having to declare http://gs1.org/voc explicitly. To do this we'd need to add their preferred prefixes to our context (current status viewable at http://webschemas.org/docs/jsonldcontext.json), check for conflicts and also maybe liaise with W3C team about keeping, or not keeping, similar W3C lists in sync.
Similar considerations for #1390
There's also a strand of consideration around using multiple context files (or not) or a context that imports both. We don't really have a best practice yet. It might be good also to request schema: prefix in other popular context files, for similar reasons.
Adding menu markup schema: issue schemaorg#1288 Proposal: https://docs.google.com/document/d/1q0M8jdJrYZJHvD_sQXvhkGtG07XmzyPgmjnUad3lGD0 New: Types-Menu, MenuItem, MenuSection Properties-hasMenuItem, hasMenuSection Modifying existing: menu, nutrition, offers, suitableForDiet Note the initial proposal referenced allergen which it was subsequentially decided it probably will be addressed in another issue (schemaorg#1411).