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

CODE: Site should handle /Person/Xyz more gracefully #6

Closed
danbri opened this issue Apr 17, 2014 · 5 comments
Closed

CODE: Site should handle /Person/Xyz more gracefully #6

danbri opened this issue Apr 17, 2014 · 5 comments

Comments

@danbri
Copy link
Contributor

@danbri danbri commented Apr 17, 2014

We encourage people to use /-based extensions, so these shouldn't 404.

Possible designs include:

  1. redirect to http://schema.org/Person#Xyz and have .js notice the fragment
  2. make a stub page with a hyperlink back to /Person
@danbri
Copy link
Contributor Author

@danbri danbri commented Apr 17, 2014

@danbri danbri changed the title Site should handle /Person/Xyz more gracefully CODE: Site should handle /Person/Xyz more gracefully Jun 15, 2014
@danbri danbri added the python code label Jun 16, 2014
@danbri
Copy link
Contributor Author

@danbri danbri commented Jul 7, 2014

Also the foo-input notation used with Action types...

@danbri
Copy link
Contributor Author

@danbri danbri commented Aug 12, 2014

Regarding actions notation, http://schema.org/docs/actions.html is now on the site.

danbri added a commit that referenced this issue Sep 18, 2014
Added example for an entity that is both an ItemList and a CreativeWork
@danbri danbri modified the milestone: sdo-venkman release Oct 12, 2014
@danbri
Copy link
Contributor Author

@danbri danbri commented Jan 26, 2015

see also #284

@danbri
Copy link
Contributor Author

@danbri danbri commented May 6, 2015

Ok, I've made a pass at both of these features. /cc @rvguha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.