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

Proposed renaming and sectioning #15

Closed
BigBlueHat opened this issue Sep 20, 2019 · 5 comments
Closed

Proposed renaming and sectioning #15

BigBlueHat opened this issue Sep 20, 2019 · 5 comments

Comments

@BigBlueHat
Copy link
Member

BigBlueHat commented Sep 20, 2019

I'd like to rename the BP to "JSON-LD Best Practices" (removing the 1.1), and break the sections up into:

  • Authoring
    • contexts
    • data documents
  • Publishing
  • Consuming
@ajs6f
Copy link
Member

ajs6f commented Sep 20, 2019

What is the distinction between Authoring and Publishing? Is it in whether the context is being written or re-used?

@BigBlueHat
Copy link
Member Author

Authoring would be about what goes into the JSON-LD document itself--i.e. @context ordering, when to use language/id maps, etc.

Publishing would be about putting that document someplace(s) for distribution--i.e. embedding in HTML, serving over HTTP, embedding in email, etc.

@ajs6f
Copy link
Member

ajs6f commented Sep 24, 2019

Okay. Would you be interested in breaking down Authoring to authoring contexts and authoring instance data?

@BigBlueHat
Copy link
Member Author

Definitely. Good call.

@BigBlueHat
Copy link
Member Author

I've updated the issue accordingly.

@azaroth42 azaroth42 added this to Non TR Work in JSON-LD Management Oct 10, 2019
@gkellogg gkellogg removed this from Non TR Work in JSON-LD Management Dec 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants