Not documented string marker?

[Marcus Held]

Hi,

I'm using your UBJSON implementation (https://github.com/thebuzzmedia/universal-binary-json-java) and I'm confused in writing a String.

In UBJOutputStream:209 you use the Type [s] instead of [S] and call it "STRING_COMPACT". I tried to find something about it in the documentation but only the [S] marker is described.

Can you tell me where the [s] marker is documented?

~ Marcus

[Marcus Held]

Ok. As I worked further with this implementation I realized that it is based on draft 8. Is there a draft 10 implementation of UBJSON?

[Riyad Kalla]

Sorry for the confusion Marcus; I haven't updated the Java impl yet to the latest draft. 

----------------
Riyad
http://thebuzzmedia.com

--
You received this message because you are subscribed to the Google Groups "Universal Binary JSON (UBJSON)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to universal-binary...@googlegroups.com.
To post to this group, send email to universal-...@googlegroups.com.
Visit this group at http://groups.google.com/group/universal-binary-json.
For more options, visit https://groups.google.com/d/optout.

[Marcus Held]

Are there any plans that this will happen within the next few weeks? If not, can I see the draft 8 specification somewhere?

~ Marcus

Am Mittwoch, 9. Juli 2014 15:33:32 UTC+2 schrieb riyad.kalla:

Sorry for the confusion Marcus; I haven't updated the Java impl yet to the latest draft. 

----------------
Riyad
http://thebuzzmedia.com

On Wed, Jul 9, 2014 at 3:44 AM, Marcus Held <marcu...@gmail.com> wrote:

Ok. As I worked further with this implementation I realized that it is based on draft 8. Is there a draft 10 implementation of UBJSON?

Am Mittwoch, 9. Juli 2014 12:23:25 UTC+2 schrieb Marcus Held:

Hi,

I'm using your UBJSON implementation (https://github.com/thebuzzmedia/universal-binary-json-java) and I'm confused in writing a String.

In UBJOutputStream:209 you use the Type [s] instead of [S] and call it "STRING_COMPACT". I tried to find something about it in the documentation but only the [S] marker is described.

Can you tell me where the [s] marker is documented?

~ Marcus

--
You received this message because you are subscribed to the Google Groups "Universal Binary JSON (UBJSON)" group.

To unsubscribe from this group and stop receiving emails from it, send an email to universal-binary-json+unsub...@googlegroups.com.

[Riyad Kalla]

Marcus,

I don't have the bandwidth right now to carry the impl forward to Draft 11 - this is one of the pain points of UBJSON right now, it is still a little bit in flux and I'm waiting for discussion to settle down before doing a big rev on the implementation.

I had planned (and may still plan) for Draft 11 to be the final 1.0 release of UBJSON - the only portion of the spec under hot debate right now is allowing strongly-typed containers to contain other strongly-typed containers (turtles all the way down!) - https://github.com/thebuzzmedia/universal-binary-json/issues/43

As annoying as this moving target is, the movement is getting less and less year over year which was always my goal.

The website only (intentionally) represents the latest spec and I don't have a clearcut enumeration of each version of the spec -- the reason for this is that the changes between the different drafts were not always nicely incremental; there was some backstepping and mild pivoting that took place around some of the more pivotal releases (Draft 4, 8, 10, etc.) and I don't want the confusion of [s] meaning "COMPACT STRING" and then 1 year later [s] meaning "SEGMENTED BYTE SEQUENCE" to exist in the same universe (this is just an example, this isn't actually the meaning of [s] now)

The benefit is that everyone new to the spec only learns the latest/most accurate representation.

The downside is what you recognized -- trying to actively work with previous drafts is hard (impossible?) but that is a cost I knowingly incurred for the spec... my goal is not to make working with previous drafts easier -- my goal is to focus first and foremost on the spec and understanding use cases across the scope of computing and then my followup goal to that is getting some really top tier implementations in all the major languages to enable it's use.

We are transitions from Step 1 (soldify spec) into Step 2, but I'd really like to wrap the decision up around strongly typed containers first because if we backstep there at all it will effect a lot of optimized scenarios, implementations and binary data support.

Hope that helps provide some context as to why this isn't a simpler answer. I do appreciate the interest in UBJSON; the folks that have leveraged it have gotten a lot of gains out of it.

Best wishes,

----------------
Riyad
http://thebuzzmedia.com

To unsubscribe from this group and stop receiving emails from it, send an email to universal-binary...@googlegroups.com.

[Marcus Held]

Hey Riyad,

it's been a while since I worked with UBJSON in the theory, but right now I'm in the last steps for my implementation and I really want to evaluate UBJSON, too. Unfortunately I don't have the time to write my own implementation from the latest UBJSON spec, so I want to use the old draft 8 one. But I need to know the draft 8 spec to write the theory in my thesis. Is this (http://universal-binary-json.readthedocs.org/en/0.8/index.html) the draft 8 spec from UBJSON?

Best wishes,
Marcus

----------------
Riyad
http://thebuzzmedia.com

----------------
Riyad
http://thebuzzmedia.com

To unsubscribe from this group and stop receiving emails from it, send an email to universal-binary-json+unsubscri...@googlegroups.com.

To post to this group, send email to universal-...@googlegroups.com.

Visit this group at http://groups.google.com/group/universal-binary-json.
For more options, visit https://groups.google.com/d/optout.

[Riyad Kalla]

Hey Marcus,

I'm not actually sure _who_ maintains that site... that does seem to be the Draft 8 spec, but I cannot be 100% sure.

If you go to the GitHub Issues page (https://github.com/thebuzzmedia/universal-binary-json/issues?q=is%3Aissue+) you can set filters based on Milestones to back out what has changed since Draft 8 to confirm (For example, look at what changed in Draft 9 and 10 and make sure they aren't on that page) if that helps.

Best,

----------------
Riyad
http://thebuzzmedia.com

To unsubscribe from this group and stop receiving emails from it, send an email to universal-binary...@googlegroups.com.

[Alexander Shorin]

Well, it's very easy to figure who (:

https://readthedocs.org/projects/universal-binary-json/

It builds from source code on github which matches Draft 8 version as
it was. Suddenly, at some point I make no updates for it so it miss
any bits of draft 9 and draft 10. Need to fix that for sure, but any
help is welcome!


--
,,,^..^,,,

[Riyad Kalla]

I should have known! :)

Alex is like my better half... if you find something good about the spec or some helpful documentation, he probably did it :)