search

soundasleep / iaml

Automatically exported from code.google.com/p/iaml
3 stars 1 forks source link

Replace custom datatypes with XSD builtin datatypes #200

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What new or enhanced feature are you proposing?
Currently, IAML has defined its own range of data types. They should be 
replaced with the XSD equivalents, but only in the case where the semantics 
persist. i.e.:

iamlString -> string
iamlInteger -> int (32 bit signed)

iamlURL -> anyURI: URIs can be relative or fragments, so we still require a URL 
(especially for OpenID URLs).

iamlDateTime remains a custom data type, because we define additional semantics 
for its conversion (e.g. to/from String and int). iamlEmail also remains a 
custom data type, as does iamlOpenIDURL.

What goal would this enhancement help you achieve?
More standards-compliant.

Original issue reported on code.google.com by soundasleep on 11 Jun 2010 at 12:30

GoogleCodeExporter commented 9 years ago 
The problem with using XSD data types natively is that EMF serialises them to 
the form:

  bundleentry://8628.fwk23065739/cache/www.w3.org/2001/XMLSchema.xsd#//string;XSDSimpleTypeDefinition=9

This is not portable at all; if the cache identifier (8628...) is modified, the 
reference is lost.

Original comment by soundasleep on 18 Jun 2010 at 4:33

GoogleCodeExporter commented 9 years ago

Original comment by soundasleep on 3 May 2011 at 7:15

GoogleCodeExporter commented 9 years ago

Original comment by soundasleep on 8 Jul 2011 at 2:48

GoogleCodeExporter commented 9 years ago 
mass tagging old issues to future work

Original comment by soundasleep on 26 Sep 2011 at 9:54