Skip to content
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

JSON-LD context file should declare gs1 vocab prefix #1411

danbri opened this issue Oct 20, 2016 · 1 comment


Copy link

@danbri danbri commented Oct 20, 2016

It would be great if anyone could write e.g. gs1voc:AllergenTypeCode-WHEAT or somesuch without having to declare explicitly. To do this we'd need to add their preferred prefixes to our context (current status viewable at, 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.


This comment has been minimized.

Copy link

@jaygray0919 jaygray0919 commented Oct 20, 2016

We have re-formulated a subset of the GS1 OWL declarations as an S.O @Class @Property hierarchy?
Is that what you are looking for?


gmackenz added a commit to gmackenz/schemaorg that referenced this issue Oct 26, 2016
Adding menu markup schema: issue schemaorg#1288


  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).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.