>>>
>> I mentioned it as it was referred to in -04 4.5. But you are right, paths,
>> query parameters and object class names have the same properties.
>> If there is a single item added by the extension, and it's equal to
>> extension identifier - it's all same.
>> For class names and query parameters if an extension would want to add
>> several there is no other choice than prefix, as the same name cannot be
>> duplicated.
>> For JSON names and paths one may do a container with one name and include
>> all needed values in there, or have a flat list with prefixes. It would be
>> "foo_val1": "..." vs. "foo":{ "val1": "..." } for JSON, or foo_subpath1 vs
>> foo/subpath1 for paths.
>
> This and the various combinations of an extension using the bare id in a path
> but not JSON, etc... adds unneeded complexity. That's why bare ids are not a
> good idea.
>
having combinations of extension mechanism is not desired, but you can have
bare identifier in url path and in json right?
for example, url can be: /base/path/my-foo-extension/my-new-val
is this not logically the same as this json example?
{
“standard-key1”: “val1”,
“standard-key2”: “val2”,
“my-foo-extension: { “my-new-key”: “my-new-val” ,
“more-key”: “more-val"}
}
-
Maarten
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]
