graphicOverview 2.0 about mdjson-schemas HOT 9 CLOSED

So what are the thoughts on including a "datauri" property to allow direct embedding of browseGraphic images?

Here's an example

from mdjson-schemas.

Great idea, the communication staff types would appreciate the ability to display embedded images.

from mdjson-schemas.

Is fileConstraint supposed to be an array or an object? This example shows it as an array, which contradicts the one above. I'm not sure I see the benefit of having an array here, since the properties themselves are arrays.

from mdjson-schemas.

Instead of a dataURI property, I added "dataUri" to the onlineFunction codelist.

from mdjson-schemas.

So what is your method for camel case naming? Universal resource identifier is URI. Uri is not a word. Should we treat all acronyms as words?

from mdjson-schemas.

I'll need to check the file constraint schema. I think this one was laid in early and not updated as constraint was worked. The example you point to looks better. At least it includes security constraints.

from mdjson-schemas.

Good catch, I did forget to revisit this issue after completing constraint. One of the ISO loops, constraint is in graphic and graphic is in constraint. The JSON example has been updated.

from mdjson-schemas.

I was just following the mdJson approach to camelCasing. Personally, I prefer to capitalize the acronyms, e.g. mdJSON or dataURI. At least if they form the last "word".

from mdjson-schemas.

Yeah, I like your rule, at least it's good to have one for consistency. I'll leave it as URI and look for other places I may have used uri and change them.

from mdjson-schemas.