S1000D version 2.2 in Framemaker 2019

Forum|Forum|3 years ago
November 5, 2022
2 replies
435 views

Hi, I am trying to import the S1000D version 2.2 schema in Framemaker. So far unsuccesful. I read about a simple application pack for this version but cannot find it anywhere.

Anyone any ideas on how to go about using this version of S1000D in Framemaker?

all help is appreciated!

Marcel Veenhof

This topic has been closed for replies.

M

matsb99251617

Inspiring

Not 100% sure, but I think FrameMaker only supports 4.0.1. Regardless, based on my experience from various S1000D projects, FrameMaker's built-in support for S1000D is shaky - and you don't want shakiness in S1000D projects. I assume that is the reason Adobe themselves eventually decided to refer to Mekon's S1000D plugin instead (under the Help menu), which also offers additional features and supports all issues from 1.6 and up:

https://aerospace-defence.com/index.php/tech-pubs/products/create/eclipse-s1000d-framemaker/

In all cases you should ask the customer for an organisational and/or project BREX and validate all data modules against those (and the S1000D default BREX, ofcourse) prior to delivery. I assume you are familiar with the process of registering MOIs?

Best regards,

Mats

M

Marcel26975912mh7fAuthor

Participant

Hi Mats, thank you. Yes, but this is a small project and I only wanted to author a handful of S1000D Data Modules to start with. Getting an S1000D version 2.2 DTD to work with Framemaker is already an obstacle. There used to be a Framemaker application package with version 2.2 I saw somewhere. But probably for older Frame versions... Mekon is an option, but this should be something that I can get to work right?

M

matsb99251617

Inspiring

Hi,

If you can make it work, sure. But if it's a small project and only involves updating, I would do it in Notepad++. And very important to do the validation against the S1000D default BREX file (and possibly the DIG BREX if it's a European def project) and the project BREX files. Also, cannot stress enough the importance of registering the MOI/MI, unless this is just a private pet project that will live on your c drive. NSPA and the S1000D consortium is adamant about this and they positively do not want PMs/DMs floating around where the MOI/MI is unregistered. Same with NCAGE.

Bets regards,

Mats