Thread: Re: [Xsltforms-support] Question Re Implementing Custom Types

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Alain – FANTASTIC, thank you!  I will test and get back to you ASAP. 😊

-Tony Bufort

www.ajbconsulting.us <http://www.ajbconsulting.us/> 

         Anthony J. (Tony) Bufort
              Owner / Sr. Developer

EMAIL: ajb...@aj... <email:ajb...@aj...> 

PHONE: (425) 221-4447

SKYPE: ajbufort

LINKEDIN: www.linkedin.com/in/anthonybufort <http://www.linkedin.com/in/anthonybufort> 

 A fully licensed, fully insured Washington state entity.                

From: Alain Couthures <ala...@ag...> 
Sent: Sunday, October 15, 2023 1:10 AM
To: ajb...@aj...; Steven Pemberton <ste...@cw...>; xsl...@li...
Subject: Re: [Xsltforms-support] Question Re Implementing Custom Types

Hello Tony,

I have fixed some issues for supporting OSCAL schema.

Please give a try to the xsltforms.js file attached.

Thank you for your feedback!

--Alain

Steve, Alain, et al,

Thanks for the quick replies. 😊

Alright, so I am using the OSCAL complete schema, v 1.1.0, along with an SSP instance (see attached).

Though the instance is an SSP, I have started testing using the complete schema, as I am testing other aspects of my code in the process.

In the resultant HTML, I get output like this:

…so things are getting found and displayed, but I am not getting any validation or date-picker goodness.

In my previous bind I sent you, I slimmed it down for purposes of brevity.  Here is the actual bind…

<xf:bind id="/system-security-plan/metadata/published"

         ref="/o:system-security-plan/o:metadata/o:published"

         type="oscal-metadata-published-FIELD"/>

My expectation is that XSLTForms would find the type and its restriction base, follow that to the underlying type (DateTimeWithTimezoneDatatype), then follow its underlying type (DateTimeDatatype) to <xs:restriction base="xs:dateTime">, acknowledging the native type and allowing for both a rendering of a date-picker in the browser (Opera latest version in my case) and validation benefits within the resultant XForm.

Thank you for considering my problem.

-Tony

 <http://www.ajbconsulting.us/> www.ajbconsulting.us

         Anthony J. (Tony) Bufort
              Owner / Sr. Developer

EMAIL: ajb...@aj... <mailto:ajb...@aj...> 

PHONE: (425) 221-4447

SKYPE: ajbufort

LINKEDIN:  <http://www.linkedin.com/in/anthonybufort> www.linkedin.com/in/anthonybufort

 A fully licensed, fully insured Washington state entity.                

From: Steven Pemberton <ste...@cw... <mailto:ste...@cw...> > 
Sent: Friday, October 6, 2023 1:11 AM
To: ajb...@aj... <mailto:ajb...@aj...> ; xsl...@li... <mailto:xsl...@li...> 
Subject: Re: [Xsltforms-support] Question Re Implementing Custom Types

Could you show us the instance you are referencing?

Steven

On Friday 06 October 2023 06:45:05 (+02:00), ajb...@aj... <mailto:ajb...@aj...>  wrote:

Hello Alain and Company,

I am a new user of XSLTForms, exploring the framework, and am quite impressed, especially considering it’s a free product.

However, I would like confirmation that what I am seeing is indeed the case, or if I am missing something, regarding handling custom types.

In my model definition I reference a schema file, expecting to link up the types defined therein to my bind statements.  The types I am trying to use are simpleTypes.  Here is an example:

<xs:simpleType name="DateTimeWithTimezoneDatatype">
      <xs:annotation>
         <xs:documentation>A string representing a point in time with a required timezone.</xs:documentation>
      </xs:annotation>
      <xs:restriction base="DateTimeDatatype">
         <xs:pattern value="(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(0[1-9]|[12][0-9]|30)))T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\.[0-9]+)?(Z|(-((0[0-9]|1[0-2]):00|0[39]:30)|\+((0[0-9]|1[0-4]):00|(0[34569]|10):30|(0[58]|12):45)))"/>
      </xs:restriction>

</xs:simpleType>

And the bind trying to use it (the ‘o:’ namespace used in @ref is indeed confirmed correct):

<xf:bind id="/published" ref="/o:published" type=" DateTimeWithTimezoneDatatype"/>

And finally, the input field:

<xf:input bind="/published" incremental="true" type-ref=" DateTimeWithTimezoneDatatype">

    <xf:label>

         <b>Published:</b>

    </xf:label>

</xf:input>

I get no ostensible complaints from the xf processor, but no validation behavior either (i.e. entering invalid values provokes no response). 

(Note that the slashes in the @id and @bind attributes seem to be permissible if non-standard.)

Can the XSLTForms processor handle the schema type as defined above?  It seems to acknowledge the type, but not operate using it.

Or are users expected to create type-handling additions in xsltforms.js?

I am unclear as to the situation in XSLTForms 1.7, which is the version I am using.

Please advise, and thank you in advance!

-Tony Bufort,

AJB Consulting

 <http://www.ajbconsulting.us/> www.ajbconsulting.us

         Anthony J. (Tony) Bufort
              Owner / Sr. Developer

EMAIL: ajb...@aj... <mailto:ajb...@aj...> 

PHONE: (425) 221-4447

SKYPE: ajbufort

LINKEDIN:  <http://www.linkedin.com/in/anthonybufort> www.linkedin.com/in/anthonybufort

 A fully licensed, fully insured Washington state entity.                

_______________________________________________ Xsltforms-support mailing list Xsl...@li... <mailto:Xsl...@li...>  https://lists.sourceforge.net/lists/listinfo/xsltforms-support 