OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

humanmarkup-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [humanmarkup-comment] RE: HM.VR_AI: Goals and Overview : HumanML_VR_AI Facilitator


>I don't know what you would do or what microparse is supposed to mean
>but I am sure that values like 5in, 25,6km, 34cc will become
>unmanageable in no time.

That is exactly not what I am suggesting.  

>Just use primitives and specify both the primitive for an attribute and
>the corresponding abstract type in your schemata, then use this info
>from your application. Isn't that what XSD is about?

That is what I am suggesting.  I would use floating point primitives 
and try to standardize around a metric measurement type since that 
is the world standard if not the US common practice.  One will have 
better luck with geographic systems.   Mapping systems consider the 
measurement type (eg, miles vs km) to be a layer about the actual 
coordinate system.   GML is a good example for feature layers.

len






[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC