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

Add JSON as a specific document type + fix naming? #588

Closed
eriksiegel opened this Issue Oct 30, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@eriksiegel
Contributor

eriksiegel commented Oct 30, 2018

Section 3.1 of the spec mentions XML, text and non-XML as document types. The following remarks:

  1. Shouldn't JSON be mentioned as a specific type? I think (not sure) we decided that JSON "flows" through the pipelines as an XDM type. We discussed this briefly in #555, specifically this comment mentions what you get when you use collection() to retrieve a JSON document.
  2. non-XML as document type name IMHO doesn't make much sense any more... Text is also non-XML. Change to binary or other?
@xml-project

This comment has been minimized.

Contributor

xml-project commented Oct 30, 2018

Yes, section 3.1 is pretty overtaken by our discussions.
Not sure how to call non-XML, non-Text, non-JSON documents. I have a slight preference for "other-documents" because this would allow implementers to introduce additional processor specific document types (among them binary documents).
Do we have to call out HTML-documents (mentioned in p:load) as a special document type?

@ndw

This comment has been minimized.

Contributor

ndw commented Oct 31, 2018

👍

@ndw ndw self-assigned this Oct 31, 2018

@ndw ndw closed this in #604 Nov 1, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment