[x3d-public] reading schematron diagnostics

[John Carlson]

My apologies for not including xslt3 errors.   I had already submitted some
of those.   I think it’s more important to address validator errors, rather
stylesheet errors, as you say.

But the difference between saxon9he.jar and xslt3 errors is still
interesting for the future, especially the explosion (10x) in ProtoDeclares.

I will work on the validation errors soon.

John

John

On Sat, Feb 6, 2021 at 11:58 AM Don Brutzman <brutzman at nps.edu> wrote:

> step by step...
>
> On 2/5/2021 1:55 AM, John Carlson wrote:
> >
> > Thanks, Don.   I will look over the X3D file some more later.
>
> gosh i love diagnostics!  um, compared to the alternative of no
> diagnostics...
>
> > Should the order of the fieldValues match the order of fields?
>
> not required
>
> > I’m beginning to sound like Harry Potter.  Lol
>
> We haven't yet defined a policy for "Web3D Wizard" but am sure that
> consensus is possible following much concerted effort, controversy, sound
> and fury...
>
> > Thanks!
> >
> > John
>
> happy to help when i can, you are finding the gaps/seams and we're all in
> this together. take care.  8)
>
> > On Fri, Feb 5, 2021 at 2:11 AM Don Brutzman <brutzman at nps.edu <mailto:
> brutzman at nps.edu>> wrote:
> >
> >     These Schematron alerts are readable if you split them up.  Here is
> explanation for first.
> >
> >     On 2/4/2021 10:54 PM, John Carlson wrote:
> >      > ProtoInstance name='x3dconnector' DEF='connector1'> <fieldValue
> name='startnode' value=''/> has matching ProtoDeclare but no corresponding
> field match for this fieldValue
> >
> >     The above warning says that your ProtoInstance named "x3dconnector"
> has an initial field value named "startnode", but there is no corresponding
> field "startnode" defined in the governing ProtoDeclare named
> "x3dconnector".
> >
> >     No name found usually means that you have a flawed ProtoInstance.
> Though the mismatch/misunderstanding might be in the ProtoDeclare or
> ExternProtoDeclare.  As author, you must ensure that all the names match.
> >
> >      > [/X3D/Scene/ProtoInstance[1]/fieldValue[1], hint]
>
> p.s. i changed role attribute of this diagnostic from "hint" to "error"
> since it is an error.
>
> >     This provides the location of the node in your scene graph.  Thus go
> to the X3D node, then the scene node, then the first ProtoInstance [1] ,
> then the first fieldValue [1].
> >
> >     These are super helpful.  If the flaw is in your original X3D model,
> then stylesheets and other tools simply won't work - GIGO.
> >
> >     Good luck!
>
> all the best, Don
> --
> Don Brutzman  Naval Postgraduate School, Code USW/Br
> brutzman at nps.edu
> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
> X3D graphics, virtual worlds, navy robotics
> http://faculty.nps.edu/brutzman
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20210206/a0f81ec4/attachment.html>