[DDI-SRG] "fixed" implementation question

Pascal Heus pascal.heus at gmail.com
Thu Dec 6 14:32:31 EST 2007


Looked a bit at JSON but not particularly interested. Adobe Flex (using 
E4X) actually understands  both XML and JSON but why deal with another 
format.
*P

I-Lin Kuo wrote:
> We're considering returning JSON in the non-SOAP webservices I'm 
> implementing now. We're not doing it yet because there isn't a high 
> demand for it. Personally, I think E4X (Ecmascript for XML) is a 
> better bet in the future.
>
> On Dec 6, 2007 1:17 PM, arofan.gregory <arofan.gregory at earthlink.net 
> <mailto:arofan.gregory at earthlink.net>> wrote:
>
>     Folks:
>
>      
>
>     Just as a side-question dealing with Javascript, have you guys
>     looked at JSON? It's a standard way of rendering Javascript
>     objects which in some cases can be used to capture an XML-esque
>     data set for easier web processing in JS.
>
>      
>
>     Cheers,
>
>      
>
>     Arofan
>
>      
>
>     ------------------------------------------------------------------------
>
>     *From:* ddi-srg-bounces at icpsr.umich.edu
>     <mailto:ddi-srg-bounces at icpsr.umich.edu>
>     [mailto:ddi-srg-bounces at icpsr.umich.edu
>     <mailto:ddi-srg-bounces at icpsr.umich.edu>] *On Behalf Of *I-Lin Kuo
>     *Sent:* Wednesday, December 05, 2007 4:21 PM
>     *To:* Pascal Heus
>     *Cc:* DDI Technical Implementation Committee
>     *Subject:* Re: [DDI-SRG] "fixed" implementation question
>
>      
>
>     OK. then I'll drop the issue.
>
>     On Dec 5, 2007 5:08 PM, Pascal Heus <pascal.heus at gmail.com
>     <mailto:pascal.heus at gmail.com>> wrote:
>
>     I-Lin:
>     I saw and discussed the new Identifier design before. I don't
>     think it should be a problem to have the attribute optional
>     (fixed). I agree with J that  we usually know what to expect.
>     *P
>
>     I-Lin Kuo wrote:
>
>     I don't think javascript is schema-aware but I imagine these
>     attributes would be of interest to DexTris. Pascal, chime in?
>
>     On Dec 5, 2007 3:35 PM, J Gager < j.b.gager at gmail.com
>     <mailto:j.b.gager at gmail.com>> wrote:
>
>     It is my opion that anything that would want to know this
>     information would probably be schema aware. I can't imagine
>     something that is complex enough to care wheter an individulal
>     artefacts are maintainable or versionable not validating the XML
>     first.
>
>      
>
>     We have used fixed attributes in numerous XML implementations and
>     it has never come up as an issue.
>
>      
>
>     The DDI is very complex, and secondary validation is most likely
>     required for any useful application. I don't think creating the
>     standard against the lowest level of tools is the right design
>     decision.
>
>      
>
>     But that is just my 2 cents.
>
>      
>
>     J
>
>      
>
>     ------------------------------------------------------------------------
>
>     *From:* ddi-srg-bounces at icpsr.umich.edu
>     <mailto:ddi-srg-bounces at icpsr.umich.edu> [mailto:
>     ddi-srg-bounces at icpsr.umich.edu
>     <mailto:ddi-srg-bounces at icpsr.umich.edu>] *On Behalf Of *I-Lin Kuo
>     *Sent:* Wednesday, December 05, 2007 4:12 PM
>     *To:* DDI Technical Implementation Committee
>     *Subject:* [DDI-SRG] "fixed" implementation question
>
>     HI all,
>
>     In Wendy's TIC report email, I saw a couple of lines using fixed,
>     e.g. "@isMaintainable fixed="true"".
>
>     I just want to check that it's not being implemented in the
>     obvious way,
>
>     <xs:attribute name="isMaintainable " type="xs:string" fixed="true"/>
>
>     Implementing it this way would be a very bad idea, in my opinion.
>     Implemented this way, the @isMaintainable may be omitted in an
>     instance document and yet validate against the schema. When this
>     instance is processed, the attribute isMaintainable is visible
>     only when you are processing in a schema-aware fashion. Most XSLT
>     engines and streaming processors are not schema aware. The end
>     result is that the results of applying an XSLT stylesheet to an
>     instance will differ, depending on whether the stylesheet is run
>     with a schema-aware processor or an unaware processor.
>
>     I recommend the following implementation:
>
>     <xs:attribute name="isMaintainable " type="ddi:fixed" required="true"/>
>
>     where ddi:fixed is defined to be "true", restricting xs:string.
>
>     -- 
>     I-Lin Kuo
>
>
>     _______________________________________________
>     DDI-SRG mailing list
>     DDI-SRG at icpsr.umich.edu <mailto:DDI-SRG at icpsr.umich.edu>
>     http://www.icpsr.umich.edu/mailman/listinfo/ddi-srg
>
>
>
>
>     -- 
>     I-Lin Kuo
>
>
>
>     ------------------------------------------------------------------------
>
>
>      
>
>     _______________________________________________
>
>     DDI-SRG mailing list
>
>
>     DDI-SRG at icpsr.umich.edu <mailto:DDI-SRG at icpsr.umich.edu>
>
>     http://www.icpsr.umich.edu/mailman/listinfo/ddi-srg
>      <http://www.icpsr.umich.edu/mailman/listinfo/ddi-srg>
>
>       
>
>      
>
>
>
>
>     -- 
>     I-Lin Kuo
>
>
>
>
> -- 
> I-Lin Kuo 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.icpsr.umich.edu/pipermail/ddi-srg/attachments/20071206/de08b199/attachment.html 


More information about the DDI-SRG mailing list