Hi! On Tue, Jan 31, 2012 at 13:44, Thomas Beale < thomas.beale at oceaninformatics.com> wrote:
> If going for an RDF-like URI based approach for "program directives" or > "implementation_directives" then those serialization formats that aim for > human readability (e.g. ADL and YAML) may want to use some kind of > URI-prefixing-mechanism to make the directives shorter and more readable. > (Similar approaches are used in XML (namespaces) and many > RDF serialization formats.) > > I would opt for "implementation_directives", less ambiguous. > In that part of the mail I was thinking of shortening serialisations of things like... ["http://schema.openehr.org/GUI-v0_1#view";] = <" http://schema.openehr.org/GUI-v0_1#pass_through";> ...to something like... ["gui:view <http://schema.openehr.org/GUI-v0_1#view>"] = <"gui:pass_through<http://schema.openehr.org/GUI-v0_1#pass_through> "> ...by somewhere in the file defining gui: ...to mean... http://schema.openehr.org/GUI-v0_1#<http://schema.openehr.org/GUI-v0_1#pass_through> // Erik -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120131/87a8e003/attachment.html>
