[x3d-public] Possible new method suggester service based on X3DUOM.

[John Carlson]

I have discovered I have *many* mapToMethod2.js spread all over the place on sourceforge, GitHub, etc.

Can we create a service for providing the contents of mapToMethod.js and mapToMethod2.js served up as an interweaved JSON object?

I suggest working on the java/nashorn branch to provide this on a JavaScript server using node.js and/or php.  Does anyone want to be maintainer of the server? We can deploy to Heroku as an example.

I have many setIS moved to mapToMethod.js from mapToMethod2.js.  Many things need to be retested.

I noticed that http was replaced in many places with https (not a problem that I know of).

Once we fix mapToMethod*.js, we can move to fieldTypes.js.

Steps:
1. Define use cases/user stories
2. Design and Document API
3. Implement reference implementation
4. Test reference implementation
5. Rewrite clients to use services
6. Test clients
7. Deploy to production node.js and php servers.

I need help with 1 and 2.

Is there an easier way to accomplish maintain a single master?

Thanks,

John

Sent from Mail for Windows 10

From: John Carlson
Sent: Monday, August 12, 2019 11:36 AM
To: Brutzman, Donald (Don) (CIV); semantics at web3d.org
Cc: X3D Graphics public mailing list
Subject: RE: [Semantics] X3D Semantic Web meeting minutes


Great! Should help out with mapToMethod.js, generating setIS.

Thanks a bunch, now to change mapToMethodGenerator.py

You may want to look at mapToMethod2.js for any additional items to add to X3DUOM!

John


===========================================

4. Don has made some changes to X3D Unified Object Model (X3DUOM) that are reflected in the latest build, adding "IS" "connect" and "field" support.  These match the design patterns for other fields.

Excerpted:

:X3DNode a owl:Class .
:hasIS a owl:ObjectProperty ;
   rdfs:domain :X3DNode ;
   rdfs:range :IS ;
   rdfs:subPropertyOf :hasChild .
:fieldISHasParentX3DNode a owl:ObjectProperty ;
   owl:inverseOf :hasIS ;
   rdfs:subPropertyOf :hasParentX3DNode .

:connect a owl:Class .
:nodeField a owl:DatatypeProperty ;
   rdfs:domain :connect ;
   rdfs:range x3d:SFString .
:protoField a owl:DatatypeProperty ;
   rdfs:domain :connect ;
   rdfs:range x3d:SFString .

Background: IS/connect constructs are used to join nodes/fields within a ProtoBody, a fairly advanced X3D capability. Script and various Shader nodes have field definitions.

Tooltips:
- https://web3d.org/x3d/content/X3dTooltips.html#IS
- https://web3d.org/x3d/content/X3dTooltips.html#connect
- https://web3d.org/x3d/content/X3dTooltips.html#field

===========================================


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190812/1e74258b/attachment.html>